Reports until 16:07, Thursday 20 February 2020
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:07, Thursday 20 February 2020 - last comment - 09:49, Friday 21 February 2020(55206)
Ops Day Shift Summary
Ops Shift Log: 02/20/2020, Day Shift 16:00 – 00:00 (08:00 - 16:00) Time - UTC (PT)
State of H1: Unlocked  
Intent Bit: Locking
Support: N/A
Incoming Operator: Jenne, Sheila
Shift Summary: IFO is recovering from a lock loss. Have not had to intervene, but have lost lock at various places after DRMI_1F.  
 
Activity Log: Time - UTC (PT)
08:00 (00:00) Take over from Jim
17:54 (09:54) Damped ETM-X Mode 13 – Changed gain from 0 to 15
17:57 (09:57) Drop out of Observing due to TCS-X laser glitch
18:00 (10:00) Turn over IFO to Jenne & Sheila for commissioning
18:05 (10:05) Vanessa – Cleaning at Mid-X
18:31 (10:31) Set ETM-X Mode 13 gain back to 0
                       Mode had damped from 5.5 to 0.39
19:12 (11:12) Switch to EARTHQUAKE mode for incoming mag 5.9 from Russia
19:21 (11:21) Lock Loss – Earthquake from Russia
19:42 (11:42) Sheila – Going into LVEA to tweak the ALS DIFF Beat note
20:00 (12:00) Two tours through control room
20:02 (12:02) Sheila – Out of the LVEA
20:15 (12:15) Chandra – Escorting Praxair vacuum repair tech to CP1
20:58 (12:58) Niko – Going into the Optics Lab
21:29 (13:29) Lock loss - Unknown
21:41 (13:41) Praxair finished and off site
22:07 (14:07) Relocked at NLN and back in Observing
23:00 (15:00) Lock loss – Unknown
00:00 (16:00) Turn over to TJ
Comments related to this report
jeffrey.kissel@LIGO.ORG - 16:24, Thursday 20 February 2020 (55209)DetChar, ISC, Lockloss, OpsInfo
Link 

J. Kissel, J. Driggers

We've been having trouble losing lock during the MOVE_SPOTS portion of the IFO "for the past day or two" (annecdotal), and there were two more instances today at 2020-02-20 23:28 UTC and 2020-02-20 23:49 UTC. These were on the way up from the "unknown" lockloss that Jeff mentions at 23:00 -- though, note: we are blaming today's change in DARM offset for these two lock losses at 21:29 and 23:00 (see LHO aLOG 55204).

Anyways -- looking for clues as to what's going on, I remembered the "good catch" that Georgia had back in July 2019 regarding the spots falling off the transmon QPDs (see LHO aLOG 50810), and thought this problem might be that. After conferring with Jenne, she informs me that we're now moving the transmon itself by centering on the B QPDs in order to prevent exactly this. This was done in November 2019 (see LHO aLOG 53362). 

So it *should* no longer be a problem.

But Jenne and I agree it's worth a check to confirm, so I attach screenshots of the QPDs during these two acquisition attempts.

As one can see, while the ISC_LOCK guardian state is cooking between 430 (ENGAGE_ASC_FOR_FULL_IFO) and 506 (MOVE_SPOTS), the transmon QPD's centering is well within the +/- 1.0 range, happily centered.

NOT IT! OH well...
Images attached to this comment
sheila.dwyer@LIGO.ORG - 09:49, Friday 21 February 2020 (55219)
Link

Remember that if you are wondering about what the history is of locklosses from a certain state, you can very easily obtain reliable information using the lockloss website. 

  • look up the number of the guardian state you are interested in by typing in control room terminal: guardutil states ISC_LOCK 
  • open up the website: lockloss
  • type the state number (506 for MOVE SPOTS) into the guardian state field in the row labeled filter events and hit submitt.  

In this case, I changed the state numbers when I rearranged the states on Jan 1st (see  54240, and 54219 for the story of how move spots stopped working during the computer crash and tumblegeddon), we had 3 locklosses from move_spots between then and Feb 6th when Jenne removed the accidental 2 minute wait I'd introduced when moving the states around 54949.  We had the two minute wait removed from Feb 6th until Feb 11th, we had 9 locklosses from MOVE_SPOTS durring those 5 days.  In the 6 days since I added a 2 minute pause back 55029, we've had 3 locklosses, 1 of which happened yesterday.