TITLE: 12/26 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 10mph Gusts, 7mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 1.01 μm/s
QUICK SUMMARY:
We are Observing and the detector has been Locked for 7 hours. Microseism is still very high but looks like it might be starting to lower a bit.
TITLE: 12/26 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 22Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
Since I last posted nothing of note has happned here.
Still locked, still Observing.
LOG:
I did a site sweep through the main buildings and took some pictures of the thermostats in the VPW.
STATE of H1: Observing at 154Mpc
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 5mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.94 μm/s
QUICK SUMMARY:
InLock Sus charge measurements likely caused the lockloss this morning. Though there was a PI message at the same time. but the PI didn't seem high enough to break a lock.
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1387641172
Relocking started before 1600UTC.
16:45 UTC NOMINAL_LOW_NOISE reached and OBSERVING at 16:51 UTC
SQZ manager dropped us into commissioning at 17:22 UTC
Back to Observing at 17:24 UTC
N2 truck arrived at Y end around 17:34.
I missed the time that the N2 truck left. I believe it was shortly after 1900 UTC
The Temps in the in the VPW ranged from 66F to 73F. Im not sure what the correct range should be, but the one that read 73 was nearest the warmed server exhaust on that side of the room.
Tue Dec 26 10:04:53 2023 INFO: Fill completed in 4min 49secs
Trip was -60F for this fill, TCmins -63C,-57C
TITLE: 12/26 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.89 μm/s
QUICK SUMMARY:
When I first arrived the IN-Lock Charge measurements were running. I was hoping that it would finish with out locking but it did unlock itself before finishing. Relocking now.
TITLE: 12/26 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: We are Observing and have now been Locked for 14.5 hours.
Very quiet shift, with the only thing happening was that ITMY Mode 20 (aka narrower ITMY Mode 6) had started ringing back up slowly. It seems like during the first two hours that we had been locked, the ITMY 5 gain setting had helped ITMY20 settle down to around 4.06, and then over the next four hours ITMY20 continued decreasing at a lower rate of change from 4.06 -> 3.99. However, after this, ITMY20 started slowly ringing back up, and 4.5hours later was back to being above 4.06. During all of this, ITMY 5, 6, and 10 were still decreasing. I decided to try turning the ITMY5 gain to 0 to see what that would do, but that caused mode 5 to immediately start rising at a much faster rate than mode 20 had been before, so I turned the gain back on and they've all been decreasing again the past 3.5 hours.
LOG:
00:00 Detector Observing and Locked for 6.5hours
Observing at 155Mpc and have been Locked for 10.5 hours. Nothing to report.
TITLE: 12/26 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.85 μm/s
QUICK SUMMARY:
We are Observing and detector has been Locked for 6.5 hours.
TITLE: 12/25 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: We stayed locked for most of the shift, 1 lockloss. Locked and observing for ~6:30 as of 00:00UTC
16:41UTC Lockloss after only 36 minutes, using 'guardctrl log -a "12/25/2023 16:38 UTC" -b "12/25/2023 16:42 UTC" DIAG_SDF' it seems the SQZer lost lock first. Automated relock
Xarm has been locking at higher power than usual, ~1.2
I also set ITMX mode 12s gain and max gain to 0 in lscparams as its been ringing up the past few locks and reloaded ISC_LOCK and VIOLIN_DAMPING.
I did a quick walkthrough of the OSB, Staging building, LSB, and LExC and saw nothing of note.
Mon Dec 25 10:06:01 2023 ALERT: Fill done (errors) in 5min 58sec
TCs started high (31C/34C) so I increased the trip temps before today's fill from -70C to -60C. Despite this, Gerardo had to cancel the fill after it started overflowing, TCmins were -51.5C/-46.5C.
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1387557678, only 36 minutes into the lock
Back into observing at 17:33
TITLE: 12/25 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 2mph Gusts, 1mph 5min avg
Primary useism: 0.07 μm/s
Secondary useism: 0.86 μm/s
QUICK SUMMARY:
Back into NLN at 16:04 and Observing at 16:10UTC
TITLE: 12/25 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: We are Observing and have been Locked for 10 minutes. The lockloss recovery required an Initial Alignment, and while trying to acquire MICH, it was having trouble registering that it was over the threshold because one of the beams was slightly higher than the other, so I needed to adjust the beamsplitter. After that the rest of initial alignment and locking went smoothly.
LOG:
00:00 Detector Observing and Locked for 3.25 hours
05:30 Lockloss (75026)
-- Relocking --
06:03 I took the detector to DOWN because we kept running through CHECK_MICH_FRINGES and needed to run an Initial Alignment
06:08 Started Initial Alignment
- Detector was having trouble with aligning MICH due to the beams being slightly offset in pitch and thus being too low for the trigger - I had to adjust the BS in pitch quite a bit for it to finally catch
07:06 Initial Alignment complete
07:49 Reached NOMINAL_LOW_NOISE
--Relocking End --
07:52 Into Observing
Full DQ shift report is here.
07:52UTC Back Observing
This lockloss, the 12/24 08:34UTC lockloss, and the 12/22 10:59UTC lockloss all have (below threshold) glitches in ETMX right before the locklosses.
Attached is a plot of today's noisy events related to the LN2 delivery to the tank for CP7. Since the IFO was locked flagging the respective groups.
We lost lock during the SETUP step of ESD_EXC_ETMX, plot attached. ETMX_L3_DRIVEALIGN_L2L (bottom right) had an output but I don't think it should have as the feedback is on ITMX at this point and the excitation hadn't started yet. Should check this before next Tuesday.
ESD_EXC_ETMX log before lockloss:
2023-12-26_15:52:32.263999Z ESD_EXC_ETMX [SETUP.main] ezca: H1:SUS-ETMX_L3_DRIVEALIGN_L2L_TRAMP => 1
2023-12-26_15:52:32.264996Z ESD_EXC_ETMX [SETUP.main] ezca: H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN => 1
2023-12-26_15:52:33.394157Z ESD_EXC_ETMX [SETUP.main] ezca: H1:SUS-ETMX_L3_DRIVEALIGN_L2L_SW1S => 0
2023-12-26_15:52:33.645345Z ESD_EXC_ETMX [SETUP.main] ezca: H1:SUS-ETMX_L3_DRIVEALIGN_L2L => ONLY ON: OUTPUT, DECIMATION
Looking at a successful ETMX SETUP state, you can see that there is still a small time where ETMX_L3_DRIVEALIGN_L2L has an output, the IFO just survives the glitch. This happens when the gain is changed from 0 to 1 (to allow excitation through) but before the INPUT is turned off. I've swapped the order of these two lines and added a 1sec sleep between them to make sure that the input is turned off before the gain is ramped to 1. Edit has been saved and will reload during next commisioning period.