EY Pressure looks like it dropped a tiny bit on 1-11-2017, but I don't see any other issues.

I have turned off the heat in Zone 3A in the LVEA.

We have increased fan flows in the corner in an attempt to stabilize temperatures. The 4 fans are now set to ~11000 cfm.

Highlights from my data quality shift last weekend (12-15 January 2017) at Hanford:

• Total duty cycle, in H1:DMT-ANALYSIS_READY: 50.10%
• There is a persistent data quality issue where a scratchy forest of lines show up right in the bucket, at mid-range frequencies between 30 and 500 Hz, coincident with really nasty wandering in the BNS inspiral range (typically from 70 Mpc around the start of a lock stretch down to as low as 40 Mpc by the time lockloss occurs)
• This issue appears to be caused by some nonlinear downconversion after > 1 kHz harmonics of the violin modes get high enough in amplitude to hit nonlinear effects in the sensing controls
• There appear to also be issues with alignment drift since the post-winter break resume of O2a. These are being looked into by Sheila Dwyer, Jeff Kissel, and Evan Goetz
• Hanford has also received some unfortunate winter weather conditions (we hope everyone at the site stays safe!) that necessitated snow plowing at the X- and Y-ends, which gave rise to glitchiness in h(t) due to upconverted 1-10 and 10-30 Hz ground motion.
• Sheila may have isolated the cause of the persistent 1080 Hz glitches we've seen since the start of O2 down to changes in the OMC length gain
• PCAL clipping has been fixed by Travis Sadecki.

Full notes may be found here: https://wiki.ligo.org/DetChar/DataQuality/DQShiftH120170111

Lowered LLCV settings on both CP3 & CP4

CP3 from 17% to 15%

CP4 from 34% to 33%

Exhaust temps were lower than ambient and exhaust pressures above zero.

TITLE: 01/17 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventitive Maintenance
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 7mph Gusts, 4mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.57 μm/s
QUICK SUMMARY: Freezing rain on the way in. Maintenance has already began.
 

TITLE: 01/17 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Preventative Maintenance
INCOMING OPERATOR: TJ

SHIFT SUMMARY: A bit of a rough night.  Started with an EQ.  Proceeded with one short lock with dwindling range.  Some IMC locking issues after lockloss that turned out to be user error.  Back to Observing at the end of the shift.

LOG: See previous logs.

15:20 Bubba and contractors unloading a van at OSB receiving. 

15:36 A/C work starting in control room.

The IMC hasn't locked since the lockloss.  While following the troubleshooting Wiki instructions, I attempted to use Dataviewer to look at trends of various IMC related channels to no avail (see screenshot of error) no matter which data rate setting I chose.  With no data to point me to what is wrong, I cleared the IMC WFS as a hail mary.  This didn't help.  I'm not sure what to do next here.

Didn't notice anything out of the ordinary on the FOMs, other than the range dropping since the beginning of the lock stretch.

Changing the gain of PI mode 9 kicked us out of Observe.

With microseism above the 90th percentile, I had to wait for the EQ to ring down entirely before make much progress locking (~2 hours).

5.4M Guisa, Cuba

Was it reported by Terramon, USGS, SEISMON? Yes, Yes, No

Magnitude (according to Terramon, USGS, SEISMON): 5.4, 5.4, NA

Location: 43km S of Guisa, Cuba; LAT: 19.9, LON: -76.6

Starting time of event (ie. when BLRMS started to increase on DMT on the wall): 9:15 UTC

Lock status?  Locking at the time, became unable to proceed with locking.

EQ reported by Terramon BEFORE it actually arrived? No, I noticed it on the BLRMS before the USGS even reported it.

TITLE: 1/17 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Initial Alignment
OUTGOING OPERATOR: Jeff B

QUICK SUMMARY: After the PSL crash at the end of Jeff's shift, the alignment doesn't look so good, so I'm running through IA.

ISC_LOCK at DOWN and observatory mode in corrective maintenance upon arrival. The HAM6 ISI is tripped. I will attempt to lock but given the alogs from last night it sounds like I may need help from a commissioner.

Running 'ops_auto_alog -t Day' reported an error:

patrick.thomas@operator0:~$ ops_auto_alog.py -t Day
Traceback (most recent call last):
  File "/opt/rtcds/userapps/release/cds/h1/scripts/ops_auto_alog.py", line 300, in 
    alog.main(Transition,shift)
  File "/opt/rtcds/userapps/release/cds/h1/scripts/ops_auto_alog.py", line 218, in main
    operator = self.get_oper_w_date('{day}-{month_name}'.format(day=lday, month_name=self.all_months[lmonth]), 'Owl')
  File "/opt/rtcds/userapps/release/cds/h1/scripts/ops_auto_alog.py", line 130, in get_oper_w_date
    date_ln = self.get_date_linum(date) - 1
TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'