TITLE: 06/13 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 22mph Gusts, 17mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:  Currently locked for ~1 hour, but have transitioned Observatory Mode to Preventative Maintenance in prep for Tuesday maintenance activities.

TITLE: 06/13 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 32Mpc
INCOMING OPERATOR: Travis
SHIFT SUMMARY:
Appearance of noise around 38 and 80 Hz (alog 36819).
Three lock losses, the first coincident with the arrival of an earthquake.
Verbal alarms is crashing upon hitting the observing intent bit.
NOISE_TUNINGS is being announced twice by verbal alarms along with an error message (see previous alogs).
H1:ALS-X_REFL_SERVO_COMBOOST is alternating between 1 and 2 (see SDF differences in previous alogs).

LOG:

07:14 UTC Restarted nuc5 and video0
09:01 UTC Lock loss
09:18 UTC Lock loss from CARM_ON_TR
09:21 UTC Changed observatory mode to earthquake
~10:00 UTC Observing
09:46 UTC Lock loss
10:48 UTC Starting initial alignment
11:22 UTC Initial alignment done
~11:52 UTC Observing
13:01 UTC Peter walking to mid Y
13:34 UTC Peter back
13:43 UTC Lock loss
14:08 UTC Ken to warehouse
15:00 UTC Bubba and Apollo to CER
15:04 UTC Set ISI config to SC_OFF_NOBRSXY
15:05 UTC Pep to end X
15:06 UTC Pest control on site

Back to observing at 14:20 UTC. Screenshot of accepted SDF differences attached. It appears that H1:ALS-X_REFL_SERVO_COMBOOST keeps alternating between 1 and 2.

Again:
NOISE_TUNINGS was announced twice by verbal alarms, along with: 'TypeError while running test: LOCK_STATE'.
Verbal alarms crashed upon hitting the observing intent bit.

Lock loss at 13:43 UTC. No obvious issues prior.

NOISE_TUNINGS was announced twice by verbal alarms, along with: 'TypeError while running test: LOCK_STATE'. This occurred the last time as well.

Accepted the attached SDF differences. Why are these coming up each time?

Verbal alarms crashed again upon hitting the observing intent bit.

Hopefully the initial alignment will help this lock.

Lock loss at 9:46 UTC. Ran initial alignment. Relocking.

Accepted the attached SDF differences. Verbal alarms crashed upon hitting the observing intent bit. Previously seen DARM noise is gone.

Lock loss at 09:00 UTC. Possibly from the mechanism causing the DARM noise?

Range is dropping with it. See attached.

TITLE: 06/13 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 58Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 9mph Gusts, 7mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.11 μm/s 
QUICK SUMMARY:

Restarted nuc5 and video2.

TITLE: 06/13 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 57Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: 15hour lock, range has been a bit lower than the last lock (59Mpc) but the wind has calmed down and the rest of the environment is calm.

Locked and Observing for 12hrs. The range drop that we saw previously definitely seems to correlate with the wind, which is odd since the wind was only peaked at 35mph for a few tens of minutes and then slowly decreased again.

There does still seem to be some more noise than usual in the 30-1000hz and our range is still only at 60Mpc, about 5Mpc worse than the last lock.

When I restarted the calibration pipeline last Thursday, June 8 (see https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=36727 ), I noticed that gstlal-calibration-1.1.7 had been installed on h1dmt0 and h1dmt2. This apparently happened automatically during Tuesday maintenance and was not intentional. However, this change did not affect the process or the output until the restart on June 8. Due to the amount of testing already done with this version (the last batch of C01 was made with it; also see https://bugs.ligo.org/redmine/issues/5531) and the difficulty of reverting to version 1.1.4, it was decided to continue using 1.1.7 at LHO. We have had 5 days of online running since this restart, and no problems have occurred. LLO plans to continue using 1.1.4 for one more week before upgrading to 1.1.7 on June 20.

New features/bug fixes included in 1.1.7 as compared to 1.1.4:
* Algorithm to compute SRC detuning parameters; 4 more 16 Hz channels:
        - {IFO}:GDS-CALIB_F_S
        - {IFO}:GDS-CALIB_F_S_NOGATE
        - {IFO}:GDS-CALIB_SRC_Q_INVERSE
        - {IFO}:GDS-CALIB_SRC_Q_INVERSE_NOGATE
* Command line option to remove calibration lines (not yet being used, but would add a 16 kHz channel, {IFO}:GDS-CALIB_STRAIN_CLEAN )
* Latency reduced by 5 seconds (was 10 - 14 seconds, now 5 - 9 seconds)
* Bug fix to mark 3 seconds before and after raw data dropouts bad in the CALIB_STATE_VECTOR. This 3 seconds is due to the settling of the FIR filters. The risk of running without this big fix is that there can be glitches around raw data dropouts that need to be manually vetoed (see https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=32486 )

The eagle-eyed alog reader would have noticed that the regular robo-alog entries reporting on CP3 and CP4 autofills have been missing lately. We have discontinued this service now that the vacuum team have fixed the LN2 pump liquid level gauges and these pumps are back under PID control.

I found a channel name typo in /opt/rtcds/userapps/release/isc/common/medm/ISC_CUST_BULLSEYE.adl was fixed. The file was committed to the repository.

Previously, H1:PSL-DIAG_BULLSEYE_WID_INMON display on the screen actually showed H1:PSL-DIAG_BULLSEYE_PIT_INMON.