Summary:  H1 was out from 7:58 - 9:45.  Not totally clear when to Intervene due to repeating locklosses.

A minute before my shift started H1 lost lock.  I immediately got set up to lock H1 with our new operator protocol (T1900725) of allowing H1 to lock as much as it can WITHOUT operator intervention.  Still think there are some states/steps where we might want to change intervention thresholds. 

To Intervene, Or Not Intervene

For example, there were several locklosses in a row which happened in odd states (several in a row while waiting for DRMI to acquire & one during FIND_IR)...I was fearing I was in a loop of locklosses at this point!  And so, to prevent waisting time, on the 9th (!) lock, I threatened to run an alignment by opening up all the nodes needed to do that, and (wouldn't ya know it!) H1 then locked all the way up!!  Ha!  

As for actual intervention, it only happened on the very first lock (tweaking ETMy for y-arm green locking) & after that, I sat on my hands and noted where it dropped out.

H1:LSC-PRCLFF FM4 is OFF

Looks like Guardian is taking us to the standard state of keeping PRCLFF's FM4 OFF, but with tests last night, there was an SDF diff for wanting it ON.  I went back to Accepting FM4 OFF.  Attached is a screenshot of the SDF diffs I observed and then ACCEPTED to get us back to OBSERVING.

Notes On Operator Intervention & Locking:

• 7:58 lockloss! (After 19.5hr lock)
  • LOCK#1 7:59 -8:09
    • Green arms:  Y-arm not locking. 
      • After 5-min Ops Wait:  ETMy Pit moved +0.3 clicks & immediately locks up.
    • DRMI:  LOCKLOSS went down at ACQUIRE_DRMI_1F  :-/
  • LOCK#2 8:11 - 8:27
    • Lockloss #1 at ENGAGE_ASC_FOR_FULL_IFO 
  • LOCK#3 8:28 - 8:41
    • Lockloss #2 at ENGAGE_ASC_FOR_FULL_IFO 
    LOCK#4 8:42 - 8:48
    • DRMI:  LOCKLOSS at ACQUIRE_DRMI_1F  
  • LOCK#5 8:49-8:52
    • LOCKLOSS at FIND_IR
  • LOCK#6 8:53-8:58
    • DRMI:  LOCKLOSS at ACQUIRE_DRMI_1F
  • LOCK#7 8:59-9:05
    • DRMI:  LOCKLOSS at ACQUIRE_DRMI_1F
  • LOCK#8 9:06-9:10
    • DRMI: LOCKLOSS at ACQUIRE_DRMI_1F
  • LOCK#9 9:11 -  9:42
    • During this DRMI acquisition, I decided to opt out of the new Operator Intervention procedure & go for an alignment.  I began opening up all the ALIGN windows to get ready....and wouldn't you know it, H1 FINALLY makes it past the ASC steps and eventually to...
    • Nominal Low Noise!