Reports until 16:39, Saturday 06 January 2024
H1 General
ibrahim.abouelfettouh@LIGO.ORG - posted 16:39, Saturday 06 January 2024 - last comment - 20:53, Saturday 06 January 2024(75225)
Transition from ETMX Locklosses - Potential Causes Investigation

Sheila, Ryan S, Ibrahim

Continuation of Transition from EX Failures - The Lockloss causing state

Images attached to this report
Comments related to this report
ryan.short@LIGO.ORG - 17:10, Saturday 06 January 2024 (75227)CAL, ISC

Expanding on the point about the ETMX ESD calibration lines being on, first noticed by Sheila:

The ETMX cal lines should be off for all of lock acquisition up until the TURN_ON_CALIBRATION_LINES state (and turned off while in NLN_CAL_MEAS). However, these were being turned back on during SDF_REVERT after a lockloss as they had been incorrectly accepted as on in the h1susetmx SAFE.snap SDF table. Interestingly, it looks like these were not turned off for some reason when going to NLN_CAL_MEAS during the commissioning time yesterday (see attached ndscope; perhaps contributing to problems mentioned in alog75204?). During this lock acquisition, I set the ETMX L3 cal line gains back to zero and accepted them in SDF (screenshot attached). This appears to have fixed the problem with locklosses during TRANSITION_FROM_ETMX which have been plaguing us since yesterday, as H1 has just reached low noise and started observing.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 20:53, Saturday 06 January 2024 (75231)

Thanks to Ibrahim and Ryan for following up on these problems and aloging this. 

Two things to add to what Ibrahim said about the EY filter:  I plotted (and looked at) only one quadrant of the PUM drive in the screenshots, which was close to saturating the 20 bit DAC on EY L2, but not quite saturating.  Since the PUM also gets ASC signals all 4 quadrants get somewhat different signals and probably one of the unplotted quadrants is what saturated and caused the locklosses.

The filter which was missing from EY in TRANSITION_FROM_ETMX is called muBoost, and is meant to offload the microseism drive from the PUM to L1.  It is in FM4 in ETMY L1 LOCK and FM2 in ETMX L1 LOCK.  This seems to have been an oversight, which has probably been this way for quite a while.  FM4 is already turned on in the LOWNOISE_ESD_ETMY state. I've just now committed ISC_LOCK to the svn revision 27023.

This has probably been an ocassional problem for a long time, but the combination of more ground motion due to wind and microseism and having the calibration line on with the linearization on while the bias ramps down made this state not work at all.

The problem with the calibration line is that it passes through the linearization for the ESD which we only use in the high noise high range ESD configuration.  As we ramp the bias to zero in order to switch the ESD driver to low noise, if the calibration line is on the linearization does some large and strange things, which have been a cause of locklosses in the past.