Reports until 21:28, Monday 25 March 2024
H1 General (Lockloss)
anthony.sanchez@LIGO.ORG - posted 21:28, Monday 25 March 2024 (76700)
Monday Ops Eve Shift Mid Shift Report

TITLE: 03/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
CURRENT ENVIRONMENT:
   
SEI_ENV state: CALM
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY:

Lock lasted 8 hours and 51 min
Lockloss 3:34 UTC still investigating the cause of this lockloss.
Camilla had some measurements running while we were in Observing see Alog 76695 and was concerned that perhaps her measurements had made the arm powers drop significantly. So I pulled up some ndscopes of H1:GRD-ISC_LOCK_STATE_N and the Circulating Arm powers  H1:ASC-X_PWR_CIRC_OUT16 & H1:ASC-Y_PWR_CIRC_OUT16.
I did see that the arm power did dip before H1:GRD-ISC_LOCK_STATE_N changed to a down state.

But!!! I also did the same for the Lockloss that happened this morning with out her measurement running and saw the same behavior of the Arm power dipping before the Down state was declared by ISC_LOCK. I then decided (arbitrarily) that it was reasonable to think that the time between the ISC_LOCK state change and an observed loss of 10% of the Power in the arms would be a good metric to determine if the lockloss was "Caused" by this measurement.
I have effectively convinced myself that Camilla's A2L measurements have not caused this lockloss.... but I'm open to evidence that I have overlooked.

Relocking:
I have not taken ISC_LOCK through Initial_Alignment before relocking. H1 Is alrerady back to NOMINAL_LOW_NOISE  44 Minutes from NLN to NLN with out intervention from the Operator.  49Min 9 Sec from OBSERVING to OBSERVING.


 

Images attached to this report