TITLE: 03/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: H1 was locked this morning following the windstorm of last night, but lost lock during commissioning time. Relocking after that was simple, but after again losing lock about an hour later, H1 has not been able to relock since then.

I'll write up a separate and more detailed entry later, but most of the struggle with relocking stemmed from an issue I started noticing with ALS-Y that would cause spontaneous locklosses at states after LOCKING_ARMS_GREEN. At seemingly random intervals, the ALS-Y PLL would jump from its Locked state into Ramp Gain, which flags the PLL as "not okay," causing Guardian to assume a lockloss. Since I don't know what causes this state transition, I'm not sure what the underlying issue might be, but so far when this happens the first thing I can see changing is this FIBR_LOCK_STATE. Eventually, these glitches stopped late in the afternoon. An example of one of these instances (in this case during FIND_IR) is shown in the ndscope screenshot attached.

• 15:30 - Dropped observing for commissioning
• 17:09 - Lockloss from commissioning activities
• 18:44 - Observing; straightforward relock without an alignment
• 19:54 - Lockloss - alog83533
  • ALS-Y issues begin, locking proves impossible
• 20:57 - Jim power cycling HAM3 CPS rack to address noise - alog83528
• 22:52 - ALS-Y issues seem to have stopped, but can't lock DRMI, so starting initial alignment
• 23:13 - IA finished

LOG: