TITLE: 05/31 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 126Mpc
SHIFT SUMMARY:

1. Lockloss at 12:13 UTC - DRMI Unlocked due to Myanmar quake.
   1. Guardian immediately went into Earthquake mode after this - it’s coming through on picket fence now. Seems like it was just the 5.8 Myanmar.- Sei just went back to WINDY/CALM as of 12:23 UTC.
2. Lock 2: 
   1. ALS X and Y both at increase flashes
      1. Had to touch both X and Y
         1. Lost lock during Locking_ALS - had to relock
         2. Lost lock during Locking _ALS again
         3. Lost lock a few times post-EQ but would always catch immediately without needing to increase flashes post-manual movement.
         4. Lost lock as soon as IR was found 
   2. POP Signals are terrible even in PRMI so will misalign the PRM and adjust the BS
   3. I couldn’t make the POP signals any better - by moving the usual culprits so will take an initial alignment (EQ combined with temp change informs this decision).
      1. Init_Align went smoothly
      2. ALS X looks much more stable
   4. DRMI Locked with 0 help (post initial alignment) - never had this happen!
   5. Steep EQ coming in put SEI_CONF in EARTHQUAKE Automatically - at max power as this is hitting (rode through Japan EQ in Earthquake mode)
   6. Back to NLN at 14:34 UTC
3. IFO is in NLN and OBSERVING as of 14:47 UTC

Other:

1. Picket fence only gathering/showing data from one seismometer. Tried restarting and troubleshooting but the issue persisted. - I think it was an issue from the seismometer’s side because they all came back online around the same time (I also restarted it again). This has now happened 3 times (where it fixes itself now stuck on one seismometer).
2. In response to the ISS pump power not reaching its threshold: with guidance from vicky, we turned down the threshold on pump_iss_setpoint from 60uW to 50uW. I saved the change in the code but before I could reload its guardian, it reached the nominal "observing" mode so I think it worked since this is where it was getting stuck.
   • From the log, the power would go close to 60 and then reset, which was preventing us from observing so this should fix it. Thanks Vicky!