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.

• 23:00 - Running initial alignment
• 23:20 - Starting lock acquisition
• 00:19 - Observing
• 00:23 - Lockloss - alog85225
• 02:10 - Observing

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.

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:

• 1420 ISC LOCK & INIT ALIGN loaded
• 1423-1439 INITIAL ALIGNMENT started for a 2nd time but with reloaded init align
• 1440 LOCKING  (60W at about 1526---paving way for thermalized h1 for calibration at 1830utc)
• 1541 back to OBSERVING
• 1830-1859 Saturday Calibration
• 1917-1919 and 1949-1956:  Out for Sqz Adjustments afterr noticing H1-Live channel was higher than reference (Vicky helped me get through this).
• 2202 Lockloss due to M6.1 EQ @Japan (this was preceded by EQ alarms on Verbal and EQ Mode toggled between states a few times)
• 2300-2321 Initial Alignment 

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.

• Wind is low, microseism on the rise but still low
• All other systems nominal

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.

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:

1. Ran SCAN_SQZANG_FDS:  This made DARM FOM look better (back at reference for high frequency, but it was still higher for the "H1 Live" trace on nuc33).
2. Adjusted OPO Temperature:  Able to increase H1:SQZ-CLF_REFL_RF6_ABS_OUTPUT a bit (see attached), but still higher for the "H1 Live" trace on nuc33.  Then returned to Observing.

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.

Measurement NOTES:

• Posted heads up reminder for the Sat Morning Calibration on the IGWN channel on Mattermost.
• Following instructions (link)
• H1 at NLN for for almost 2hrs55min (over 3hrs at 60W).
• Calibration_Monitor medm screenshot is attached
• 1830-1859 utc Out of Observing for CALIBRATION
•  Broadband measurement started at 1434565843.086414 (18:30:25utc)
  • Measurement at:  /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250621T183025Z.xml
•  Simullines measurement
  • gps START time:  1434566163.985407 (18:35:45utc)
  • gps STOP time: 1434567563.816039 (18:59:95utc)
  •  File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250621T183546Z.hdf5
  • File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250621T183546Z.hdf5
  • File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250621T183546Z.hdf5
  • File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250621T183546Z.hdf5
  • File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/
• 1859 ISC_LOCK taken back to NLN for observing

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:

• Timing allowed for a 2nd alignment to happen at a time when the BS was cooled off over an hour.
• Alignment above happened after INIT ALIGN was reloaded (to get PRC ALIGN OFFLOADED back into INITIAL ALIGNMENT).
• ISC LOCK was also LOADed.
• DRMI locked up fairly smoothly and automatically.
• H1 hit 60 wats at 1526utc
• Had (2) SDFs diffs (for "H1:LSC-REFL_SUM_{A,B}_IN2GAIN") in CS_ISC related to what Elenna mentions in alog 85206.  These were ACCEPTED (see attached).

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.

TITLE: 06/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

Walked in to see H1 down from a lockloss at 1317utc.  It had a 16.5+hr lock (no obvious culprits for the lockloss).  I am in a little early, but was too late to:

• Prevent ISC_LOCK from automatically going into an alignment with a "hot-ish" BS....so another alignment may be needed.  But the alignment did start 45min after the lockloss at 1403utc, so maybe our BS is cooled.
  • And looks like PRC ALIGN OFFLOADED was skipped due to INIT ALIGN (needing a LOAD).
  • I'm thinking, I might just do another complete INITIAL ALIGNMENT with a reloaded INIT ALIGN.
• And to RELOAD:  ISCLOCK & INITALIGN

TITLE: 06/21 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Very quiet evening where H1 was observing throughout; current lock stretch is up to just over 8 hours.

• High frequency BLRMs (and DARM) were slowly getting worse over the first few hours of the lock, but have since leveled out (this didn't seem to affect inspiral range much)
• Wind speeds have been coming down for the last couple hours and the forecast for the night looks favorable
• Since we've been observing, I haven't had a chance to load ISC_LOCK and INIT_ALIGN, so that'll have to be done tomorrow

TITLE: 06/20 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

Today's main activity was supposed to be a Commissioning Time (from 8am-2pm (PDT) [1500-2100utc]), but with a lockloss near the start, much of the commissioing time was focused on troubleshooting for locking issues with DRMI and also ALS (some commissioning tasks happened at the beginning & end of today's Commissioning Period of 8am-2pm (PDT) [1500-2100utc].

ALSO A New NOTE for Operators: 

1. It looks like we can now run the usual INITIAL_ALIGNMENT (vs MANUAL_ALIGNMENT), because for IFO_ALIGN, the PRC_ALIGN_OFFLOADED state now looks good (see Elenna's alog85200).  However, Sheila noted, we should be mindful of the BS heating (Camilla's alog84922).  In other words, we should run alignments about 30min after a lockloss (or even 60min)---to allow the BS time to cool down and return to its "nominal" pointing at the beginning of locks.
2. Elenna has some changes in ISC_LOCK, so after the next lockloss, we'll need to run a LOAD of ISC_LOCK and ACCEPT the SDF Diffs which come up (see Elenna's alog85207).

VAC Note:  There were hopes we could turn OFF the HAM1 Pump, but there is a pressure we need to get below before we can do this, and we were not there today.  Travis mentioned it will have to wait until Monday.
LOG:

• 1510 Commmissioning begins (sheila)
  • Sheila starts with running Jennie's DARM offset step script.  Then Keith Kuns@MIT and Sheila will run a measurement using the Squeezer to check H1 mode matching via the ADF (Audio Diagnostic Field).
• 1528 LOCKLOSS (this was just after Keith started his SQZ measurement--which we don't think was the reason for the lockloss; bad timing H1)
• LOCKING notes:  Letting H1 try to lock on its own
  • Y-arm did a Scan Alignment
  • DRMI didn't look great, so I went for CHECK FRINGES + PRMI
  • 1602-1622  Manual Initial Alignment (PRM tweaked to get AS_A up to 1.32 (from 1.28))
  • For DRMI, it looked better post-alignment, BUT after 11min, GRD took to PRMI.
    • 1640 Sheila running a check at PRMI_ASC but no change made; after this DRMI locked, but had lockloss at ENGAGE ASC as the PR Gain rung up before the lockloss.
  • For next locking attempt hold at DRMI LOCKED PREP ASC
    • Although the X-arm was locked above 1, it was taken to a SCAN ALIGNMENT which was odd.
• 1617-1629 H2 Room cleaning (kim, nellie)
• 1625 Setting up measurement in PCal Lab (francisco)
• 1630 Receiving roll-up opened (for cardboard) (kim)
• 1708-1714 Connecting cable to CM board at racks (sheila, matt)
• 1802-1819 Parts check in lvea (mitch)
• 1804 3IFO checks (betsy, suresh, LIGO visitors)
• 1820-1837 Running another Manual Alignment 
  • PRC ALIGN OFFLOADED  looks it works---Elenna checked it out during this alignment:  So we should be able to run the standard INITIAL_ALIGNMENT
• MORE Locking Notes:  Had several more locklosses during the commissioining time---due to ALS & ENGAGE ASC for FULL IFO.  Focus switched to troubleshooting the ALS locking, DRMI locking, and getting through ENGAGE ASC. 
  • 2046 H1 finally back to NOMINAL LOW NOISE.  Elenna was able run a measurement once we were back to NLN & once she was done, she disconnected the SR560 out on the floor and disconnected it from the racks and then turned out the LVEA lights.
• 1930 ISS array work in the optics lab (keita, rahul)
• 1957-2005 Checking shutters in Pcal Lab (francisco)
• 2115 Back to OBSERVING

TITLE: 06/20 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 141Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 28mph Gusts, 14mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: H1 has been locked for over 2 hours.

• Will load ISC_LOCK when next out of observing - alog85207
• Wind speeds have been rising, microseism low
• All other systems nominal

While Corey ran an initial alignment, I went to PREP_PRC_ALIGN to check the WFS error signal for that state. Both pitch and yaw looked good, I confirmed the signals cross zero when expected, and so I turned on the PRC ALIGN state and the initial alignment engaged and offloaded properly. Seems like we can use PRC align now!

I tagged OpsInfo so operators know. I recommend that the operators just pay attention during PRC Align over the next few days just to ensure nothing is going wrong (watch build ups as the ASC engages and confirm it's going in the right direction).

Headless Start: 1434382652

2025-06-19 08:42:24,391 bb measurement complete.
2025-06-19 08:42:24,391 bb output: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250619T153714Z.xml
2025-06-19 08:42:24,392 all measurements complete.
Headless End: 1434382962

Simulines Start: 1434383042

2025-06-19 15:55:14,510 | INFO | Drive, on L3_SUSETMX_iEXC2DARMTF, at frequency: 8.99, and amplitude 0.53965, is finished. GPS start and end time stamps: 1434383704, 1434383727
2025-06-19 15:55:14,510 | INFO | Scanning frequency 10.11 in Scan : L3_SUSETMX_iEXC2DARMTF on PID: 2067315
2025-06-19 15:55:14,511 | INFO | Drive, on L3_SUSETMX_iEXC2DARMTF, at frequency: 10.11, is now running for 28 seconds.
2025-06-19 15:55:17,845 | ERROR | IFO not in Low Noise state, Sending Interrupts to excitations and main thread.
2025-06-19 15:55:17,846 | ERROR | Ramping Down Excitation on channel H1:LSC-DARM1_EXC
2025-06-19 15:55:17,846 | ERROR | Ramping Down Excitation on channel H1:SUS-ETMX_L2_CAL_EXC
2025-06-19 15:55:17,846 | ERROR | Ramping Down Excitation on channel H1:SUS-ETMX_L3_CAL_EXC
2025-06-19 15:55:17,846 | ERROR | Ramping Down Excitation on channel H1:CAL-PCALY_SWEPT_SINE_EXC
2025-06-19 15:55:17,846 | ERROR | Ramping Down Excitation on channel H1:SUS-ETMX_L1_CAL_EXC
2025-06-19 15:55:17,846 | ERROR | Aborting main thread and Data recording, if any. Cleaning up temporary file structure.
PDT: 2025-06-19 08:55:22.252424 PDT
UTC: 2025-06-19 15:55:22.252424 UTC
Simulines End GPS: 1434383740.252424

Could not generate a report using the wiki instructions (probably due to incomplete sweep).