Displaying report 1-1 of 1.
Reports until 16:02, Saturday 06 May 2023
H1 General (SUS, VE)
austin.jennings@LIGO.ORG - posted 16:02, Saturday 06 May 2023 - last comment - 11:44, Monday 08 May 2023(69378)
Saturday Operator Summary

TITLE: 05/06 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning at 130 Mpc
SHIFT SUMMARY:

Main Notes:

- Second ER15 candidate! @ 17:09:35

- ACQUIRE_XARM_IR during IA is still failing, and therefore I cannot run a full initial alignment

- ACQUIRE DRMI 1F has been quite cumbersome recently trying to acquire

- IFO is at OBSERVING @ NLN @23:02
Lock #1:

- Came in with IFO locked, switched to OBSERVING @ 14:56 UTC, out of OBSERVING @ 17:00 UTC due to difference from VAC SDF (was only temporary, but maybe this channel should be unmonitored), screenshot attached - Tagging Vac

- PI 24 ring ups at 15:26/15:37 UTC, but the SUS_PI guardian was able to damp it - no intervention needed

- Starting a calibration suite @ 17:01 UTC in NLN CAL MEAS

- EX saturation @ 18:02 UTC and again @ 20:20, huge jump in ADS signals and OMC DCPD output went off the rails - glitch?

- Back to NLN and OBSERVING @ 18:53 UTC

- LOCKLOSS @ 2026 UTC - this looks like an ASC ringup, potentially from SRC1/2 and/or MICH? - however ground motion looks a bit elevated so that could be a culprit as well

Lock #2:

- IMC had issues acquiring, but resetting ISC_LOCK to INIT and having it tried again worked fine

- DRMI issues 3x times trying to lock, gave up and trying an initial alignment - just like yesterday I again cannot ACQUIRE_XARM_IR. Skipping IA and trying again.

- Acquired NLN @ 22:38

- Some OBSERVE snaps are preventing me from going to OBSERVING, SUSITMY - Screenshots attached, accepting and went into OBSERVING, Tagging SUS

LOG:

No log for this shift.

Images attached to this report
Comments related to this report
austin.jennings@LIGO.ORG - 08:40, Sunday 07 May 2023 (69389)

For ITMY diffs, the changes I accepted showed up as differences on SDF observe. Accepting them and setting them back to what they were before.

Images attached to this comment
elenna.capote@LIGO.ORG - 11:44, Monday 08 May 2023 (69408)

This doesn't appear to be an ASC instability lockloss. Looks like something kicked all the ASC signals right before lockloss- potentially the large ground motion you mention? I attached a screenshot of the DRMI signals for example.

Images attached to this comment
Displaying report 1-1 of 1.