Summary of the DQ shift from Monday 30th Jan to Wednesday 1st Feb (inclusive), click here for full report:
-
High and variable duty cycles; 95%, 66% and 80% Observing for each day of the DQ shift. The 66% was Maintenance day.
-
Range sitting around 65-68 Mpc.
-
Noticed a single overflow of H1:ASC-AS_C_SEG# (which relates to my aLOG).
-
One of the locklosses on the 30th Jan may be caused by winds (despite they are not as strong as the ones LHO is capable of handling) (see attached pic for time coincidence).
-
The other lockloss on the 30th Jan while there was a time coincidence with Keita operating the ETMY SDF restore screen, it may have been only coincidental because the most obvious cause was the strong peak on ground motion at ETMY which started tens of minutes before the lockloss.
-
The highest NewSNR glitch reported by PyCBC live took place on the 30th Jan, with a NewSNR of 11.9. It was a blip glitch coincidental with SUS-PR2_M2 and CS LVEA MAG. (see attached pics).
-
As usual ETMY ESD overflows dominated the sharp range drops.
-
Reminder: The ETMX ESD high voltage amplifier turned off after some Beckhoff work this morning. This was turned back on, however there is indication of considerable discrepancy between running current after the switch on and previous notes that Patrick had.
-
Notice that 15-25 Hz glitches up to half an hour before the lockloss of the 31st Jan may have been due to scattering from RM2 mirror (see attached pic).
-
First lockloss of 1st Feb may have been related to increased very low frequency (0.01-0.03Hz) motion on ETMY, also observed saturations of the End Y Transmission B QPD. (see attached pics)
-
The 2nd lockloss of 1st Feb was due to TCSy Laser Tripped, IR Sensor Fault. Once resolved, it was followed by yet another TCSy Laser Trip . This may be related to the excess noise of 'ITMY TCS CO2 outofloop ISS' during the day. (see attached pic)
-
Long time duration range drop of 1st Feb after first lockloss (about 15:00 UTC) is clearly due to PI ring up (also mentioned by operator). (see pic)
-
Hveto had one relatively high Significant veto channel before the first lockloss of 1st Feb, with Round 1 winner being H1:ASC-AS_A_RF45_Q_YAW_OUT_DQ (signidicance of 79.38). These glitches are coincident with huge glitches on the main suspension channels 14 secs before lockloss.
-
IMPORTANT: Between the first and 2nd lockloss of 1st Feb there were continues Softwarte saturation of H1:LSC-X_ARM_CTRL.