camilla.compton@LIGO.ORG - posted 17:43, Wednesday 10 May 2023 - last comment - 17:00, Thursday 11 May 2023(69489)
Strange SQZ_MANAGER behavior today - will investigate tomorrow
Naoki, Camilla
- at 2023/05/10 22:32:17 UTC to SQZ_MANAGER was in DOWN but the beam diverter was open
- at 2023/05/10 22:21:03 UTC SQZ_MANAGER was requested to NO_SQUEEZING but stayed at FDS.
We will investigate this logic tomorrow. We think we got into a strange state as the FC was struggling to lock in IR but Naoki double the IR gain and SQZ_FC is now working.
Images attached to this report
Comments related to this report
- at 2023/05/10 22:32:17 UTC to SQZ_MANAGER was in DOWN but the beam diverter was open
- Issue: the Beam diverter was still busy as it had just been requested to open, see attached.
- Solution: added a SYS-MOTION_C_BDIV_E_BUSY checker into the turn_off_sqz() function and a checker in DOWN.
- at 2023/05/10 22:21:03 UTC SQZ_MANAGER was requested to NO_SQUEEZING but stayed at FDS.
- Issue: SQZ_MANAGER didn't ignore us but the target, NO_SQZ, isn't a jump to state so it was waiting for arrive in FDS, but didn't see attached. Eventually beam diverter was closed when wait_for_fc timer was up and it jumped to SQZ_READY_IFO
- Solution: we don't want to make NO_SQZ a jump state so I added a NO_SQZ request checker in FDS if the guardian hasn't yet arrived to return SQZ_READY_IFO. This means the beam div will be closed, there will be no squeezing and if NO_SQZ is re-requested it will successfully go there.
- Changed in SQZ_MANAGER.py svn version 25618 and reloaded.
Images attached to this comment
