Got the wake up call at 338amPDT. And literally while I was waking up and trying to remember what to do for the NOTIFY + MANAGER guardian nodes (I just "init-ed" both...is that the right thing? that's what both of their User Messages said to do), I noticed that there was a Message that said there was an issue with the SQZ MANAGER.
As I was getting ready to open up the SQZ guardians and assess (I'm pretty sure I spelled that right--I remember Hugh giving me grief for misspelling it in an alog before!), H1 was already back to OBSERVING. I literally did nothing! H1 was in OMC Whitening at 932utc, sent wake up call at 1037utc, and automatically went to Observing on its own at1043utc. I'm going to go back to bed ASAP!
Great job getting H1 thru all the environmental catastrophes at the end of your shift, Ibrahim! :)
Corey you were woken up because we were still in OMC_Whitening Damping Violins when the Timer for the "OPS Wake Up" (IFO_Notify) Guardian ran past an hour (the timer for this state), and thus rang your alarm clock early.
Ibrahim did buy you some time for some more Z's by waiting until we were in OMC_Whitening to set the Remote OWL Shift button, but the Violins just took So0 long to Damp (1 hour 10 min ).
SQZ sub system was working just fine in this case. Less than a second after ISC_LOCK hit NLN, the SQZ_MAN was completed, and 9 seconds later we were Observing.
Unfortunate timing really. Some times, H1 just wants you to watch while it Locks it's self, I guess.