Reports until 08:12, Saturday 18 November 2023
H1 General
oli.patane@LIGO.ORG - posted 08:12, Saturday 18 November 2023 - last comment - 10:37, Saturday 18 November 2023(74273)
Ops DAY Shift Start

TITLE: 11/18 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Austin
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 1mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY:

Detector is down with ISC_LOCK in Initial Alignment - looks like IA completed at 12:19UTC but then it stayed there, with H1 MANAGER saying assistance required 8 minutes earlier due to the IA timer expiring, which is the same issue that had woken Austin up a couple of hours previously. I assume that he did not get the second call for whatever reason? Either way, I started locking.

H1 MANAGER:

2023-11-18_12:11:11.082073Z H1_MANAGER [RUNNING_ALIGNMENT.run] timer['initial_alignment'] done
2023-11-18_12:11:11.136738Z H1_MANAGER [RUNNING_ALIGNMENT.run] Timer expired, alignment taking too long
2023-11-18_12:11:11.197052Z H1_MANAGER JUMP target: ASSISTANCE_REQ
2023-11-18_12:11:11.198696Z H1_MANAGER [RUNNING_ALIGNMENT.exit]
2023-11-18_12:11:11.252860Z H1_MANAGER JUMP: RUNNING_ALIGNMENT->ASSISTANCE_REQ
2023-11-18_12:11:11.252860Z H1_MANAGER calculating path: ASSISTANCE_REQ->LOW_NOISE
2023-11-18_12:11:11.252860Z H1_MANAGER no path from ASSISTANCE_REQ->LOW_NOISE
2023-11-18_12:11:11.258125Z H1_MANAGER executing state: ASSISTANCE_REQ (50)
2023-11-18_12:11:11.258405Z H1_MANAGER [ASSISTANCE_REQ.enter]
2023-11-18_12:11:11.316931Z H1_MANAGER [ASSISTANCE_REQ.run] USERMSG 0: Human assistance required! Request INIT to clear

IFO_NOTIFY:

2023-11-18_11:31:21.378817Z IFO_NOTIFY executing state: WAITING (20)
2023-11-18_12:11:11.271937Z IFO_NOTIFY [WAITING.run] H1_MANAGER requires assistance. Sending
2023-11-18_12:11:11.380463Z IFO_NOTIFY EDGE: WAITING->ALERT_ACTIVE
2023-11-18_12:11:11.382711Z IFO_NOTIFY calculating path: ALERT_ACTIVE->ALERTS_ENABLED
2023-11-18_12:11:11.382711Z IFO_NOTIFY new target: ALERTS_ENABLED
2023-11-18_12:11:11.384404Z IFO_NOTIFY executing state: ALERT_ACTIVE (30)
2023-11-18_12:11:11.393434Z IFO_NOTIFY [ALERT_ACTIVE.enter]
2023-11-18_12:11:11.465917Z IFO_NOTIFY [ALERT_ACTIVE.run] USERMSG 0: See log for alert. Select INIT to reset

Comments related to this report
oli.patane@LIGO.ORG - 10:37, Saturday 18 November 2023 (74275)

16:35 While relocking, detector kept jumping back down to ACQUIRE_PRMI from ACQUIRE_DRMI_1F, so I followed https://cdswiki.ligo-wa.caltech.edu/wiki/Troubleshooting%20the%20IFO#Difficulty_locking_DRMI_1F.2F3F instructions
    - After a couple of tries, at 17:15 the ifo took us through CHECK_MICH_FRINGES, and after we went up normally.
18:13 NOMINAL_LOW_NOISE
18:19UTC Observing