I found no apparent correlations between the ALS glitch rates and any environmental factors as presented in Alog 49603, specifically wind speed, and the temperature and relative humidity of the roof and the MSR. I proceeded to run my code for O2, and generated a timeline of the ALS glitch rates over the duration of O2.  This timeline shows that the ALS glitch rates have increased by 30 times in the X arm and 11 times in the Y arm over the O2 commissioning break.  The mean glitch rates in the X arm before and after commissioning were 0.063 glitches/s, and 1.937 glitches/s.  The mean glitch rates in the Y arm before and after commissioning were 1.018g/s and 11.49g/s.  

I have also plotted the glitch rates for O2 and O3 on the same plot. This shows us that while the glitch rates in the X and Y arms both increase after the O2 commissioning break, the glitch rate in the Y arm drops again while we were preparing for O3.  The mean glitch rate in the Y arm since the start of preparation for O3 has been 0.847g/s.  However, the mean glitch rate in X since the start of preparations for O3 is 1.767g/s; almost as bad as in O2.   

I have indicated the time when the fiber was re-buried, and this doesn't seem to have effected the glitch rates.  I have also indicated the time at which the MSR work in alog 36645 was done (June 5th, 2017).  This was when Richard put a big yellow tubing around the fiber to protect it from a flapping tag and a fan that was blowing near it.  This also does not seem to have improved the glitch rates.

The script error:

Traceback (most recent call last):
  File .../scripts/HAM_cps_spectra.py", line 57, in
    cps_data= conn.fetch(start,stop,merged)
  File ".../dist-packages/nds2.py", line 3426, in fetch
    return _nds2.connection_fetch(self, gps_start, gps_stop, channel_names)
RuntimeError: Low level daq error occured [13]: Requested data were not found.
There is a gap in H1:ISI-HAM2_CPSINF_H1_IN1_DQ from gps 1247216400 to gps 1247217000.
Please note that there may be more gaps, this was the first one identified.

This says there is a gap in the data starting from 1247216400, however, current time is 1247210375, and I've lined up those two times below, so it's easy to see that the gap is in the future by 6025 seconds, which is 100.42 minutes.

1247210375
1247216400

TITLE: 07/15 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 116Mpc
OUTGOING OPERATOR: Niko
CURRENT ENVIRONMENT:
    Wind: 13mph Gusts, 11mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: locked in Observe, all is well

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

STATE of H1: Observing

INCOMING OPERATOR: Cheryl

SHIFT SUMMARY: Quiet shift, was briefly knocked out of Observing by SQZ becoming unlocked. Locked for 16.5 hours, Observing at 117 Mpc.

LOG:

23:00 (16:00) Start of shift

00:33 (17:33) SQZ lost lock, taking us out of Observing

00:36 (17:36) Back in Observing. SQZ_MANAGER was stuck at LOCK_CLF, had to request DOWN and back to SQUEEZING

07:00 (00:00) End of shift

Using information saved by the lockloss tool, I created some plots that help summarize different aspects of our locklosses for the O3 run so far. I've put these plots on the DCC, so that they can be updated throughout the run (and more plots can be added).

The first plot is a histogram of our NLN lock durations, the second is a histogram of which suspensions have saturated first before lockloss, and the third is a histogram of what states we have lost lock from. This is in its early stages, so if anyone has suggestions on other relevant data to plot/more effective plotting methods, let me know.

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

State of H1: Locked

Intent Bit: Observing

Weather: 0-20 mph wind

Primary 0.03 – 0.1Hz: 0.01 um/s

Secondary 0.1 – 0.3Hz: 0.1 um/s

Outgoing Operator: Travis

Quick Summary: Observing for 9 hours, medium wind

TITLE: 07/14 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
INCOMING OPERATOR: Niko
SHIFT SUMMARY:  Observing for the entire shift.  Otherwise uneventful.
LOG:

18:40 Kyle to both mids

19:48 Kyle back

20:40 Hugh and guest to Observation Deck

20:53 Hugh and guest back

Continuing logic troubleshooting of new pump installation at Y-mid (no craning, pwr tools, ladders etc.).  I will make a comment to this entry when I leave.

TITLE: 07/14 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: Jim had H1 back to Observing 0.5 hours before my shift started. Hopefully the EQs are done for the day.

TITLE: 07/14 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
INCOMING OPERATOR: Travis
SHIFT SUMMARY: Down for most of the shift because of earthquakes
LOG:
9:36 lock loss due to 7.3 eq

After eq was able to get arms locked, but DRMI was bad. Initial alignment took forever, not because it wouldn't lock, but because wfs wouldn't go below threshold.

14:35 Back to observing after eq ring down, initial alignment

Went to sei_conf earthquake state at 9:25, and I put ISC_LOCK in the not-oft-used earthquake state at 9:32, which took us out of Observing. Followed by a lock loss at 9:36. Not sure why, because the ground was still moving less that the peak velocities of the previous smaller earthquake.

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

STATE of H1: Observing

INCOMING OPERATOR: Jim

SHIFT SUMMARY: Rode through an extremely sharp 4.0 EQ in West Montana and a 6.6 EQ in Australia. Wind has been consistently peaking at around 20-25 mph for the shift.

LOG:

23:00 (16:00) Start of shift

01:55 (18:55) Quickly switched SEI_CONFIG to EQ mode after noticing a sharp seismic spike (4.0 in Western Montana).

02:06 (19:06) Switching back to WINDY, though it seems ASC is still recovering from the EQ.

06:02 (23:06) Switching to EQ for 6.6 in Australia

07:00 (00:00) End of shift

Yesterday, right after my shift ended, there was an EX glitch that seemed to be ringing down successfully when something happened and we lost lock 15 seconds later. I noticed that the lockloss tool hasn't been able to analyze this lockloss yet, and I thought that it was interesting enough to run the lockloss using my local lockloss tool (maybe this is a common type of lockloss, I'm not sure). Here is the link to the results:

https://ldas-jobs.ligo-wa.caltech.edu/~yannick.lecoeuche/index.cgi?event=1247036507

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

State of H1: Locked

Intent Bit: Observing

Weather: 0-25 mph wind

Primary 0.03 – 0.1Hz: 0.01 um/s

Secondary 0.1 – 0.3Hz: 0.1 um/s

Outgoing Operator: Travis

Quick Summary: Observing for 14.5 hours, medium wind

TITLE: 07/13 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
INCOMING OPERATOR: Niko
SHIFT SUMMARY:  Uneventful day for interferometry; no GRBs, no candidate triggers, not even any EQs of significance.  200+ people through the control room for the Saturday tour.
LOG:

14:14 Betsy to cleaning area to get C3 covers

14:16 Betsy out

TITLE: 07/13 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 116Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    Wind: 7mph Gusts, 4mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:  Lock is 6.5 hours old.  No issues at this time.

TITLE: 07/13 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
INCOMING OPERATOR: Travis
SHIFT SUMMARY:
LOG:

7:01 Lockloss as soon as I arrive, no obvious cause

8:34 Back to Observing, only thing I touched was alignment during PRMI, it was back