TITLE: 09/30 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Reacquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Trying to relock and at LOCKING_ALS. Relocking from the previous lockloss wasn't too bad so hopefully this relocking goes smoothly as well. We had superevent candidate S240930aa during my shift!
LOG:
23:00UTC Observing and have been Locked for 2 hours
23:32 Lockloss
00:09 Started an initial alignment after cycling through CHECK_MICH_FRINGES
00:47 Initial alignment done, relocking
01:28 NOMINAL_LOW_NOISE
01:32 Observing
04:00 Superevent S240930aa
04:54 Lockloss
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
21:43 | PEM | Robert | Y-arm | n | Testing equipment | 23:33 |
We went out of Observing at 04:53:56, and then lost lock four seconds later at 04:54:01.
TITLE: 09/29 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Oli
SHIFT SUMMARY: H1 was locked this morning until winds picked up, which kept it down through midday. Was able to get relocked this afternoon, but we just had another lockloss as I'm drafting this log.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
23:58 | SAF | H1 | LVEA | YES | LVEA is laser HAZARD | Ongoing |
17:01 | PEM | Robert | Y-arm | n | Testing equipment | 18:34 |
21:43 | PEM | Robert | Y-arm | n | Testing equipment | Ongoing |
Lockloss @ 09/29 23:32UTC. Ryan S and I had been watching the FSS channels glitching but Ryan closed them literally seconds before the lockloss happened so not sure yet if it was the FSS but we think it might've been. Wind is also above 30mph and increasing so could've been that too
Even though the wind was (just a bit) over threshold, it definitely looks like the FSS (green, lower right) was the cause of the lockloss
09/30 01:30UTC Observing
TITLE: 09/29 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 27mph Gusts, 16mph 3min avg
Primary useism: 0.10 μm/s
Secondary useism: 0.15 μm/s
QUICK SUMMARY:
Observing at 150Mpc and have been Locked for 2 hours. Winds are still above 25mph but microseism is getting lower.
Since the lockloss at earlier this morning, high winds up to 40mph have made locking H1 problematic; on occasion we can lock DRMI, but rarely. Unfortunately, the forecast says these winds will stick around for most of today.
Lockloss @ 16:51 UTC - link to lockloss tool
Cause looks to me to be from high winds; gusts just hit up to 40mph and suspensions were moving right before the lockloss in a familiar way.
H1 back to observing at 21:09 UTC. After a few hours, thanks to a lull in the wind, H1 was able to get relocked. Fully automatic acquisition.
Sun Sep 29 08:11:15 2024 INFO: Fill completed in 11min 11secs
TITLE: 09/29 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 17mph Gusts, 10mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.16 μm/s
QUICK SUMMARY: H1 appears to have unlocked around an hour ago and is currently relocking up to INJECT_SQUEEZING. Four locklosses in total overnight; I'll start looking into them shortly.
TITLE: 09/29 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Observing at 155Mpc and have been Locked for 9 hours. We've been Locked my entire shift so it's been a quiet evening. Didn't get a chance to take today's calibration measurements because Virgo and Livingston stayed nice and locked.
LOG:
23:00 Observing and have been Locked for 3 hours
Closes FAMIS#26447, last checked 79824
Driftmon plots, auxiliary plots
Everything is looking good. BRSX is close-ish to the lower threshold after the latest picomotor move (80269) but looks to be staying level.
First spike on BRSX plot is pico work from September 19th (80183)
Second spike on BRSX plot is pico work from September 24th (80269)
Observing at 150Mpc and have been Locked for 7 hours now. It's been a quiet evening.
Closes FAMIS#26331, last checked 80086
Note: I'm trending them back two weeks since last week the check wasn't able to be done.
Corner Station Fans (attachment1)
- All fans are looking normal and within range.
Outbuilding Fans (attachment2)
- All fans are looking normal and within range.
TITLE: 09/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Mostly quiet shift with just one lockloss and an easy reacquisition. Because of the lockloss, however, we did not get the usual calibration sweeps done today.
H1 has now been locked and observing for 3 hours.
TITLE: 09/28 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 7mph Gusts, 4mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.24 μm/s
QUICK SUMMARY:
Currently Observing at 155Mpc and have been Locked for 3 hours. Microseism is trending back down and winds are low.
Lockloss @ 18:58 UTC - link to lockloss tool
No obvious cause, but the lockloss tool gave this the FSS_OSCILLATION tag. This happened two minutes before I was planning on running the scheduled calibration sweeps.
H1 back to observing at 20:04 UTC. Fully automated relock without an initial alignment.
It looks like the reason for dropping observing at 04:53:56 UTC (four seconds before lockloss) was due to the SQZ PMC PZT exceeding its voltage limit, so it unlocked and Guardian attempted to bring things back up. This has happened several times before, where Guardian is usually successful in bringing things back and H1 returns to observing within minutes, so I'm not convinced this is the cause of the lockloss.
However, when looking at Guardian logs around this time, I noticed one of the first things that could indicate a cause for a lockloss was from the IMC_LOCK Guardian, where at 04:54:00 UTC it reported "1st loop is saturated" and opened the ISS second loop. While this process was happening over the course of several milliseconds, the lockloss occurred. Indeed, it seems the drive to the ISS AOM and the secondloop output suddenly dropped right before the first loop opened, but I don't notice a significant change in the diffracted power at this time (see attached screenshot). Unsure as of yet why this would've happened to cause this lockloss.
Other than the ISS, I don't notice any other obvious cause for this lockloss.
After comparing Ryan's channels to darm, still not sure whether this lockloss was caused by something in the PSL or not, see attached