Reports until 10:37, Wednesday 06 March 2024
H1 ISC (OpsInfo)
ryan.short@LIGO.ORG - posted 10:37, Wednesday 06 March 2024 - last comment - 16:49, Friday 08 March 2024(76154)
Changes to ISC_LOCK Guardian for O4b Commissioning

Per commissioner request, I've made two changes to the early main locking steps as set in ISC_LOCK:

  1. By default, ISC_LOCK now goes through CHECK_SDF rather than SDF_REVERT so settings are preserved lock to lock
  2. The timer for moving the ALS arm nodes to INCREASE_FLASHES during LOCKING_ARMS_GREEN has been increased from 2 minutes to 20

Changes have been loaded and committed to svn.

Comments related to this report
ryan.short@LIGO.ORG - 15:43, Wednesday 06 March 2024 (76163)OpsInfo, SQZ

I've also commented out SQZ_MANAGER from the list of managed nodes in ISC_LOCK. This allows SQZ to work independently without main IFO locking telling SQZ_MANAGER what to do for now.

EDIT: We later learned that lines 214-215 of ISC_LOCK needed to be commented out as well since this is a request of SQZ_MANAGER in the DOWN state.

ryan.short@LIGO.ORG - 16:11, Thursday 07 March 2024 (76195)

Furthering this effort as main IFO locking is progressing, I've commented out the first couple lines in the LOWNOISE_LENGTH_CONTROL state which interacts with SQZ_MANAGER, which at this point is not managed.

victoriaa.xu@LIGO.ORG - 16:49, Friday 08 March 2024 (76217)ISC, SQZ

Naoki, Vicky - We have undone these changes guardian changes for the break (brought back SQZ_MANAGER in list of managed nodes, in first few lines of LOWNOISE_LENGTH_CONTROL, and lines 214-215 requesting sqz to down).

SQZ_MANAGER is back to being managed in ISC_LOCK as usual. We will see the lock sequence through a few times and get it running smoothly, and update on that after relocking.