TITLE: 10/16 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 10mph Gusts, 8mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.39 μm/s
QUICK SUMMARY:

• We've relocked following a 6.4 EQ from Alaska, locked for 36 minutes, in observing since 14:43UTC
• All systems look good, range is slowly increasing

ALS_DIFF had stepped over a resonant offset by about 35. I'm not yet sure if this offset is changing by this much each lock, or if there is something else going on.

TITLE: 10/16 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 161Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: We've now been Locked for 2hrs 15mins and everything is looking good besides some wind at around 20mph.

Relocking from the 10/15 03:18 earthquake lockloss, I needed to touch both green arms, and IR DIFF could not be found so I needed to adjust the DARM offset, but lost lock while doing that, and during the next relock I had to help with DIFF again.

LOG:

23:00UTC Detector Observing and has been Locked for 11hours 35mins

00:00:02 Verbal said WAP on in LVEA, EX, EY (dropped to a value of 0 for 5s starting at 00:00:00)
    - Rarely shows up (unless we actually forgot the wifi on) but when it does it's always at 00:00UTC

03:18 Lockloss due to nearby Canadian earthquake (73488)
    - Relocking: needed to go to GREEN_ARMS_MANUAL for both arms, and needed to pause at CHECK_IR and touch DIFF Offset
03:55 Lockloss from CHECK_IR
04:46 Into NOMINAL_LOW_NOISE

04:57 Observing

Lockloss @ 10/16 03:18UTC due to a sudden local earthquakeearthquake from west Canadian coast. Peakmon jumped up to 2200 counts very quickly.

03:18:40 DIAG_MAIN message: SERVO_BOARDS: IMC_REFL_SERVO_SPLITMON > 8V

03:18:45 SRM saturation

03:18:49 Earthquake mode activated

03:18:54 SRM saturation

03:18:56 SRM saturation

and Lockloss

These past couple of days we have had a lot of sudden ground motion for some reason.

EDIT: USGS actually did measure this one as coming from off the west coast of Canada, so makes sense why we did not get notified in time. The local earthquakes from previous days had not shown up on USGS however so were definitely from much closer than this one was.

We're Observing at 155Mpc and have been locked for nearly 16hours now.

At 00:00:02UTC we did get the 'WAP on in LVEA, EX, EY' notification on Verbals, which happens every once in a while at 00:00UTC when the values go from 2 down to 0 and then back to 2 5s later. Nothing else to note.

TITLE: 10/15 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 18mph Gusts, 13mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.30 μm/s
QUICK SUMMARY:

Detector Observing and has been Locked for almost 12hours now. Everything is looking good. Wind has picked up a bit in the last few hours.

TITLE: 10/15 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 165Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Quiet day, EY chiller issue thats seems to have been resolved. The wind has been picking up over the past 3 hours. We've been locked for 11:35 as of 23:00 UTC.

LOG:

No log

We've been locked for 7:55, everythings stable. The EY water temperature has recovered it seems.

I was just going to put in an alarm bypass for the EY chiller supply water temperature and noticed that it has returned to its operational temperature in the past 30 mins. 6 hour trend shown.

Sun Oct 15 10:08:06 2023 INFO: Fill completed in 8min 2secs

TITLE: 10/15 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.32 μm/s
QUICK SUMMARY:

• We've been locked for 3:40, in Observing since 11:34UTC
• All systems look good

After a 1hr59min lock, H1 had a lockloss and H1 was stuck at FIND_IR with ALS DIFF needing "Search for IR Resonance by hand"  at 947utc/247amPT.

Unfortunately, my computer has been monumentally slow so.  I have rebooted my computer and it is a little bit easier, but still very hard to work on H1 because of the slow NoMachine interface.  I was able to FIND IR (very slowly due to my computer) by moving the DIFF OFFSET only a few clicks.  

ISC LOCK continued.

• My computer/NoMachine slowly was able to open other screens (i.e. AS AIR video, ndscope to look at POP18 & 90).  
• DRMI did not lock, so ISC LOCK (I am guessing went to only ACQUIRE_PRMI) and stayed in this state for quite a few minutes...
• Was able to (slowly) determine PRMI locked, but was misaligned.
• I (eventually) took ISC_LOCK to PRMI_ASC.  Once it made it there, I requested the NLN state.
• H1 locked DRMI, but it has been stuck at ACQUIRE_DRMI_1F for about 8min so far.  I don't know now it's not proceeding.  ISC LOCK's log says that 10:36utc it wants to "try_PRMI".... but I'm confused if this is an old notification....because my computer is slow.  
• This.  Is.  Frustrating!!
• Going to give this a few more minutes and then consider driving to site because this set-up is not optimal.