TITLE: 09/29 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Locked for 5 hours. The relock had an odd SRM M3 Wd trip during DRMI acquisition, but once untriped it went through Mich Bright, then PRMI, then it got DRMI. 
LOG:

• 2235 Lock loss
• 0005 Observing
• 0027 S250929c
•  

Looks like when one of the triggers for SRCL turned on, it tripped M3 a handful of seconds later. Another odd thing I'm seeing after I've untripped and tried PRMI is that the triggering seems to be turning on and off rapidly.

1443133532

Nothing obvious.

TITLE: 09/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Quiet shift, we stayed locked the entire time.
LOG: N/A

The LSC front end has an FPU (floating point unit) error. The recent range drop post glitch looks to line up with a ~50 SNR low frequency glitch as seen on the Omicron plot on nuc27, and 2.5 hours ago there's some extra noise in the low frequency SQZ blrms. The recent glitch look to be from  =< 450Hz, as it's seen only in BAND_1-5.

• 13:16 UTC Observing

TITLE: 09/28 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 4mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.39 μm/s 
QUICK SUMMARY: Locked for almost 7 hours, calm environment.

Sun Sep 28 10:10:39 2025 INFO: Fill completed in 10min 35secs

TITLE: 09/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 7mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.35 μm/s 
QUICK SUMMARY:

• We've been locked for just over an hour
  • 13:!6 UTC Observing

Got called at 4:50 due to a mysterious SRM trip at 4:47 AM. IFO was in SRC ALIGN for initial alignment and SRM was railing during PREP_FOR_SRY. ST2 and ST3 sus tripped, which makes me think that initial alignment may have caused it? Microseism is on the rise but nothing jumps at me otherwise (attached).

Either way, I untripped it and waited until IFO got to DRMI which it just did. Flashes look good. Will continue light monitoring but I think guardia can take it from here.

Reset myself as the OWL.

TITLE: 09/28 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Quiet shift, locked for 5 hours. Range is much more stable than the last lock and up a few Mpc.
LOG:

• 2353 Observing

TITLE: 09/28 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 4mph Gusts, 1mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.33 μm/s 
QUICK SUMMARY: Just got back to observing after a 31 hour lock. 

Relocking took a bit longer due to an earthquake off of the coast of oregon rolling through. The only thing of note was that I changed the threshold in ALIGN_IFO for the MICH Bright convergence checker from 1.5 to 2. This average convergence checker I've seen take longer then it should so I wanted to try to speed it up a bit.

TITLE: 09/27 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY: The SQZer struggled a little before and during the calibration measurement, 1 lockloss that we are still recovering from (move spots as of 23:30).
LOG:                                                                                                                       

• 15:25 UTC Superevent S250927ck
• 17:31 UTC Superevent S250927cy
• 18:22 UTC Dropped Observing from the SQZ LO losing lock and struggled to relock alog87175
• 19:23 UTC  CAL measurement
  • 19:33 UTC More SQZ issues
• 19:53 UTC Observing
• 21:34 UTC lockloss
• 22:16 - 22:28 UTC earthquake mode, 5.2 from Oregon cascadian subduction zone. (We didn't see it on seismon or usgs until after it hit)
• 22:39 UTC Initial alignment

FAMIS26688

The EX fan2 is starting to get noisy. EY fan 1 is also starting to see some extra noise during the night (see the green trace on attachment 2).

Corner station and other outbuildings look good.

FAMIS26666

A few known blips from the power outage and the corrupted frames (alog86985), but it also looks like the temperature changed in both BRSs this week. I don't see any alogs on this, but it does seem to be putting it in the correct direction, leading me to think this was done by someone.

Other than that, the drift looks good.

Yesterday Gerardo instructed my to plug in the ion pump that's on top of HAM5 if we have a lock loss. The plug and recepticle are located on the NW corner of HAM5. Turning on the ion pump will help transition off of the carts that are pumping there sooner than waiting until a weekday.

21:34 UTC lockloss

• 18:22 The SQZ LO lost lock and struggled to relock and delayed the start of the calibration measurement
  • The first issue was the OPO not wanting to lock, following the wiki I started by cycling through DOWN
    • I restored FC2/FC1 alignments based on osems to when we locked the SQZer at the beginning of the lock, no dice
    • I maximized the H1:SQZ-SHG_GR_DC_POWERMON using  SHG_TEC_SETTEMP, accepted in SDF (36.05 -> 35.75)
    • It was still struggling to get a trans of at least 80, it would go right past it. It would get just over 80 then keep adjusting the ISS setpoint and the trans would decrease. I ended up changing the setpoint from 80 to 75 in sqzparams which got it locked.
  • Now the FC won't lock, the green trans is too low, I followed the wiki to maximize it
    • Restored ZM3, moved FC2 to maximize H1:SQZ-FC_TRANS_C_LF_OUTPUT, I couldn't get it above 50. Now it loses it at IR ("CLF frequency out of range")
    • I ran the SCAN_OPO_TEMP state and now it can lock IR
• 19:33 during the calibration measurement it lost lock again
  • The OPO keeps losing lock again. I maximized the SHG temp again, there was a suprising amount of gains still to be had (36.05 -> 35.05). Should I have done this again after running SCAN_OPO_TEMP earlier?
  • FCs not locking again, as soon as the calibration measurement finished it finally was able to hold green lock

We have been locked for around 29 hours at the start of the measurement.

Broadband:

Start: 2025-09-27 19:23:09 UTC

Stop: 2025-09-27 12:28:20 UTC

Files: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250927T192309Z.xml
 

Simulines: The SQZer lost lock in the middle of this at 19:33, and wasn't able to relock until the measurement completed.

Start: 2025-09-27 19:28:45 UTC // 1443036543.471832 GPS

Stop: 2025-09-27 19:52 UTC // 1443037941.223046 GPS
Files:

2025-09-27 19:52:03,067 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250927T192846Z.hdf5
2025-09-27 19:52:03,076 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250927T192846Z.hdf5
2025-09-27 19:52:03,081 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250927T192846Z.hdf5
2025-09-27 19:52:03,085 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250927T192846Z.hdf5
2025-09-27 19:52:03,089 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250927T192846Z.hdf5