aLIGO LHO Logbook

H1 General - Lock loss 2237 UTC

thomas.shaffer@ligo.org — Thu, 24 Jul 2025 15:41:25 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85970

1437431869

Ending a 21 hour lock. No obvious cause, lock loss tool analyzing.

H1 SEI - ISI CPS Noise Spectra Check - Weekly

ryan.short@ligo.org — Thu, 24 Jul 2025 15:29:33 -0700

Author: ryan.short@ligo.org

Report ID: 85969

FAMIS 26053, last checked in alog85829

The script reports BSC high frequency noise is elevated for the following sensors:

ITMY_ST1_CPSINF_H3

Non-image files attached to this report

CPS_spectra_15:22-07_24_2025.pdf

H1 PSL - PSL 10-Day Trends

ryan.short@ligo.org — Thu, 24 Jul 2025 15:15:23 -0700

Author: ryan.short@ligo.org

Report ID: 85967

FAMIS 31095

Late to this check this week, but not too much to report. Jason's incursion last week for an FSS tuneup (alog85769) is clearly seen, and generally things have been stable since. Only strangeness is a noisier FSS TPD signal as of about 2 days ago, which I looked a little closer into.

Zooming in on the FSS TPD signal during an observing period (see second to last attachment), these look to be brief jumps in power on the TPD on the order of 20-30mV that I don't see evidence of anywhere else; AMP2 output, PMC output, and ISS actuation all seem nominal during these times. These jumps look to be happening constantly any time the IFO is at or above the 'LOCKING_ALS' steps, and it was during this step during relocking after Tuesday maintenance when the jumps first started. The only thing that changed during Tuesday's maintenance period that might have an effect is the sat amp modifications to MC1 and MC3 (alog85922), possibly changing something about the IMC's feedback to the FSS? See final attachment for behavior while the IFO is unlocked and the FSS TPD signal goes quiet. I've been watching the RefCav REFL camera spot while these jumps happen, and I do notice a very slight shift of the spot, but not a change in shape. I'm not sure how to explain this behavior or why it would have started, but at least so far it hasn't seemed to be much of a "problem," although I'll be keeping an eye on it.

Images attached to this report

H1 ISC - Stepping OMC ASC loop offsets to improve optical gain

jennifer.wright@ligo.org — Thu, 24 Jul 2025 14:47:15 -0700

Author: jennifer.wright@ligo.org

Report ID: 85966

Summary: I didn't see any conclusive difference that showed we could get an improvement from a change in a particular direction. Since the optical gain moves around so much its hard to see the effect of small or quick changes. It might be worth doing a longer test were we step these offsets in sets of three different values per dof (3*4 steps) and do each for five mins (~ 1 hour).

I orginally was trying to use the results of our last injection (2025-06-16 20:41:15 UTC to2025-06-16 21:01:57 UTC ) to determine how to change the OMC ASC alignment.

Using /ligo/home/jennifer.wright/git/2025/OMC_Alignment/20250116_OMC_Alignment_EXC.xml we injected four low frequency lines into H1:OMC-ASC_{POS,ANG}_{X,Y}_EXC - these channels come after the filter banks (ASC-OMC_A_PIT_OFFSET, then ASC-OMC_B_PIT_OFFSET, then ASC-OMC_A_YAW_OFFSET, then ASC-OMC_B_YAW_OFFSET) where the nominal offsets are set. The injection is at four different frequencies (0.0113, 0.0107, 0.0097 and 0.0103 Hz).

The analysis then involves looking at the 410 Hz line height on the OMC DCPD SUM to interpret the effect on optical gain.

However it is not clear from this plot that the full range of phase space has been looked at - ie we have not changed the offset with a large enough amplitude to check their current position is optimal.

Thus today I stepped ASC-OMC_A_PIT_OFFSET, then ASC-OMC_B_PIT_OFFSET, then ASC-OMC_A_YAW_OFFSET, then ASC-OMC_B_YAW_OFFSET - these filter banks are before the ones used above in the model and are the ones where the offset for the QPDs is set. In the

Towards the last three measurements we realised that we need to do larger changes ~0.04 counts to see a change in kappa C then wait for 3-4 mins. On the long term trend none of these changes seemed to produce any meausurable gain, but it would be good to repeat this measurement with longer times spent at each step and perhaps go in slightly larger steps.

The ndscope template is in /ligo/home/jennifer.wright/git/2025/OMC_Alignment/20250724_change _offsets_by_hand.yaml

Images attached to this report

H1 ISC - Amount of Locklosses per day and percentage of ETM GLITCH Locklosses has not significantly increased

camilla.compton@ligo.org — Thu, 24 Jul 2025 14:42:16 -0700

Author: camilla.compton@ligo.org

Report ID: 85968

Between Dec 2024 and Feb 2025, 20% of our Observe locklosses were tagged ETM_GLITCH, see 82609.

Since then we've roughly had the same amount of OBSERVE locklosses per day, and the same percentage of ETM_GLICH locklossses.

The amount of locklosses per day in the last 10 days is slightly increased, but not much.

1st March - 1st April (32 days) 14/75 (2.3 LL/day) = 19% ETM_GLITCH
11th - 29th June (18 days): 9/42 (2.3 LL/day) = 22% ETM_GLITCH
1st to 24th July (24 days): 13/60 (2.5 LL/day) = 22% ETM_GLITCH

Looking just in the last 10 days where we feel we've been having more locklosses:

July 14th to 24th (10 days): 6/29 (2.9 LL/day) = 21% ETM_GLITCH

ISC, Lockloss

H1 AOS - Comment to Investigation of Lock losses due to Earthquakes

preeti.sharma@ligo.org — Thu, 24 Jul 2025 12:04:26 -0700

Author: preeti.sharma@ligo.org

Report ID: 85964

After removing EQ events which happend during the locklosses, the probability of surviving lock during an EQ in O2 winter was found to be 54%, O3b winter was 64%, O4a winter was 73% and O4b winter was 41%.

H1 CAL - L2 Calibration line height lowered

elenna.capote@ligo.org — Thu, 24 Jul 2025 11:47:52 -0700

Author: elenna.capote@ligo.org

Report ID: 85963

I lowered the L2 calibration line height by a factor of 2.2- the measurement uncertainty was around 0.0007, and our target is 0.002. Now the uncertainty seems to lie around 0.0016. I updated the guardian and SDF with the new injection amplitude- 3.5.

H1 DetChar - Comment to 20.2 Hz line appeared Jun 9, turns on and off

timothy.ohanlon@ligo.org — Thu, 24 Jul 2025 11:20:00 -0700

Author: timothy.ohanlon@ligo.org

Report ID: 85959

I looked briefly into the 20 Hz Noise without much success. Comparing the floor accelerometers, the noise is louder in the EBAY than the LVEA (although the signal of the EBAY accelerometer doesn't look good since the vent). The next closest is HAM1 followed by BS. So the noise is around the -X-Y corner of the LVEA, likely in the EBAY, Transition Area or Optics Lab because HAM6 sees less motion than HAM1 and EBAY sees the most.

Images attached to this report

H1 CAL - Comment to Calibration Sweep

elenna.capote@ligo.org — Thu, 24 Jul 2025 10:55:05 -0700

Author: elenna.capote@ligo.org

Report ID: 85962

I (with help and input from Sheila and Joe B) pushed a new calibration today before this report was run.

First, we tried pushing the 20250628T190643Z report, but again that "failed" because the broadband showed a higher uncertainty than expected, again. The kappa C value also dropped from 0.993 before the push to 0.985 after the push and TDCF burn in. We puzzled over this for a bit, until I brought up that maybe this report is too out of date to be useful. We also had to make minor ring heater changes to avoid PIs just after this report had been generated. Sheila trended the optical gain and saw that it did decrease by about 1% after we changed the ring heater.

So, I took a look at the report from 20250719T225835Z, and it looked very promising. The sensing function fit residual showed it was much more flat than the 6/28 report. I pushed this report next, and after burn in kappa C returned to be about 0.993. The broadband also showed this was a better calibration. We think this is improved, and we will stick with this calibration!

Open questions: why is the error still at 2% at 20 Hz? Can we improve the optical gain further?

Images attached to this report

H1 CAL - Calibration Sweep

thomas.shaffer@ligo.org — Thu, 24 Jul 2025 10:47:59 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85961

Ran a broad band (171106UTC), then a simulines. This was after running a serparate bb and start of a simulines that I had to bail out of because I had not gone back to NLN_CAL_MEAS. This allowed Elenna and Sheila to decide on something else and we reran after they made some changes.

Simulines start:

PDT: 2025-07-24 10:16:43.573765 PDT
UTC: 2025-07-24 17:16:43.573765 UTC
GPS: 1437412621.573765

Simulines end:
PDT: 2025-07-24 10:40:03.824053 PDT
UTC: 2025-07-24 17:40:03.824053 UTC
GPS: 1437414021.824053

Files:

2025-07-24 17:40:03,654 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250724T1
71644Z.hdf5
2025-07-24 17:40:03,661 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_2025
0724T171644Z.hdf5
2025-07-24 17:40:03,666 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_2025
0724T171644Z.hdf5
2025-07-24 17:40:03,670 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_2025
0724T171644Z.hdf5
2025-07-24 17:40:03,675 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_2025
0724T171644Z.hdf5

Images attached to this report

Non-image files attached to this report

H1_calibration_report_20250724T171644Z.pdf

H1 SQZ - Comment to SQZ Dataset for 10kHz

camilla.compton@ligo.org — Thu, 24 Jul 2025 09:25:49 -0700

Author: camilla.compton@ligo.org

Report ID: 85960

Sheila and Matt point out that the HOM at 5kHz and 10kHz are clear to see, see attached.

Images attached to this report

H1 SQZ - SQZ Dataset for 10kHz

camilla.compton@ligo.org — Thu, 24 Jul 2025 09:19:05 -0700

Author: camilla.compton@ligo.org

Report ID: 85957

Sheila, Camilla

Took data roughly following 83594 with the aim of saving H1:OMC-DCPD_524K_A2_IN1 data with the PD sum after TJ changed the matrix as in 85937.

DTT saved as /ligo/home/camilla.compton/sqz/templates/dtt/20250724_SQZdata.xml screenshot attached and /ligo/home/sheila.dwyer/Noise_Budget_repos/quantumnoisebudgeting/data_files/higher_order_modes_sqzdataset.xml screenshot attached.

Note that the calibration was pushed during this FIS Mid SQZ data so CAL_DELTAL should be taken with a grain of salt.

Type	Time (UTC)	Angle	DTT Ref in SQZ	DTT ref in HOM
No SQZ	15:20:00 -15:37:00	N/A	ref 0	ref 0,1
FIS Mean SQZ (no ADF)	15:44:30 - 15:49:30	N/A	ref 1	ref 2,3
FIS ASQZ	15:52:30 - 15:55:30	(+)245	ref 2	ref 4,5
FIS Mid + SQZ	15:57:00 - 16:00:00	(-) 260	ref 3	ref 6,7
FIS Mid - SQZ	16:30:00 - 16:03:30	(-) 110	ref 4	ref 8,9
FIS SQZ (tuned for high freq)	16:06:00 - 16:09:00	(-) 150	ref 5	ref 10,11

Checked the NLG with 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.09708	0.002293	0.007017	-2.58e-5	13.8	-8	With changing OPO temp

Images attached to this report

H1 SQZ - Comment to instructions to get high frequency cross corelation data

thomas.shaffer@ligo.org — Thu, 24 Jul 2025 08:46:00 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85958

The python script wouldn't run at first, narrowed it down to the channels it uses. Since these are test points, they were already opened by something else and so the script couldn't use it. I had to clear the test points, via "diag -l -c" then "tpclear 179 *" then it would run. The script and dtt were run at 821PT and saved in the same template.

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Thu, 24 Jul 2025 07:30:25 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85956

TITLE: 07/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 1mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: Locked for 13 hours. Temps look good, no alarms, calm environment. Planned calibration and commissioning time today from 1500-1930UTC (0800-1230PT).

H1 General - OPS Wednesday EVE shift summary

ryan.crouch@ligo.org — Wed, 23 Jul 2025 22:00:13 -0700

Author: ryan.crouch@ligo.org

Report ID: 85949

TITLE: 07/24 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: One lockloss with an automated recovery. We've been locked for 3.5 hours.
LOG: NO log.

00:07 UTC Observing, there was a big YAW excursion and ringdown seen in ASC during INJECT_SQZING
00:08 UTC lockloss
- 01:36 UTC Observing

H1 ISC - Comment to Locklosses with YAW ASC Excursion

ryan.crouch@ligo.org — Wed, 23 Jul 2025 20:32:03 -0700

Author: ryan.crouch@ligo.org

Report ID: 85955

Both of these YAW ASC locklosses saw TMSX_Y start oscillating a few seconds before the lockloss.

07/23 03:50UTC: YAW ASC excursion
07/23 10:49UTC: YAW ASC excursion

Images attached to this report

H1 General - Comment to 00:08 UTC lockloss

ryan.crouch@ligo.org — Wed, 23 Jul 2025 18:09:34 -0700

Author: ryan.crouch@ligo.org

Report ID: 85954

Looking at all the suspicious things together, it looks like TMSX_Y started moving first before any of the ASC loops? Only ~100ms before CSOFT started moving.

Images attached to this report

H1 SUS - Comment to Satamp swap OSEM noise part 3 (PR2, MC2)

oli.patane@ligo.org — Wed, 23 Jul 2025 18:00:27 -0700

Author: oli.patane@ligo.org

Report ID: 85953

The comparisons for the rest of this swap set (TMSX, ETMX M0/R0/L0) have been posted as 85952

H1 SUS - Satamp swap OSEM noise part 3.5 (TMSX, ETMX M0/R0/L1)

oli.patane@ligo.org — Wed, 23 Jul 2025 17:59:37 -0700

Author: oli.patane@ligo.org

Report ID: 85952

These are the remainder of the noise comparison plots for before and after the sat amp swaps for TMSX and ETMX M0/R0/L1. These swaps were done for TMSX, ETMX M0/R0/L1, MC2, and PR2 on July 15 (85770). I posted noise comparison plots for MC2 and PR2 (85786), but we didn't yet have a good 'after' time where End X wasn't in maintenance, going through an earthquake, or moving stuff around for relocking. Now we have had a good time stretch, so here are the results:

Note: For ETMX L1, there are no DAMP channels, so instead I looked at the WIT_{L,P,Y} channels. Not sure how accurate these are. The edits to make this possible in the script /ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/damp_regression_compare.m have been svn'd as r12483

TMSX Results /ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/TMSX/SAGM1/Results/allDampRegressCompare_H1SUSTMSX_M1_NoiseComparison_1435150628vs1437199319-1200.pdf r12479 Data /ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/TMSX/SAGM1/Data/dampRegress_H1SUSTMSX_M1_1435150628_1200.mat /ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/TMSX/SAGM1/Data/dampRegress_H1SUSTMSX_M1_1437199319_1200.mat r12479

ETMX M0 Results /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGM0/Results/allDampRegressCompare_H1SUSETMX_M0_NoiseComparison_1435060998vs1436769334-1200.pdf r12480 Data /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGM0/Data/dampRegress_H1SUSETMX_M0_1435060998_1200.mat /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGM0/Data/dampRegress_H1SUSETMX_M0_1436769334_1200.mat r12480

R0 Results /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGR0/Results/allDampRegressCompare_H1SUSETMX_R0_NoiseComparison_1435060998vs1436769334-1200.pdf r12841 Data /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGR0/Data/dampRegress_H1SUSETMX_R0_1435060998_1200.mat /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGR0/Data/dampRegress_H1SUSETMX_R0_1436769334_1200.mat r12481

L1 Results /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGL1/Results/allDampRegressCompare_H1SUSETMX_L1_NoiseComparison_1435060998vs1436769334-1200.pdf r12482 Data /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGL1/Data/dampRegress_H1SUSETMX_L1_1435060998_1200.mat /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGL1/Data/dampRegress_H1SUSETMX_L1_1436769334_1200.mat r12482

Non-image files attached to this report

allDampRegressCompare_H1SUSTMSX_M1_NoiseComparison_1435150628vs1437199319-1200.pdf

allDampRegressCompare_H1SUSETMX_M0_NoiseComparison_1435060998vs1436769334-1200.pdf

allDampRegressCompare_H1SUSETMX_R0_NoiseComparison_1435060998vs1436769334-1200.pdf

allDampRegressCompare_H1SUSETMX_L1_NoiseComparison_1435060998vs1436769334-1200.pdf

H1 ISC - Comment to Locklosses with YAW ASC Excursion

elenna.capote@ligo.org — Wed, 23 Jul 2025 17:48:37 -0700

Author: elenna.capote@ligo.org

Report ID: 85950

The lockloss that Ryan S. reports as being from a sitewide power glitch in this alog had a similar behavior in the suspension channels and yaw loops. Apparently the power glitch that caused the lockloss also tripped the HEPI pumps, but I'm not sure how that relates to the control loop behavior. I'm not sure if this is useful to link with these other locklosses or not.

Generally, every yaw ASC loops sees this behavior, but it's hard to tell what is moving first, or the most, since the channels are not calibrated into useful units. As a note, the soft loops are not DC coupled, so I imagine they are just following the other loops. Our lockloss scopes plot the very slow ASC channels, so here is a faster plot of some of the ASC channels before one of these locklosses. The centering loop signals are moving away from zero, but not large enough that the beam is at the edge of the WFS.

I broke out my old TMS servo scope to see if we are being pulled off the TMS QPDs. Clearly the X TR B yaw signal is increasing, but it may be because it's trying to follow a large movement in the hard loops. TMS X yaw moves about 1 urad before the lockloss as well.

In the first yaw excursion lockloss Camilla notes above, the ETMX HEPI RZ appears to oscillate in the two seconds before lockloss. I don't see that in the other yaw excursion lockloss though.

Images attached to this report

H1 General - Comment to 00:08 UTC lockloss

ryan.crouch@ligo.org — Wed, 23 Jul 2025 17:43:23 -0700

Author: ryan.crouch@ligo.org

Report ID: 85951

PRC2 and CSOFT Yaw stepped out right before the LL. TMSX_Y started to oscillate 4 seconds before the LL, PM1_Y had an excursion ~3 seconds before the LL.

Images attached to this report

H1 General - 00:08 UTC lockloss

ryan.crouch@ligo.org — Wed, 23 Jul 2025 17:09:30 -0700

Author: ryan.crouch@ligo.org

Report ID: 85948

00:08 UTC lockloss after only 4 minutes, wiggle in PR_GAIN right before we lost lock

Lockloss

H1 ISC - Comment to Correlated noise budget with Jitter subtraction

elenna.capote@ligo.org — Wed, 23 Jul 2025 16:55:45 -0700

Author: elenna.capote@ligo.org

Report ID: 85947

And here is a text file that contains the frequency vector and correlated noise ASD (the red trace in this plot) in units of strain.

Non-image files attached to this report

correlated_noise_asd.txt

H1 ISC - Comment to Correlated noise budget with Jitter subtraction

elenna.capote@ligo.org — Wed, 23 Jul 2025 16:46:12 -0700

Author: elenna.capote@ligo.org

Report ID: 85946

As another follow up on the gaussianity of the data, I made a spectrogram of the rayleigh statistic of each DCPD signal. Based on my (relatively new) understanding of the rayleigh statistic, I believe these plots are indicating that the DCPD data is fairly gaussian in the broadband, with one large glitch about halfway through the data set. This is the glitch that I discuss excising above.

Images attached to this report

LHO General - Ops Day Shift End

thomas.shaffer@ligo.org — Wed, 23 Jul 2025 16:27:29 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85934

TITLE: 07/23 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 lock losses and a longer recovery for the second thanks to an earthquake. We are on our way back right now, locking DRMI.
LOG:

1313 GRB E583131 - Fermi 774969189
1446 GRB E583144 - Fermi 774974742
1815 Lock loss - 1437329730
1945 Observing
2057 Lock loss - 1437339457
- Not the cause of the lock loss, but an earthquake rolled in just after reacquisition started and delayed that process.
- Once the ground motion settled we tried locking for ~1 hour with DRMI unsuccessfully. Ended up running an initial alignment even though we had many good looking flashes.
- During initial alignment, had to intervene and move SRM in yaw for SRY to catch.

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
21:06	SAF	LVEA IS LASER HAZARD	LVEA	Y	LVEA IS LASER HAZARD	22:03
16:15	CDS	Fil, Marc	MY	n	Pick up from H2, drop off at MY	16:52
17:14	-	Betsy	Opt Lab	n	Parts and such	17:43
20:13	-	Randy	EX	n	Checking in lab space	20:49

H1 General - OPS Wednesday EVE shift start

ryan.crouch@ligo.org — Wed, 23 Jul 2025 16:08:31 -0700

Author: ryan.crouch@ligo.org

Report ID: 85945

TITLE: 07/23 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 18mph Gusts, 12mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:

We're still coming back from the most recent lockloss
At the end of an intial alignment
Its a little windy out

H1 General - Lock loss 2057UTC

thomas.shaffer@ligo.org — Wed, 23 Jul 2025 14:27:42 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85944

1437339457

No immediate, obvious cause.

H1 ISC - Comment to Correlated noise budget with Jitter subtraction

elenna.capote@ligo.org — Wed, 23 Jul 2025 13:52:10 -0700

Author: elenna.capote@ligo.org

Report ID: 85943

I am adding a comment to clarify that the thermal noise budget uses a Ti:Ta loss angle of 3.89e-4 rad, in line with the Gras 2020 paper, to calculate the coating thermal noise. My 35% increase estimate is therefore 1.35 * 1.13e-20 m/rtHz (at 100 Hz) = 1.52e-20 m/rtHz (at 100 Hz).

The O4 detector paper includes a full demonstration of the thermal noise budget, where the thermal noise is dominated by coating brownian noise, which is determined partially by the Ti:Ta loss angle. Therefore, I am assuming that if the overall thermal noise is higher by 35%, it is because the coating thermal noise is higher by 35%. I didn't make any fit of the slope, but the ratio of the noise with the thermal noise trace is fairly flat from 100-300 Hz.

H1 CAL - Updating pydarm release to tag 20250723.0

joseph.betzwieser@ligo.org — Wed, 23 Jul 2025 11:23:20 -0700

Author: joseph.betzwieser@ligo.org

Report ID: 85940

I'm followed the pydarm deployment instructions here, to update the LHO pydarm install. This is the 20250723.0 tag for pydarm, which includes an option to not generate the broadband vs sweep vs uncertainty budget plot. This is intended to be only used if for some reason NDS is unable to serve the H1:GDS-CALIB_STRAIN data used in the plot, which would crash or hang the code. If NDS is having issues, a problem report should be made to the CDS group. This is not the default cds conda environment, but the default you get when typing pydarm at a command line, or specifically invoking by running "conda activate /ligo/groups/cal/conda/pydarm".CAL

H1 General - Lockloss

oli.patane@ligo.org — Wed, 23 Jul 2025 11:16:08 -0700

Author: oli.patane@ligo.org

Report ID: 85939

Lockloss at 2025-07-23 18:15 UTC after almost 5.5 hours locked

Lockloss

H1 ISC - Comment to pimon minor changes

thomas.shaffer@ligo.org — Wed, 23 Jul 2025 11:07:59 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85938

Apparently, it struggles to save the time series data and will freeze up. I've changed it back to only save the PSDs on lockloss and we'll see if it survives better.

H1 SQZ - instructions to get high frequency cross corelation data

sheila.dwyer@ligo.org — Wed, 23 Jul 2025 10:43:11 -0700

Author: sheila.dwyer@ligo.org

Report ID: 85937

Writting this down for tomorow because we may have to repeat this at some point. We'd like to get a cross correlation measurement to high frequency when the IFO has been thermalized for 4+ hous. Tomorow we can do this earlier in the lock if need be to make sure that everything works.

From sitemap OMC > DCPD TEST (at the bottom of list), open the INMTRX circled here, add a 1 where shown here

Take SQZ_MANAGER to NO_SQUEEZING

cd /ligo/home/sheila.dwyer/Noise_Budget_repos/quantumnoisebudgeting

open dtt template in /data_files/higher_order_modes.xml run it at roughly the same time that you run this script adapted from Elena 85817

conda activate labutils

python get_OMCDCPS_524kHz.py

save the dtt template when finished.

Side note, it seems that we can only access two of these 524kHz test points with the script, and also only two at a time with dtt. So we will use dtt to save the sum spectra and the script to save the inidividual PDs.

Images attached to this report

LHO VE - Wed CP1 Fill

david.barker@ligo.org — Wed, 23 Jul 2025 10:23:42 -0700

Author: david.barker@ligo.org

Report ID: 85936

Wed Jul 23 10:09:09 2025 INFO: Fill completed in 9min 5secs

Richard confirmed a good fill via camera.

Images attached to this report

H1 ISC - Locklosses with YAW ASC Excursion

camilla.compton@ligo.org — Wed, 23 Jul 2025 08:47:11 -0700

Author: camilla.compton@ligo.org

Report ID: 85935

In 85846 on Friday 18th, Elenna notes a lockloss after YAW ASC excursion, we have been having very short locks and I see evidence of two more of these yaw excursion in the last 24 hours:

07/23 00:27UTC: Differnt type of LL, caused by small EQ plus some wind?
07/23 03:50UTC: YAW ASC excursion, Plot of L2 Quads, Plot of ASC signals
07/23 06:25UTC: Different type ofg LL, unsure why.
07/23 10:49UTC: YAW ASC excursion, Plot of L2 Quads, Plot of ASC signals

Seen in CSOFT, SRC1, PRC2 and mainly on the L2 stage of quads. In the last 1-2 seconds before LL.

Lockloss

Images attached to this report

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Wed, 23 Jul 2025 07:31:04 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85933

TITLE: 07/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 2mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY: Locked for 1.5 hours, a few automated lock losses and reacquisitions over the last shift. Plans for today are...Observing!

H1 General - OPS Tuesday day shift summary

ryan.crouch@ligo.org — Tue, 22 Jul 2025 22:00:47 -0700

Author: ryan.crouch@ligo.org

Report ID: 85930

TITLE: 07/23 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Two locklosses, we're still coming back from the second one. We just lost it at CARM_OFFSET_REDUCTION at 04:57.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
21:06	SAF	LVEA IS LASER HAZARD	LVEA	Y	LVEA IS LASER HAZARD	22:03
23:47	CAL	Tony, Rick	PCAL lab	LOCAL	Checks	00:26

00:28 UTC Lockloss from an Earthquake alog85928
- 00:44 UTC A gust of wind made us lose lock during CHECK_MICH and the IMC struggled to relock and we were staying at 10Ws, I had to request us back to 2Ws. I wrote a decorator for this scenario but it seems like we only put it in a place that would catch this during Initial Alignment alog83552
- 01:30 - 01:50 UTC Initial alignment
03:50 UTC lockloss after only 1:07, no clear reason

H1 General - 03:50 UTC lockloss

ryan.crouch@ligo.org — Tue, 22 Jul 2025 20:51:48 -0700

Author: ryan.crouch@ligo.org

Report ID: 85932

03:50 UTC lockloss

Lockloss

H1 General - Comment to 00:28 UTC lockloss

ryan.crouch@ligo.org — Tue, 22 Jul 2025 19:54:54 -0700

Author: ryan.crouch@ligo.org

Report ID: 85931

02:46 UTC Observing

H1 ISC - Correlated noise budget with Jitter subtraction

elenna.capote@ligo.org — Tue, 22 Jul 2025 19:12:10 -0700

Author: elenna.capote@ligo.org

Report ID: 85899

This work was completed with help from Sheila Dwyer, Derek Davis, and Vicky Xu.

Sheila and Oli took 3000 seconds of no squeezing data on June 25 which I have used to run a correlated noise budget. This alog is long, but it details my methods to take this measurement while accounting for glitches, excess jitter noise and unsubtracted noise. I then discuss generating a noise budget using this data, and investigate the thermal noise level. There are many great background references for how the correlated noise is measured, but one of my favorites is Martynov et al. (2017).

I used the OMC DCPD A and B channels at 16 kHz, so this alog focuses on the correlated noise up to 5 kHz. Sheila is currently working on correlated noise measurements at higher frequency using the full-rate DCPD channels.

Executive summary:

These results show that above 1 kHz, the correlated noise is well-estimated by jitter noise from 1-2 kHz and our current frequency noise projection from 2-4 kHz. Above 4 kHz it appears we are overestimating the frequency noise, something that we could improve with a model of the CARM loop. Above 2 kHz, the frequency noise level is roughly a factor of 6-7 below DARM in amplitude. Jitter peaks are within a factor of 2-3 in amplitude from 1-2 kHz. The classical noise floor from 100-300 Hz appears similar to coating thermal noise with an amplitude that is 35% higher than our noise budget estimates. Below 100 Hz, we have not fully estimated our classical noise in the budget.

Jitter subtraction:

From 100-1000 Hz, I was able to use a strong jitter injection to estimate a transfer function and subtract the jitter noise from OMC DCPD A and B using IMC WFS A yaw as a single witness. The subtraction performed fairly well, with the exception that it injected a large peak just above 300 Hz where the jitter noise injection coherence dropped. I was also unable to get a strong enough measurement of the jitter coupling above 1 kHz so two broad jitter peaks remain in the data from 1-2 Hz. I applied a 1 kHz low pass to the subtraction to ensure that I only subtracted in the region with a high-fidelity measurement of the jitter transfer function.

Calculating the correlated noise:

I used a function written by Sheila and Vicky that applies the DARM OLG and sensing function using pydarm and the calibration model. The DARM OLG is applied to the correlated noise calculation using a formula written by Kiwamu Izumi in T1700131, equation 10. The resulting noise is calibrated into meters using the sensing function. I applied this correlated noise estimation method to the DCPD signals with and without jitter subtraction.

Managing bias from glitches:

Since the correlated noise budget requires taking a long data set, it is likely that the data will capture glitches which can bias the PSD and CSD estimates for the calculation, and possibly inflate the noise estimate. There are several methods that can be used to overcome this bias (gating, median averaging, etc). First, I found it useful to plot a whitened timeseries of each DCPD using the gwpy whitening function. This made it evident that there was one large glitch about halfway through the dataset. The gwpy gating function identified a 2 second period over which to gate. However, since the gating period was of a similar length to my fft length, I ended up choosing to reject the fft segments that included the glitch completely. I took a mean average of the remaining fft segments for the PSD and CSD estimates. Note that my method includes no overlap, which loses some resolution, but makes this calculation easier.

Accounting for unsubtracted incoherent noise:

For 3000 seconds of data, an fft length of 2 seconds, and two rejected PSD segments, the total number of averages is 1498. The largest possible amount of noise reduction in this method is sqrt(sqrt(1498)) = 6.2. This is sufficient to resolve the classical noise below 1 kHz, but not above. There are a few ways to improve the resolution for a fixed length. One is to reduce the fft length further to increase averages, since less frequency resolution is required at high frequency anyway (this is only useful if you don't care about your low frequency resolution). This plot shows a test of that, using different fft lengths for the same data length, with incoherent noise reduction ranging from a factor of 4.1 (fft length 10 s) to 8.8 (fft length 0.5 s).

You can also compare the correlated noise of the DCPDs (XCOR) with the noise in DCPD sum (SUM). The difference between these two noise estimates is the reduction of the incoherent noise (n), achieved in the correlated noise by the known factor of the number of averages (N). In other words, both noise estimates contain the same amount of classical noise (c).

SUM = c + n

XCOR = c + n/sqrt(N)

c = (XCOR - SUM/sqrt(N)) / (1 - 1/sqrt(N))

Without sacrificing the frequency resolution below 1 kHz, we can measure the classical noise above 1 kHz by accounting for any un-reduced incoherent noise. I compare a correlated noise estimate using this formula with my shortest fft length from above. For the rest of this post, I refer to this as the "full classical noise estimate"

Therefore, this work includes three different estimates of the correlated noise, one without jitter subtraction, one with jitter subtraction from 100-1000 Hz, and one with jitter subtraction and the application of my equation above. This plot compares these estimates with the unsqueezed DARM (aka SUM). All of these estimates use what I am referring to as the "excised mean average", which is the process I detailed above of excising ffts with glitches and mean-averaging the remainder.

Creating the noise budget:

I then added some of our noise budget traces: thermal noise, laser noise (frequency and intensity), controls noise (ASC and LSC), residual gas noise, and a correlated quantum noise trace generated using SQZ parameters from Sept 2024 (some likely out of date). Comparing these traces, it is evident that we have a large gap between our full classical noise estimate and our estimate of our known noises. First noise budget plot here

Evan Hall and Kevin Kuns did a similar exercise using pre-O4 data, alog 68482, and calculated that the thermal noise is approximately 30% higher than our estimate. I find a similar result using the jitter-subtracted correlated noise- the noise level from 100-300 Hz matches well with a thermal noise that is about 35% higher than our noise budget estimate, here is a ratio of the full classical noise estimate with the CTN estimate. I also find that the noise in this region is fairly gaussian. For example, I plotted the distribution of the ffts of the jitter-subtracted correlated noise at 105 Hz and their distribution matches a chi-squared distribution with two degrees of freedom (of course, this ignores the two outlier fft segments that contain the glitch). I referenced Craig Cahillane's dissertation appendix D: the PSD sample mean for gaussian noise with n samples follows a chi-squared distribution of 2n degrees of freedom. This should at least help convince us that the noise level here isn't being biased by some non-gaussian source; this was a concern that Vicky and I had when generating the correlated noise budget in the O4 detector paper.

I also recreated the noise budget with the thermal noise trace inflated by 35% here. Except for some unsubtracted jitter noise that I did not include in the budget, this effectively reconciles the correlated noise budget above 100 Hz.

These results show that we have also underestimated the noise below 100 Hz. It is not clear to me yet how much of that noise can be explained with a better estimate of the correlated quantum noise. Sheila and I are hoping to use some of the parameters she is generating from her sqz modeling to calculate possible lower and upper bounds of the correlated quantum noise and compare them with the entire correlated noise budget.

Non-image files attached to this report

whitened_DCPD_timeseries.pdf

short_ff_bias_comparison.pdf

correlated_noise_bias_comparison.pdf

correlated_noise_budget_as_is.pdf

ctn_ratio.pdf

correlated_noise_budget_high_CTN.pdf

fft_distribution.pdf

fft_length_test.pdf

H1 CDS - Comment to CDS Maintenance Summary: Tuesday 22nd July 2025

david.barker@ligo.org — Tue, 22 Jul 2025 17:41:38 -0700

Author: david.barker@ligo.org

Report ID: 85929

The ETMY Sat Amp swap this morning was completed in 15 minutes, meaning the HWWD did not complete its 20 minute count-down.

It appears that the false-positive HWWD rate for ETMY increased with the new Sat Amps, unlike ETMX where they have disappeared, or the ITMs where the rates were unchanged.

ETMY HWWD STAT and COUNTDOWN trends show below.

Images attached to this report

H1 General - 00:28 UTC lockloss

ryan.crouch@ligo.org — Tue, 22 Jul 2025 17:29:47 -0700

Author: ryan.crouch@ligo.org

Report ID: 85928

00:28 UTC lockloss potentially from a 5.5 from the eastern Russian peninsula.

Lockloss

H1 CDS - CDS Maintenance Summary: Tuesday 22nd July 2025

david.barker@ligo.org — Tue, 22 Jul 2025 17:12:52 -0700

Author: david.barker@ligo.org

Report ID: 85927

WP12691 Install production GC/CDS network switch

Jonathan, Nyath:

The production Juniper GC/CDS network switch was installed and the temporary Brocade switch removed. The control room phones were transferred one at a time to verify the switch port configuration.

WP12690 Vacuum HAM1 Ion Pump Readout

Gerardo, Patrick:

For the past few months the IP13 EPICS channels have actually been reading out IP1_B's signals, and IP7_A which has actually been reading out the new IP13 signals.

Patrick made the internal hardware mapping Beckhoff changes on h0vacmr to map IP13 with its signals.

In the new system there is no IP7, but we elected to keep these channels in place so that recent HAM1's Ion Pump data can be trended using the IP7_A chans.

Attached plot shows IP13 (blue) transistioning from IP1_B (orange) to IP7_A (green)

WP12689 Add two 512Hz fast channels for HLTS PR3,SR3

Jeff, Brian, Edgard, Oli, Dave:

This morning we started updating the h1suspr3 and h1sussr3 models but the number of DAQ changes was significantly more than the expected two additional fast channels per model so we needed to review the changes in detail. Here is what I found

In sus/common/models three files were changed (svn version numbers shown):

HLTS_MASTER_W_EST.mdl production=r31259 new=32426

SIXOSEM_T_STAGE_MASTER_W_EST.mdl production=r31287 new=32426

ESTIMATOR_PARTS.mdl production=r31241 new=32426

HLTS_MASTER_W_EST.mdl:

only change is to the DAQ_Channels list, added two chans M1_ADD_[P,Y]_TOTAL

SIXOSEM_T_STAGE_MASTER_W_EST.mdl:

At top level, change the names of the two ESTIMATOR_HXTS_M1_ONLY blocks:

PIT -> EST_P

YAW -> EST_Y

Inside the ADD block:

Add two testpoints P_TOTAL, Y_TOTAL (referenced by HLTS mdl)

ESTIMATOR_PARTS.mdl:

Rename block EST -> FUSION

Rename filtermodule DAMP_EST -> DAMP_FUSION

Rename epicspart DAMP_SIGMON -> OUT_DRIVEMON

Rename testpoint DAMP_SIG -> OUT_DRIVE

DAQ_Channels list changed according to the above renames.

DAQ Changes:

This results in a large number of DAQ changes for SR3 and PR3. For each model:

+496 slow chans, -496 slow chans (rename of 496 channels).

+64 fast chans, -62 fast chans (add 2 chans, rename 62 chans).

Work Rescheduled:

We ran out of time this morning so the h1suspr3, h1sussr3 model restarts and DAQ restart has been rescheduled for next Tuesday, 29th July.

Images attached to this report

H1 General - Quick oscillations during Observing

oli.patane@ligo.org — Tue, 22 Jul 2025 16:44:43 -0700

Author: oli.patane@ligo.org

Report ID: 85926

Elenna, Camilla, TJ, Matt, Oli

A few hours into a lock stretch we suddenly had a couple of large oscillations come in (ndscope1). They happened at 1437260896 for 2 seconds and at 1437260919 for 2 seconds. There were no saturations and our range did not drop more than 10 Mpc the next minute.

In DARM (ndscope2), the frequency of these oscillations is between 5.7-6 Hz. In the QUAD MASTER_OUT (ndscope3) and ASC (ndscope4, ndscope5) channels, the oscillation frequency is around 2.5 Hz. In the QUAD oplev channels (ndscope6), the oscillation frequency is around 2.5 Hz, and it's seen in all quads except ITMX. There is also a slight delay between when the quads move, with ITMY looking like it moved first.

DetChar, ISC, SUS

Images attached to this report

LHO General - Ops Day Shift End

thomas.shaffer@ligo.org — Tue, 22 Jul 2025 16:30:20 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85914

TITLE: 07/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Long list of maintenance activities checked off for the day (Trello board). Relocking was uneventful, I tried playing with some gains and timers to help catch DRMI faster but I'm unsure this actually helped. We've been observing for 3.5 hours.

Relocking after maintenance
- Initial alignment went fully auto
- DRMI was taking longer than expected considering the amount of triggers and good flashes that we were getting. This has been the norm lately, but still not the norm for O4. I tried changing some LSC gains and filter trigger times (mostly MICH & PRCL). I'm not sure if it was just coincidence or my changes helped, but more PRCL gain (12->15) and a lower PRCL trig time (0.2->0.15) is where it eventually caught. I did not save these changes.
2006 Observing

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
21:06	SAF	LVEA IS LASER HAZARD	LVEA	Y	LVEA IS LASER HAZARD	22:03
14:58	CDS/GC	Jonathan	MSR	n	GC switch swap	15:24
15:01	PCAL	Tony, Francisco	PCAL lab	yes	Prep for todays meas	15:18
15:02	FAC	Chris, Eric	Ends, Mids, Mech room	n	Fan lubing	16:36
15:05	FAC	Nelly	LVEA	yes	Tech clean	16:16
15:06	SEI	Jim	EY, EX	n	HEPI accumulator checks	17:32
15:07	FAC	Randy, Mitchell	high bay	n	Fork lift and crane equipment	17:29
15:09	VAC	Jordan, Janos	MY, EY	n	Turbopump functionality testing	18:09
15:11	-	Betsy	LVEA	yes	Parts hunt	15:47
15:12	IAS	Jason	LVEA	yes	FARO health check	18:01
15:16	CDS/SUS	Fil	EY	n	sat amp swap	16:02
15:17	SUS	Oli	CR	n	Sat amp swap tests, SR3 meas.	18:26
15:22	VAC	Norco	EX	n	LN2 fill	17:17
15:26	VAC	Gerardo	FCTE	n	Measuring cables	16:03
15:28	PCAL	Tony, Francisco, Tooba	EY	YES	PCAL meas.	17:38
15:31	CDS	Richard	CER Mezz, LVEA	Yes	Check on OMC PZT power supply	16:03
15:32	SQZ	Camilla, Leo, Jennie	LVEA	YES	SQZT7 work	19:18
15:33	CDS	Marc, Erik	CER Mezz	yes	Power supply swap for ITM esds	16:26
15:42	VAC	Janos	MX	n	Looking at LN2 with contractor	16:06
15:47	-	Betsy	EY, EX	n	Checking on safety space	16:02
15:51	CDS/VAC	Patrick	Office	n	PLC code update on h0vacmr	16:31
16:06	VAC	Janos	MY, MX	n	Checking on vac stuffs	17:29
16:07	VAC	Gerardo	EX	n	Checking and maybe fixing vac stuff	16:36
16:17	FAC	Nelly	EX	n	Tech clean	17:16
16:38	CDS/SUS	Fil, Marc	LVEA	yes	MC1,MC3 sat amp swap	17:02
16:44	FAC	Eric	MY	n	Damper fix	18:02
17:13	FAC	Chris	Mids, Ends, LVEA	YES	Checking for tanks	18:45
17:16	FAC	Nelly	FCES	n	Tech clean	18:02
17:19	-	Mike, Kim, guest	LVEA	yes	Tour	18:36
17:28	VAC	Gerardo, Jordan	LVEA	yes	Checking on AIP BSC	18:03
17:34	CDS	Fil, Marc	CER	yes	OMC PZT power supply swap	18:02
17:34	FAC	Tyler	Mids	n	3IFO checks	18:34
17:53	PCAL	Tony, Francisco	PCAL lab	yes	Setup meas.	18:06
18:11	CDS	Marc	LVEA	yes	Check on beir garten sat boxes	18:59
18:14	FAC	Nelly	EY	n	Tech clean	18:48
18:54	OPS	Tony	LVEA	yes	LVEA sweep	18:59
20:00	FAC	Eric	EY	n	Check on hvac	20:40
22:46	-	Camilla, Leo, Leo's family	OSB roof	n	Looking out from the roof	23:02

H1 General - OPS Tuesday EVE shift start

ryan.crouch@ligo.org — Tue, 22 Jul 2025 16:19:00 -0700

Author: ryan.crouch@ligo.org

Report ID: 85925

TITLE: 07/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 6mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

We've been locked for a little over 3 hours
The wind isn't too bad and is forecast to stay the same if not reduce
Secondary microseism looks stable at just under the 50th percentile, maybe a slight increase over the past 2 hours
The 1-3Hz ground motion is unusually high, the last time it was this high was 05/31 to 06/01

H1 SUS - Weekly In-Lock SUS Charge Measurement FAMIS

ryan.crouch@ligo.org — Tue, 22 Jul 2025 16:14:42 -0700

Author: ryan.crouch@ligo.org

Report ID: 85920

Closes FAMIS28415, last checked in alog85784.

All 4 charge measurements were able to run this morning. ETMX has a fairly large error for it Veff and Veff2, everything else looks similar to the last measurement.

SUS

Images attached to this report

H1 SUS - Comment to Top Sat Amps Modified: MC1, MC3, and ETMY (MO, RO, TMS)

oli.patane@ligo.org — Tue, 22 Jul 2025 14:27:29 -0700

Author: oli.patane@ligo.org

Report ID: 85924

Once the new satamps were installed, I ran the script satampswap_bestpossible_filterupdate_ECR_E2400330.py to update the compensation filters for these suspensions. These 'best possible' compensation gains come from the tests Jeff did on each satamp before installation, which are found in /ligo/svncommon/SusSVN/sus/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Results/.

My input and the corresponding output is below:

oli.patane@cdsws27:/ligo/svncommon/SusSVN/sus/trunk/Common/PythonTools$ py satampswap_bestpossible_filterupdate_ECR_E2400330.py -o TMSY ETMY_M0_R0 All updated filters grabbed for TMSY TMSY M1 F1 compensation filter updated to zpk([5.3],[0.0969],1,"n") TMSY M1 F2 compensation filter updated to zpk([5.28],[0.0964],1,"n") TMSY M1 F3 compensation filter updated to zpk([5.2],[0.095],1,"n") TMSY M1 LF compensation filter updated to zpk([5.26],[0.096],1,"n") TMSY M1 RT compensation filter updated to zpk([5.17],[0.0945],1,"n") TMSY M1 SD compensation filter updated to zpk([5.26],[0.0961],1,"n") write /opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSTMSY.txt Done writing updated filters for TMSY All updated filters grabbed for ETMY ETMY R0 F1 compensation filter updated to zpk([5.2],[0.0951],1,"n") ETMY R0 F2 compensation filter updated to zpk([5.2],[0.0951],1,"n") ETMY R0 F3 compensation filter updated to zpk([5.25],[0.0959],1,"n") ETMY R0 SD compensation filter updated to zpk([5.35],[0.098],1,"n") ETMY M0 F1 compensation filter updated to zpk([5.31],[0.0971],1,"n") ETMY M0 F2 compensation filter updated to zpk([5.27],[0.0965],1,"n") ETMY M0 F3 compensation filter updated to zpk([5.22],[0.0955],1,"n") ETMY M0 SD compensation filter updated to zpk([5.17],[0.0946],1,"n") ETMY M0 LF compensation filter updated to zpk([5.2],[0.0951],1,"n") ETMY M0 RT compensation filter updated to zpk([5.28],[0.0965],1,"n") ETMY R0 LF compensation filter updated to zpk([5.29],[0.0967],1,"n") ETMY R0 RT compensation filter updated to zpk([5.26],[0.0962],1,"n") write /opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSETMY.txt Done writing updated filters for ETMY All done! Remember to double check and load in the filters for ['TMSY', 'ETMY_M0_R0'] oli.patane@cdsws27:/ligo/svncommon/SusSVN/sus/trunk/Common/PythonTools$ py satampswap_bestpossible_filterupdate_ECR_E2400330.py -o MC1 MC3 All updated filters grabbed for MC1 MC1 M1 RT compensation filter updated to zpk([5.13],[0.0937],1,"n") MC1 M1 SD compensation filter updated to zpk([5.25],[0.096],1,"n") MC1 M1 T1 compensation filter updated to zpk([5.26],[0.0962],1,"n") MC1 M1 T2 compensation filter updated to zpk([5.18],[0.0947],1,"n") MC1 M1 T3 compensation filter updated to zpk([5.32],[0.0972],1,"n") MC1 M1 LF compensation filter updated to zpk([5.12],[0.0938],1,"n") write /opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSMC1.txt Done writing updated filters for MC1 All updated filters grabbed for MC3 MC3 M1 T3 compensation filter updated to zpk([5.32],[0.0972],1,"n") MC3 M1 LF compensation filter updated to zpk([5.19],[0.0949],1,"n") MC3 M1 RT compensation filter updated to zpk([5.35],[0.0979],1,"n") MC3 M1 SD compensation filter updated to zpk([5.19],[0.0949],1,"n") MC3 M1 T1 compensation filter updated to zpk([5.31],[0.097],1,"n") MC3 M1 T2 compensation filter updated to zpk([5.24],[0.0958],1,"n") write /opt/rtcds/userapps/release/sus/h1/filterfiles/H1SUSMC3.txt Done writing updated filters for MC3 All done! Remember to double check and load in the filters for ['MC1', 'MC3']

After this I loaded in these new filters.

H1 ISC - Comment to Nonsens Jitter Cleaning updated

elenna.capote@ligo.org — Tue, 22 Jul 2025 14:09:02 -0700

Author: elenna.capote@ligo.org

Report ID: 85923

Here is a ratio comparison plot, showing the ratio of CLEAN / NOLINES for an observing time last night and today. We're still thermalizing, so this may change slightly. Matt and I adjusted the plot colors and alpha so the old cleaning is on the bottom and you can see where we are no longer injecting extra noise, and also where the cleaning has improved slightly, especially for the peaks at a few hundreds of Hz.

Non-image files attached to this report

compare_ratios.pdf

H1 SUS - Top Sat Amps Modified: MC1, MC3, and ETMY (MO, RO, TMS)

filiberto.clara@ligo.org — Tue, 22 Jul 2025 14:07:45 -0700

Author: filiberto.clara@ligo.org

Report ID: 85922

WP 12696
ECR E2400330
Drawing D0901284-v5
Modified List T2500232

The following SUS SAT Amps were upgraded per ECR E2400330. Modification improves the whitening stage to reduce ADC noise from 0.05 to 10 Hz. The EY PUM and UIM SAT Amps were NOT upgraded.

Suspension	Old	New	OSEM
ETMY MO	S1100098	S1100088	F1F2F3SD
ETMY MO/RO	S1100079	S1100083	RTLF/RTLF
ETMY RO	S1100087	S1000281	F1F2F3SD
TMSY	S1100172	S1100148	F1F2F3LF
TMSY	S1100107	S1100172	RTSD
MC1	S1100128	S1100118	T1T2T3LF
MC1/MC3	S1000292	S1000287	RTSD/T1T2
MC3	S1000297	S1100119	T3LFRTSD

F. Clara, J. Kissel, O. Patane, M. Pirello

H1 TCS - 10.215kHZ PI that we pass over during Thermlalization

camilla.compton@ligo.org — Tue, 22 Jul 2025 13:46:48 -0700

Author: camilla.compton@ligo.org

Report ID: 85921

TJ noticed the DCPD signals rising ~25 minutes into the lock, we found this was a PI t 10.215kHz. Matt notes that we've seen this at the start of each lock even before we changed the ring heaters last. It just damps down again by itself, we expect as the HOM pass over it. Plots attached. This PI doesn't appear to be in our monitored PI list.

ISC

Images attached to this report

H1 General - EndY Station

anthony.sanchez@ligo.org — Tue, 22 Jul 2025 13:29:59 -0700

Author: anthony.sanchez@ligo.org

Report ID: 85919

Francisco, Tooba, and I went to EY today to do an End Y PCAL End Station measurement.

We followed the Procedure outlined in T1500062-v19.
Beamspot before we started

Ran the following script & the out put follows:
(pcal_env) anthony.sanchez@cdsws31: python generate_measurement_data.py --WS PS4 --date 2025-07-21
/ligo/gitcommon/Calibration/pcal/O4/ES/scripts/pcalEndstationPy/generate_measurement_data.py:52: SyntaxWarning: invalid escape sequence '\R'
log_entry = f"{current_time} {command} \Results found here\: {results_path}\n"
Reading in config file from python file in scripts
../../../Common/O4PSparams.yaml
PS4 rho, kappa, u_rel on 2025-07-21 corrected to ES temperature 299.2 K :
-4.702207423037734 -0.0002694340454223 3.166921849830658e-05
Copying the scripts into tD directory...
Connected to nds.ligo-wa.caltech.edu
martel run
reading data at start_time: 1437237350
reading data at start_time: 1437237810
reading data at start_time: 1437238140
reading data at start_time: 1437238500
reading data at start_time: 1437238870
reading data at start_time: 1437239200
reading data at start_time: 1437239330
reading data at start_time: 1437240000
reading data at start_time: 1437240340
Ratios: -0.5346791724911457 -0.543267360018835
writing nds2 data to files
finishing writing
Background Values:
bg1 =        18.235622; Background of TX when WS is at TX
bg2 =        5.180516; Background of WS when WS is at TX
bg3 =        18.271548; Background of TX when WS is at RX
bg4 =        5.304736; Background of WS when WS is at RX
bg5 =        18.324199; Background of TX
bg6 =        -0.468829; Background of RX

The uncertainty reported below are Relative Standard Deviation in percent

Intermediate Ratios
RatioWS_TX_it      = -0.534679;
RatioWS_TX_ot      = -0.543267;
RatioWS_TX_ir      = -0.527180;
RatioWS_TX_or      = -0.534309;
RatioWS_TX_it_unc = 0.063072;
RatioWS_TX_ot_unc = 0.066352;
RatioWS_TX_ir_unc = 0.058208;
RatioWS_TX_or_unc = 0.055534;
Optical Efficiency
OE_Inner_beam                      = 0.986071;
OE_Outer_beam                      = 0.983489;
Weighted_Optical_Efficiency        = 0.984780;

OE_Inner_beam_unc                  = 0.047991;
OE_Outer_beam_unc                  = 0.047969;
Weighted_Optical_Efficiency_unc    = 0.067854;

Martel Voltage fit:
Gradient = 1637.880346;
Intercept = 0.388593;

Power Imbalance = 0.984192;

Endstation Power sensors to WS ratios::
Ratio_WS_TX = -0.927690;
Ratio_WS_RX = -1.383303;

Ratio_WS_TX_unc = 0.053210;
Ratio_WS_RX_unc = 0.043963;

=============================================================
============= Values for Force Coefficients =================
=============================================================

Key Pcal Values :
GS = -5.135100; Gold Standard Value in (V/W)
WS = -4.702207; Working Standard Value

costheta     =      0.988362; Angle of incidence
c            =      299792458.000000; Speed of Light

End Station Values :
TXWS         =        -0.927690; Tx to WS Rel responsivity (V/V)
sigma_TXWS   =        0.000494; Uncertainity of Tx to WS Rel responsivity (V/V)
RXWS         =        -1.383303; Rx to WS Rel responsivity (V/V)
sigma_RXWS   =        0.000608; Uncertainity of Rx to WS Rel responsivity (V/V)

e = 0.984780; Optical Efficiency
sigma_e = 0.000668; Uncertainity in Optical Efficiency

Martel Voltage fit :
Martel_gradient = 1637.880346; Martel to output channel (C/V)
Martel_intercept = 0.388593; Intercept of fit of Martel to output (C/V)

Power Loss Apportion :
beta          =        0.998844; Ratio between input and output (Beta)
E_T          =        0.991787; TX Optical efficiency
sigma_E_T          =        0.000336; Uncertainity in TX Optical efficiency
E_R          =        0.992935; RX Optical Efficiency
sigma_E_R          =        0.000337; Uncertainity in RX Optical efficiency

Force Coefficients :
FC_TxPD          =        9.152859e-13; TxPD Force Coefficient
FC_RxPD          =        6.233084e-13; RxPD Force Coefficient
sigma_FC_TxPD          =        5.803098e-16; TxPD Force Coefficient
sigma_FC_RxPD          =        3.482293e-16; RxPD Force Coefficient
data written to ../../measurements/LHO_EndY/tD20250722/

This produced:
Martel_Voltage_test.png
WS_at_TX.png
WS_at_RX.png
WS_at_RX_BOTH_BEAMS.png
These dont look unreasonable, so we ran the End station trends report script to give us the LHO_EndY_PD_ReportV5.pdf.

Images attached to this report

Non-image files attached to this report

Sosb-office25072213010.pdf

LHO_EndY_PD_ReportV5.pdf

H1 ISC - Nonsens Jitter Cleaning updated

elenna.capote@ligo.org — Tue, 22 Jul 2025 13:16:00 -0700

Author: elenna.capote@ligo.org

Report ID: 85913

[Matt, Jenne, Elenna]

Matt and I tried running a new jitter training on CALIB STRAIN CLEAN, and noticed that we could likely subtract a bit more jitter noise from CLEAN, and also probably reinject less noise, especially around the power lines. We then reran a training on NOLINES to prepare to apply the new cleaning today.

Jenne then walked me through how to generate the script which would update the cleaning parameters. I copied over the old observe.snap file, in case I made a mistake and need to revert to the old coefficients.

Once we were in observing, I ran Jenne's template which checks how the cleaning is performing. It definitely looks like it is doing a good job. I accepted the new parameters. Once we are locked for a little longer, I will generate some comparison plots to the old cleaning parameters.

Images attached to this report

H1 SUS - Measuring SR3 OLG TFs to get DAMP filter compensation gains

oli.patane@ligo.org — Tue, 22 Jul 2025 12:54:28 -0700

Author: oli.patane@ligo.org

Report ID: 85918

Ivey used the ISO calibration measurements that I took earlier (85906) to calculate what the OSEMINF gains should be on SR3 (85907), and this script also calculates what it thinks the compensation gain in the DAMP filter bank should be.
The next step is to use OLG TFs to measure what values we would use in the DAMP filter bank to compensate for the change in OSEMINF gains, and we can compare them to the calculated values to see how close they are.

I took two sets of OLG measurements for SR3:
- a set with the nominal OSEMINF gains
    T1: 1.478
    T2: 0.942
    T3: 0.952
    LF: 1.302
    RT: 1.087
    SD: 1.290
- a set with the OSEMINF gains changed to the values in 85907
    T1: 3.213
    T2: 1.517
    T3: 1.494
    LF: 1.733
    RT: 1.494
    SD: 1.793

Measurement settings:
- SR3 in HEALTH_CHECK but with damping loops on
- SR3 damping nominal (all -0.5)
- HAM5 in ISOLATED

Nominal gain set:
/ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/SAGM1/Data/2025-07-22_1700_H1SUSSR3_M1_WhiteNoise_{L,T,V,R,P,Y}_0p02to50Hz_OpenLoopGainTF.xml r12478

New gain set:
/ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/SAGM1/Data/2025-07-22_1800_H1SUSSR3_M1_WhiteNoise_{L,T,V,R,P,Y}_0p02to50Hz_OpenLoopGainTF.xml r12478

Once I had taken these measurements, I exported txt files for each dof's OLG and used one of my scripts, /ligo/svncommon/SusSVN/sus/trunk/HLTS/Common/MatlabTools/divide_traces_tfs.m to plot the OLG for each dof to compare the traces between OSEMINF gain differences and then divide the traces and grab an average of that, which will be the compensation gain put in as a filter in the DAMP filter bank (plots). The values I got for the compensation gains are below:
    L: 0.740
    T: 0.732
    V: 0.548
    R: 0.550
    P: 0.628
    Y: 0.757

DOF	OLTF measured and calculated DAMP Compensation gains	ISO Calibration measurement calculated compensation gains (85907)	Percent difference (%)
L	0.740	0.740	0.0
T	0.732	0.719	1.8
V	0.548	0.545	0.5
R	0.550	0.545	0.9
P	0.628	0.629	0.2
Y	0.757	0.740	2.3

These are pretty similar to what my script had found them to be last time before the satamp swap (85288), as well as being very similar to the values that Ivey's script had calculated.
Maybe the accuracy from Ivey's script means that in the future we don't need to run the double sets of OLG transfer functions and can jsut use the values that the script gives.

Images attached to this report

H1 AOS - SQZT7 Beam Profiling with different ZM4 and ZM5 PSAMS Settings

camilla.compton@ligo.org — Tue, 22 Jul 2025 12:33:26 -0700

Author: camilla.compton@ligo.org

Report ID: 85917

Leo, Jennie, Camilla, WP 12694

Jennie followed instructions for set up in 85775. We removed the SQZ beam iris at the bottom of the LPM (added for alignment capture during OFI vent work). Then took beam profiles in this SQZ path of the SEED beam with various PSAMS settings, adjusted PSAMS settings as in 85775 and used the servo for nominal settings. All data is attached. Jennie then reverted settings back to nominal.

Non-image files attached to this report

SQZT7_PSAMS_July22.pdf

H1 SUS - Comment to OSEM calibration of H1:SUS-SR3

oli.patane@ligo.org — Tue, 22 Jul 2025 12:31:55 -0700

Author: oli.patane@ligo.org

Report ID: 85916

Comparing these new OSEMINF gains to the gains we got last time we did this (84367) (before the satamp swap), they are pretty similar:

OSEM	Previous Calculated OSEMINF gains (84367)	New Calculated OSEMINF gains (85907)	Percent difference (%)
T1	3.627	3.213	12.1
T2	1.396	1.517	8.3
T3	1.345	1.494	10.4
LF	1.719	1.733	0.8
RT	1.490	1.494	0.2
SD	1.781	1.793	0.6

So that's another indicator that the sat amp swap did not have much of an effect on the suspension response to suspoint excitations

H1 General - LVEA Sweep

anthony.sanchez@ligo.org — Tue, 22 Jul 2025 12:29:32 -0700

Author: anthony.sanchez@ligo.org

Report ID: 85915

I did a sweep of the LVEA & found Camilla and Jennie W working on the Squeeze tables. Then needed 10-15 more minutes and ensured me that they'd turn off the lights once they were done making sure the Squeezer was Squoze.

H1 ISC - Kepco Power Supplies Replaced

marc.pirello@ligo.org — Tue, 22 Jul 2025 11:55:56 -0700

Author: marc.pirello@ligo.org

Report ID: 85912

We replaced the following supplies this maintenance period:

Mezannine in CER:
VDD-C5-U30 RHS -24 Digital S1201957 replaced with upgraded supply S1202024 per WP12688
VDD-C6-U42 RHS HAM6 OMC PZT HV Power Supply 110V 80mA replaced with HV spare supply due to unexplained tripping of original supply per WP12704

We also staged upgraded replacement supplies 4x in the CER Mezannine, 2x at EY, and 2x at EX.

F. Clara, M. Pirello, E. vonReis

LHO VE - Quarterly Functionality Test Performed on EY/MY Turbo Pumps

anna.iudintseva@ligo.org — Tue, 22 Jul 2025 11:20:03 -0700

Author: anna.iudintseva@ligo.org

Report ID: 85911

Procedure checklist for both stations completed. No issues were identified at this time. MY: Scroll pump hours: 89 Turbo pump hours: 226 Crash bearings: 100% EY: Scroll pump hours: 88 Turbo pump hours: 1295 Crash bearings: 100%

LHO VE - Tue CP1 Fill

david.barker@ligo.org — Tue, 22 Jul 2025 11:16:21 -0700

Author: david.barker@ligo.org

Report ID: 85910

Tue Jul 22 10:09:18 2025 INFO: Fill completed in 9min 14secs

Gerardo confirmed a good fill curbside.

Images attached to this report

LHO FMCS - VEA temperature trends

eric.otterman@ligo.org — Tue, 22 Jul 2025 11:09:04 -0700

Author: eric.otterman@ligo.org

Report ID: 85909

Chris and I greased the fan bearings for the VEA spaces and alternated the fans. This has resulted in abnormalities in the temperature trending, but these changes will even out after a short period.

H1 SUS - OSEM calibration of H1:SUS-SR3

ivey.zhong@ligo.org — Tue, 22 Jul 2025 09:32:24 -0700

Author: ivey.zhong@ligo.org

Report ID: 85907

OSEM calibration of H1:SUS-SR3 Stage: M1 2025-07-22_1530 (UTC). The suggested (calibrated) M1 OSEMINF gains are (new T1) = 2.174 * (old T1) = 3.213 (new T2) = 1.610 * (old T2) = 1.517 (new T3) = 1.569 * (old T3) = 1.494 (new LF) = 1.331 * (old LF) = 1.733 (new RT) = 1.374 * (old RT) = 1.494 (new SD) = 1.390 * (old SD) = 1.793 To compensate for the OSEM gain changes, we estimate that the H1:SUS-SR3_M1_DAMP loops must be changed by factors of: L gain = 0.740 * (old L gain) T gain = 0.719 * (old T gain) V gain = 0.545 * (old V gain) R gain = 0.545 * (old R gain) P gain = 0.629 * (old P gain) Y gain = 0.740 * (old Y gain) The calibration will change the apparent alignment of the suspension as seen by the at the M1 OSEMs NOTE: The actual alignment of the suspension will NOT change as a result of the calibration process The changes are computed as (osem2eul) * gain * inv(osem2eul). Using the alignments from 2025-07-22_1530 (UTC) as a reference, the new apparent alingments are: DOF Previous value New value Apparent change --------------------------------------------------------------------------------- L -5.0 um -3.1 um +1.8 um T -21.6 um -15.5 um +6.1 um V 11.8 um 9.8 um -2.0 um R -576.3 urad -327.5 urad +248.9 urad P -266.5 urad -158.3 urad +108.2 urad Y -585.0 urad -431.9 urad +153.1 urad We have estimated a OSEM calibration of H1 SR3 M1 using HAM5 ST1 drives from 2025-05-21_0000 (UTC). We fit the response M1_DAMP/HAM5_SUSPOINT between 5 and 15 Hz to get a calibration in [OSEM m]/[GS13 m] This message was generated automatically by OSEM_calibration_SR3.py on 2025-07-22 16:24:05.000267+00:00 UTC %%%%%%%%%%%%%%%%%%%%%%%%%%%% EXTRA INFORMATION The H1:SUS-SR3_M1_OSEMINF gains at the time of measurement were: (old) T1: 1.478 (old) T2: 0.942 (old) T3: 0.952 (old) LF: 1.302 (old) RT: 1.087 (old) SD: 1.290 The matrix to convert from the old Euler dofs to the (calibrated) new Euler dofs is: +0.74 -0.0 +0.0 -0.0 +0.0 -0.001 +0.0 +0.719 -0.0 +0.0 +0.0 -0.0 -0.0 +0.0 +0.545 -0.006 +0.0 +0.0 +0.0 +0.0 -1.209 +0.545 -0.003 -0.0 +0.0 +0.0 +0.18 -0.013 +0.629 -0.0 -0.148 +0.0 -0.0 +0.0 -0.0 +0.74 The matrix is used as (M) * (old EUL dof) = (new EUL dof) The dof ordering is ('L', 'T', 'V', 'R', 'P', 'Y') Please see the attached images of before calibrating and after calibrating.SEI, SUS

Images attached to this report

H1 AOS - Updated h0vacmr PLC to correct inputs to IP13

patrick.thomas@ligo.org — Tue, 22 Jul 2025 09:31:04 -0700

Author: patrick.thomas@ligo.org

Report ID: 85908

WP 12690 Gerardo M., Patrick T. "Update the PLC code on h0vacmr to reflect the current cabling of IP13 to Beckhoff terminal 25, channels 3 and 4." This work permit has been completed. The code is now at commit efc3db6abdaf3f286903a874e7f765e9d867f9f9. There are no issues to report.

H1 SUS - New OSEMINF gain calibration measurements taken for SR3

oli.patane@ligo.org — Tue, 22 Jul 2025 09:04:28 -0700

Author: oli.patane@ligo.org

Report ID: 85906

This is part of the work we are doing for the Estimator. As part of that work, we are finetuning the OSEMINF gains, which we did previously for SR3 (84298), but since we've swapped the satamps we want to check how different these new values will be compared to the current gains as well as the gains we found that last time.

I ran excitations through the H1:ISI-HAM5_ISO_{X,Y,Z} filter banks with the settings of:

HAM5 in ISOLATED
SR3 in ALIGNED (or in HEALTH_CHECK with damping turned back on - the alignment sliders being on or off doesn't make a difference)
SR3 M1 gains all -0.1

Measurements can be found at /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/Common/Data/2025-07-22_1530_H1ISIHAM5_ST1_WhiteNoise_ISO_{X,Y,Z}_0p05to40Hz_calibration.xml, svn revision r12476.

H1 CDS - WP 12691 move CDS/GC connection off temporary switch

jonathan.hanks@ligo.org — Tue, 22 Jul 2025 08:42:54 -0700

Author: jonathan.hanks@ligo.org

Report ID: 85905

As per WP 12691 we moved the CDS/GC connection off of a temporary switch. This is a follow up to WP 12580 which had left us on a temporary switch. The new switch is a larger switch and all the phones can be plugged in now.

LHO General - Ops Day Shift Start

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

Author: thomas.shaffer@ligo.org

Report ID: 85904

TITLE: 07/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY: Locked for 9 hours, magnetic injections currently running. Long list of planned maintenance today, see the Trello for more details.

H1 CDS - Workstations updated

erik.vonreis@ligo.org — Tue, 22 Jul 2025 07:30:42 -0700

Author: erik.vonreis@ligo.org

Report ID: 85903

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

H1 General - Ops EVE Shift End

anthony.sanchez@ligo.org — Mon, 21 Jul 2025 22:12:46 -0700

Author: anthony.sanchez@ligo.org

Report ID: 85902

TITLE: 07/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
Every thing was locked and humming along until the sudden lockloss from the 6.5M Earthquake off coast of Russia.
Held in Down for ~2.5 hours while the Earth rang down.
Ran an Initial Alignment and H1 is currently at CARM_OffSET reduction.
Wind is vey low, ground motion has dropped should be a good night of locked IFO.
LOG:
No Log

H1 General - Lockloss from NLN

anthony.sanchez@ligo.org — Mon, 21 Jul 2025 20:11:23 -0700

Author: anthony.sanchez@ligo.org

Report ID: 85901

@ 02:08:55 UTC Known Lockloss caused by a 6.5M Earthquake. I'm using the GEOFON site because USGS took ~ 10 min to report the quake.
Earthquake mode was activated, then less than 30 seconds later we were unlocked.
No earthquake was listed as incoming, Picket fence was lit up and had active ground motion.

Lockloss, SEI

Images attached to this report

H1 SUS - Compensation filters for MC2, PR2, TMSX, and ETMX M0/R0/L1 updated to satamp channel specific filters

oli.patane@ligo.org — Mon, 21 Jul 2025 17:01:53 -0700

Author: oli.patane@ligo.org

Report ID: 85900

After last week's satamp changes (85770), the compensation filters found in the OSEMINF filter bank for MC2, PR2, TMSX, and ETMX M0/R0/L1 were all updated to a generic compensation filter of 5.31:0.0969. I have now updated those filters based on the experimental measurements Jeff got for each satamp's channel (the same as what I did in 85746).

To update the compensation filters, I used the newest version of my script satampswap_bestpossible_filterupdate_ECR_E2400330.py, svn revision r12475. This newest version of the code allows you to specify which stage you want to update, if you aren't wanting to update every stage listed in the txt files. Here is a txt file of my inputs and the corresponding outputs for the lines of code that I ran.

I have loaded these more accurate filters in for these suspension/stages.

Images attached to this report

Non-image files attached to this report

satamp_filter_update.txt

H1 General - Monday Ops Eve Shift Start

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

Author: anthony.sanchez@ligo.org

Report ID: 85898

TITLE: 07/21 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 15mph Gusts, 12mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:
H1 is currently Locking at Move.
Secondary microseism looks to be falling.
All systems look great.

Brushfire look out was done by Oli today, who said... "No fires today."
Roof pictures attached.

Images attached to this report

LHO General - Mon DAY Ops Summary

corey.gray@ligo.org — Mon, 21 Jul 2025 16:30:00 -0700

Author: corey.gray@ligo.org

Report ID: 85882

TITLE: 07/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

Started with a locked H1, and then started Monday Commissioning for 4-hours (15-19utc/8-noonPDT). Had a lockloss at the beginning of commissioning and it took 2hrs to get back to NLN (mostly let ISC_LOCK acquire on its own...it just took a bit.).

Lockloss in the afternoon looked a bit odd with the alignment not looking great. Tried to not run an Initial Alignment (i.e. run CMFringes + PRMI), but alignment looked bad. After 45min of acquiring, went for an Initial Alignment (which wasn't trivial due to a finicky IMC--see below), and after the IA, H1's alignment looked much better. It's all a question of when to run/not run an alignment due to the BS cooling down after locklosses.

EQs continued to rumble for most of the morning (many from Japan).
LOG:

1435-1529 MX chiller yard checks (randy)
1503 Commissioning Begins
1504-1632 MY technical cleaning (nellie)
- 1632 MX technical cleaning (nellie)
1515 LOCKLOSS
- It was hard, but tried to not touch H1 for locking (since last night and most of the weekend reacquisition was fairly automated), but I did move the BS a few clicks during the 1st DRMI 20min acquisition (no lock). Went automatically to PRMI for the 1st time, but after about 11min, I intentionally went to CHECK MICH FRINGES. Then for 2nd PRMI I did touch PRM a few clicks, but restored it....and it finally acquired after 11min on its own. DRMI's 2nd attempt (after Check Mich Fringes + PRMI) had decent POP18/90 flashes, but the camera did show some yaw misalignment but it eventually locked after about 7min.....and then a lockloss at START TR CARM :(
- 1717 H1 back to Observing for Commissioning
1634 Grabbing extra power supply for HAM6 HV (in prep for swap for tomorrow's Maintenance) (fil)
1733-1802 MX, EX Mechanical Room visits to check HVAC air filters (chris)
1902 Back to Observing
1957-2015 EY trip to pick up nitrogen air cyllinders (chris)
- 2025-2050 Cyllinders not there, so went to EX (chris)
2053-2241 TCS work at the Triples Lab in Staging (camilla, tony)
2133 LOCKLOSS (after 4.25 hr lock)
- Summary: Although, locking was good overnight with no Alignments needed, this one looked bad, and so ultimately decided to run an Initial Alignment (after locking for 45min).
- ALSx had 2 locklosses at the beginning after Offloading and the ITM Camera signal was dropping along with ARM transmission before the lockloss.
- For 1st DRMI locking, alignment was very bad (from camera and flashes). Guardian took DRMI to PRMI within 3minutes! But I went to Check Mich Fringes. And for PRMI, it locked but ASC didn't really do much for PRMI.
- 2216 Started an Initial Alignment.....but the IMC took over 10min to lock (eventually locked perhaps due to taking IMC_LOCK to DOWN a few times). DRMI locked in just over 4min.....but then there was an accidental user error lockloss. But not an issue, because for the next lock, DRMI acquired in under 5min again. This is what I'm handing off to Tony.
2150-2155 Looking at Power Supply in CER (richard)
2241-2255 PCal measurements (francisco)

H1 PSL - Comment to ISS array work - horizontal scan

jennifer.wright@ligo.org — Mon, 21 Jul 2025 15:32:41 -0700

Author: jennifer.wright@ligo.org

Report ID: 85891

To work out the relative intensity noise:

RIN = change in power/ power

= ( change in current/ current) / responsivity of PD

= (change in voltage/voltage) / (responsitvity * load resistance)

Therefore to minimise RIN we want to minimise change in voltage / voltage for each PD.

To get the least coupling to array input alignment we work out

relative RIN coupling = (delta V/ V) / beam motion at QPD

This works because the QPD is designed to be in the same plane as the PD array.

PD	DC Voltage [V] mean	AC Voltage [mV] pk-pk	Beam Motion at QPD [mm]	Relative Coupling [1/m]
1	-4.08	420	0.222	465
2	-3.81	380	0.222	450
3	-3.46	380	0.222	496
4	-3.71	420	0.222	511
5	-3.57	540	0.222	683
6	-3.5	500	0.222	645
7	-2.91	540	0.222	838
8	-3.36	540	0.222	726

These are all a factor of 50 higher than those measured by Mayank and Shiva but after discussion with Keita either we need higher resolution measurements or we need to further optimise input alignment to the array to minimise the coupling.

X1 SUS - Comment to 2nd round of B&K measurements of HRTS mounted on BBSS structure in staging building

rahul.kumar@ligo.org — Mon, 21 Jul 2025 15:25:48 -0700

Author: rahul.kumar@ligo.org

Report ID: 85896

Attached below is a pdf document in which I have repeated tests 6abc and 7abc accelerometer / hit location data, but with the HRTS removed (called as test 8abc and 9abc). In both the cases the Vibration Absorbers (VA) are attached to the BBSS. There are no VA on the HRTS.

Non-image files attached to this report

BnK_Test_BBSS_HRTS_V2(July2025).pdf

H1 PSL - Comment to Calibrating ISS QPD

jennifer.wright@ligo.org — Mon, 21 Jul 2025 15:17:53 -0700

Author: jennifer.wright@ligo.org

Report ID: 85897

I got the above caluclation of the QPD calibration in the horizontal direction wrong as I use the total change in voltage we measured across the whole range of horizontal scan and not just the linear region where the beam is close to centred on the QPD.

The horizontal beam scan calibration is actually:

sqrt(11.8^2 + 44.1^2) = 10.6 V/mm

with an angle of tan^-1(11.8/44.1) = 14.9 degrees to the X direction on the QPD.

H1 PSL - Comment to ISS array work - horizontal scan

jennifer.wright@ligo.org — Mon, 21 Jul 2025 15:12:23 -0700

Author: jennifer.wright@ligo.org

Report ID: 85890

horizontal dither calibration = 10.57 V/mm

dither Vpk-pk on QPD x-direction = 2.2V

dither Vpk-pk on QPD y-direction = 0.8V

dither motion in horizontal direction in V on QPD = sqrt(2.2^2 + 0.8^2)

motion in mm on QPD that corresponds to dither of input mirror = sqrt(2.2^2 + 0.8^2) / 4.644 = 0.222 mm

Code is here for calibration of horizontal beam motion to QPD motion plus calibration of dither measurements.

Non-image files attached to this report

Calibrate_QPD.m

H1 ISC - pimon minor changes

thomas.shaffer@ligo.org — Mon, 21 Jul 2025 14:44:40 -0700

Author: thomas.shaffer@ligo.org

Report ID: 85895

Elenna noticed that pimon that we run on nuc25 hadn't been consistently saving data. There were large periods of time that didn't have anything recorded. I first verified that it would still write log and npz files, then I redirected them to /ligo/data/pimon/locklosses/ where it will now put all of the npz files. Elenna also asked that the script saves the time series and not the PSDs, so I made that change as well. I'm not sure the file size difference, the PSDs were about 3.6Mb, so we should keep an eye on that and get rid of old ones.

Operators, please verify that pimon is running on nuc25, and restart it if necessary. The normal launch script will start it up.

OpsInfo

H1 ISC - Calibration lines in DHARD

elenna.capote@ligo.org — Mon, 21 Jul 2025 13:07:54 -0700

Author: elenna.capote@ligo.org

Report ID: 85894

The calibration lines still appear in DHARD P and Y to varying degrees. Here is a higher resolution spectrum of DHARD P and Y, with OMC DCPD sum for reference. DHARD P shows all four calibration lines (L1 15.6 Hz, L2 16.4 Hz, L3 17.6 Hz and PCAL 17.1 Hz) between 15-18 Hz, while DHARD Y only seems to show the 16.4 Hz line in L2.

Today, Sheila and I also looked at the phasing of AS A/B 45 WFS. Our thinking was that a DARM line could be phased to be mainly in Q for each segment. The segments all show the calibration lines prominently, so they can be used as a phasing reference. It was immediately apparently that for all segments of both WFS, the DARM line is at least a factor of 2 higher in I than in Q. We decided not to make any phasing changes at this time, since rephasing these lines into Q would change the sign dramatically and may impact locking when we put DARM on RF.

Images attached to this report

H1 ISC - New MICH ASC lowpasses engaged

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

Author: elenna.capote@ligo.org

Report ID: 85893

Instead of redesigned the MICH ASC loops, I just updated the lowpasses to be at 12 Hz instead of 15 Hz, which should reduce the gain by 15 dB between 10-20 Hz for both pitch and yaw. I tested them today with no issues, so I adjusted the MICH ASC engagement in ISC_DRMI guardian, and updated SDF (accidentally overwrote the screenshot with my screenshot of the filter).

Images attached to this report

H1 SQZ - FC Detuning Checked, already in best spot

camilla.compton@ligo.org — Mon, 21 Jul 2025 11:56:40 -0700

Author: camilla.compton@ligo.org

Report ID: 85892

Elenna and I checked the FC detuning by taking it slowly from nominal -26 to -50, where we could clearly see low freq DARM was worse, and then stepping to -15 (any lower unlocked the FC in 85886) using ezcastep H1:IOP-LSC0_RLF_FREQ_OFS -s 30 '+1,35', see attached plot. The best de-tuning is close to where we already are, leaving it at -27.

Images attached to this report

LHO VE - Mon CP1 Fill

david.barker@ligo.org — Mon, 21 Jul 2025 10:25:19 -0700

Author: david.barker@ligo.org

Report ID: 85889

Mon Jul 21 10:08:47 2025 INFO: Fill completed in 8min 44secs

Images attached to this report

H1 AOS - Comment to LOWNOISE ASC Locklosses

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

Author: elenna.capote@ligo.org

Report ID: 85888

We haven't had a lockloss in this state since this fix (but we've had plenty of locks), so I am going to declare this problem fixed!

H1 DetChar - Comment to 20.2 Hz line appeared Jun 9, turns on and off

derek.davis@ligo.org — Mon, 21 Jul 2025 09:24:11 -0700

Author: derek.davis@ligo.org

Report ID: 85887

Looking into past alogs, I noticed that I reported this same issue last summer in alog 79948. Additional discussion about this line can be found in the detchar-requests repository (requires authentication). In this case, the line appeared in late spring and disappeared in early autumn of 2024. No source was identified before the line disappeared.

Going back further, I also see the same feature appearing in late spring and disappearing in early autumn of 2023. The presence of the line is hence correlated with the outside temperature, likely related to some aspect of the air conditioning system that is only needed when it is (roughly) hotter outside than inside. This also means that we can expect this line to remain present in the data until autumn unless mitigation measures are taken.

H1 SQZ - Lockloss while setting up for FC detuning Commisioning

camilla.compton@ligo.org — Mon, 21 Jul 2025 09:02:44 -0700

Author: camilla.compton@ligo.org

Report ID: 85886

First I tried taking H1:IOP-LSC0_RLF_FREQ_OFS down towards zero but we lost FC lock at H1:IOP-LSC0_RLF_FREQ_OFS = -8. FC would not re-lock until I brought it back to -15.

Wanted to scan FC de-tuning from -15 to -60 but the command didn't seem to work with negative steps.

Then 5s after moving FC detuning from -15 to -60, the IFO lost lock, 1437146099. The lockloss appears unrelated to the FC detuning change as the FC lost lock after we see ETMX_L3 start to be unstable, plot. There was slightly increased noise at low frequency but not enough scatter to cause a lockloss.

Ideally would have ran ezcastep H1:IOP-LSC0_RLF_FREQ_OFS -s 30 '+1,45' to get 30sec steps from -60 to -15. We've been at -44 before with no issues, 83526, but wanted to make the low frequency noise worse to be able to fit to the best place.

Images attached to this report

H1 AOS - Updating pydarm release to tag 20250721.0

joseph.betzwieser@ligo.org — Mon, 21 Jul 2025 08:46:10 -0700

Author: joseph.betzwieser@ligo.org

Report ID: 85885

I'm followed the pydarm deployment instructions here, to update the LHO pydarm install. This is the 20250721.0 tag for pydarm, which includes a bug fix for high frequency roam line handling, letting us indicate the correct reference model in the pydarm_H1.ini file. This is not the default cds conda environment, but the default you get when typing pydarm at a command line, or specifically invoking by running "conda activate /ligo/groups/cal/conda/pydarm".

H1 SQZ - Comment to SQZ angle ADF srevo back on in guardian

camilla.compton@ligo.org — Mon, 21 Jul 2025 08:39:32 -0700

Author: camilla.compton@ligo.org

Report ID: 85884

Since we've had this servo running, the range has been higher and sqz more stable, see attached.

Images attached to this report

LHO General - Comment to Mon DAY Ops Transition

corey.gray@ligo.org — Mon, 21 Jul 2025 07:51:30 -0700

Author: corey.gray@ligo.org

Report ID: 85883

Notes From Ops Shift Check Sheet

1) Dust Monitor Check Notifications for LVEA5 & LAB2

Ran the "check_dust_monitors_are_working" script the last two mornings and received notifications for the following:

*H1:PEM-CS_DUST_LVEA5 WARNING: dust counts did not change, please investigate
H1:PEM-CS_DUST_LAB2 Error: data set contains 'not-a-number' (NaN) entries

2) Access System "Flashing Doors"

EY has (2) flashing doors, but I'm pretty sure this has been ongoing for years.
VPW has 3 door issues: Exterior Roll-up, LDAS entry, Dirty shop entry & Wood shop has Roll-up door issue.

3) LHO Control Room Screenshots & FOMs

H1 Glitches (nuc27) not posting (this has been the case for a while)

LHO General - Mon DAY Ops Transition

corey.gray@ligo.org — Mon, 21 Jul 2025 07:40:44 -0700

Author: corey.gray@ligo.org

Report ID: 85881

TITLE: 07/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 113Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 9mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:

Arriving to a Dust Alarm in the PSL over the last hr (there have been winds around the corner station the last 2hrs but only about 15mph).

For H1 over the last 12 hrs we have had 4 locks (current one is 90min) where 2 (of3) locklosses were ETMx Glitches, and it looks like all reacquisition was automatic overnight.

H1 is scheduled for Commissioning from 15-19utc (8-noonPDT).

H1 General - Ops Eve shift & Lockloss from NLN

anthony.sanchez@ligo.org — Sun, 20 Jul 2025 22:01:27 -0700

Author: anthony.sanchez@ligo.org

Report ID: 85880

TITLE: 07/21 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
Started the Shift unlocked due to earthquake.

Got back to observing for 1 minute before a lockloss.
Then relocked again for an hour and 17 minutes before another Unknown Lockloss from NLN.

Relocking now, currently at LOW_NOISE_COIL_DRIVERS we should be locked by soon .

Lockloss

Images attached to this report

H1 General - Sunday Eve Shift report.

anthony.sanchez@ligo.org — Sun, 20 Jul 2025 18:44:51 -0700

Author: anthony.sanchez@ligo.org

Report ID: 85879

Went up to the Roof to check for fires or smoke. Took some pictures in all directions.

Inherited an unlocked H1 after a large earthquake from Alaska.
Did an Initial Alignment which had an SRM WD trip towards the end. So I reran it with out any issues.
We reached NOMINAL_LOW_NOISE at 01:25 UTC
Observing at 1:27 UTC.

And Lost lock to an Unknown Lockloss at 1: 29 UTC.

Lockloss

Images attached to this report

LHO General - Sun DAY Ops Summary

corey.gray@ligo.org — Sun, 20 Jul 2025 16:29:29 -0700

Author: corey.gray@ligo.org

Report ID: 85872

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

Flurries of earthquakes from Japan. Had another HAM6 High Voltage power supply failure. Able to finally finish the change for removing the SR3 Dither Pitch Offset. Shift ended with a M6.2 Alaska earthquake which took H1 down.
LOG:

1600 Verbal: "nearby earthquake from Japan" (was a M5.2). Received several of these notifications as flurry of EQs in Japan rolled through.
1732 LOCKLOSS seismic motion is elevated, but doesn't look like it was EQ-caused
- 1745 Removed SR3 Dither Pit Offset and updated safe.snap (alog)....and...
- 1800-1822 Ran Initial Alignment with new SR3 pointing due to offset being zeroed
1736-1746 EQ Mode activated
- 1813-1823 EQ Mode activated
1845 Noticed H1 was STUCK at PREP_DC_READOUT_TRANSITION. This was due to the OMC not locking.
- 1913-2004 Phoned Elenna for help. She eventually found out we had another HAM6 High Voltage Power Supply issue for the OMC 100V PZTs.
2030 OBSERVING
2119-2150 PCal Measurement in the PCal Lab (tony)
2233 LOCKLOSS due to M6.1 Alaska earthquake.

H1 SUS - Comment to SR3 Dither Pitch Offset Zeroed + H1SUSSR3 safe.snap Updated

corey.gray@ligo.org — Sun, 20 Jul 2025 14:24:57 -0700

Author: corey.gray@ligo.org

Report ID: 85878

After the OMC Power Supply issues noted above, H1 made it to NLN, but it did in fact have SDF Diffs for OBSERVE.snap for H1SUSSR3. Those new settings were ACCEPTED in SDF (see attached), and this is task is now complete.

Images attached to this report

H1 ISC - Comment to More OMC High Voltage OMC Power Supply Weirdness

corey.gray@ligo.org — Sun, 20 Jul 2025 14:21:30 -0700

Author: corey.gray@ligo.org

Report ID: 85877

Added a new comment for today's HAM6 Power Supply Issue to the already-opened FRS Ticket 34433.

OPS NOTE: If you are having trouble locking the OMC (no light on the HAM6 OMC Trans camera, stuck at PREP_DC_READOUT_TRANSITION, and no evidence of the OMC PZT2 working), it might due to this power supply!

FRS, OpsInfo

H1 ISC - More OMC High Voltage OMC Power Supply Weirdness

corey.gray@ligo.org — Sun, 20 Jul 2025 14:17:10 -0700

Author: corey.gray@ligo.org

Report ID: 85876

(Corey, Elenna [remote], Tony)

Recent Backstory Alogs:

JUN 1st: (Corey, Craig, Georgia) HAM6 HV PZT Kepco Power Supply was stuck in the Constant Current ("CC") state (alog84698)
JUN 13th: (Keita, RyanC) Output Voltage was 0V and it was also in the Constant Current ("CC") state (alog85030)

Today, while locking H1 noticed that we were stuck in PREP_DC_READOUT_TRANSITION. DIAG_MAIN was mentioning an OMC issue. OMC_LOCK guardian was in a loop of trying to sweep the PZT to FIND_CARRIER, but Elenna noticed that the PZT was not sweeping. Then she remmebered the previous issues!

(I was on the wrong trail, because I had assumed the SR3 change I made somehow was the cause of the issue---it was NOT.)

Went out to the CER and went upstairs to the rack which has the HAM6 HV OMC PZT power supply....
It was OFF! (see 1st photo) The rocker switch was in the OFF state. (This is different from both cases noted above from last month.)
Read up on Craig's and Keita's alogs
Turned the Power Supply ON
But had 0.0V and 0.0mA + it also was stuck in the CC state (didn't take a photo, but basically it looked like THIS from Keita's alog)
Checked the "V SET" and saw that it was 0 V, so took this to 110V (which is also noted on the sticker on the front of the Power Supply). Went to "I SET" and saw that it was 0.0 mA, and did not change this value.
Still had the Constant Current .
Eventually did another Power Cycle via the front rocker switch and this time the Power Supply came up in the Constant Voltage ("CV")--which we wanted. (Is there an easier way to transition to this state? I went through the MENU and did not find anything.
WE BACK!: At this point, we had: CV, 110V, and a non-zero Current. (see 2nd photo for photo of the power supply display)
Elenna took the OMC_LOCK guardian from MANAGED --to--> AUTO, and started moving the PZT2 in 1.0 count steps. She saw this working on her medm and I saw the Current changing on the front display of the Power Supply.
At this point, we were back in business and returned to the Control Room.
ISC_LOCK was continuing on (because the OMC had locked).

We still had the OMC_LOCK in a non-ISC_LOCK-managed AUTO state and we were not totally sure of how to have ISC_LOCK remanage OMC_LOCK. Tony found a 2015 alog from Patrick which we used to get OMC_LOCK managed again. H1 continued on and has been in OBSERVING.

FRS, ISC, OpsInfo

Images attached to this report

H1 SUS - SR3 Dither Pitch Offset Zeroed + H1SUSSR3 safe.snap Updated

corey.gray@ligo.org — Sun, 20 Jul 2025 12:13:13 -0700

Author: corey.gray@ligo.org

Report ID: 85875

Finally had the opportunity (due to H1 Lockloss during my shift) to address the SR3 Dither Pitch Offset Oli noted last week (alog 85830), and I first looked at during a lockloss at the end of my shift Friday evening (alog 85855)---but my changes did not hold for the Dither Pitch Offset due to the H1SUSSR3 SDF needing its safe.snap changed/accepted.

It's been ages since I've updated an safe.snap, so pardon the less elegant steps I took to update the SR3 SDF here---Basically I

Turned the OFFSET button OFF (then Accepted the SDF diff for the safe.snap) and then
Took the OFFSET from 32.3 to 0 (then Accepted the SDF diff, once again, for the safe.snap).

Both updates are screenshot-ed separately! Ha. The new SR3 OPTICALIGN_P_OFFSET was already at its new offset (of 457.9...which used to be 445.8) since Friday (and aligned). So now that the SR3 pointing changed with the Dither Offset going to zero, I ran a new alignment.

Currently, H1 has locked DRMI and I'm sure the final step here would be updated thing observe.snap with the changes noted above.

ADDENDUM: Currently stuck at PREP_DC_READOUT_TRANSITION, where the OMC can't lock. I'm wondering if this is due to the SR3 change....Where the SR3 Top Mass was at one spot since Fri evening, and now with the Dither Offset being zeroed, we now have SR3 Top Mass back to it's pointing we had for the last few weeks up until Friday night. (see attached ndscope trend over the weekend)

SUS

Images attached to this report

LHO VE - Sun CP1 Fill

david.barker@ligo.org — Sun, 20 Jul 2025 10:16:06 -0700

Author: david.barker@ligo.org

Report ID: 85874

Sun Jul 20 10:08:56 2025 INFO: Fill completed in 8min 52secs

Images attached to this report

LHO General - Notes From Ops Shift Check Sheet

corey.gray@ligo.org — Sun, 20 Jul 2025 08:06:53 -0700

Author: corey.gray@ligo.org

Report ID: 85873

1) Dust Monitor Check Notifications for LVEA5 & LAB2

Ran the "check_dust_monitors_are_working" script the last two mornings and received notifications for the following:

*H1:PEM-CS_DUST_LVEA5 WARNING: dust counts did not change, please investigate
H1:PEM-CS_DUST_LAB2 Error: data set contains 'not-a-number' (NaN) entries

2) Access System "Flashing Doors"

MSR door in the Control Room was ajar, so it was closed
EY has several flashing doors, but I'm pretty sure this has been ongoing for years.
VPW has 3 door issues: Exterior Roll-up, LDAS entry, Dirty shop entry
Wood shop has Roll-up door issue.

3) LHO Control Room Screenshots & FOMs

USGS needed a RELOAD this morning
H1 Glitches (nuc27) not posting (this has been the case for a while)

CDS, FMP, PEM

LHO General - Sun DAY Ops Transition

corey.gray@ligo.org — Sun, 20 Jul 2025 08:00:18 -0700

Author: corey.gray@ligo.org

Report ID: 85871

TITLE: 07/20 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 5mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

Whoa, big earthquake overnight as RyanC notes in his wake-up calls. Crazy 20hrs with high winds first which then died and tagged in the big EQ! Seismic motion elevated 8hrs ago for the EQ, and finally calmed down within the last hour. H1's been locked for the last 2+hrs. Nice to see that the violins weren't rung up after the shaky night!

Images attached to this report

H1 General - Comment to OPS OWL assistance

ryan.crouch@ligo.org — Sun, 20 Jul 2025 04:56:59 -0700

Author: ryan.crouch@ligo.org

Report ID: 85870

We found IR and DRMI locked after less than 30 seconds.

H1 General - OPS OWL assistance

ryan.crouch@ligo.org — Sun, 20 Jul 2025 04:51:43 -0700

Author: ryan.crouch@ligo.org

Report ID: 85869

11:03 UTC guardian called again after not being able to find IR.

11:13 - 11:49 UTC I decided to run an initial alignment. Xarm IR struggled so I trended the IMs and had to move IM2 a bunch in pitch to return it to its previous position pre watchdog trip.

11:50 UTC Back to regular locking

H1 General - OPS OWL assistance

ryan.crouch@ligo.org — Sun, 20 Jul 2025 00:07:27 -0700

Author: ryan.crouch@ligo.org

Report ID: 85868

12:01 GRD called, we got hit by 2 large semi close earthquake from the eastern Russian penisula, a 6.7 then a 7.4. A few ISIs and suspensions tripped, it'll be a few hours till the ground motion comes down enough to relock. We were going through DRMI_ASC at the time of the earthquakes.

SEI