aLIGO LHO Logbook

H1 General - ALS arm CHECK_CRYSTAL_FREQUENCY fault state

ryan.crouch@ligo.org — Tue, 15 Jul 2025 12:53:47 -0700

Author: ryan.crouch@ligo.org

Report ID: 85761

I wrote this state at the end of 2023, to automate the relocking of the PLL through turning on the Beckoff autolocker and inputting crystal frequency values to search around. These frequencies it uses to search are assuming the values will be close to zero, so it assumes there isn't an offset alog81425.

We've been going into this fault state more often recently. This state is more of a band-aid for this issue than an actual fix to whatever's happening with the PLLs. ALS-Y sees this issue more frequently than ALS-X, each arm is locking at a different frequency these days, around 0 Hz for Xarm and around 100 for Yarm. Yarm seems more dynamic than Xarm for its' frequency, it has been changing more than Xarm over the past year.

I've updated the code today to use a dictionary with a list for each arm from the single list it was using so hopefully it will make it a little faster.

I'm writing some code with Tonys' statecounter to see exactly how many times we are going into this state for each arm over the past months, and years.

Images attached to this report

LHO VE - Quarterly Functionality Test Performed on EX/MX Turbo Pumps

travis.sadecki@ligo.org — Tue, 15 Jul 2025 12:43:58 -0700

Author: travis.sadecki@ligo.org

Report ID: 85772

FAMIS tasks 31305 and 31320, WP 12682

Procedure checklist for both stations completed. No issues were identified at this time.

MX: Scroll pump hours: 228.5
Turbo pump hours: 140
Crash bearings: 100%

EX: Scroll pump hours: 7155.9
Turbo pump hours: 1108
Crash bearings: 100%

H1 PSL - PSL FSS RefCav Tune-up (WP 12683)

jason.oberling@ligo.org — Tue, 15 Jul 2025 12:40:27 -0700

Author: jason.oberling@ligo.org

Report ID: 85769

This morning I performed an on-table alignment of the FSS RefCav beam, since yesterday's T.O.O. remote alignment tweak did not get the cavity transmission back above 0.8 V. As usual, I began with a power budget of the FSS beam, and left the ISS ON to keep the power in the FSS path stable:

FSS In: 277.5 mW
AOM In: 276.8 mW
AOM Out, Single Pass: 196.5 mW
- Single Pass Diffraction Efficiency: 71.0%
AOM Out, Double Pass: 53.3 mW (135.3 mW)
- Double Pass Diffraction Efficiency: 27.1 % (68.9%)
EOM Out: (136.0 mW)

Immediately it looks like the beam alignment through the AOM in its second pass is way off, but I've never seen the double pass diffraction efficiency this low so I decided to check alignment through the components in the beam path from the AOM to the RefCav before I started making adjustments. Sure enough, the beam was being clipped by the iris that sits between M22 and L11 (this iris block the undesired orders output from the AOM). I opened the iris and measured the power again, this is the number in parenthesis in the above bullets. So the diffraction efficiencies look around normal, but the beam was not well aligned to the iris. This was also seen in the EOM, as it was off alignment as well (but not enough that it was clipping the beam). I went ahead and slightly adjusted the AOM to maximize the single pass diffraction efficiency, and M21 to maximize the double pass diffraction efficiency, with the following results:

AOM Out, Single Pass: 200.1 mW
- Single Pass Diffraction Efficiency: 72.3%
AOM Out, Double Pass: 137.5 mW
- Double Pass Diffraction Efficiency: 68.7%

At this point, I adjusted the iris position to center it horizontally, and then adjusted M22 to get the beam a bit better centered vertically (iris is on a fixed mount with no vertical adjustment, and I didn't want to go too far and cause problems downstream; not super important that the beam be centered, as the iris is left open enough to pass the desired beam while blocked the others). This done, I opened the iris just enough to let the desired beam pass while still blocking the others. The EOM alignment was adjusted until the beam was centered on both the input and output EOM apertures; I measured 137.3 mW transmitted through the EOM, so free of clipping (the slight difference in double pass AOM Out and EOM Out is normal, the power meter never reads exactly the same). I then manually adjusted the picomotor equipped mounts (M32 and M47) to recenter the beam on the front and back of the RefCav input iris, then locked the RefCav. It locked without issue, so I proceeded to use the picomotors to fine tune the beam alignment into the RefCav.

Initial RefCav TPD: 0.719 V
Final RefCav TPD: 0.816 V

To end the work in the enclosure I unlocked the RefCav, aligned the reflected beam onto the RFPD, then relocked the RefCav and calculated the visibility:

Unlocked: 1.150 V
Locked: 0.207 V
Visibility: 82.0%

I then turned the ISS OFF (so it's not actuating on the beam power while the enclosure is returning to thermal equilibrium after the incursion), cleaned up equipment I had used, placed the enclosure into Science Mode, and left the LVEA. I checked on the PSL after about 45 minutes and things appeared to have settled out, so I did one final remote beam alignment of both the PMC (to account for any alignment changes during the incursion) and the RefCav. The PMC alignment was done with the ISS OFF, I then turned the ISS ON (RefSignal of -1.99 V, diffracted power moving between ~3.6% and ~4.0%) to record the final PMC Trans and Refl values and tweak the RefCav alignment. Results:

PMC
- Initial (ISS OFF)
  - Trans: ~104.9 W
  - Refl: ~23.4 W
- After Alignment (ISS OFF)
  - Trans: ~105.9 W
  - Refl: ~22.7 W
- Final (ISS ON)
  - Trans: ~106.0 W
  - Refl: ~22.8 W
RefCav (ISS ON)
- Initial TPD: ~0.836 V
- Final TPD: ~0.838 V

This ended the RefCav tune up for today. I'm not sure why the iris was clipping the beam, I have not seen that in the time I've been working on the PSL. Best guess I have is drift of mirror M22 due to slow temperature changes, since the diffraction efficiencies of the AOM were still pretty good and this is the only mirror between the AOM and the iris (could also be the PBS cube PBS01, but I don't think so as there was not an increase in the power of the rejected polarization beam). We will continue to monitor this as we usually do, but things are in decent shape right now. This closes LHO WP 12683.

H1 AOS - Comment to LOWNOISE ASC Locklosses

elenna.capote@ligo.org — Tue, 15 Jul 2025 11:58:52 -0700

Author: elenna.capote@ligo.org

Report ID: 85768

The glitch appears to be occuring due to the CHARD P change. We ramp a boost off with 2 seconds, and a new shaping and low pass on with 2 seconds, and then change the gain with 5 seconds. Looking at the step response of the shaping and lowpass filter, this ramp should probably be 10 seconds, and the gain also 10 seconds to match. I will keep the boost at 2 seconds to ramp off though. I increased the wait timer to 10 seconds to match this ramping. Model and guardian changes saved and loaded.

I am still not sure what is going on with DHARD P, but as a test I've now separated the low pass and loop shape from the engagement of the boost, since we know those individually are stable to engage. We now engage FM4 with a 10 second ramp and wait time, then engage FM8 with a 5 second ramp and wait time. I edited the ramps and gaurdian code to do so, svaed and loaded. This is kind of annoying, but it might help me debug what's going wrong here.

H1 ISC - Comment to Kepco Health Checkup

marc.pirello@ligo.org — Tue, 15 Jul 2025 11:57:29 -0700

Author: marc.pirello@ligo.org

Report ID: 85767

Looks like there is a PD Amplifier (D1301017) and an ESD Driver (D1600092) being powered by this +/- 24V supply set.

H1 AOS - Comment to LOWNOISE ASC Locklosses

elenna.capote@ligo.org — Tue, 15 Jul 2025 11:44:18 -0700

Author: elenna.capote@ligo.org

Report ID: 85766

We had another lockloss from this state at the 00:47 mark last night, 1436615757 so I'm not sure this fixed the problem.

However, the lockloss was proceeded by a glitch about 30 seconds before, like another lockloss I noticed in this state. This could be coincidence again, but it's looking a little suspicious!

H1 PSL - Comment to Summary of all ISS PD Array units that are not in use as of now (Randy, Rahul, Jennie, Keita)

keita.kawabe@ligo.org — Tue, 15 Jul 2025 11:25:33 -0700

Author: keita.kawabe@ligo.org

Report ID: 85765

I have found a bag with a label "Dirty Assy - not in ISC - single parts w/ s/n's in ICS". Inside the bag was an assembly that is a combination of upgrades and obsolete parts.

Base plate (D1300323)
A plate BS and two plate mirrors for the array (D1000957-V2 as a kit) and related parts
- Clamp bar for the plate optics (D1300324)
- 2pc Clamp Post (D1400144)
- 6pc plate adjustment cam (D14001410)
- 3pc spring clamps for the plate optics D1300330
Two blue glass beam dumps
PD array elevator assy (D1400140)
- 50:50 BS (D1002114-V1)
- PROBABLY ATF 99:1 sampler (but it could be a high reflector of the same size as we have such high reflectors made by ATF in one of the boxes of ISS array spare parts, though I don't know why).
- Elevator post D1400143
Upgrade to elevate the QPD position
- A kit of posts (D1300718-V3-1 SN 003 and 005, D1300718-V3-2 SN 003, 2pc D1300718-V3-3 SN 003 and 008)
- QPD mounting plate (D1300719-V2 SN 002)
QPD assembly including QPD itself (most likely Q3000) but w/o tilt mechanism
Obsolete PD array plate D1300322-V1
Old experiment? 2pc of 3mm PD, most likely Excelitas C30665GH.
- This is different from all production units that are supposed to use 2mm Excelitas C30642GH, but these two diodes share the same outer dimensions and pin-compatible.

I'm going to send the upgrade parts to elevate the QPD position to C/B. In addition, I went through all of the boxes we know are somehow related to ISS 2nd loop (again) and found some unused blue glasses. This means that we have enough parts to produce 3 spares if we have to (though it would be a lot of work).

Here's the inventory list of the 2nd loop spare parts as of now: https://dcc.ligo.org/LIGO-E2500191

Images attached to this report

H1 ISC - Kepco Health Checkup

marc.pirello@ligo.org — Tue, 15 Jul 2025 10:56:44 -0700

Author: marc.pirello@ligo.org

Report ID: 85764

This morning I used a new method of testing airflow and found one power supply in the corner that we missed with thermal testing.

Mezzanine:
C5-U30-RHS Stuck Fan, -24V Digital, S1201957. Current draw is <1A, no overheating detected, it could have been like this for a while.
This supply services H1-SUS-R5 ISC SC Digital. This is paired with the +24V in this rack.

All remaining supplies, good temperature, good airflow, no oscillations.

EX:
All supplies, good temperature, good airflow, no oscillations.

EY:
All supplies, good temperature, good airflow, no oscillations.

LHO VE - Tue CP1 Fill

david.barker@ligo.org — Tue, 15 Jul 2025 10:28:45 -0700

Author: david.barker@ligo.org

Report ID: 85763

Tue Jul 15 10:07:36 2025 INFO: Fill completed in 7min 32secs

Gerardo confirmed a good fill curbside.

Images attached to this report

LHO General - FAC maintenance activities for Tuesday

eric.otterman@ligo.org — Tue, 15 Jul 2025 10:27:16 -0700

Author: eric.otterman@ligo.org

Report ID: 85762

This morning, I completed the quarterly maintenance of the air handler at the FCES. There were no deficiencies noted. I also completed the thermal imaging of the circuit breaker panels at the end stations. Similarly, there were no deficiencies noted. At both end stations, the panels dedicated to CDS equipment had breakers that showed slightly elevated temperatures, but this is normal. No breakers were observed to be over 30 C.

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Tue, 15 Jul 2025 07:34:22 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85760

TITLE: 07/15 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 15mph Gusts, 9mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY: We've only been at low noise for 20 min, but magnetic injections are running now. Maintenance day today.

H1 CDS - Workstations updated

erik.vonreis@ligo.org — Tue, 15 Jul 2025 07:07:45 -0700

Author: erik.vonreis@ligo.org

Report ID: 85759

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

H1 General - OPS Owl Shift

ibrahim.abouelfettouh@ligo.org — Tue, 15 Jul 2025 04:29:40 -0700

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 85758

IFO is in ENGAGE_ASC_FOR_FULL_IFO and LOCKING

Got called at 2:30 AM after guardian failed to lock ALS during 30mph wind gusts (which seems to have been the cause of the lockloss itself) The cause for the call itself was that ISC_LOCK had stalled after a few attempts in which I simply unstalled it. However, DRMI was still having issues locking and alignment looked poor. A 5.7 EQ (+ aftershock) delayed my running initial alignment but it ran automatically after the EQ passed. Locking is so far fully automatic and DRMI locked with a much better signal. The lockloss stalling issue doesnt seem to have recurred while relocking.

H1 General - OPS Monday EVE shift summary

ryan.crouch@ligo.org — Mon, 14 Jul 2025 22:00:18 -0700

Author: ryan.crouch@ligo.org

Report ID: 85755

TITLE: 07/15 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Lockloss at the beginning of the shift, high winds made relocking a struggle till they calmed down in the last 1.5 hours. We've been locked for about an hour as of 05:00 UTC.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
22:56	SAF	LVEA	LVEA	YES	LVEA IS LASER HAZARD \u0d26\u0d3f(\u239a_\u239a)	14:34
22:46	ISS	Keita	Optics Lab	No	Working on PSL ISS system	00:08

00:11 UTC Observing
00:23 UTC lockloss after only 15 minutes
- The winds are teetering around 30-40 mph for gusts and 20-30 mph for the 3 minute avg
- We've lost lock in the same spot twice during CARM_OFFSET_REDUCTION with a large DHARD oscillation and a "Low recycling gain" warning. Potentially meaning alignment is off somewhere?
- 02:39 - 02:57 UTC Initial Alignment
- 04:08 UTC Observing

Images attached to this report

H1 General - Comment to 00:23 UTC lockloss

ryan.crouch@ligo.org — Mon, 14 Jul 2025 21:08:29 -0700

Author: ryan.crouch@ligo.org

Report ID: 85757

04:08 UTC Observing

H1 SUS - Updating compensation filters for satamp-swapped suspensions with more precise filters

oli.patane@ligo.org — Mon, 14 Jul 2025 17:49:55 -0700

Author: oli.patane@ligo.org

Report ID: 85746

Originally, the suspensions who have already had their satamps swapped for ECR E2400330 had their compensation filters updated to a generic 5.31:0.0969 zp filter that would get put in using my script /ligo/svncommon/SusSVN/sus/trunk/Common/PythonTools/satampswap_generic_filterupdate_ECR_E2400330.py (r12449).

However, Jeff went through the entire set of new satamps and tested each channel to determine the actual transimpedance and frequency response of each channel. We can use the measured frequency response to replace the generic filter with more precise compensation filters, so I have made a script that does just that - it updates the compensation filters in OSEMINF FM1 for whichever suspension you want with the more accurate zero and pole values for each channel. This script can be found at /ligo/svncommon/SusSVN/sus/trunk/Common/PythonTools/satampswap_bestpossible_filterupdate_ECR_E2400330.py (r12449).

I have used this script to update the compensation filters for the suspensions that have already had their satamps swapped (see txt file): SR3, SRM, BS, PRM, PR3, ITMX, ITMY, SR2. These new filters have all been loaded in.

Running the Best Possible Filter Update Script

This script can be found at /ligo/svncommon/SusSVN/sus/trunk/Common/PythonTools/satampswap_bestpossible_filterupdate_ECR_E2400330.py. To run it, all you need to do is:

Make sure the txt measurement files exist for that optic in /ligo/svncommon/SusSVN/sus/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Results/
In the PythonTools directory, do python3 satampswap_bestpossible_filterupdate_ECR_E2400330.py -o (or --opt), followed by the name of the optic or optics. If updating for multiple optics at once, put a space between each
Once the txt filter file has been updated, you must then go to the suspension's GDS screen to check the filter diffs and load in the new filters. Before loading in the new filters, make sure we are in DOWN and put the suspension into SAFE

Examples:

python3 /ligo/svncommon/SusSVN/sus/trunk/Common/PythonTools/satampswap_bestpossible_filterupdate_ECR_E2400330.py --opt SR2

Or to update multiple suspensions at once:

python3 /ligo/svncommon/SusSVN/sus/trunk/Common/PythonTools/satampswap_bestpossible_filterupdate_ECR_E2400330.py -o SR2 ITMX PRM

Running the Generic Filter Update Script

In case the measurements aren't done but you would like to update the compensation filters, you can use the generic filter script, satampswap_generic_filterupdate_ECR_E2400330.py. To run this script:

In the PythonTools directory, do python3 satampswap_bestpossible_filterupdate_ECR_E2400330.py -o (or --opt), followed by the name of the optic or optics. If updating for multiple optics at once, put a space between each
Once the txt filter file has been updated, you must then go to the suspension's GDS screen to check the filter diffs and load in the new filters. Before loading in the new filters, make sure we are in DOWN and put the suspension into SAFE

Images attached to this report

Non-image files attached to this report

satampswap_SR3_SRM_BS_PRM_PR3_ITMX_ITMY_SR2.txt

H1 General - 00:23 UTC lockloss

ryan.crouch@ligo.org — Mon, 14 Jul 2025 17:25:04 -0700

Author: ryan.crouch@ligo.org

Report ID: 85756

00:23 UTC lockloss

H1 SUS - Comparing transfer function fitting programs

ivey.zhong@ligo.org — Mon, 14 Jul 2025 17:14:11 -0700

Author: ivey.zhong@ligo.org

Report ID: 85750

Ivey, When fitting transfer functions for the OSEM estimator, I tested several transfer function fitting programs to find one that is both accurate and efficient. A brief side note: In the 6/24 M1-to-M1 dataset that Oli took, we observed an unexpected right-hand zero near 1.2 Hz (see attached plot), where we had expected a left-hand zero. After comparing with the 4/15 and 4/18 datasets, we found no corresponding right-hand zero, suggesting the 6/24 zero is likely due to noise. I wrote a document highlighting the pros and cons of each of the fitting programs here: TF Fitting Comparison (Google Doc) The programs include: Vectfit3 (I recommend using this with strong inverse weighting): Uses vector fitting. Created by Bjorn Gustavsen. Not built into MATLAB. Performs nearly identically to Vectfit4, but has more documentation. Rational: Built-in MATLAB function. Uses the AAA algorithm. Spectrumest: Built-in MATLAB function. Chooses an internal algorithm based on the data. Rationalfit: Built-in MATLAB function. Uses vector fitting. Generally, these programs fit poles and end behavior well, but often compromise the accuracy of the fit in the zero regions. In these cases, we often have to manually refine the fit in the zero regions. However, Vectfit3 performs very well on the 6/24 M1-to-M1 and SusPoint-to-M1 datasets when used with strong inverse weighting. We were able to produce better fits than manual methods, and expect this approach to be more efficient for future use. Example plots are available here: Plot Comparison Slides (Google Slides) Attached is the MATLAB code used for the M1-to-M1 fits. To use vectfit3, you must download the package here. All other functions used are built into MATLAB's toolboxes. Measurement file paths:

 /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/Common/Data/2025-06-24_1700_H1ISIHAM5_ST1_WhiteNoise_SR3SusPoint_L_to_Y_0p02to50Hz.xml

 /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/SAGM1/Data/2025-06-24_1900_H1SUSSR3_M1_WhiteNoise_L_to_Y_0p02to50Hz.xml

SEI, SUS

Images attached to this report

Non-image files attached to this report

Fitting_w_Many_Programs.m

H1 General - Comment to Lockloss @ 21:56 UTC

ryan.crouch@ligo.org — Mon, 14 Jul 2025 17:12:36 -0700

Author: ryan.crouch@ligo.org

Report ID: 85754

00:11 UTC Observing

H1 CAL - Comment to PCAL EX Measurement

francisco.llamas@ligo.org — Mon, 14 Jul 2025 17:07:50 -0700

Author: francisco.llamas@ligo.org

Report ID: 85753

Comment regarding the missing signal on the EX Pcal MEDM:

We noticed that H1:CAL-PCALX_OFS_DRIVE_MON was not working as expected a few weeks ago. On this expedition to make ES measurements, Dripta and I used a few breakout boards to ensure that the "OFS drive monitor" signal was coming out of the Pcal chassis and into the ADC Chassis. We confirm that there was a signal coming out of the Pcal Interface Chassis back board (D1400149V1), the DB9 output labeled "To Fast ADC", pins 1 and 6 (not the same name but, by process of elimination, we assume that "OFS drive monitor" is, in the drawing, "InLoopOut±") , so we can rule out the Pcal chassis. Due to lack of time, however, we were not able to pinpoint the step at which this signal is lost.

Tony found the next step in our hunt: Page 3 of D1300226V13 shows the ADC side of "To Fast ADC", specifically, "ADC CHAN±00" is assigned, in the drawing, to InLoopOut± . I am tagging CDS for any insight on their side. Discussions and a follow-up plan are in progress to find the signal.

CDS

LHO General - Ops Day Shift Summary

ryan.short@ligo.org — Mon, 14 Jul 2025 16:30:02 -0700

Author: ryan.short@ligo.org

Report ID: 85751

TITLE: 07/14 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Two locklosses today, one of which during commissioning time from a M6.8 earthquake out of Panama. The second lockloss we're still recovering from, and even after running an initial alignment, there have been several lockloss at low states, possibly from rising wind speeds.

14:26 - Lockloss from LOWNOISE_ASC
15:42 - Reached NLN, jumping into commissioning
17:25 - Entered EQ mode
17:48 - Lockloss
18:28 - Ground has calmed down, starting lock acquisition
20:18 - Observing
21:56 - Lockloss - alog85747
- 22:33 - Lockloss during DRMI, starting initial alignment
- 22:52 - Alignment finished, starting lock acquisition

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
22:56	SAF	LVEA	LVEA	YES	LVEA IS LASER HAZARD	14:34
14:50	FAC	Randy	MY	N	Checking on forklift	15:05
15:46	PEM	Robert, Sam	LVEA/CR	-	Accoustic injections	17:55
16:29	FAC	Kim	MY	N	Technical cleaning	17:30
16:29	FAC	Nellie	MX	N	Technical cleaning	17:13
17:16	FAC	Tyler	BT near EX	N	Bees	17:40
17:33	PSL	Jason	MX	N	Inventory	18:04
17:59	PEM	Robert	LVEA	-	Replacing viewport covers	18:16
22:46	ISS	Keita	Optics Lab	N	ISS array work	Ongoing

H1 General - OPS Monday EVE shift start

ryan.crouch@ligo.org — Mon, 14 Jul 2025 16:26:43 -0700

Author: ryan.crouch@ligo.org

Report ID: 85752

TITLE: 07/14 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 25mph Gusts, 16mph 3min avg
    Primary useism: 0.09 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

We're relocking after a 21:56 UTC lockloss
- The wind is a little high
  - From windy.com the wind is predicted to get a little worse before calming down later tonight
- Lots of low state (pre-DRMI) and one at DARM_TO_RF

H1 PSL - Comment to Calibrating ISS QPD

jennifer.wright@ligo.org — Mon, 14 Jul 2025 15:36:46 -0700

Author: jennifer.wright@ligo.org

Report ID: 85749

I redid the graphs for the horizontal motion of the input beam to X motion on the QPD with better labels (first attached graph) and did a fit for the Y data on the QPD collected at each horizontal position of the input beam (second attached graph). The third graph attached is comparing both fits on one graph.

Images attached to this report

H1 General - Lockloss @ 21:56 UTC

ryan.short@ligo.org — Mon, 14 Jul 2025 15:27:12 -0700

Author: ryan.short@ligo.org

Report ID: 85747

Lockloss @ 21:56 UTC after almost 2 hours locked - link to lockloss tool

This appeared to line up with an incoming M5.8 EQ from Japan, but the R-waves hadn't fully arrived and the ground wasn't moving all the much at the time. Also, the first errant thing happening I can see is a hit on DARM, which seems unusual.

Lockloss

Images attached to this report

H1 SUS - Results of the 7/08 SR3 Yaw OSEM estimator test

edgard.bonilla@ligo.org — Mon, 14 Jul 2025 11:53:44 -0700

Author: edgard.bonilla@ligo.org

Report ID: 85745

Ivey, Edgard

Follow up to Oli's estimator test [LHO: 85615].

Ivey took the data for the three tests that Oli ran and got some spectra to show that the estimator is working as expected. We can see three traces in each one of the figures attached:

The Blue traces are using light damping, that is, using the OSEMs as we have them right now, but dividing the M1_DAMP_Y gains by a factor of 5. [Light damping]
The Red traces are the current settings. [ OSEM only damping ]
The Yellow traces are the estimator damping. This tries to get the best of both worlds by using the HAM5 GS13 and the models we posted in [LHO: 85446] [ Estimator damping ]

The first figure shows the M1 Yaw signals as seen by the M1 OSEMs. As you can see, the spectrum is completely dominated by sensor noise, except at the suspension resonances. Under light damping, the OSEM actually sees the suspension modes ring, but under 'OSEM only' and Estimator damping, the resonances don't show up anymore, as expected. We note that there is a bit of the 3 Hz resonance that seems to not be fully damped by the estimator.

The second figure is one of the money plots. It shows the M3 Yaw as seen by the SR3 OPLEV. In it, we can see that the OSEM only, and the Estimator damping are both successful at damping down the resonances of the suspension. This means that the Estimator is working as intended. We note that in the estimator case, there is a bit of excess noise at 2 Hz.

The last figure shows the total drive request for the M1 OSEMs in drive cts. As expected, the Estimator is requesting less drive above 5 Hz when compared to the OSEM only damping (which is the current setting). Since this is completely aligned with our expectations, we believe this implies that the estimator is working as intended and we are likely reducing the SR3 M1 Y OSEM noise injection into M3 Y by a factor of 5 at 10 Hz and above.

We also note that the drive request at 2 Hz has a bump likely due to model mismatch. This effect is likely the cause for the excess 2Hz noise seen in the OPLEV signal. We might need to model it to see why it would lead to a coherent addition of motion that can be captured by the M3 OPLEV.

Since this test was so successful, our expectation is that we will be trying to affix the OSEM calibrations, a Yaw estimator, and then a Pitch estimator for SR3 in the next few weeks. Stay Tuned!

SUS

Non-image files attached to this report

July_08_2025_SR3_Yaw_estimator_analysis.pdf

H1 PSL - Comment to PSL 10-Day Trends

ryan.short@ligo.org — Mon, 14 Jul 2025 11:21:11 -0700

Author: ryan.short@ligo.org

Report ID: 85744

A M6.6 EQ out of Panama knocked H1 out of lock this morning, so I took that opportunity to touch up the RefCav alignment. I was only able to increase the signal on the TPD from about 0.700 V to 0.764 V, so not quite back to what it was before, meaning Jason will need to adjust alignment on-table tomorrow as planned.

H1 SEI - Comment to Trying High Bandwidth control for earthquake

elenna.capote@ligo.org — Mon, 14 Jul 2025 11:12:56 -0700

Author: elenna.capote@ligo.org

Report ID: 85743

I refined the script to include some sleeps, and wrote another script to revert the reversion so it will put the ASC and LSC feedforward back in the nominal low noise state.

Both scripts are attached. They should be tested!

Non-image files attached to this report

lownoise_asc_revert.py

go_back_lownoise.py

H1 SEI - Comment to Trying High Bandwidth control for earthquake

elenna.capote@ligo.org — Mon, 14 Jul 2025 10:58:58 -0700

Author: elenna.capote@ligo.org

Report ID: 85742

This was a "large earthquake" aka within the yellow band on the EQ response zone plot. Since these earthquakes are highly likely to cause lockloss, Jim and I are thinking we could try this high bandwidth control reversion for these earthquakes to see if this can help us survive the earthquake. This would take us out of observing and kill the range (we were at about 70 Mpc before the lockloss), but we could then go back to lownoise once the earthquake passes.

Jim also thinks he can make some adjustments to other seismic controls, but I'll let him explain how that would work since he is the expert.

H1 SEI - Comment to Trying High Bandwidth control for earthquake

elenna.capote@ligo.org — Mon, 14 Jul 2025 10:48:50 -0700

Author: elenna.capote@ligo.org

Report ID: 85741

We lost lock when the ground motion got to be about 2.5 micron/s.

H1 SEI - Trying High Bandwidth control for earthquake

elenna.capote@ligo.org — Mon, 14 Jul 2025 10:45:38 -0700

Author: elenna.capote@ligo.org

Report ID: 85740

Jim, Elenna

We had a 6.6 earthquake begin rolling in from Panama, so Jim and I tried to take the ASC arm control loops to the high bandwidth state. I also turned off the LSC feedforward which drives the ETMY PUM.

This obviously creates a lot of noise in DARM, but we are curious to see if it helps us ride out a large earthquake.

This consists of:

turning off low pass and other shaping filters for DHARD P, DHARD Y, CHARD Y and CHARD Y
adjusting CHARD P and Y gains
increasing DSOFT P and Y gains
changing LSC feedforward gains to zero

Some of these things can be done by hand, but others, like transitioning filters and gains together have to be done with guardian code to ensure they are done at the same time. I copied and pasted lines of code into a guardian shell.

These are the lines of code that will do everything I mentioned above:

ezca.get_LIGOFilter('ASC-CHARD_Y').ramp_gain(300, ramp_time=10, wait=False)

ezca.switch('ASC-CHARD_Y', 'FM3', 'FM8', 'FM9', 'OFF')

ezca.switch('ASC-DHARD_Y', 'FM1', 'FM3', 'FM4', 'FM5', 'FM8', 'OFF')

ezca.switch('ASC-CHARD_P', 'FM9', 'ON')

ezca.switch('ASC-CHARD_P', 'FM3', 'FM8', 'OFF')

ezca['ASC-CHARD_P_GAIN'] = 80

ezca.get_LIGOFilter('ASC-DSOFT_Y').ramp_gain(30, ramp_time=5, wait=False)

ezca.get_LIGOFilter('ASC-DSOFT_P').ramp_gain(10, ramp_time=5, wait=False)

ezca.switch('ASC-DHARD_P', 'FM4', 'FM8', 'OFF')

ezca['LSC-PRCLFF_GAIN'] = 0

ezca['LSC-MICHFF_GAIN'] = 0

ezca['LSC-SRCLFF1_GAIN'] = 0

I saved this as a script called "lownoise_asc_revert.py" in my home directory. This is a bit of a misnomer since it also reverts the LSC feedforward.

We are still locked so far, but we are waiting to see how this goes (R wave just arrived).

ISC

H1 PSL - Comment to PSL 10-Day Trends

jason.oberling@ligo.org — Mon, 14 Jul 2025 10:15:46 -0700

Author: jason.oberling@ligo.org

Report ID: 85739

I plan on taking a look at RefCav alignment during maintenance tomorrow; Ryan will perform a remote RefCav alignment today ONLY if a valid T.O.O. presents itsefl (i.e. a large EQ has us down for some time). The last time I did a remote alignment on July 1st I was not able to get back to the previous TPD voltage, an indication that something upstream of the picomotors is moving (this something is usually the double-pass AOM). Further, the RefCav REFL spot on the PSL Quad Display (the lower-left image) hints that an enclosure incursion may be necessary; the central spot is mostly centered between the upper and lower lobes (which hints that the alignment into the RefCav is likely OK), but the lobes themselves are much brighter than normal. This is generally an early indication that an on-table RefCav beam alignment is in our near future.

The plan at this point is for me to try a remote alignment early in the maintenance period, unless Ryan is able to try it during a T.O.O. today. Should the TPD return to above 0.8 V then nothing further happens, we will continue to monitor this as we normally do; but if it cannot then I will go into the enclosure and perform and on-table RefCav beam alignment (I have filed WP 12683 in case I do have to go into the enclosure). The IMC will need to be UNLOCKED while I am working on the RefCav, regardless of if I'm in the Control Room or in the PSL enclosure (same goes for if Ryan gets a T.O.O. to do the remote alignment today).

H1 AOS - LOWNOISE ASC Locklosses

elenna.capote@ligo.org — Mon, 14 Jul 2025 09:21:42 -0700

Author: elenna.capote@ligo.org

Report ID: 85738

I previously noted a glitch about 30 seconds before lockloss in LOWNOISE ASC, 85685. However, we had two more locklosses from this state last night and I do not see such a glitch so that is a random coincidence. One of those locklosses appears to be caused by an earthquake. However, since 6/11, we have had 9 locklosses in this state that occurred exactly 47 seconds into the state, which seems suspicious, one of those occurred last night, and the lockloss with the glitch was the same.

This seems to be coincident with the engagement of a few DHARD P filters:

2025-07-14_14:26:54.641531Z ISC_LOCK executing state: LOWNOISE_ASC (522) 2025-07-14_14:26:54.642230Z ISC_LOCK [LOWNOISE_ASC.enter] 2025-07-14_14:26:54.655894Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_PIT3_OSC_CLKGAIN => 300 2025-07-14_14:26:54.656325Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_PIT4_OSC_CLKGAIN => 300 2025-07-14_14:26:54.656732Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_PIT5_OSC_CLKGAIN => 300 2025-07-14_14:26:54.657043Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_YAW3_OSC_CLKGAIN => 300 2025-07-14_14:26:54.657438Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_YAW4_OSC_CLKGAIN => 300 2025-07-14_14:26:54.657892Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_YAW5_OSC_CLKGAIN => 300 2025-07-14_14:26:54.658134Z ISC_LOCK [LOWNOISE_ASC.main] timer['LoopShapeRamp'] = 5 2025-07-14_14:26:54.658367Z ISC_LOCK [LOWNOISE_ASC.main] timer['pwr'] = 0.125 2025-07-14_14:26:54.783581Z ISC_LOCK [LOWNOISE_ASC.run] timer['pwr'] done 2025-07-14_14:26:59.658298Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done 2025-07-14_14:26:59.719537Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y_GAIN => 200 2025-07-14_14:26:59.720456Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y_SW1 => 256 2025-07-14_14:26:59.846249Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y_SW2 => 20 2025-07-14_14:26:59.971686Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y => ON: FM3, FM8, FM9 2025-07-14_14:26:59.972384Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_Y_SW1 => 5392 2025-07-14_14:27:00.098073Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_Y_SW2 => 4 2025-07-14_14:27:00.223528Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_Y => ON: FM1, FM3, FM4, FM5, FM8 2025-07-14_14:27:00.224135Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CSOFT_P_SMOOTH_ENABLE => 0 2025-07-14_14:27:00.224497Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CSOFT_Y_SMOOTH_ENABLE => 0 2025-07-14_14:27:00.224868Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_P_SMOOTH_ENABLE => 0 2025-07-14_14:27:00.225188Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_Y_SMOOTH_ENABLE => 0 2025-07-14_14:27:00.225433Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10 2025-07-14_14:27:10.225728Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done 2025-07-14_14:27:10.281803Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_TRAMP => 5 2025-07-14_14:27:10.408120Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_SW2 => 16 2025-07-14_14:27:10.533563Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P => OFF: FM9 2025-07-14_14:27:10.534285Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_SW1 => 256 2025-07-14_14:27:10.660088Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_SW2 => 4 2025-07-14_14:27:10.785453Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P => ON: FM3, FM8 2025-07-14_14:27:10.786315Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_GAIN => 208 2025-07-14_14:27:10.786535Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 5 2025-07-14_14:27:15.786858Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done 2025-07-14_14:27:15.847152Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_Y_TRAMP => 5 2025-07-14_14:27:15.847580Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_Y_GAIN => 5 2025-07-14_14:27:15.848666Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_P_GAIN => 5 2025-07-14_14:27:15.848917Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 5 2025-07-14_14:27:20.849050Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done 2025-07-14_14:27:20.906577Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMX_M0_DAMP_Y_TRAMP => 10 2025-07-14_14:27:20.907206Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ETMX_M0_DAMP_Y_TRAMP => 10 2025-07-14_14:27:20.907700Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMY_M0_DAMP_Y_TRAMP => 10 2025-07-14_14:27:20.908422Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMX_M0_DAMP_Y_GAIN => -0.5 2025-07-14_14:27:20.908830Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ETMX_M0_DAMP_Y_GAIN => -0.5 2025-07-14_14:27:20.909148Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMY_M0_DAMP_Y_GAIN => -0.5 2025-07-14_14:27:20.909562Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ETMY_M0_DAMP_Y_GAIN => -0.5 2025-07-14_14:27:20.909789Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10 2025-07-14_14:27:30.910055Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done 2025-07-14_14:27:30.968166Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_P_GAIN => -0.2 2025-07-14_14:27:30.968527Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_Y_GAIN => -0.2 2025-07-14_14:27:30.968806Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_L_GAIN => -0.2 2025-07-14_14:27:30.969073Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_R_GAIN => -0.2 2025-07-14_14:27:30.969343Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_T_GAIN => -0.2 2025-07-14_14:27:30.969606Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_V_GAIN => -0.2 2025-07-14_14:27:30.969838Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10 2025-07-14_14:27:40.970003Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done 2025-07-14_14:27:40.972085Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_P_SW1 => 1024 2025-07-14_14:27:41.097962Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_P_SW2 => 4 2025-07-14_14:27:41.223313Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_P => ON: FM4, FM8 2025-07-14_14:27:41.223637Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10 2025-07-14_14:27:41.593743Z ISC_LOCK [LOWNOISE_ASC.run] Unstalling IMC_LOCK 2025-07-14_14:27:41.765955Z ISC_LOCK JUMP target: LOCKLOSS

I will take a look and see if there is anything unstable about these filters. Whatever is occurring seems to be too fast to be seen in the ASC signals themselves, and at first glance I don't see anything strange in the suspension channels either.

DHARD FM4 is engaged with a 10 second ramp- this is a change I made on 6/11: 84973 because we had lost lock on that day twice in the same spot. Two of the locklosses at 47 seconds occurred before that change. Then, later that day on 6/11 I reengaged a boost in DHARD P, which only has a 5 second ramp, 84980. Engaging that boost shouldn't be unstable, but maybe something bas occurrs when they ramp at different times. I'm lengthing the ramp to 10 seconds.

LHO General - Comment to Ops Day Shift Start

ryan.short@ligo.org — Mon, 14 Jul 2025 08:49:14 -0700

Author: ryan.short@ligo.org

Report ID: 85737

H1 relocked back to low noise at 15:42 UTC. Jumping straight into planned commissioning time which is scheduled until 19:00 UTC.

H1 General - Comment to Lockloss @ 18:53 UTC - Power Glitch

david.barker@ligo.org — Mon, 14 Jul 2025 08:42:01 -0700

Author: david.barker@ligo.org

Report ID: 85736

Jonathan checked the front panel on the MSR UPS and confirmed it logged nothing at the time of this power glitch.

H1 PSL - PSL 10-Day Trends

ryan.short@ligo.org — Mon, 14 Jul 2025 08:34:36 -0700

Author: ryan.short@ligo.org

Report ID: 85735

FAMIS 31094

FSS TPD signal has been dropping over the past week, so it could probably do with some RefCav alignment adjustments soon. Otherwise, not much else to report.

Images attached to this report

LHO General - Ops Day Shift Start

ryan.short@ligo.org — Mon, 14 Jul 2025 08:00:14 -0700

Author: ryan.short@ligo.org

Report ID: 85734

TITLE: 07/14 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 18mph Gusts, 13mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: H1 looks to have been down most of the night (since 04:00 UTC during last night's evening shift). High winds combined with an earthquake made for difficult locking with only a few attempts making it to LOWNOISE_ASC before a lockloss. Currently trying to lock DRMI.

Wind moderate, microseism low
All other systems nominal

H1 General - Comment to Lockloss @ 18:53 UTC - Power Glitch

david.barker@ligo.org — Mon, 14 Jul 2025 07:43:12 -0700

Author: david.barker@ligo.org

Report ID: 85733

FRS34721

Note that none of the UPS units emailed us regarding this event, which is unusual for a glitch which caused HEPI pump controller issues.

H1 General - IFO needed assistance since earthquake.

anthony.sanchez@ligo.org — Mon, 14 Jul 2025 07:16:16 -0700

Author: anthony.sanchez@ligo.org

Report ID: 85732

I woke up, with my alarm clock and started an initial alignment since H1 needed assistance. Around 6am.
Once
Going throught the locking proccess now.

H1 General - OPS Sunday EVE shift summary

ryan.crouch@ligo.org — Sun, 13 Jul 2025 22:02:58 -0700

Author: ryan.crouch@ligo.org

Report ID: 85729

TITLE: 07/14 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Wind/Aligning
INCOMING OPERATOR: Tony
SHIFT SUMMARY: The TCSY laser tripped off then we lost lock in the last hour, the winds rose to around 40mph after this. H1 is trying to do an intial alignment as of 05:00 UTC as the DRMI flashes weren't great, the winds have calmed a bit so hopefully it goes well and the arms can stay locked.
LOG: No log.

23:30 - 23:38 UTC We dropped observing from the SQZ PMC unlocking as the volts were too low, I ran a SQZ_ANG_ADJ after it relocked but it doesn't look like it helped
PR2 camera is blue, since 20:53 UTC. This might be from Robert?
I created a damping filter for EY mode19 (2nd harmonic mode) as there wasn't one, matching it to the monitor filter. I saved but did not load it so that's what the CRC error is from on H1SUSETMY (Tagging SUS, CDS)
- butter("BandPass",8,1481.960,1481.980)
03:58 UTC TCSY tripped, then we lost lock 2 minutes later at 04:00 UTC from an ETMX glitch
- I reset the lasers controller and power supply, alog85730
- The winds have picked up considerably up to 40mph in the past half hour as I'm relocking

CDS, SUS

H1 General - Comment to Lockloss 04:00 UTC

ryan.crouch@ligo.org — Sun, 13 Jul 2025 21:39:30 -0700

Author: ryan.crouch@ligo.org

Report ID: 85731

Following the WIKI and TJ's instructions I went into the LVEA (TJ was my phone buddy) to restart the controller than I went into the mechanical room and reset the power supply which was reading a current and voltage of 0 when I arrived. There were no flow/chiller alarm nor RTD/IR sens alarm.

H1 General - Lockloss 04:00 UTC

ryan.crouch@ligo.org — Sun, 13 Jul 2025 21:04:50 -0700

Author: ryan.crouch@ligo.org

Report ID: 85730

TCS CO2Y tripped and dropped us out of Observing at 03:58 UTC then we lost lock 2 minutes later, lockloss. The lockloss appears to have been an ETMX glitch.

Lockloss, TCS

H1 AOS - New suggested settings for ITMY compensation plate offsets, pitch: -317, yaw: -122

robert.schofield@ligo.org — Sun, 13 Jul 2025 18:29:43 -0700

Author: robert.schofield@ligo.org

Report ID: 85728

The pumps were still running last month when I suggested preliminary CP-Y settings (85084). I wanted to get back to it with a little higher sensitivity after the pumps were shut off. As a result of this second look, I suggest new settings of Pitch: -317 and Yaw: -122; They represent only a slight reduction in scattering noise coupling, but the new settings don't consume as much actuator range.

The technique I used to pick a minimum was the same as used here: https://alog.ligo-wa.caltech.edu/aLOG/uploads/76969_20240404184914_Fig3-Sensitivity-To-IY-CP-Yaw-Also-Bright-Spot.pdf

The structure in the coupling variation was like it was before the break (see link), at a scale of about 20 microradians in CP angle. The maximum coupling in the CP sweeps after the vent was about half of what it was in the sweeps before the vent, so maybe there was some improvement.

I made videos of the beam spot on the HAM3 ballast baffle and its support before and after the compensation plate adjustment. The compilation video uses the same slider program (see details in video description) before and after the compensation plate move:

https://youtu.be/nbZ7da6LE9s

H1 General - Comment to OPS Sunday EVE shift start

ryan.crouch@ligo.org — Sun, 13 Jul 2025 16:41:17 -0700

Author: ryan.crouch@ligo.org

Report ID: 85727

We dropped observing from 23:30 - 23:38 UTC as the SQZ PMC lost lock, I also ran a SCAN_SQZ ang

LHO General - Ops Day Shift Summary

ryan.short@ligo.org — Sun, 13 Jul 2025 16:30:11 -0700

Author: ryan.short@ligo.org

Report ID: 85726

TITLE: 07/13 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Major excitement of the day was a lockloss caused by a power glitch which necessitated a recovery of end station HEPI pump controllers. Aside from that, calibration sweeps were run opportunistically and relocking went very smoothly.

17:38 - Dropping observing while L1 is unlocked for cal sweeps - alog85720
18:09 - Sweeps finished; adjusting OPO temp - alog85721
18:19 - Observing
18:53 - Lockloss and power glitch - alog85722
- End station HEPIs and ISIs trip
- Going to end stations to reset pump controllers
- 20:36 - Recovered, starting alignment
- 21:04 - Alignment finished, starting lock acquisition
21:50 - Observing

H1 General - OPS Sunday EVE shift start

ryan.crouch@ligo.org — Sun, 13 Jul 2025 16:00:16 -0700

Author: ryan.crouch@ligo.org

Report ID: 85725

TITLE: 07/13 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 8mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

We've been locked for a little over an hour
2ndary microseism has come down, wind is low to moderate
SQZ PMC is reporting low volts again

H1 General - Comment to Lockloss @ 18:53 UTC - Power Glitch

ryan.short@ligo.org — Sun, 13 Jul 2025 14:52:09 -0700

Author: ryan.short@ligo.org

Report ID: 85724

H1 back to observing at 21:50 UTC. Initial alignment and lock acquisition both ran fully automatically and without issues.

H1 General - Comment to Lockloss @ 18:53 UTC - Power Glitch

ryan.short@ligo.org — Sun, 13 Jul 2025 13:36:40 -0700

Author: ryan.short@ligo.org

Report ID: 85723

Pump stations and all seismic systems fully recovered. Starting an initial alignment now.

H1 General - Lockloss @ 18:53 UTC - Power Glitch

ryan.short@ligo.org — Sun, 13 Jul 2025 12:19:07 -0700

Author: ryan.short@ligo.org

Report ID: 85722

Lockloss @ 18:53 UTC from site power glitch, trend attached. This tripped the end station HEPI pump controllers (and so far nothing else, that I've noticed), so I consulted with Jim and he walked me through what needs to be done to reset them. Heading out to the end stations now.

Images attached to this report

H1 SQZ - OPO Temperature Adjusted

ryan.short@ligo.org — Sun, 13 Jul 2025 11:32:03 -0700

Author: ryan.short@ligo.org

Report ID: 85721

After running calibration sweeps this morning while L1 was out of lock, I also took the opportunity to touch up the OPO temperature with the SQZ_OPO_LR Guardian as I noticed the range gradually decreasing over this lock stretch. This went well, improving CLF_REFL_RF6 a bit and gaining H1 about 6-8Mpc of BNS range.

H1 returned to observing at 18:19 UTC.

Images attached to this report

H1 CAL - Broadband and Simulines Calibration Sweeps

ryan.short@ligo.org — Sun, 13 Jul 2025 11:27:27 -0700

Author: ryan.short@ligo.org

Report ID: 85720

Since the scheduled calibration time was missed yesterday due to a lockloss, while L1 was out of lock this morning, I took the opportunity to drop observing at 17:38 UTC and run the broadband and Simulines sweeps. Calibration report and screenshot of the calibration monitor screen are attached.

Broadband: 17:39 to 17:44 UTC

Simulines: 17:45 to 18:08 UTC

2025-07-13 18:08:34,702 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250713T174519Z.hdf5
2025-07-13 18:08:34,709 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250713T174519Z.hdf5
2025-07-13 18:08:34,714 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250713T174519Z.hdf5
2025-07-13 18:08:34,719 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250713T174519Z.hdf5
2025-07-13 18:08:34,723 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250713T174519Z.hdf5

Images attached to this report

Non-image files attached to this report

H1_calibration_report_20250713T174519Z.pdf

LHO VE - Sun CP1 Fill

david.barker@ligo.org — Sun, 13 Jul 2025 10:27:42 -0700

Author: david.barker@ligo.org

Report ID: 85719

Sun Jul 13 10:08:24 2025 INFO: Fill completed in 8min 20secs

Images attached to this report

LHO General - Ops Day Shift Start

ryan.short@ligo.org — Sun, 13 Jul 2025 07:51:17 -0700

Author: ryan.short@ligo.org

Report ID: 85718

TITLE: 07/13 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 2mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: One lockloss overnight with an automatic recovery. H1 has now been locked and observing for 5 hours.

Wind and microseism low
All other systems nominal

H1 General - 05:09 UTC lockloss

ryan.crouch@ligo.org — Sat, 12 Jul 2025 22:11:28 -0700

Author: ryan.crouch@ligo.org

Report ID: 85717

05:09 UTC lockloss

Lockloss

H1 General - OPS Saturday EVE shift summary

ryan.crouch@ligo.org — Sat, 12 Jul 2025 22:10:52 -0700

Author: ryan.crouch@ligo.org

Report ID: 85714

TITLE: 07/13 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: A lockloss towards the end of the shift and right after relocking.
LOG: No log

I've added the damping settings I found the other day (FM1+FM2+FM10 G=-50) into lscparams after seeing it work for many lock stretches, the VIOLIN_DAMPING GRD could use a reload to see this change.

00:01 - 00:05 UTC dropped Observing from the SQZer's PMC losing lock
02:56 UTC lockloss from an ETMX glitch
- 03:58 UTC initial alignment, DRMI locked after 7 minute now
- 05:08 NLN
05:09 lockloss, ??? Annoying

H1 SUS - Second harmonic violin modes

ryan.crouch@ligo.org — Sat, 12 Jul 2025 20:20:40 -0700

Author: ryan.crouch@ligo.org

Report ID: 85715

I took some high resolution spectra in the 1460 - 1500 bandwidth of DARM to look at the second harmonic violin mode region, all of these might not be violin modes. I found 5 over 10^-16, 1468.4961 1472.7793, 1481.9717 (monitor filter on ETMY mode19), 1492.0198, and 1497.1934 (the worst offenders), these were reduced to 3 when I took another spectra with a smaller bw an hour later. There were also several above 10^-17, 1464.5293, 1464.0234, 1467.3916 1468.5879, 1471.2969, 1471.7012, 1472.9668, 1482.0117, 1494.3535, 1494.3711, 1499.5937, 1500.4248. The frequencies I saw don't match the old ones reported in the wiki's violin mode table or in T1800327 but I believe these documents were from pre-O3.

SUS

Images attached to this report

H1 General - Lockloss 02:56 UTC

ryan.crouch@ligo.org — Sat, 12 Jul 2025 20:09:22 -0700

Author: ryan.crouch@ligo.org

Report ID: 85716

Lockloss 02:56 UTC from an ETMX glitch just under 1/4 of a second before the LL

Lockloss

H1 General - Comment to OPS Saturday EVE shift start

ryan.crouch@ligo.org — Sat, 12 Jul 2025 17:07:52 -0700

Author: ryan.crouch@ligo.org

Report ID: 85713

We dropped observing from 00:01 - 00:05 UTC from the SQZer's PMC losing lock, it relocked with a much higher/better voltage. I wanted to adjust the OPO temp then run a scan SQZ_ANG but I didn't notice that GRD IFO was in AUTO so it brought us back as soon as the SQZer relocked after I had done a few steps of the OPO, the range is a couple Mpc better now though.

SQZ

LHO General - Ops Day Shift Summary

ryan.short@ligo.org — Sat, 12 Jul 2025 16:35:08 -0700

Author: ryan.short@ligo.org

Report ID: 85712

TITLE: 07/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Pretty straightforward day of public site tours and only one lockloss with a fully automatic relock after. Planned calibration sweep was missed because of this; Ryan C. says he'll run it if L1 drops out of observing this evening. H1 has now been locked for 4.5 hours.

14:25 - S250712cd
17:23 - Lockloss - alog85709
- 18:01 - Finished initial alignment
18:54 - Observing

H1 General - OPS Saturday EVE shift start

ryan.crouch@ligo.org — Sat, 12 Jul 2025 16:06:28 -0700

Author: ryan.crouch@ligo.org

Report ID: 85711

TITLE: 07/12 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 9mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

We've been locked for just over 4 hours
- We had our best range ~30 minutes after locking, I can see ZM4 is drifting a bit mostly in P, but the angle is probably not optimized for being fully thermalized as the ANG servo isn't being used right now
The calibration measurement was not run due to a lockloss, if LLO loses lock I'll drop observing and run the measurement
The SQZ_PMC GRD is reporting the PMC PZT volts are low

Images attached to this report

H1 PEM - HVAC Fan Vibrometers FAMIS Check

ryan.crouch@ligo.org — Sat, 12 Jul 2025 14:58:55 -0700

Author: ryan.crouch@ligo.org

Report ID: 85587

Closes FAMIS26404, last checked in alog85561

Everything looks the same as it did last week.

Images attached to this report

H1 General - Comment to Lockloss @ 17:23 UTC

ryan.short@ligo.org — Sat, 12 Jul 2025 12:28:05 -0700

Author: ryan.short@ligo.org

Report ID: 85710

H1 back to observing at 18:54 UTC.

Fully automatic relock, but I ran an alignment first as things looked pretty far out at the start.

H1 General - Lockloss @ 17:23 UTC

ryan.short@ligo.org — Sat, 12 Jul 2025 10:30:44 -0700

Author: ryan.short@ligo.org

Report ID: 85709

Lockloss @ 17:23 UTC after 8 hrs locked - link to lockloss tool

Looks to be an ETMX glitch about a half second before the lockloss.

Lockloss

Images attached to this report

LHO VE - Sat CP1 Fill

david.barker@ligo.org — Sat, 12 Jul 2025 10:18:17 -0700

Author: david.barker@ligo.org

Report ID: 85708

Sat Jul 12 10:08:39 2025 INFO: Fill completed in 8min 36secs

Images attached to this report

LHO General - Ops Day Shift Start

ryan.short@ligo.org — Sat, 12 Jul 2025 07:46:10 -0700

Author: ryan.short@ligo.org

Report ID: 85707

TITLE: 07/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 1mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY: H1 has been locked and observing for 5.5 hours. Looks like one automatic relock overnight, and currently in a stand down for a candidate event at 14:25.

Wind low, microseism also low and falling
All other systems nominal

H1 General - OPS Friday EVE shift summary

ryan.crouch@ligo.org — Fri, 11 Jul 2025 22:00:37 -0700

Author: ryan.crouch@ligo.org

Report ID: 85705

TITLE: 07/12 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: One lockloss with an easy relock. We've been locked for just over 3.5 hours.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
22:56	LASER	LVEA	LVEA	YES	LVEA IS LASER HAZARD \u0d26\u0d3f(\u239a_\u239a)	14:34
23:03	ISC	Keita	OptLab	N	ISS array work	23:56

23:57 UTC lockloss
- After DRMI struggled, during PRMI I held in PRMI_LOCKED and adjusted PRM by hand, DRMI then locked quickly and the camera spot looked good.
- 01:27 UTC Observing, I ran a SQZ SCAN_ANG before going into observing and adjusted the OPO temperature while relocking

H1 General - Comment to 23:57 UTC lockloss

ryan.crouch@ligo.org — Fri, 11 Jul 2025 18:28:14 -0700

Author: ryan.crouch@ligo.org

Report ID: 85706

01:27 UTC Observing

H1 SUS - Satamp swap OSEM noise part 2 (ITMX, ITMY, SR2)

oli.patane@ligo.org — Fri, 11 Jul 2025 17:36:01 -0700

Author: oli.patane@ligo.org

Report ID: 85699

I ran my damp_regression_compare script (85369) on the suspensions that we swapped the satellite amplifiers for today, BS, PRM, PR3, SRM, and SR3. The results show a decrease in the OSEM noise of at least 2x!

Part of what the script does is save the channel data as a .mat file so it's quicker to run next time, so I'll post that as well as the results.

On Tuesday Fil swapped the sat amps for ITMX, ITMY, and SR2 (85619). Like I did for the first set of satamp swaps (85485), I've used my damp_regression_compare script found in sustrunk to compare the noise performance (85369).

ITMX M0 Results: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGM0/Results/allDampRegressCompare_H1SUSITMX_M0_NoiseComparison_1435482383vs1436080373-1200.pdf r12442 Data: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGM0/Data/dampRegress_H1SUSITMX_M0_1435482383_1200.mat /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGM0/Data/dampRegress_H1SUSITMX_M0_1436080373_1200.mat r12442 R0 Results: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Results/allDampRegressCompare_H1SUSITMX_R0_NoiseComparison_1435482383vs1436080373-1200.pdf r12443 Data: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Data/dampRegress_H1SUSITMX_R0_1435482383_1200.mat /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Data/dampRegress_H1SUSITMX_R0_1436080373_1200.mat r12443

ITMY M0 Results: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Results/allDampRegressCompare_H1SUSITMY_M0_NoiseComparison_1435482383vs1436080373-1200.pdf r12444 Data: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Data/dampRegress_H1SUSITMY_M0_1435482383_1200.mat /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGM0/Data/dampRegress_H1SUSITMY_M0_1436080373_1200.mat r12444 R0 Results: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Results/allDampRegressCompare_H1SUSITMY_R0_NoiseComparison_1435482383vs1436080373-1200.pdf r12445 Data: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Data/dampRegress_H1SUSITMY_R0_1435482383_1200.mat /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Data/dampRegress_H1SUSITMY_R0_1436080373_1200.mat r12445

SR2 Results: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SR2/SAGM1/Results/allDampRegressCompare_H1SUSSR2_M1_NoiseComparison_1435482383vs1436080373-1200.pdf r12446 Data: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SR2/SAGM1/Data/dampRegress_H1SUSSR2_M1_1435482383_1200.mat /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SR2/SAGM1/Data/dampRegress_H1SUSSR2_M1_1436080373_1200.mat r12446

Non-image files attached to this report

allDampRegressCompare_H1SUSITMX_M0_NoiseComparison_1435482383vs1436080373-1200.pdf

allDampRegressCompare_H1SUSITMX_R0_NoiseComparison_1435482383vs1436080373-1200.pdf

allDampRegressCompare_H1SUSITMY_M0_NoiseComparison_1435482383vs1436080373-1200.pdf

allDampRegressCompare_H1SUSITMY_R0_NoiseComparison_1435482383vs1436080373-1200.pdf

allDampRegressCompare_H1SUSSR2_M1_NoiseComparison_1435482383vs1436080373-1200.pdf

H1 General - 23:57 UTC lockloss

ryan.crouch@ligo.org — Fri, 11 Jul 2025 16:59:22 -0700

Author: ryan.crouch@ligo.org

Report ID: 85704

23:57 UTC lockloss

Lockloss

H1 General - Comment to OPS Friday EVE shift start

ryan.crouch@ligo.org — Fri, 11 Jul 2025 16:43:39 -0700

Author: ryan.crouch@ligo.org

Report ID: 85703

23:43 UTC Observing

H1 General - Comment to Lockloss @ 22:23 UTC

ryan.crouch@ligo.org — Fri, 11 Jul 2025 16:43:28 -0700

Author: ryan.crouch@ligo.org

Report ID: 85702

23:43 UTC Observing

LHO General - Ops Day Shift Summary

ryan.short@ligo.org — Fri, 11 Jul 2025 16:28:56 -0700

Author: ryan.short@ligo.org

Report ID: 85701

TITLE: 07/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Two locklosses this shift, but recovery so far has been straightforward. H1 is currently relocking and up to MAX_POWER.

15:41 - Lockloss - alog85685
- 17:06 - Lockloss during LOWNOISE_ASC
18:00 - Observing
22:23 - Lockloss - alog85697

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
22:56	LASER	LVEA	LVEA	YES	LVEA IS LASER HAZARD \u0d26\u0d3f(\u239a_\u239a)	14:34
18:26	ISC	Keita	OptLab	N	ISS array work	19:20
20:16	FAC	Randy	MY	N	Plug in forklift	20:31
20:17	ISC	Jennie	OptLab	Local	ISS array work	20:54
21:50	PEM	RyanC	VacPrepLab	N	Testing dust monitors	22:24
23:03	ISC	Keita	OptLab	N	ISS array work	Ongoing

H1 General - OPS Friday EVE shift start

ryan.crouch@ligo.org — Fri, 11 Jul 2025 16:01:21 -0700

Author: ryan.crouch@ligo.org

Report ID: 85700

TITLE: 07/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 10mph Gusts, 6mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

We are still trying to recover and lock DRMI after a 22:23 UTC lockloss
2ndary microseism is increasing
Wind is low

H1 ISC - Comment to OMC scans with SR3 heater on

jennifer.wright@ligo.org — Fri, 11 Jul 2025 15:56:48 -0700

Author: jennifer.wright@ligo.org

Report ID: 85698

I also analysed the single bounce measurements Elenna and Sheila made after OM2 was heated up. So these have both SR3 and OM2 hot.

For both these measurements C02 was the third highest mode and C01 was the fourth highest. I took 120s starting 45s into the scan.

Measurement 1: 23:40:38 UTC on 2025/05/16 with ITMX aligned and ITMY mis-aligned.

See the spectrum with labelled peaks here.

And the PZT calibration here.

Mode mis-match is:

0.93/( 0.93 + 17.29 ) = 5.10 %

Measurement 2: 23:46:48 UTC on 2025/05/16 with ITMY aligned and ITMX mis-aligned.

See the spectrum with labelled peaks here.

And the PZT calibration here.

100 * 0.56/( 0.56 + 17.62 ) = 3.08 %

Bear in mind that this is assuming that there is no astigmatism in the OMC (since there is but we cannot resolve 02 vs 20 modes). This requires some careful analysis of uncertainties to get useful info about how we should tune for better mode-matching. Watch this space.

Non-image files attached to this report

1431474101_omc_scan_with_estimated_lines_1st____sr3_hot__om2_hot__10w_psl__itmy_mis_aligned.pdf

1431474101_pzt_calib_1st____sr3_hot__om2_hot__10w_psl__itmy_mis_aligned.pdf

1431474471_omc_scan_with_estimated_lines_2nd____sr3_hot__om2_hot__10w_psl__itmx_mis_aligned.pdf

1431474471_pzt_calib_2nd____sr3_hot__om2_hot__10w_psl__itmx_mis_aligned.pdf

H1 General - Lockloss @ 22:23 UTC

ryan.short@ligo.org — Fri, 11 Jul 2025 15:36:51 -0700

Author: ryan.short@ligo.org

Report ID: 85697

Lockloss @ 22:23 UTC after 4.5 hours locked - link to lockloss tool

No obvious cause, but ETMX starts moving strangely about a half a second before the lockloss.

Lockloss

Images attached to this report

H1 SUS - Comment to Satamp swap OSEM noise first looks

oli.patane@ligo.org — Fri, 11 Jul 2025 15:34:21 -0700

Author: oli.patane@ligo.org

Report ID: 85696

Since a few of the before times I picked for some of the suspensions were during times where they had ISC control on, I've rerun them with a better starting time where there was no ISC control

BS
Results: /ligo/svncommon/SusSVN/sus/trunk/BSFM/H1/BS/SAGM1/Results/allDampRegressCompare_H1SUSBS_M1_NoiseComparison_1435154988vs1435435038-1200.pdf r12436
Data: /ligo/svncommon/SusSVN/sus/trunk/BSFM/H1/BS/SAGM1/Data/dampRegress_H1SUSBS_M1_1435154988_1200.mat /ligo/svncommon/SusSVN/sus/trunk/BSFM/H1/BS/SAGM1/Data/dampRegress_H1SUSBS_M1_1435435038_1200.mat r12437

PRM
Results: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PRM/SAGM1/Results/allDampRegressCompare_H1SUSPRM_M1_NoiseComparison_1435154988vs1435435046-1200.pdf
      r12438
Data: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PRM/SAGM1/Data/dampRegress_H1SUSPRM_M1_1435435046_1200.mat      /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/PRM/SAGM1/Data/dampRegress_H1SUSPRM_M1_1435154988_1200.mat
     r12438

SRM
Results: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SRM/SAGM1/Results/allDampRegressCompare_H1SUSSRM_M1_NoiseComparison_1435154988vs1435435046-1200.pdf
      r12441
Data: /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SRM/SAGM1/Data/dampRegress_H1SUSSRM_M1_1435435046_1200.mat     /ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SRM/SAGM1/Data/dampRegress_H1SUSSRM_M1_1435154988_1200.mat
    r12441

Non-image files attached to this report

allDampRegressCompare_H1SUSBS_M1_NoiseComparison_1435154988vs1435435038-1200.pdf

allDampRegressCompare_H1SUSPRM_M1_NoiseComparison_1435154988vs1435435046-1200.pdf

allDampRegressCompare_H1SUSSRM_M1_NoiseComparison_1435154988vs1435435046-1200.pdf

H1 SUS - SR3 M1 to M1 transfer functions with calibrated OSEMs

edgard.bonilla@ligo.org — Fri, 11 Jul 2025 15:12:57 -0700

Author: edgard.bonilla@ligo.org

Report ID: 85695

We grabbed the measurement data that Oli generated on [LHO: 85288] which was taken using the calibrated OSEMINF gains that we obtained by driving the ISI an looking at the OSEM response at high frequencies [see LHO: 84367].

The TL;DR is that the calibration works:

The diagonal elements of the measured and modeled plants now match.
The measured TFs are a bit more symmetric.
We see the expected reduction in cross-couplings to Roll and Pitch.

The .pdf attached can be found in

https://svn.ligo.caltech.edu/svn/sus/trunk/HLTS/H1/SR3/SAGM1/Results/2025-06-24_1900_H1SUSSR3_M1_ALL_TFs.pdf

We can see that the diagonal M1 to M1 modeled and measured transfer functions actually match one another much better than before (for an example uncalibrated plot, click here to see April 2025). This happens even though the calibration did not involve M1 to M1 transfer functions.

We can assess the impact that the calibration had on the M1 to M1 cross-couplings by plotting a normalized version of the cross-coupled transfer functions. For example, the Length-Pitch normalized transfer function will be (L2P)_norm=(L2P)/sqrt(P2P*L2L).

This way we can get rid of the overall scaling factors that come from the OSEM calibration and focus on the cross-coupling. The result is shown in the second attachment. The columns correspond to M1 drives, and the rows are OSEM displacements, all plots are dimensionless. The blue trace is after OSEM calibration, and red is before OSEM calibration, and from 2024/08/08 to avoid the gains that were in the yaw and pitch TEST drive paths in the more recent data [see LHO: 84259].

The cross-couplings of=n this last plot can be broken down into 4 general types of cross-couplings:

1) Things that don't change much (L2T, L2P, etc)- Nothing to say.

2) Cross couplings that improve quite a bit with the calibration. [V2R, V2P R2V, and R2P]. This were what we expected from the original calibration procedure. Especially cross-couplings involving the Roll degree of freedom were expected to improve.

3) Cross couplings that got a bit worse, but were expected [Y2R, Y2V, L2V, and L2R]. These are related to the fact that the average calibration for the LF and RT OSEMs is very different for the three osems atop the suspension T1, T2, and T3. The cross-coupling is not higher, it's just a normalization quirk.

4) Cross-coupling that got worse and was unexpected. Only P2R fits this category. The calibration should make the plant more symmetric, so it is at least good that P2R and R2P seem more similar now. Since the coupling that's changing is going to Roll, we believe this is actually more accurate to the underlying Pitch-Roll plant compared to the results from before.

The next steps for this work are to semi-automate the calibration process, and to methodically deploy the calibration to other suspensions now that the SatAmp work has been done.

SUS

Images attached to this report

Non-image files attached to this report

2025-06-24_1900_H1SUSSR3_M1_ALL_TFs.pdf

X1 SUS - bbssopt parameter set updated

oli.patane@ligo.org — Fri, 11 Jul 2025 12:31:03 -0700

Author: oli.patane@ligo.org

Report ID: 85674

We have finally confirmed that the current BBSS build is stable for both LHO and LLO, and we have figured out the model parameter set that matches the builds, so I've finally gone ahead and merged the parameter changes from the parameter set we had been using as the default for a while, bbssopt_2025_d0plus3p0_l1mins3p0_m2plus0p3_FDRd1plus3p5.m, into bbssopt.m (r12435). The differences between the original FDR parameter set (from T2000599-v1) and this hopefully final set are as follows:

d4 -= 1e-3 Adjustment to get better fit to measurements 76071, 82138
l3 -= 4.5e-3 Loop length change 79004
d1 += 3.5e-3 Equal to blade position = -4mm
m2 += 0.3 Mass added to M2
d0 += 3e-3 Height change of added spacer
l1 -= 3e-3 Wire length change to counter height added by spacer

I have used my compareallbbss_tfs.m script (CSWG:11252) to make comparison plots between the BSFM, the original FDR parameter set from T2000599-v1, and this parameter set. This parameter set has been uploaded to T2000599 as -v4.

H1 General - Latest safety results from November 2024 injections

geoffrey.mo@ligo.org — Fri, 11 Jul 2025 12:16:13 -0700

Author: geoffrey.mo@ligo.org

Report ID: 85694

Here are the latest H1 safety results from the November 2024 injections (sorry for the very long delay): https://drive.google.com/drive/folders/1CgwhWlKpG9CFnaiLvHnF2bWZVyHMN4gz?usp=sharing. It'd be great if folks could take a quick scroll through this spreadsheet (sorted by statistically most unsafe at the top) and see if there are any channels which have been determined to be unsafe (column F) which shouldn't be, or if there are any that should be added to the channel lists. Thanks!

DetChar, INJ

H1 ISC - Comment to OMC scans with SR3 heater on

jennifer.wright@ligo.org — Fri, 11 Jul 2025 11:52:37 -0700

Author: jennifer.wright@ligo.org

Report ID: 85693

First measurement has

1.69/(1.69+15.86) = 9.63 % mode mis-match.

Second measurement has

1.25*100/(1.25 + 16.46) = 7.06 % mode mis-match

LHO VE - Fri CP1 Fill

david.barker@ligo.org — Fri, 11 Jul 2025 11:29:31 -0700

Author: david.barker@ligo.org

Report ID: 85692

Fri Jul 11 10:07:27 2025 INFO: Fill completed in 7min 24secs

Jordan confirmed a good fill curbside.

Images attached to this report

H1 General - Comment to Lockloss @ 15:41 UTC

elenna.capote@ligo.org — Fri, 11 Jul 2025 11:24:26 -0700

Author: elenna.capote@ligo.org

Report ID: 85691

For the lockloss from lownoise ASC, there appears to be some glitch in the suspension channels about 30 seconds before the lockloss, and it appears in all four test mass L2 channels and not in EX L3, suggesting it is coming from the ASC. However, I don't see any glitch in the ASC channels themselves. I also don't know if this caused the lockloss, or is just random. Pointing out in case we see it again.

Images attached to this report

H1 TCS - TCS Monthly Trends FAMIS

oli.patane@ligo.org — Fri, 11 Jul 2025 11:05:25 -0700

Author: oli.patane@ligo.org

Report ID: 85690

Closes FAMIS#28462 , last checked 84837

CO2 Trends (ndscope1)

Everything is looking good

HWS Trends (ndscope2)

Everything is generally looking good, with both ITMX and ITMY SLEDPOWERMON slowly going down, which they tend to do. The only possible concern I can see would be that zooming out to almost a year ago (ndscope3), it looks like the level that ITMX SLEDPOWERMON is at now is a lower value than it has been in the past year.

Images attached to this report

H1 General - Comment to Lockloss @ 15:41 UTC

ryan.short@ligo.org — Fri, 11 Jul 2025 11:02:30 -0700

Author: ryan.short@ligo.org

Report ID: 85689

Back to observing at 18:00 UTC.

BS and PRM needed adjustment during DRMI locking, but no initial alignment was run. Also had an unknown lockloss during LOWNOISE_ASC, so acquisition took a bit longer this time.

H1 ISC - PIMON running on CR computer

elenna.capote@ligo.org — Fri, 11 Jul 2025 10:45:09 -0700

Author: elenna.capote@ligo.org

Report ID: 85688

Since we had a few PI-caused locklosses last week, we realized that the PI monitor (PIMON) didn't seem to be running properly and saving the data 524 kHz DCPD data at the end of the lock. TJ has been trying to debug the issue. In the meantime, I have left PIMON running on a control room computer that I am logged into, and the lockloss data is being saved into /ligo/gitcommon/labutils/PIMON/locklosses and the script plot_locklosses.py in /ligo/gitcommon/labutils/PIMON can be used to plot the data from the locklosses.

Fortunately, we haven't had any PI locklosses that we know of since last week. Whenever control room computers are rebooted, we need to restart the script.

Lockloss

H1 ISC - Comment to DARM Offset Steps while changing CO2s

jennifer.wright@ligo.org — Fri, 11 Jul 2025 09:45:22 -0700

Author: jennifer.wright@ligo.org

Report ID: 85687

Camilla pointed out its annular heating we are changing with the C02s here, not central.

H1 ISC - DRMI and PRMI Acquisition Timers Doubled

ryan.short@ligo.org — Fri, 11 Jul 2025 09:07:27 -0700

Author: ryan.short@ligo.org

Report ID: 85686

To allow for the longer acquisition times we've been seeing to catch D/PRMI despite good-looking alignment and buildups, I've doubled the timers in ISC_LOCK for DRMI to try PRMI and PRMI to try MICH_FRINGES from 10 minutes to 20 minutes each. Changes have been loaded and committed to SVN.

OpsInfo

H1 General - Lockloss @ 15:41 UTC

ryan.short@ligo.org — Fri, 11 Jul 2025 08:52:14 -0700

Author: ryan.short@ligo.org

Report ID: 85685

Lockloss @ 15:41 UTC after 18 hours locked - link to lockloss tool

No obvious cause that I can see.

Lockloss

H1 PSL - PSL Status Report - Weekly

ryan.short@ligo.org — Fri, 11 Jul 2025 08:20:08 -0700

Author: ryan.short@ligo.org

Report ID: 85684

FAMIS 26430

Laser Status:
    NPRO output power is 1.853W
    AMP1 output power is 70.03W
    AMP2 output power is 140.2W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 23 days, 22 hr 6 minutes
    Reflected power = 23.42W
    Transmitted power = 105.4W
    PowerSum = 128.8W

FSS:
It has been locked for 0 days 18 hr and 23 min
TPD[V] = 0.7448V

ISS:
The diffracted power is around 3.7%
Last saturation event was 0 days 21 hours and 23 minutes ago

Possible Issues:
PMC reflected power is high

H1 CDS - Comment to Early report on HWS cameral control

evan.goetz@ligo.org — Fri, 11 Jul 2025 07:53:32 -0700

Author: evan.goetz@ligo.org

Report ID: 85683

Excellent, thank you Camilla and Dave! This is very helpful.DetChar

LHO General - Ops Day Shift Start

ryan.short@ligo.org — Fri, 11 Jul 2025 07:42:13 -0700

Author: ryan.short@ligo.org

Report ID: 85682

TITLE: 07/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 10mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY: H1 has been locked and observing for 17 hours.

Wind moderately low, microseism rising but still low
ALl other systems nominal

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Thu, 10 Jul 2025 21:59:26 -0700

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 85681

TITLE: 07/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

IFO is in NLN and OBSERVING since 21:43 UTC (7 hr lock!)

Extremely quiet shift in which there were no saturations, no SQZ drops and 1 Superevent!

Nothing else to report

LOG:

None

H1 General - Ops Day Shift End

oli.patane@ligo.org — Thu, 10 Jul 2025 16:54:38 -0700

Author: oli.patane@ligo.org

Report ID: 85680

TITLE: 07/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Currently Observing at 145Mpc and have been Locked for 2 hours. Wind seems to be coming down.

Lots of struggles relocking today after the 17:54 lockloss due to increase of winds and gusts as well as issues with treh ALSX crystal frequency. Eventually made it up.

LOG:

14:30UTC Observing and Locked for 11 hours
15:00 Out of Observing for Commissioning
17:54 Lockloss
    - Issues with ALSX crystal frequency
    - Issues with wind
    - Ran IA
    - Many lower level locklosses from wind and ALSX crystal frequency
    - Lockloss from TRANSITION_FROM_ETMX due to wind
21:43 NOMINAL_LOW_NOISE
21:48 Observing

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
22:56	LASER	LVEA	LVEA	YES	LVEA IS LASER HAZARD \u0d26\u0d3f(\u239a_\u239a)	14:34
14:35	FAC	Randy	EX	n	Pump alignment (14:30)	16:40
14:36	FAC	Chris, Eric	XARM	n	Beam tube sealing	15:43
15:05	PEM	Robert	LVEA	YES	Checking if measurement is working	16:13
15:48	FAC	Tyler	X1, XARM	n	Looking at box and joints	16:48
16:32	FAC	Nellie	OpticsLab	n	Tech clean	16:36
17:23	PEM	Robert, Sam	LVEA	YES	Measurement setup	18:06
17:37	EPO	Jonathan, EJ	Roof	n	Tour?	17:42
17:58		Jennie	LVEA	YES	Telling PEM team about lockloss	18:06
22:55	ISC	Keita	OpticsLab	y(local)	ISS array	00:25

H1 CDS - Comment to Early report on HWS cameral control

camilla.compton@ligo.org — Thu, 10 Jul 2025 16:33:12 -0700

Author: camilla.compton@ligo.org

Report ID: 85678

Looking at the HWS camera data, Dave's code was successfully stopping the HWS camera dueing NLN from 27th June, as expected 85373.

However, looking at the f-scans from the last week, the 2Hz comb was there until 3rd July but was gone on 4th July and hasn't returned since.

Nothing HWS related should have changed on the 3rd July (ops shift log 85519).

DetChar, TCS

Images attached to this report

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Thu, 10 Jul 2025 16:24:23 -0700

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 85679

TITLE: 07/10 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 26mph Gusts, 9mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 21:43 UTC

Conditions look great except for slightly high winds (same as yesterday). Have been in the control room for about an hour and there have been no SQZ locklosses!

H1 SUS - Comment to ITMY R0 alignment tramp brought back to 30sec from 300

oli.patane@ligo.org — Thu, 10 Jul 2025 14:51:24 -0700

Author: oli.patane@ligo.org

Report ID: 85677

Accepted in Observing

Images attached to this report

H1 General - Comment to Lockloss

oli.patane@ligo.org — Thu, 10 Jul 2025 14:50:59 -0700

Author: oli.patane@ligo.org

Report ID: 85676

21:48 Back to Observing after accepting SDF diffs that revert the SQZ ADF changes since those were just for commissioning (CSSQZ, LSC0)

Images attached to this report

H1 SQZ - Comment to Start of a SQZ Data set, checked OPO temp and NLG

elenna.capote@ligo.org — Thu, 10 Jul 2025 14:40:04 -0700

Author: elenna.capote@ligo.org

Report ID: 85675

I ran a script that pulls the full 524 kHz OMC DCPD A and B channels during the no squeezing time. The data that was saved was 10 minutes of no squeezing data. I saved the data into .gwf files at the full rate, and another downsampled to 64 kHz.

The data is saved in /ligo/home/elenna.capote/OMC_DCPD/251007-102149_xcorr_data as OMC_DCPD_{A,B}_{524,64}.gwf which can be easily read by gwpy. Unfortunately I can't upload them here because the alog doesn't accept this file format, but I can pass it along to you as necessary if you don't have control room access.

H1 ISC - Comment to OMC scans with SR3 heater on

jennifer.wright@ligo.org — Thu, 10 Jul 2025 12:09:12 -0700

Author: jennifer.wright@ligo.org

Report ID: 85661

Finally got round to fitting the two single bounce mode scans done with SR3 hot and OM2 cold. The first we had ITMX aligned, the second we switched to ITMY aligned.

These can currently be processed using OMCscan.py in the /dev branch for the labutils/omcscan repository at /ligo/gitcommon/labutils/omc_scan, you need to have activated the labutils conda environment to do so.

The call statements for the data processing are:

python OMCscan.py 1431449762 130 "1st 1431449762 - SR3 hot, 10W PSL, ITMY mis-aligned" "single bounce" -s -v -o 2 -m

python OMCscan.py 1431450536 140 "2nd 1431450536 - SR3 hot, 10W PSL, ITMX mis-aligned" "single bounce" -s --verbose -m -o 2

For each measurement the tag -s specifices that the sidebands were not on and so in order to calibrate the PZT the code uses the two TM00 modes and then you have to tell it in what height order the 10 and 20 modes appear relative to the highest peak which will be one of the 00 modes.

def identify_C02(self):

"""If in single bounce configuration, and with sidebands off,

identify 10 and 20 modes in order to improve fit.

Assumes that

OMCscan.identify_peaks()

and

OMCscan.identify_carrier_00_peaks()

have already been run.

Output:

-------

self.peak_dict: dictionary

first set of keys are carrier, 45 upper, 45 lower

second set of keys are TEM mode, e.g. "00", "01", "20", etc.

third set of keys is the fsr number

"""

# Create temporary dictionary to combine into self.peak_dict

peak_dict = {}

peak_dict["carrier"] = {"10": {}, "20": {}}

#print(peak_dict)

nn = [2, 1]

mm = 0

#freq_diff = np.empty(np.size(self.peak_frequencies)) not sure why this line here.

#set frequency to be that of third largest peak.

first_order = np.argsort(self.peak_heights)[-4]#-4 for second meas.

second_order = np.argsort(self.peak_heights)[-3]#change index to match where 20 is in terfirst meas if measuring from start of scan.ms of peak height.

#print(third_larg)

for ii, peak_freq in enumerate(self.peak_frequencies):

if peak_freq == self.peak_frequencies[second_order]:

#print("found C02")

#print(f"List fields in IFO {self.fields_MHz}")

#print(type(self.fields_MHz))

#print(f"OMC HOM spacing {self.omc_hom} MHz")

#print(type(self.omc_hom))

field = f"carrier"

#print(f"mode {field}{nn[0]}{mm}")

peak_dict[field]["20"][-1] = {

"height": self.peak_heights[ii],

"voltage": self.peak_pzt_voltages[ii],

"frequency": self.peak_frequencies[ii],

"true_frequency": np.mod((self.fields_MHz - (nn[0] + mm) * self.omc_hom), self.omc_fsr),

"label": r"$c_{20}$",

}

self.peak_ided[ii] = 1

elif peak_freq == self.peak_frequencies[first_order]:

field = f"carrier"

peak_dict[field]["10"][-1] = {

"height": self.peak_heights[ii],

"voltage": self.peak_pzt_voltages[ii],

"frequency": self.peak_frequencies[ii],

"true_frequency": np.mod((self.fields_MHz - (nn[1] + mm) * self.omc_hom), self.omc_fsr),

"label": r"$c_{10}$",

}

self.peak_ided[ii] = 1

else:

continue

# Merge dictionaries

#if not "20" in peak_dict["carrier"].keys():

self.peak_dict["carrier"] = {**self.peak_dict["carrier"], **peak_dict["carrier"]}

#print(self.peak_dict)

#print(self.peak_ided)

return

For both measurements I only took slightly over 1 FSR of the data, this is because in order to fit a polynomial to the known peaks (allowing us to calculate the PZT non-linearity), the code assumes the 1st order is the 3rd highest and 2nd order is the 4th highest. In the code above you need to change the indexes in the below lines to match the height order of the peaks (ie. and index of -4 is fourth highest peak).

first_order = np.argsort(self.peak_heights)[-4]

second_order = np.argsort(self.peak_heights)[-3]

When the mode-matching is bad this may not be true, also if there are multiple FSRs in the scan this also may not be true.

First measurement 1st order mode is fifth highest, 2nd order mode is third highest. The scan is here. I took 130 s of data. The PZT fit is here.

Second measurement the 1st order mode was the 4th highest, 2nd order mode was the third highest. The scan is here. I took 140s of the scan data. The PZT fit is here.

Non-image files attached to this report

1431449762_omc_scan_with_estimated_lines_1st_1431449762___sr3_hot___10w_psl__itmy_mis_aligned.pdf

1431450536_omc_scan_with_estimated_lines_2nd_1431450536___sr3_hot___10w_psl__itmx_mis_aligned.pdf

1431449762_pzt_calib_1st_1431449762___sr3_hot___10w_psl__itmy_mis_aligned.pdf

1431450536_pzt_calib_2nd_1431450536___sr3_hot___10w_psl__itmx_mis_aligned.pdf

H1 ISC - Locking ALS instability

elenna.capote@ligo.org — Thu, 10 Jul 2025 11:50:25 -0700

Author: elenna.capote@ligo.org

Report ID: 85673

There appears to be an instability when locking ALS. The X arm green build up and ASC signals begin to shake as the DARM gain is ramped to 40 and then 400. This caused multiple locklosses until we held at green arms for a longer convergence time before going to locking ALS. I have attached a screenshot of the successful lock but the oscillation still occurred. Maybe the extra WFS convergence time ensures the green controls are more robust against the darm gain change. We should look into this.

Images attached to this report

H1 SQZ - Start of a SQZ Data set, checked OPO temp and NLG

camilla.compton@ligo.org — Thu, 10 Jul 2025 11:49:46 -0700

Author: camilla.compton@ligo.org

Report ID: 85669

Jennie, Elenna, Camilla, Matt

Plan was to take data roughly following 83594 with more mid-sqz data points (adjusting sqz angle to every 50degrees or so looks good).

We lost lock while doing this, maybe from some compression plate moving ringing up ASC 85670.

DTT saved as camilla.compton/Documents/sqz/templates/dtt/20250710_SQZdata.xml and screenshot attached.

Starting angle at 141deg

Type	Time (UTC)	Angle	DTT Ref	Notes
No SQZ	17:21:30 - 17:31:30	N/A	ref 0
FIS Mean SQZ (no ADF)	17:40:00 - 17:43:00	N/A	ref 1
FIS Mid SQZ +50deg	17:49:00 - 17:52:00	(-) 191	ref 2
~~FIS Mid SQZ +100deg~~	~~17:53:00 - 17:56:00~~	~~(-) 241~~	~~ref 3~~	Scatter shelf and Lockloss

Checked the NLG before and after adjusting the OPO crystal temp the normal way, using the SEED beam.

OPO Setpoint	Amplified Max	Amplified Min	UnAmp	Dark	NLG	OPO Gain	Note
80uW	0.0518		0.007026	-1.35e-5	7.35	-8	Before changing OPO temp, to match Kevins data
80uW	0.083055	0.0023519	0.007026	-1.35e-5	11.8	-8	With changing OPO temp

Sheila and Matt found that we get different temperature optimizations when optimizing the SEED beam or the RF6 with OPO locked. We tested this out again by checking the NLG again before and after using Sheila's new 85532 SCAN_OPOTEMP OPO GRD state, with a silightly increased range (0.015 rather than 0.01 and 180s rather than 120s), see plot in exports/SQZ/GRD/OPOTEMP_SCAN/. It adjusted temp -0.002deg, the NLG did not change, stayed at ~11.8.

Images attached to this report