TITLE: 02/02 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 1mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.45 μm/s
QUICK SUMMARY:

IFO is at NLN as of 12:44 UTC

SQZ is failing to lock FC per Tony's OWL alog. I am investigtaing now.

TITLE: 02/02 Owl Shift: 0600-1530 UTC (2200-0730 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.37 μm/s
QUICK SUMMARY:
I got a call to help H1 get relocked. When I logged in to start helping we were in POWER_10W.
Once we reached NOMINAL_LOW_NOISE ... we lost lock before Observing can be reached.
Once H1 Got past DRMI_1F I tried to get some Z's.

Allowing the H1 some time to relock, once it got back to Nominal_low_noise again the SQZ manager was stuck on beam diverter step, and hence H1 Called me back.

After poking around and trying to recreate my steps last time this happened: alog 82192

I started reading the troubleshhoting guide for SQZ: https://cdswiki.ligo-wa.caltech.edu/wiki/Troubleshooting%20SQZ

I tried to request FDS_READY_IFO[50] and miss clicked  [52]  Which changed the alignment of the FC2 mirrors and ZM4. [Not any other ZM mirrors!] 

Since then: I was able to narrow down the problem to the SQZ_FC not locking anymore. Likely because the ZM3 mirrors have now been moved.
 

TITLE: 02/02 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Largely uneventful shift with one lockloss and a somewhat lengthy relock. Wind hasn't been too bad and microseism is steady. H1 has now been locked for just over 2 hours.

• 02:03 - Lockloss; alog82582
  • Lockloss during CARM_OFFSET_REDUCTION (ETMX saturations started at DARM_TO_RF)
• 03:53 - Observing

Lockloss @ 02:03 UTC - link to lockloss tool

No obvious cause, but there's an ETMX glitch immediately prior. End lock stretch at 16.5 hours.

TITLE: 02/02 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 09:29 UTC (15 hr lock!) with a two drops from OBSERVING

OBS Drop 1: Planned Saturday Calibration Sweep - alog 82579 - CALIBRATION from 19:32 to 20:15 UTC (~45 mins)

OBS Drop 2: SQZ opo lockloss - PREVENTATIVE MAINTENANCE from 21:51 to 23:31 UTC (~1hr 40 mins). Details below.

Troubleshooting with Camilla and Sheila led to the same conclusion that the SHG power was too low. Sheila determined that it was as high as it could go but tuning the SHG temperature gave it some extra power, which is ultimately what allowed SQZ-OPO CONTROLMON signal to get back to a lockable number. This will likely need to be readjusted since it is slowly going down in counts if the opo/sqz have issues locking (though may have leveled out check screenshot). The instructions are: Sitemap -> SQZ -> SQZT0 -> Colorful SHG Box -> Set Temperature and such that H1:SQZ-SHG_GR_DC_POWERMON is maximized in counts (picture below of Sheila's adjustments). Accepted SHG temp change SDF attached.

Other SQZ Adjustments:

• Sheila adjusted the polarization into the SHG fiber.
• amilla and I adjusted the start voltage of the OPO Voltage scan under the idea that this may be too narrow of a scan for the opo locking threshold but this did not work. I later reverted it.
• Prior to the calling SQZ experts, I also adjusted the opo temp slightly to no avail. I also adjusted the SQZ phase but then reverted the change.

Other: the H2 building had a temperature excursion overnight that prompted Dave to troubleshoot with me first remotely and then in-person. He came on site to see the issue with the HVAC not keeping the temperature low (set point was 67 but temp went all the way to over 80). Since power cycling failed, Jonathan and Dave agreed to turn off non-essential computers and electronics until they can more thoroughly investigate the issue during the week. I've attacched the H2 Building Environment medm which shows the temperature peaking at 85F before electronics were turned off and thermostats power cycled. The blue trace shoes the air flow failing to correctly adjust with the temperature and the red trace shows the temperature.

LOG:

None

TITLE: 02/02 Eve Shift: 0030-0600 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: 21mph Gusts, 14mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.39 μm/s
QUICK SUMMARY: H1 has been locked for 14.5 hours.

• Wind is moderately high, secondary microseism steady for the past day around the 95th percentile

Planned Saturday Calibration sweep done using the usual wiki.

Broadband Start Time: 1422473671

Broadband End Time: 1422473990

Simulines Start Time: 1422474640

Simulines End Time: 1422476061

Files Saved:

2025-02-01 20:13:26,497 | 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-02-01 20:14:03,332 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250201T195022Z.hdf5
2025-02-01 20:14:03,340 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250201T195022Z.hdf5
2025-02-01 20:14:03,345 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250201T195022Z.hdf5
2025-02-01 20:14:03,350 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250201T195022Z.hdf5
2025-02-01 20:14:03,355 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250201T195022Z.hdf5
ICE default IO error handler doing an exit(), pid = 2441668, errno = 32

Sat Feb 01 10:16:34 2025 INFO: Fill completed in 16min 30secs

TCmins [-110C, -84C] OAT (7C, 44F) DeltaTempTime 10:16:45

TITLE: 02/01 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.37 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 09:29 UTC

Dust in PSL and EX slightly elevated, which is expected after yesterday's >40mph winds. Will continue monitoring.

TITLE: 02/01 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Windy evening which has kept H1 down for a good portion of the shift with many unsuccessful locking attempts, including one from TRANSITION_FROM_ETMX. H1 is still relocking, so far completely automatically, currently up to DRMI. Fortunately, the wind has started to calm down a bit.

• 00:02 - Starting initial alignment
• 00:21 - IA finished, starting lock acquisition
• 01:17 - Observing
• 03:03 - Lockloss (likely from wind; alog82575)
  • Several low-state locklosses from high winds and previously reported ALS issues
  • Lockloss in CARM_OFFSET_REDUCTION; ETMX saturations started at DHARD_WFS
  • Lockloss at end of TRANSITION_FROM_ETMX; known vulnerability here during high ground motion

Lockloss @ 03:03 UTC - link to lockloss tool

Very likely due to wind; gusts have hit up to 40mph and swarms of tumbleweeds are blowing outside. Range had been dropping as many ASC signals were oscillating more as the wind got worse.

FAMIS 26451, last checked in alog82034

Things looks good and generally stable since the last check.

FAMIS 26357, last checked in alog82452

Fans were switched at EX, EY, MX, and the mechanical room 3 days ago. All fans now in operation look to be behaving and within acceptable noise limits (MR fan 2 was noisy for a couple days after being switched on, but has since calmed down).

TITLE: 02/01 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

IFO is in LOCKING in ACQUIRE_PRMI

Two locklosses today:

One due to ETM Glitch - alog 82566

One due to EQ - alog 82567

Otherwise, calm shift.

LOG:

None

TITLE: 01/31 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 13mph 3min avg
    Primary useism: 0.10 μm/s
    Secondary useism: 0.56 μm/s
QUICK SUMMARY: H1 just recently lost lock from a M5.5 EQ out of Ecuador and relocking will start soon.

• Wind moderately low, secondary microseism elevated around 95th percentile

Earthquake caused Lockloss (5.5 from Ecuador). While we would usually survive this, high microseism meant we were mor susceptible.

Mayank, Sheila, Jennie W, Ryan S, Elenna, Jenne, Camilla, Robert.

Follow on from 82401, mostly copied Jenne's 77968. 

As soon as we started setup, the IFO unlocked from an EQ and we decided to do this with the IFO unlocked.

Ryan locked green arms in initial alignment and offloaded. Took ISC_LOCK to PR2_SPOT_MOVE (when you move PR3 it calculates and moves PR2, PRM and IM4).  

Green beatnotes were low but improved when we started moving. Steps taken: Move PR3 Yaw with sliders until ALS_C_COMM_A beatnote decreased to ~-14 and then used pico A_8_X to bring it back. Repeated until PR3 M1 pitch was 1-2urad off and then Mayank brought back pitch with PR3 sliders. Repeated moving PR3 yaw sliders and picos. 

Started with PR3 (Pitch,Yaw) at (-122, 96), went to (-125.9, 39.5), were aiming for Yaw at -34. But, at (-124, 68) we lost the beam on AS_AIR, whoops.

Once we realized that we fell off AS_AIR so took PR3 back to last time we had light on it (68urad in yaw slider), ignoring green arms with the plan of moving back to 38urad by moving SR2 to keep light on AS_AIR.  Moved SR2 in single bounce (ITMY misaligned)  to increase light on AS_AIR. We couldn’t go any further in PR3 yaw with keeping light on AS AIR so we decided to revert green picos to work with 68urad on PR3. WE took PR3 back to (-125.9, 39.5) and  reversed our steps of sliders and picos. 

After we got here, Ryan offloaded green arms and we tried to go to initial alignment. No flashes on init align in X arm or y-arm (touched BS for y-arm). We would usually be able to improve alignment while watching AS_AIR but the beam wasn’t clearly on AS_AIR. Improved beam on AS_AIR by moving SR2/3.

Ran SR2 align in ALIGN_IFO GRD. This seemed to make some clipping worse, are we clipping in SR2? Still working on SR2 alignment. Maybe we should update the ISC_LOCK  PR2_SPOT_MOVE state to have SR2/3 follow align so that we don't loose AS_C and AS_AIR. 

Sheila, Mayank

We wanted to double check the calibration of IM4 trans into power on PRM, similar to 63812 and 62213

• 10 Watts, single bounce ITMY 16:24 UTC
• OMC locked 16:35 UTC.  Sensor correction was off so this alignment is wobbling more than it otherwise would. 
• sensor correction on 16:40 UTC - 16:45 UTC.  1420908058 for 300 seconds
• IM4 trans and AS_C whitening gains were 18dB at the time of this measurement. 
• Medians:
  • H1:IMC-IM4_TRANS_NSUM_OUT16 9.855005
  • H1:IMC-PWR_IN_OUT16 9.997126
  • H1:ASC-AS_C_SUM_OUT16 0.007815647
  • H1:OMC-DCPD_SUM_OUT16 15.558
• Using Craig's code here to get all the optic transmissions (he cites where the numbers came from at the top of the file), we expect 0.244% of the power incident on PRM to reach HAM6 in single bounce. 
• If we continue to trust the calibration of AS_C, and the known transmissions that Craig collected, we would apply a correction of 0.9566 to IM4 trans.