Reports until 07:59, Thursday 15 June 2023
H1 General
ryan.crouch@LIGO.ORG - posted 07:59, Thursday 15 June 2023 - last comment - 10:47, Thursday 15 June 2023(70469)
OPS Thursday Owl shift summary

TITLE: 06/15 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
SHIFT SUMMARY:

Lock#1:

NLN at 06:00, in Observing at 06:12, out at 06:43 from the SQZer unlocking, back in Observing at 06:45

Lockloss at 08:04, most likely from some local ground motion event. Ground motion seen mostly in the 1-3, 3-10 Hz bands. The 10-30Hz band saw the motion too but not as strongly.

Lock#2:

Xarm ran through increase flashes twice, couldn't get DRMI, went through PRMI which locked quickly, then locked DRMI in ~5 minutes.

NLN at 09:23, in Observing at 09:29

Lockloss at 13:52

Lock#3:

Yarm went through increase flashes, DRMI locked without needed to go through PRMI

NLN at 14:55, waiting on ADS to converge to go into observing

LOG:

Comments related to this report
camilla.compton@LIGO.ORG - 10:47, Thursday 15 June 2023 (70477)SQZ
Link

Went out of Observing dur to OPO_SERVO railing and SQZ_OPO guardian requested itself DOWN, see attached.

In SQZ_OPO_LR Guardian:
       if abs(ezca['SQZ-OPO_SERVO_SLOWMON']) > 9:
            log('OPO servo output railing')
            return 'DOWN'
 
Expect due to SQZ OPO PZT 1 going close to edge of range. Usually locks between 40-110V. It was just below 110V. On Tuesday we went out of observing becasue of this getting to 40V but the LVEA temperature was changing at the time, see t-cursor attached 70413.
We added a SQZ_MANAGER checker in SQZ_READY_IFO and LOCK_OPO_AD_FC to relock the if PZT_1 gets < 50, I'll add this to also check for OPO_PZT_1 > 105V 100V too as we added for the SHG_PZT 70076.
SQZ_MANAGER will need to be reloaded when out of observing next.
Images attached to this comment