Here is a Bruco scan using a LDVW default settings, with max frequency 200 Hz (plots only go up to 200 Hz, but webpage has info above 200 Hz):

https://ldas-jobs.ligo.caltech.edu/~ldvw/bruco/evan.goetz/H1-CAL-DELTAL_EXTERNAL_DQ_2019-04-07-04.00.00-180/results/

Some notable features (some different compared with Gabriele's last Bruco in late March):
- Lots of coherence 5-20 Hz with OMC-DCPD_NULL_OUT_DQ
- Second channel with lots of coherence in 5-20 Hz band and the ~35 Hz calibration lines is very frequently ASC-AS_A_RF45_Q_SUM_OUT_DQ
- Some regions with marginal coherence (~0.45) with PEM-EX_MAG_EBAY_SUSRACK_Z_DQ

TITLE: 04/08 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 109Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Nothing doing
LOG:

12:53 GRB alert, only thing of note that happened all night

TITLE: 04/07 Eve Shift 23:00 – 07:00 (16:00 -00:00), all times posted in UTC

STATE of H1: Observing

INCOMING OPERATOR: Jim

SHIFT SUMMARY: Started in Observing at around 108 Mpc, dropped out briefly to troubleshoot SQZ_MANAGER issues with Sheila. At around 20:00 UTC the range dropped by about 10 Mpc and stayed low for ~2 hours. Aside from a slight wind increase and a string of small earthquakes, I’m not sure what caused it. Range has since come back up to 106 Mpc.

LOG:

23:00 (16:00) Start of shift

02:09 (19:09) Dropped out of commissioning with the same issues as Jeff last shift. Doing some troubleshooting over the phone with Sheila

02:26 (19:26) Back to Observing, problem should hopefully be solved

07:00 (00:00) End of shift

Observing at 108 Mpc. Wind is increasing, a little below 20 mph right now. Dropped out of commissioning briefly when the SQZ_MANAGER stalled, did some troubleshooting with Sheila and got back to Observing ~20 minutes later.

Ops Shift Transition: 04/07/2019, Eve Shift 23:00 – 07:00 (16:00 -00:00) - UTC (PT)

State of H1: NLN

Intent Bit: Observing

Weather: Cloudy skies. Barely any wind.

Primary 0.03 – 0.1Hz: 0.03 um/s

Secondary 0.1 – 0.3Hz: 0.3 um/s

Outgoing Operator: Jeff

Quick Summary: Been locked for ~6 hours. Microseism and wind are down from yesterday.

   Busy morning.

   Lock loss just after "LSC Servo Board Split Voltage High" Message. 
   Had GRB alert while relocking the IFO 
   Rode through a mag5.7 EQ in Chile - SIESMON said to select EARTHQUAKE state. Did not change state and IFO continued to locking at NLN with no apparent issues. 

   Dropped out of Observing due to OPO SDF Diffs. ZM1 UL, LL and ZM2 UL, LL, UR, LR saturating. Looked like Squeezer was still locked. Called Keita. He cleared the Servo Filters on the SQZ_ASC Overview, relocked the SQZ_SHG, and requested SQUEEZING from the SQZ_MANAGER. SDF Diffs cleared, and the IFO is back into Observing. 

   Right now the IFO is locked in NLN with a range of 110.6Mpc. Winds are a no more than a Light Breeze. Am tracking 5 increasing Violin modes (ETM-Y mode2, mode4, mode8 & ETM-X mode6 & ITM-Y mode12). All are under 2.5 and growing slowly if at all. Will continue to monitor.         

   15:53 (08:53) lost lock just after getting the "LSC Servo Board Split Voltage High" message. Had to do some minor hand alignment to get ALS to lock, and a quick dress up of RF18 and RF90. Rest of the relocking process completed without additional intervention.   

   Whole relocking SEISMON reported two earthquakes in Chile. A mag5.8 at 15:45:07 and a mag 5.7 at 15:45:13. USGS reported these as one event, a mag5.7 at 15:45:07. The SEISMON guidance called for EARTHQUAKE with the R3.5 wave due to arrive in approximately 600 seconds. Being in the middle of relocking, did not want to switch SEI_CONFIG modes. Saw no effect of this earthquake while relocking. 

   16:53 (09:53) Relocked and back into Observing after accepting a couple of LSC SDF Diffs.        

TITLE: 04/07 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 111Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Remained locked and in observing entire shift. One GRB alert. Noticed DIAG_MAIN notifications that the HWS code has stopped. Held lock in 'windy' through a 5.7 mag earthquake in Chili.
LOG:

Rode through a 5.7 mag earthquake in Chili originating at 10:52 UTC without changing the SEI config from 'windy'. I didn't notice the earthquake until it showed up on the BLRMS, and while the script indicated I should take the SEI config to 'earthquake', it seemed too late at that point.

13:48 UTC GRB notification (E329134). Confirmed with LLO.

Just realized that DIAG_MAIN has been flashing messages that the HWS code has stopped. They were so brief I had to look in the log:

2019-04-07_01:23:59.022623Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ETMY code stopped
2019-04-07_01:55:22.025647Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ETMX code stopped
2019-04-07_01:59:59.028707Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ITMY code stopped
2019-04-07_05:07:38.016456Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ETMY code stopped
2019-04-07_05:13:36.027085Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ETMX code stopped
2019-04-07_05:43:37.025772Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ITMY code stopped
2019-04-07_07:13:21.025773Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ITMX code stopped
2019-04-07_07:18:26.014392Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ITMX code stopped
2019-04-07_08:31:50.012318Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ETMX code stopped
2019-04-07_08:51:17.019917Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ETMY code stopped
2019-04-07_09:27:15.028043Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ITMY code stopped
2019-04-07_11:12:11.026664Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ITMX code stopped
2019-04-07_11:50:04.023291Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ETMX code stopped
2019-04-07_12:34:56.023720Z DIAG_MAIN [RUN_TESTS.run] USERMSG 0: HWS: HWS ETMY code stopped

Have remained locked and in observing. No issues to report.

TITLE: 04/07 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 113Mpc
OUTGOING OPERATOR: Niko
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 6mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.55 μm/s 
QUICK SUMMARY:

Locked and in observing. No known issues.

TITLE: 04/06 Eve Shift 23:00 – 07:00 (16:00 -00:00), all times posted in UTC

STATE of H1: Observing

INCOMING OPERATOR: Patrick

SHIFT SUMMARY: Started in initial alignment after an environment-caused lockloss, reached NLN about 2 hours later. Been Observing since then, with a brief 3 minute switch back out. Total observing time ~6 hours.

LOG:

23:00 (16:00) Start of shift

00:54 (17:54) Entering Observing

01:36 (18:36) Prematurely turned off ADS lines after a DCPD-related glitch, which took us out of Observing

01:38 (18:38) ADS lines on again, back into Observing

07:00 (00:00) End of shift

Been in Observing for ~2 hours, minus a brief drop out when I turned off the ADS lines to try and get ahead of a DCPD glitch (ADS lines are back on now). Wind is receding, microseism has leveled off at ~0.3 um/s.

[Craig, Niko]

We noticed the violin damping node was taking a long time to reach its nominal state after hitting NLN. Craig is changing the wait flag to be false for all ramp_gain to fix this.

My python script to diag_reset h1calcs when it occasionally runs long is not working as a cronjob. For now I'm running it in a tmux session on h1fescript0 (looping every minute) until I can get the cronjob functional.