It may be difficult to see in a standard spectrum, but can be clearly seen in Fscan plots linked off of the summary pages. For the "observing" Fscan, the interactive spectrum plot shows the 2 Hz comb marked automatically. See the attached image of H1:GDS-CALIB_STRAIN_CLEAN

Verifed that the cabling has not changed since 75876.

Next steps we should follow, as listed in 75876 would be to try using a different power supply or lowering the voltage to +12V. Or, there is a note suggesting Fil could make a new cable to power both the camera and CLink's via the external supply (14V is fine for both). 

Thanks Camilla. If anything can be done more rapidly than waiting another week, it would be very much appreciated. Continuing to collect contaminated data is bad for CW searches.

The DARM signals look very noisy just before the lockloss because I was injecting jitter noise. I don't think that caused the lockloss. The tool is tagging this as "ETM GLITCH" which I also think is wrong because the extra noise was bringing the DARM signal above threshhold for the glitch checker.

21:25 UTC Back to Observing

I was able to read in each 1 second frame and generate a gwpy timeseries for each DCPD data set that I then saved as a single .gwf file. I also used the gwpy resample function to decimate the data to 64k so there is a smaller version. Both sets of files are saved in the same directory and can be read in with gwpy, which should also include metadata with sample rate, gps start, and channel name.

Looks like it was due to a 13Hz ringup in the LSC channels (ndscope). Elenna and I had found a couple other recent locklosses that also had ringups at 13Hz in 85167

I took the opportunity to update h1hpiham1's safe.snap to the latest channel list, removing 47 not-found chans as part of Jim's model cleanup.

I'm adding a detchar tag here in case anyone is wondering where all the lines are coming from in the data around this time- these are purposefully injected lines. If AWG_LINES is injecting, it will be in state 10. When IDLE (no injections), it is in state 2.

 I measured the NLG with a few different opo pump powers to follow up on Camilla's observation that the NLG was low. 

dark level 2e-5, unamplified 2.914e-4

I tried to lower the seed power to see if we have some pump depletion making us underestimate the NLG, but the half wave plate was already set to minimize the seed power.

Since the NLG looks to be about the same with 80 uW as 95uW, I set it to 80 uW for now. 

Another 13 Hz ringup here: 85239

FW0 full frame gap due to crash and restart:

Jun 18 16:14 H-H1_R-1434323584-64.gwf
Jun 18 16:26 H-H1_R-1434324288-64.gwf
 

FRS34505 

This was a sucess- this run through took only 7 minutes. I am shortening the 2 minute wait before increasing the gain to 90 seconds. If that still works, maybe we can go to 60 seconds.

To be more specific, the first attempt as described above meant the state took 6 minutes, 50 seconds. I loaded the change to reduce the wait time from 120 to 90 seconds, which only shortened the state length to 6 minutes, 30 seconds. The gain was only ramped to 8 for a very short period of time. I still think we can make this shorter, which we can do by making that wait time 60 seconds, and maybe taking bigger steps in the gain each time. However, we are still in the RCG upgrade, so I will hold off on changes to the guardian for now.

YAW3 is still limiting the length of the state. In this morning's relock, YAW3 convergence took nearly an additional minute more than the other loops. Once we have caught YAW3 up to everything else, we could make the state even shorter by raising the gain of other ADS loops. Two minutes of the state are taken up in the ramp of the A2L gain, so it is taking an additional 4 minutes, 30 seconds to wait for loop convergence.

Now it seems that PIT3 is taking too much time to converge, so I updated the guardian to also increase the PIT3 gain in the same way.

Adding hera a few bits of information that were missing from the original post, together with an updated version of the script.

_______________________________________________________________________

To compensate for the OSEM gain changes, we estimate that the H1:SUS-SR3_M1_DAMP loops must be changed by a factors of:
L gain = 0.743 * (old L gain)
T gain = 0.724 * (old T gain)
V gain = 0.549 * (old V gain)
R gain = 0.549 * (old R gain)
P gain = 0.691 * (old P gain)
Y gain = 0.743 * (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-05-07_0000 (UTC) as a reference, the new apparent alingments are:

DOF    Previous value     New value       Apparent change
---------------------------------------------------------------------------------
L          -4.3 um                 -2.6 um                     +1.7 um
T          -19.7 um              -14.2 um                 +5.4 um
V          -24.0 um              -8.4 um                   +15.6 um
R          -490.6 urad          -219.3 urad          +271.4 urad
P          -300.2 urad          -203.8 urad          +96.5 urad
Y          -569.3 urad          -422.5 urad          +146.8 urad

Here I post the coherence and transfer functions between the excitations of HAM5 in X, Y, and Z to the SUSPOINT degrees of freedom.

The band from 5-10 Hz seems to be low enough amplitude that I think we can claim that the drives are clean enough in the SUSPOINT basis to perform the calibration.

Note that the high coherence between L/T and HAM5_ISO X/Y is expected, since the SR3 euler basis does not perfectly align with the cartesian basis of HAM5.

J. Kissel (for O. Patane and E. Bonilla)

Also during this barrage of measurements, Oli and Edgard gathered Open Loop Gain (IN1/IN2), Loop Suppression (IN2/EXC), and Closed Loop Gain (IN1/EXC) tfs under the presence of DAMP_EXC. 

Within the templates mentioned below, there're two data sets.
The "New OSEMINF gains" data is with with the above mentioned
    H1:SUS-SR3_M1_OSEMINF_T1_GAIN  3.627
    H1:SUS-SR3_M1_OSEMINF_T2_GAIN  1.396
    H1:SUS-SR3_M1_OSEMINF_T3_GAIN  1.345
    H1:SUS-SR3_M1_OSEMINF_LF_GAIN  1.719
    H1:SUS-SR3_M1_OSEMINF_RT_GAIN  1.490
    H1:SUS-SR3_M1_OSEMINF_SD_GAIN  1.781

The "OG OSEMINF gains" data is with the OSEMINF gains that have been present throughout O4 (as they were reverted post-measurement) 
    H1:SUS-SR3_M1_OSEMINF_T1_GAIN  1.478
    H1:SUS-SR3_M1_OSEMINF_T2_GAIN  0.942
    H1:SUS-SR3_M1_OSEMINF_T3_GAIN  0.952
    H1:SUS-SR3_M1_OSEMINF_LF_GAIN  1.302
    H1:SUS-SR3_M1_OSEMINF_RT_GAIN  1.087
    H1:SUS-SR3_M1_OSEMINF_SD_GAIN  1.29

The raw .xmls for both these data is 
    /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/SAGM1/Data/
        2025-05-21_1800_H1SUSSR3_M1_WhiteNoise_L_0p02to50Hz_OpenLoopGainTF.xml
        2025-05-21_1800_H1SUSSR3_M1_WhiteNoise_P_0p02to50Hz_OpenLoopGainTF.xml
        2025-05-21_1800_H1SUSSR3_M1_WhiteNoise_R_0p02to50Hz_OpenLoopGainTF.xml
        2025-05-21_1800_H1SUSSR3_M1_WhiteNoise_T_0p02to50Hz_OpenLoopGainTF.xml
        2025-05-21_1800_H1SUSSR3_M1_WhiteNoise_V_0p02to50Hz_OpenLoopGainTF.xml
        2025-05-21_1800_H1SUSSR3_M1_WhiteNoise_Y_0p02to50Hz_OpenLoopGainTF.xml

The open loop gain transfer functions (IN1/IN2) have already been exported
    /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/SAGM1/Data/
        2025-05-21_1800_H1SUSSR3_M1_WhiteNoise_?_0p02to50Hz_OpenLoopGainTF_tf.txt     << exports of "OG OSEMINF gains" data

        2025-05-21_2000_H1SUSSR3_M1_WhiteNoise_L_0p02to50Hz_OpenLoopGainTF_tf.txt     << exports of "New OSEMINF gains" data

Also, I've exported the loop suppression of the "OG OSEMINF gains" data as
    /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/SAGM1/Data/
        2025-05-21_1800_H1SUSSR3_M1_WhiteNoise_?_0p02to50Hz_OLGTF_LoopSuppression_tf.txt     << exports of "OG OSEMINF gains" data

Jeff Kissel loves this. Look at that factor of 40 dB / x100 improvement in yaw at 10 Hz!
I'm also glad to see a bounce / roll filter installed as well; I didn't have that in my model. 
Hopefully these are still tuned to the specific HLTS with work we did in ~2019.

I appreciate that all gains are set to -1.0 per convention. 
Can you cover the details of where you've stuck the per-DOF gain scaling to match the open loop gain of the model? 
Perhaps in the norm_${DOF} bank?

The norm filters in FM5 are unchanged. I tried to match the old and new OLTF gains around 3 Hz, which is roughly where we place the upper UGFs. I did this by hand-tuning the overall gain of the rolloff filters in FM1. I kept the dc/ac gains of the boosts equal to unity as best I could, and the dc gains of the elliptic filters equal to unity.

I've copied over the templates for these measurements from
    /ligo/home/evan.hall/Desktop/stuff/
to a standard sharable location, committed to the SusSVN,
    /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/PR3/SAGM1/Data/
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_L_0p02to50Hz_OpenLoopGainTF.xml
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_P_0p02to50Hz_OpenLoopGainTF.xml
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_R_0p02to50Hz_OpenLoopGainTF.xml
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_T_0p02to50Hz_OpenLoopGainTF.xml
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_V_0p02to50Hz_OpenLoopGainTF.xml
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_Y_0p02to50Hz_OpenLoopGainTF.xml


Of course, the amplitude and frequency dependence of excitation for this open loop gain style TF depends on the damping filter you're driving through, so I can't speak to how Evan changed this during the measurement; there doesn't seem to be two excitation options in the template. I would guess that the excitation amplitude / frequency dependence saved in the template works for the current (red trace) data, thus driving through the new "Level 2" filters. So, don't assume that the amplitudes / frequency dependence will work through the old filters; the old filters clearly have much more gain at most frequencies, so I would start by reducing the drive amplitude.

I've exported the loop suppression from this 2022-07-26_1820 data set, they're now committed as
    /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/PR3/SAGM1/Data/
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_L_0p02to50Hz_OLGTF_LoopSuppression_tf.txt
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_P_0p02to50Hz_OLGTF_LoopSuppression_tf.txt
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_R_0p02to50Hz_OLGTF_LoopSuppression_tf.txt
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_T_0p02to50Hz_OLGTF_LoopSuppression_tf.txt
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_V_0p02to50Hz_OLGTF_LoopSuppression_tf.txt
        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_Y_0p02to50Hz_OLGTF_LoopSuppression_tf.txt