Displaying report 1-1 of 1.
Reports until 22:16, Sunday 19 May 2024
H1 General (Lockloss, SEI)
anthony.sanchez@LIGO.ORG - posted 22:16, Sunday 19 May 2024 (77935)
Double lockloss & mid Eve shift update

TITLE: 05/20 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 19mph Gusts, 14mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

Unkown Lockloss
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1400201888
I did go back to check if this lockloss was caused by the smaller ISI glitches that jim and I saw that did not trip the watchdog. This is not the case for this Lockloss It is still of unknown origin.


Relocking:
I had to slightly touch up the Beam Splitter and PRM  both in pitch to get DRMI locked but other than that it went well.
We are still saturating SUS in Power 10 & 25 Watts and in Move Spots.


HAM3 ISI tripped watchdog Lockloss
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1400207843
Contacted Jim, took IMC_LOCK to Offline and went to the CER to power cycle the HAM3 ISI Chassis found in rack SEI-C2  - rack slots 30 & 31 . Once the ISI interface chassies came back on, Jim gave me a green light to start locking again.
He noted that there are some ndscopes I can use to watch for more glitches, which are identified by spikes above 20:
ndscope H1:ISI-HAM3_CPSINF_H{1,2,3}_BLRMS_65_100 H1:ISI-HAM3_CPSINF_V{1,2,3}_BLRMS_65_100  H1:ISI-HAM3_CPSINF_H{1,2,3}_BLRMS_130_200


Relocking 2:
I clicked on Nominal_Low_Noise and It went to it with out much fuss at all.

Observing reached at 4:13 UTC
Dropped to commissioning for some SQZ Scans to increase the range.

 PI 31 has been ringing up a fair amount this lock but every time it's been solved by the PI system.

Currentlt H1 has been locked and in Observing for over 1 hour.

 

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