Reports until 15:31, Monday 29 January 2024
H1 SQZ
camilla.compton@LIGO.ORG - posted 15:31, Monday 29 January 2024 - last comment - 11:29, Tuesday 30 January 2024(75606)
Edited the LOCKED_SEED_DITHER lockloss threshold

Vicky, Sheila, Camilla

While in HAM6, Sheila noticed they;d lost their SQZ beam. Vicky found that the SQZ_OPO_LR guardian had unlocked but not realized it as the variable lockloss threshold was too high. When Vicky relocked it, the beam came back fine. Plot attached showing H1:SQZ-SHUTTER_I_TRIGGER_OUT_DQ increasing but not getting over the incorrect lockoss threshold of 2800.

We edited SQZ_OPO_LR  LOCKING_SEED_DITHER state to wait 15 seconds after the boosts are turned on for the OPO to be fully locked before moving to  LOCKED_SEED_DITHER and calculating the lockloss threshold (p.round(cdu.avg(1,'H1:SQZ-SHUTTER_I_TRIGGER_OUT_DQ')*1.025)), rather than taking the average while the seed is still finishing locking. If the seed dither unlocks, SQZ_MANGER will relock it.

Strangely the HAM6 QPDs (e.g. OMC_A) NSUM went negative (rather than 0) when this happened, making Tony and the CDS team check there was no issues. Unsure why it did.

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 11:29, Tuesday 30 January 2024 (75622)

OPO was still not locking correctly in SEED_DITHER  this morning. Sometimes incorrectly thinking it was locked and other times taking over 30 seconds to be locked and thus setting it's lockloss threshold incorrectly.

We should troubleshoot this when we are next in laser hazard.