TITLE: 03/16 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

IFO is LOCKING in INITIAL_ALIGNMENT

An extremely calm shift in which H1 was locked for 9 hours today with one lockloss (cause yet known). Lockloss alog 83401.

I also ran a calibration sweep (alog 83397) since we didn't get to run one yesterday, testing out the new sweep script on the Calibration Measurement Wiki.

LOG:

Lockloss @ 23:06 UTC - link to lockloss tool

No obvious cause, and no real sign of an ETM glitch that I can see either. Starting an initial alignment now.

TITLE: 03/16 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 7mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.41 μm/s
QUICK SUMMARY: H1 has been locked for 9 hours. Calibration sweep was run earlier today, but otherwise sounds like it's been quiet.

• Wind is low, microseism steady just below 95th percentile
• All other systems nominal

Closes FAMIS 26373. Last Checked in Alog 83229

Laser Status:
    NPRO output power is 1.845W
    AMP1 output power is 70.39W
    AMP2 output power is 140.3W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 40 days, 2 hr 27 minutes
    Reflected power = 22.39W
    Transmitted power = 106.6W
    PowerSum = 129.0W

FSS:
    It has been locked for 0 days 9 hr and 26 min
    TPD[V] = 0.8039V

ISS:
    The diffracted power is around 3.5%
    Last saturation event was 0 days 10 hours and 2 minutes ago

Possible Issues: None reported

Calibration sweep was successful! Start and end times for each below (and calibration monitor attached). We are back in OBSERVING

Broadband:

Start: 1426179497

End: 1426179806

2025-03-16 10:03:08,401 bb measurement complete.
2025-03-16 10:03:08,401 bb output: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250316T165757Z.xml
2025-03-16 10:03:08,401 all measurements complete.

Simulines:

Start: 1426180040

End: 1426181443

It is SAFE TO RETURN TO OBSERVING now, whilst data is processed.
2025-03-16 17:29:49,489 | INFO | Commencing data processing.
2025-03-16 17:29:49,489 | INFO | Ending lockloss monitor. This is either due to having completed the measurement, and this functionality being terminated; or because the whole process was aborted.
2025-03-16 17:30:25,376 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250316T170703Z.hdf5
2025-03-16 17:30:25,384 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250316T170703Z.hdf5
2025-03-16 17:30:25,388 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250316T170703Z.hdf5
2025-03-16 17:30:25,393 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250316T170703Z.hdf5
2025-03-16 17:30:25,398 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250316T170703Z.hdf5

Sun Mar 16 10:10:04 2025 INFO: Fill completed in 10min 1secs

TITLE: 03/16 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 19mph Gusts, 13mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.38 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 14:00 UTC (40 min lock)

According to Corey's OWL alog 83394, H1 called Corey for help with SQZ but guardian managed to automatically lock by the time he was set up.

Wind is looking much better than yesterday. Microseism has gone down a bit and leveled off.

As I was trying to get set-up, I could see that H1 was in the INJECT SQUEEZING state (after a lockloss about 3.25hrs ago) .  So I was getting ready to focus on squeezing), but within a minute or two H1 was back to Observing automatically!  Perhaps this was a timer wake up call from being out for so long, because on Verbal, everything looked normal for H1 for the reacquisition.  Going to feed the dog breakfast (and go back to sleep...hopefully).

TITLE: 03/16 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: High winds kept H1 down for the first part of the shift, but they eventually died down enough to allow H1 to relock. After relocking, the SQZ angle servo kept railing, so I have turned it off in case it would cause problems overnight. H1 has been locked for 2 hours.

• 23:30 - Attempting to lock H1 with winds having slightly calmed
• 03:10 - Reached NLN
• SQZ angle servo kept railing, taking H1 in and out of observing four times in total (alog83391)
• 03:39 - Observing with stable SQZ angle servo
• 05:02 - Dropped observing for 30 seconds to load SQZ_MANAGER and SQZ_ANG_ADJUST [Tagging SQZ]
  • Updated sqzparams.py to set use_sqz_ang_adjust to False and nominal state of SQZ_ANG_ADJUST to 'DOWN'
  • Currently set to 166 deg (where the servo last had it)

After 14 hours of downtime, the winds have died down enough to allow H1 to lock and resume observing as of 03:17 UTC. Spent a few extra minutes in OMC_WHITENING to damp down some slightly rung-up violin modes.

As has been happening in the past few lock acquisitions, a few minutes after reaching NLN, the SQZ angle servo railed, so I reset it with SQZ_MANAGER and started observing. Tagging SQZ

...as I was typing this the SQZ angle railed again, so I again reset it. Out of observing for one minute starting at 03:21 UTC.

There was an instance towards the start of a lock stretch overnight where the SQZ angle railed and did not fix itself until 22 minutes later, all while H1 remained observing with BNS range between 40-80 Mpc.

The SQZ angle railed at 08:10:01 UTC, SQZ_MANAGER showed a notification "SQZ angle is out of range. If SQZ looks bad, request RESET_SQZ_ASC_FDS and then FREQ_DEP_SQZ", and the BNS range dropped to around 42 Mpc. At the end of my shift last night, the same thing happened and I was able to reset the angle and return to observing (alog83384), but no one was actively monitoring H1 at this time, so the SQZ angle remained railed at 276.86 deg until it flipped to 0 deg 7 minutes later and the range improved to around 80 Mpc. Then, 13 minutes after that at 08:30:55 UTC, the SQZ angle finally starts moving positive, eventually settling around 180 deg and recovering the BNS range back to about 160 Mpc. The SQZ angle stayed steady for the rest of the lock. The SQZ Guardians did not change states during this time of poor range, and I can't glean from the logs what may have been the issue here.

TITLE: 03/15 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Wind
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

IFO is LOCKING in ENVIRONMENT

IFO is extremely unstable due to the wind, which during the shift has gone between 30mph 50mph. We have been unable to lock all day, and will likely only be able to relock after 5PM local time (forecasted beginning of the end for gusts).

I stayed in IDLE for times where we were incessantly losing lock but tried locking 3 times when there was a slight lull, which got us up to MAX_POWER, before losing lock again due to wind. (Midshift Report Alog 83387).

Attached is the current state of the EY wind fence. The left pane is totally torn and slid to the left side as seen.

Microseism is also on the rise while EQ activity is low.

LOG:

TITLE: 03/15 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Wind
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 32mph Gusts, 16mph 3min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.43 μm/s
QUICK SUMMARY: H1 has been down most of they day due to high winds. Gusts are starting to slowly calm down, so we're attempting to lock now.

• Microseism elevated around 95th percentile
• All other systems nominal

We had a small lull in wind speeds and I was able to get to MAX_POWER, but then it picked back up and we lost lock. If the wind continuiies to increase, I will sit in IDLE again until the wind comes down. Forecast is now showing wind to continue until 18:00 Local Time.

Both LLO and LHO are unlocked so no calibration sweeps have been taken.

Sat Mar 15 10:08:11 2025 INFO: Fill completed in 8min 8secs

TITLE: 03/15 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 45mph Gusts, 31mph 3min avg
    Primary useism: 0.09 μm/s
    Secondary useism: 0.45 μm/s
QUICK SUMMARY:

IFO is LOCKING at INITIAL_ALIGNMENT

H1 was doing an initial alignment when I entered. Wind speeds are extremeley high (50mph), with microseism increasing in the last 8 hours.

We will likely not be able to lock until wind calms down, which is only forecast to happen in a few hours/once wind gets below 30mph.

TITLE: 03/15 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 143Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Mostly quiet shift with one lockloss and a fully automated relock. I also had to reset the SQZ angle when it ran away. H1 has been locked for 20 minutes.

• 23:17 - Observing
• 03:42 - EQ lockloss - alog83382
• 04:46 - Observing
• 04:49 - Dropped observing when SQZ_MANAGER reported the SQZ angle was out of range, so I requested 'RESET_SQZ_ASC_FDS' as directed by the notification then back to 'FREQ_DEP_SQZ' [Tagging SQZ]
  • Before I saw the Guardian notification and I decided to drop observing, DARM looked like SQZ was only injecting noise and range dropped to 70Mpc while still in observing. Would this have stayed like this until someone intervened? Should this be automated to fix this if it happens overnight, even if it means briefly dropping observing?
• 04:51 - Observing

Lockloss @ 03:42 UTC - link to lockloss tool

M5.5 earthquake out of southern Mexico (seismon lists this as nearby Guatemala). Entered earthquake mode one minute before the lockloss, although peakmon only reached up to around 600 counts.