TITLE: 06/23 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: One lockloss this shift which took a while to come back from, but overall a fairly quiet evening. H1 has been locked for 1.5 hours.
Lockloss @ 00:59 UTC after almost 23 hours locked - link to lockloss tool
No obvious cause.
TITLE: 06/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 15mph Gusts, 5mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY: H1 has been locked for 19.5 hours and all's quiet.
TITLE: 06/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
A nice very quiet shift! H1 has been humming along (currently at 19.5hr lock), and no intervention was needed during the shift. Breezes have increased slightly through the day.
LOG: n/a
Sun Jun 22 10:09:56 2025 INFO: Fill completed in 9min 52secs
TITLE: 06/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 2mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.11 μm/s
QUICK SUMMARY:
H1's been locked for almost 12.5hrs and it looks like we had a brief outage from Observing due to the SQZ dropping us out just before 1300utc/6amPDT, but SQZ MANAGER and H1 got back to OBSERVING automatically within a 5min (coincidentally, this improved the H1 Range [which had been drifting down below 150Mpc] getting it back to above 150Mpc.
Environmentally, we are doing well; useism had been above the 50th percentile and has been drifting down from this for the last 10hrs. Winds are low and it is a cloudy and cool morning.
TITLE: 06/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: One lockloss this evening after a very short observing segment followed by an automatic relock; quiet shift otherwise. H1 has been locked and observing for almost 3 hours.
Lockloss @ 00:23 UTC after just 4 minutes of observing - link to lockloss tool
No obvious cause, but maybe a very small ETM glitch? The lockloss tool tags wind, which was getting up to about 30mph at the time.
Back to observing at 02:10 UTC. Fully automatic relock, but there was a lockloss at DRMI and it was taking a long time to catch after.
TITLE: 06/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
LOG:
TITLE: 06/21 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: EARTHQUAKE
Wind: 18mph Gusts, 7mph 3min avg
Primary useism: 0.18 μm/s
Secondary useism: 0.17 μm/s
QUICK SUMMARY: H1 is recovering from a recent earthquake and has just started an initial alignment.
Almost thought there was a chance we were going to ride through this earthquake (L1 went down 14 min before us), but alas the ground motion was too much for H1 and caused a lockloss. This ended a nearly 6.5hr lock for today's shift. Observatory Mode is in the EARTHQUAKE state until we get back to NLN. Will Stay in Prep For Locking for atleast 30more min.
Back to observing at 00:19 UTC. Fully automated relock after a fully automated initial alignment.
After returing to Observing for about 18min post-Saturday-Calibration, noticed that the DARM FOM trace was above reference at high frequency (+ "H1 Live" trace on nuc33 was also above the reference). Consulted the Troubleshooting SQZ wiki, dropped out of Observing, and did the following:
These adjustments had H1 out of Observing from 1917-1922utc. It has now been 10min, and it is looking like I have made the range worse (looking like range is ~15Mpc worse). Will give it more time and see how it goes while I grab lunch.
Vicky got back to me on Mattermost. She suggested running another SCAN SQZANG (because of the OPO adjustment). Went out of observing again to do that, and that restored our range. DARM FOM is still better, but H1-Live on nuc33 is still high...it might be a little lower since my first SQZ adjustments. At any rate, back to Observing.
Measurement NOTES:
Attached is a screenshot of the Calibration Monitor + pdf of Pydarm Report
Sat Jun 21 10:10:09 2025 INFO: Fill completed in 10min 5secs
H1 is back to Observing. As noted earlier, took the opportunity to take care of some housekeeping tasks:
Next uip: Take the Saturday Morning Calibration in about 2.5hrs *knock on wood*
Per Elenna's alog85200 yesterday + RyanS's subentry (with updated INIT ALIGN), Ran a 2nd INITIAL ALIGNMENT this morning for two reasons (to (1) enact Ryan's changes with a RELOAD of INIT ALIGN, and (2) to let the BS chill for about 65min).
Looks like the PRC ALIGN OFFLOADED worked fine as Elenna notes (see attached IR signals during alignment.
Back to observing at 03:45 UTC.
As has been the norm recently, D/PRMI took a very long time to catch despite good alignment and buildups. There were also a few low-state locklosses due to the ALS-X PLL beatnote having an error, which would then take a few minutes to fix itself, so with everything together this was a lengthy relock (but I did not need to run an alignment; just some slight adjustments of PRM and BS).
After reaching low noise, SQZ couldn't lock because the SHG PZT voltage was low at around 3.4V and Guardian would not proceed. Relocking the SHG did not seem to move the PZT to a better place, so I simply lowered the minimum SHG PZT voltage threshold in SQZ_MANAGER from 5 to 3 and loaded the Guardian. After that, the SQZ_SHG Guardian is still giving a warning about the PZT voltage being low, but SQZ_MANAGER was able to make it to 'FRED_DEP_SQZ' and otherwise things looked okay, so I took H1 into observing. This may need to be reverted or addressed properly tomorrow. [Tagging SQZ]