Attached are the PSL Laser Head flow rates for the last 3 days.  On 7-22-2017 at 15:45 UTC (8:45 PDT) all 4 heads saw a drop in flow of ~0.03 lpm.  This lasted for ~2 hours, and then all flow rates returned to normal.  None of the other flows or pressures showed a change at this time, so it is unclear what the cause was.  The flow reading from the Head 2 flow sensor continues to have periods of noisy readings, which has been the case for this sensor since it was installed.

TITLE: 07/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 50Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 20mph Gusts, 17mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.15 μm/s 
QUICK SUMMARY: 3.5 hour lock at 50Mpc. useism is on the rise.

TITLE: 07/24 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:  One lockloss mid-shift.  Otherwise, no issues of note that aren't already logged.
LOG:  See previous aLogs.

14:33 Bubba to EX to check vaporizer

Confirmed with LLO.

No issues after the one lockloss during relocking noted in my earlier aLog.  Accepted SDF diff for LSC-REFL_SERVO_IN1GAIN in screeshot attached.

After the 10:16 UTC lockloss, DIAG_MAIN began reporting that, in addition to the known PCAL Y issues, PCAL X was also off by more than 1%.  Trending the RX PD OUTPUT shows that the output changed in a step coincident with the lockloss.  I'll not attempt to do anything about this at the moment and let those in the land of the living decide what actions to take. 

DIAG_MAIN was reporting that "ISI HAM6 WD saturation count is greater that 75% of max", so I pressed the "Clear Saturations Only" button from the ISI WD MEDM screen.

No obvious cause.

TITLE: 07/24 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 52Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 18mph Gusts, 13mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:  No issues handed off.  Lock is 13 hours old.

TITLE: 07/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 48Mpc
INCOMING OPERATOR: Travis
SHIFT SUMMARY: Remained in observing entire shift. Made no changes. Range has been degrading since the beginning of the lock, possibly somewhat correlated with wind.
LOG:

00:02 UTC Kyle out of VPW
00:50 UTC GRB alert
00:56 UTC Kyle leaving site

The range has been slowly degrading since the beginning of the lock ~9 hours ago. Have remained in observing.

TITLE: 07/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 18mph Gusts, 15mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.07 μm/s 
QUICK SUMMARY: Kyle is in VPW. No issues to report.

TITLE: 07/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 51Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: One lock loss that I can't explain, but it relocked with little fuss. I had one weird instance around 21:19UTC where the IFO showed signs that it was experiencing an earthquake (~1hz osciallations in control signals and IMC-F_OUT channel, slight motion in OMC Trans camera, DIAG_MAIN even reported a very breif instance of an earthquake from the LSC-CPS_FF channel), but nothing on USGS or the siesmometers. It was very brief, maybe less than a minute.
LOG:

• 16:16 GRB
• 17:07 Lock loss
• 17:58 Observing
• 21:11 GRB

Unknown cause.

TITLE: 07/23 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: TJ
SHIFT SUMMARY: started with locked, lost lock, relocked, lost lock due to monster PI modes 27 and 28, relocked,
LOG:

• started with locked
• lost lock
• relocked
• lost lock due to monster PI modes 27 and 28
• relocked
• started glitching, out of Observe for a2l
• ODD A2L RESULTS:  reduced coherence with YAW, increased coherence with pitch to around 0.9
• glitching continued, I adjusted TMSX/Y
• running another a2l
• watched BS Oplev most of the night, saw one strong glitch in the time series that then dropped the range
• second a2l finished, H1 in Observe

The glitchy periods at 10 UTC today, and 8 UTC on July 20, seem to be due to overflows in all of the test mass L2 coils. The cause of the overflows looks to be CSOFT pitch.

The attached plots show timeseries of CSOFT pitch and ITMX L2 master for one quadrant, then a spectrogram of the coil signal. It looks like most of the power is in the 2.8 Hz pitch mode of the test masses. From the summary pages, it looks like the RMS of CSOFT pitch has crept up over the last few months.

When the coil drive goes over 131,072 counts, the DAC overflows and the coil glitches. It's possible that I have things backwards, and the glitch comes first and the overflow is a symptom, but that doesn't seem to match the behavior of the RMS at non-glitchy times.

Is there a way to get CSOFT pitch lower, or maybe suppress some of the feedback at 2.8 Hz (which I think is the biggest contributor)?

FAMIS4737

All oplevs seem to be where they should be, looks good.

I'm checking the coil driver switching while we wait for the earthquake to ring down, to ensure that the analog switches are actually switching. Here's a rough note of my method:

* Set BIO state request to negative of the value that you want (i.e. -2 for state 2, -3 for state 3).  This gives you control of the coil out filter banks (ex. H1:SUS-ITMX_L2_COILOUTF_UL). Do this for all 4 quadrants.

* Turn off all filters, so you have a flat digital TF from the excitation point to the driver. Do this for all 4 quadrants.

* For BS (only one with oplev damping), disable oplev damping.

* Take TF from coil output filter bank excitation to fastimon channel (ex. H1:SUS-ITMX_L2_COILOUTF_UL_EXC to H1:SUS-ITMX_L2_FASTIMON_UL_OUT).

* Switch analog coil driver state, retake TF, confirm that it changed as expected.

* Put state request back to positive number that it started at; this resets the digital filters appropriately.

All switching seems fine for PRM M3, SRM M3, ITMX L2, ITMY L2, ETMX L2 and ETMY L2, which is all suspensions and stages that we switch coil driver states for, except for BS M2.  BS M2's UR coil is different from the other coils on BS M2. 

I'm attaching a screenshot of the BS measurements, showing that the shape of the UR analog driver is slightly different in each state, and the overall gain is different by about 8dB. 

I ask that the BS M2 coil driver be looked at first thing in the morning.