Workstations updated and rebooted. This was an os-packages update.  Conda packages were not updated.

Called again due to SQZ being unlocked, keeping us out of Observing. SQZ MANAGER was stuck in LOCK_LO_FDS with the message "Beam diverter is open but no 3MHz on OMC, could be an alignment problem". Referencing my alog 82039 from December (I realized after that I should've also been looking to maximize H1:SQZ-OMC_TRANS_RF3_DEMOD_RFMON while adjusting sliders) when Vicky helped fix this issue, I trended back ZM4 and ZM6 and noticed that they had moved a lot in the past  day. I picked the time 2025-06-30 20:30:15 UTC as my driftmon reference time since the squeezer had been locked then and the pointing looked like it was the most consistant with the past few days. I took SQZ_MANAGER to NO_SQUEEZING, then adjusted the sliders for ZM4 and ZM6 until they were pointing in the same way, and we were able to lock wtihout issue.

I got called for the same issue that Tony and Sheila had earlier today where the SHG PZT hit its voltage limit. I followed the very clear instructions given in that alog and just adjusted the PZT slider, and we were able to lock the SHG. I accepted the sdf for the SHG PZT offset.

TITLE: 07/01 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
SQZr trouble at the start of the lock but recovered and got to Observing at 00:07 UTC.

H1 was locked fine for 4 hours and 35 Minutes.
Then all the sudden Unknown Lockloss at 2025-07-01 03:56:04 UTC.

I tried to allow H1 to relock itself but it wanted me to find ASL-Y arm by hand and then seemed to get trapped in a PRMI loop. So after about 30 Minutes I did an Initial Alignment.
This did allow for a quick lock of DRMI_1F. 
H1 is currently at ENGAGE_SOFT_LOOPS and locking Quickly.  


LOG:

Unknown lockloss @ 3:56:07 UTC
No noticeable Seismic activity.
No PI ring Ups.
No saturations aside from HAM6 from the Fast Shutter.

On Friday Jun 27th Francisco and I went to the the PCAL lab and did a PCAL TX module maintenance according to T1600436.
AOM alignment was touched up

Results:

Ivey and Edgard,

We just finshed a fit of the Yaw-to-Yaw transfer functions for the OSEM estimator using the measurements that Oli took for SR3 last Tuesday [see LHO: 85288].

The fits were added to the Sus SVN and live inside '~/SusSVN/sus/trunk/HLTS/Common/FilterDesign/Estimator/fits_H1SR3_2025-06-30.mat' . They are already calibrated to work on the filter banks for the estimator and can be installed using 'make_SR3_yaw_model.m', which lives in the same folder [for reference, see LHO: 84041, where Oli got the fits running for a test].

Attached below are two pictures of the fits we made for the estimator.

The first attachment shows the Suspoint Y to M1 DAMP Y fit. We made sure to fit the asymptotic behavior as well as we could, which ends up being 0.95x10^{-3} um/nm (5% lower than expected from the OSEM calibration). The zpk for this fit is

    'zpk([-0.024+20.407i,-0.024-20.407i,-0.044+11.493i,-0.044-11.493i,0,0],[-0.067+21.278i,-0.067-21.278i,-0.095+14.443i,-0.095-14.443i,-0.07+6.405i,-0.07-6.405i],-0.001)'

The second attachment shows the M1 drive Y to M1 DAMP Y fit. We kept the same poles that we had for the other fit, but manually fit the zeros and gain to make a good match. The zpk for this fit is

'zpk([-0.051+8.326i,-0.051-8.326i,-0.011+19.259i,-0.011-19.259i],[-0.067+21.278i,-0.067-21.278i,-0.095+14.443i,-0.095-14.443i,-0.07+6.405i,-0.07-6.405i],12.096)'

Hopefully Oli and co. will have time to test this soon!

TITLE: 06/30 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 10mph Gusts, 4mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:

H1 Is Currently Locked at NLN {600} But not Observing due to a SQZ_SHG issue:
Error SQZ_SHG [LOCKED.run] USERMSG 0: PZT voltage limits exceeded.
Sheila is currently working on the issue.
 

TITLE: 06/30 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: We've had to relock twice, the second time we struggled a bit with DRMI. We're currently locked at NLN but trying to fix a SQZ SHG PZT issue.
LOG:                                                                                                                                 

• 15:00 UTC dropped Observing to start commissioning
• 15:40 UTC lockloss
  • 16:50 NLN
• 18:23 UTC lockloss
  • 19:26 UTC NLN
  • UTC Observing after some SQZ work
  • 19:55 UTC Hanford monthly safety notification test
  • 20:45 UTC we dropped Observing to fix the SQZ ANG servo
• 20:46 UTC lock loss
  • I was prompted to find YARM by hand
  • 21:28 UTC I did an alignment after 2x of DRMI being able to lock but too misaligned for ASC
  • We still couldn't get DRMI, on the 2nd round of PRMI I tried to manually help PRMI after it locked
    • DRMI still took another 12 minutes after this, with some more small adjustments by me (~45 minutes in total)
  • 23:21 UTC NLN but the SHG can't lock due to a PZT voltage issue (too low)

The h1daqnds0 system stopped accepting connections on its main nds1 port (8088).  We restarted the rts-nds and rts-daqd services around 2:59pm localtime.

There were no log messages or dmesg output.

20:46 UTC lockloss

Jennie W, Sheila, Ryan C, Ibrahim, Corey

Over the last 3 weeks three DARM offstep measurements (where we change the DARM offset to look at the fraction of the light from the differential mode which makes it past the OMC) have been taken.

This is so we can get data points to compare to my model of ARM to OMC mode-matching. These were done at three different CO2 X power levels.

Measurement 1: 2025/06/18 20:44:55 UTC

CO2 central heating on ITMX: 1.698W

CO2 central heating on ITMY: 1.694 W

The test is run with /ligo/gitcommon/labutils/darm_offset_step/auto_darm_offset.py . The data is processed with plot_darm_optical_gain_vs_dcpd_sum.py .

Graphs of the power after the OMC vs. optical gain are in the first plot,  optical gain vs. offset and anti-symmetric port power vs. power out of the omc are in this document.

The average contrast defect is 1.07 mW, the junk light is 679 mW, the transmission of the differential mode light at the AS port by the OMC is 1/1.217 = 82.2%.

Measurement 2: 2025/06/20 15:11:46 UTC

CO2 central heating on ITMX: 1.698 W

CO2 central heating on ITMY: 1.711 W

The test is run with /ligo/gitcommon/labutils/darm_offset_step/auto_darm_offset.py . The data is processed with plot_darm_optical_gain_vs_dcpd_sum.py .

Graphs of the power after the OMC vs. optical gain are in the first plot,  optical gain vs. offset and anti-symmetric port power vs. power out of the omc are in this document.

The avergae contrast defect is 1.03 mW, the junk light is 677 mW, the transmission of the differential mode light at the AS port by the OMC is 1/1.212= 82.5%.

Measurement 3: 2025/06/30 15:06:50 UTC

CO2 central heating on ITMX: 1.698 W

CO2 central heating on ITMY: 1.721 W

The test is run with /ligo/gitcommon/labutils/darm_offset_step/auto_darm_offset.py . The data is processed with plot_darm_optical_gain_vs_dcpd_sum.py .

Graphs of the power after the OMC vs. optical gain are in the first plot,  optical gain vs. offset and anti-symmetric port power vs. power out of the omc are in this document.

The avergae contrast defect is 1.09 mW, the junk light is 694 mW, the transmission of the differential mode light at the AS port by the OMC is 1/1.212= 82.5%.

This is not a very good test for our purposes as I think we want a larger change in mode-matching from thermal tuning to inform our simulations of Arm->OMC mode-mis-match.

Each time we have stepped the CO2Y down (all these darm offset measurements were meant to be repeated after decreasing the CO2 power) for this test (measurement 2 on the 20th June, alog 85238 shows attempt from 23rd June, alog 85335 shows attempt from the 25th June, alog 85429 is measurement 3) we have lost lock, so we might not be able to repeat this measurement with a larger CO2 step.

Over the weekend the ifo range has been slowly degrading due to loss of squeezing, as noted in both Ryan and Ibrahim's shift alogs. 

The attached trend shows the range drfiting with the sqz blrms 3 (centered at 350 Hz).  We could implement servos for the squeezing angle demod phase using the ADF (error signal for this servo shown in purple), or for the OPO temperature, or both.

I stepped the sqz angle demod phase to look at the ADF error signal, using z step -s 30 H1:SQZ-CLF_REFL_RF6_PHASE_DELAYSTEP +111,24 (second attachment) I then adjusted H1:SQZ-ADF_VCXO_PLL_PHASE to get a zero crossing near where the squeezer blrms were low and repeated a smaller demod angle scan, which had the error signal crossing 0 at good squeezing. I edited the guardian to ask it to turn this servo back on, (and changed the setpoint and nominal state).  The servo was osciallting a bit so I reduced the gain from -0.5 to -0.2.  Then servo went in the wrong directon, and we lost lock. 

After relocking the servo worked well, in the early part of the lock when the SQZ ASC is off. 

LLO has done some work on automating the temperature adjustment:

• Script running out of observing: 77278
• OPO temperature dither set up: 75430
• Masayuki original OPO temp set up: 60886

FAMIS 31092

Nothing much to report other than the FSS TPD signal has been dropping over the past week, so Jason plans to do a RefCav alignment tomorrow. PMC REFL has also come down very slightly.

Closes FAMIS#27818, last checked 85024 (I am a week late)

TCSX: 30.5, no water added

TCSY: 10.6, no water added

No leak in water cup

Elenna, Sheila, Oli

I've added thermalization ramping for the PRCL2 gain so that it ramps from 1.0 to 1.9 over the first 75 minutes at max power. The 'unthermalized' (1.0) and 'thermalized' (1.9) values are taken from lscparams in the new dictionary 'prcl2_gain', so any changes to be made in the future to those values should be set in that dictionary, and then the THERMALIZATION guardian reloaded so that it grabs those new values.

This addition is pretty much a copy of the way we ramp the SRCL offset, but for PRCL gain of course..

This change to the THERMALIZATION guardian as well as the dictionary addition to lscparams have been committed to svn as r32157.

18:23 UTC lockloss alog85433

15:40 UTC lockloss while we were running the CO2 stepper. alog85429