We decided to quickly take OLTFs for the ITM R0 stages since we didn't have any yet.

Note: These measurements were taken with the 0.4:10 (old) satamp

ITMY R0
- Measurements taken with suspension in HEALTH_CHECK but with damping loops on
    - optic align offsets off, L2->R0 damping off, etc
- We needed to lower the excitation amplitude for V (10 -> 2.5) and Y(300 -> 10) to keep the suspension dac from overflowing and saturating. In the case of V, we could get full measurements with the excitation amplitude at 5, but the coherence was poor, so I lowered the amplitude to 2.5 and that worked to make sure the osems weren't being overdriven. These excitation filters were originally matches to the ETM R0 ones, but we had to adjust them.
Data: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMY/SAGR0/Data/2025-07-08_1510_H1SUSITMY_R0_WhiteNoise_{L,T,V,R,P,Y}_0p02to50Hz_OpenLoopGainTF.xml r12395

J. Kissel

Continuing on the campaign of gathering open loop gain (and loop suppression & closed loop gain TFs), I measured H1SUSITMX's reaction chain R0 damping loops this morning -- see
    /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGR0/Data/
        2025-07-08_1530_H1SUSITMX_R0_WhiteNoise_L_0p02to50Hz_OpenLoopGainTF.xml
        2025-07-08_1530_H1SUSITMX_R0_WhiteNoise_P_0p02to50Hz_OpenLoopGainTF.xml
        2025-07-08_1530_H1SUSITMX_R0_WhiteNoise_R_0p02to50Hz_OpenLoopGainTF.xml
        2025-07-08_1530_H1SUSITMX_R0_WhiteNoise_T_0p02to50Hz_OpenLoopGainTF.xml
        2025-07-08_1530_H1SUSITMX_R0_WhiteNoise_V_0p02to50Hz_OpenLoopGainTF.xml
        2025-07-08_1530_H1SUSITMX_R0_WhiteNoise_Y_0p02to50Hz_OpenLoopGainTF.xml

SUS was in new HEALTH_CHECK state, so R0 tracking is OFF and alignment offsets are OFF, but damping loops are *on.*
SEI / HPI / ISI was FULLY_ISOLATED, in its best performing state.

Data analysis and commentary to come.

J. Kissel

Continuing on the campaign of gathering open loop gain (and loop suppression & closed loop gain TFs), I measured that for H1SUSTMSX M1 damping loops this morning -- see

   /ligo/svncommon/SusSVN/sus/trunk/TMTS/H1/TMSX/SAGM1/Data/
        2025-07-08_1525_H1SUSTMSX_M1_WhiteNoise_L_0p02to50Hz_OpenLoopGainTF.xml
        2025-07-08_1525_H1SUSTMSX_M1_WhiteNoise_P_0p02to50Hz_OpenLoopGainTF.xml
        2025-07-08_1525_H1SUSTMSX_M1_WhiteNoise_R_0p02to50Hz_OpenLoopGainTF.xml
        2025-07-08_1525_H1SUSTMSX_M1_WhiteNoise_T_0p02to50Hz_OpenLoopGainTF.xml
        2025-07-08_1525_H1SUSTMSX_M1_WhiteNoise_V_0p02to50Hz_OpenLoopGainTF.xml
        2025-07-08_1525_H1SUSTMSX_M1_WhiteNoise_Y_0p02to50Hz_OpenLoopGainTF.xml

SUS was in HEALTH_CHECK state, with alignment offsets and it's companion QUAD's L2/TMS tracking off, but damping loops turned back ON.

Data analysis and commentary to come.

TITLE: 07/08 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 6mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

Currently we are in an initial alignment. I'll let that finish and then put the detector in idle

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

Got a notification for H1 assistance.  H1 dropped from observing just under 3.5hrs ago.  After a couple of PRMI cycles, DRMI did lock within 40min, but immediately lost lock at DRMI LOCKED CHECK ASC.  Then an Initial Alignment was immediately run in just under an hour @1024UTC.  At this point, H1 attempted lock but had another lockloss at DRMI LOCKED CHECK ASC again, but after this lockloss H1 made it up to CARM 5PicoMeters for the next lockloss.  Next attempt made it to a CARM OFFSET Reduction Lockloss.  Then after no luck locking PRMI and it being over 3hrs, I got the wake up call.  

It's sounding like H1 has been having this Locking ailment as of late.

Going to let it finish a 2nd IA I started at @1253UTC after seeing that PRMI looked fine (flashes looked good on camera and are over 100 counts for POP18/90).  Initial Alignment just completed and locking clock is restarting. 

(Which is good, because my NoMachine is having the symptom that the mouse pointer does not match it's location in my No Machine session intermittantly (basically I'll have the mouse pointer over a spot, i.e. "X" to close an MEDM window, but when I try to click the "X" with the pointer, the pointer is actually, in the No Machine session, about 10" to the left (or right---basically somewhere else!), so it's hard to operate in my NoMachine session. The mouse would be fine on my laptop's monitor.  I've had this issue off and on for a few months.  With that said, ....after about 15min, my mouse now works OK in NoMachine!)

H1 is now back to DRMI (after the recent Alignment).  Camera flashes look centered and POP18/90 flashes are just under 200.  Leaving H1 for automatic operations  while I see if I can get return to sleep.  At 1325UTC/625amPDT, DRMI locked, btw.

TITLE: 07/08 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Very quiet shift with H1 observing after getting relocked. I was originally going to drop observing at some point to try SQZ alignment and angle scans to bring the BNS range up, but since the range has actually been improving over the course of this lock stretch and all four detectors are up and observing, I opted not to and we will see how things change overnight. H1 has now been locked and observing for 4.5 hours.

• 23:14 - Lockloss
• 00:46 - Observing

FAMIS 31093

Not much to report this week other than the FSS TPD has drifted down again slightly.

Today we've had to run many initial alignments and mess around with mirror alignments to cajol DRMI into locking. In the first part of the day, we were coming back from a big earthquake which had kept us down for hours. I don't know what we can attribute the struggle to lock to, but it can't be related to the BS heating since we had been down for many hours.

Later in the day, we were relocking after a few hours up, and just after the lockloss we proceeded to DRMI locking. The alignment was very poor. The guardian quickly took us to PRMI and then MICH FRINGES because of the very bad alignment. This is perhaps a sign that the BS slow release method isn't working so well, since it should keep the alignment decent just after lockloss. I cleared the history on the BS M1 pitch lock bank, and proceeded to help the MICH FRINGES and PRMI state by hand. Once we got back to DRMI we were able to lock relatively quickly.

I am suggesting that our DRMI locking problems are "maybe not an alignment issue" because this morning after several alignments, DRMI took a very long time to lock, and just after lockloss in the afternoon, where the slow release method should help keep the alignment good, the alignment was very bad. Maybe we should look into the triggers or engagement of the locking to see if there is a problem there. Just based on my experience this afternoon, I would want to turn off the BS slow release, or recheck that it is doing what we want it to do.

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

Relocking notes:
Today started off with an Initial_Alignment that was interrupted by earthquake mode being reactivated.
Which prompted another Inital_Alignment.
While trying to relock there was many attempts at the  DRMI-> PRMI-> Check_Mich_Fringes which yeilded no locking results.
Another Initial Alignment happened, Which allowed us to lock DRMI but we caught a lockloss at LOW_NOISE_COIL_DRIVERS, and on the next attempt OMC_WHITENING.

After that H1 Bouced around through DRMI-> PRMI-> and Check_Mich _Fridges again until another Inital_Alignment was ran.

We finally got back to NLN at 20:54 UTC and were locked for a little over 2 hours before the 4pm Lockloss struck.


LOG:                                                                           

Today while in DRMI ASC, and while trying to debug other problems with DRMI acquisition, Ryan, Tony, and I saw that the DRMI ASC starting pulling the buildups in a bad direction, which made no sense. We were trying to figure out which loops were the culprit, when I saw that the SRC1 offsets were engaged. These offsets had been put in place during the problems with the OFI, and we don't run with these offsets in full lock anymore. I turned the offsets off and the buildups starting moving in the good direction again. This is very confusing, because we've been running like this for ages probably without a problem. Today it was suddenly a problem. I commented out the lines in the ISC_DRMI guardian state PREP_DRMI_ASC where these offsets are turned on and loaded.

TITLE: 07/07 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 4mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: H1 just lost lock after a couple hours of being locked, so starting relocking now.

• Wind and microseism low
• All other systems nominal

 M. Todd, S. Dwyer

We moved the OPO crystal around again, following the work we did last week. We had much better luck this time with the translation stage controller (until the end, where we seemed to lose where we were).

After we took the measurement at -1100, we decided that given the historesis in the controller the better way to go back to a "position" was to set our OPO temperature to the value that corresponded to that position and move the controller until we re-found the green/ir coresonance.

We tried this, and then got veeery lost. But eventually found our way closer to our high NLG and ~31.4 OPO crystal temp, but it was not at the position we expected it to be at. This method may be refined in the future, where instead of doing finite steps with the controller to map out the NLG parameter space, we could sweep the OPO temp and follow it with the controller position via the co-resonance.

Regardless, we are at a much higher NLG than when we started!

18:52 UTC lockloss while we were in OMC_WHITENING damping violins

Below is the summary of the DQ shift for the week from 2025-06-16 to 2025-06-22

• During this week, the average BNS range was ~150 Mpc with a low of ~130 Mpc and a high of ~160 Mpc.
• The average duty cycle of this week was ~69%.
• We did see some line structures in the strain spectrogram at different frequencies, some of the causes are not obvious.
• There was some excess earthquake motion on Monday, Wednesday, Saturday, and Sunday.
• The wind motion was excessive on Tuesday and Thursday.
• Thursday, the glitch rate was pretty high due to the wind.
• There is a line structure at ~ 7 Hz in the corner BSC Y arm throughout the week. It was more significant on Friday.
• Hveto summary is not available on Saturday. Mostly, ASC (H1:ASC-Y_TR_B_NSUM_OUT_DQ -top count) channels were the winning channels, but other channels also won on some days.
• Lasso-No channels with significant correlation this week.
• Line count from FScan was below the alert threshold throughout the week.

The full DQ shift report with day-by-day details and plots is available here.

We had been locked for just over 3 hours, the circulating power was ~378.5kW in each arm, a little under the usual 380kW.

Broadband:

Start: 2025-07-04 00:50:39

Stop: 2025-07-04 00:55:50

Data: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250704T005039Z.xml

Simulines:

Start: 2025-07-04 00:56:56.978617 UTC // GPS: 1435625834.978617

Stop: 2025-07-04 01:20:13.539672 UTC // GPS: 1435627231.539672

Data:

2025-07-04 01:20:13,381 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250704T005657Z.hdf5
2025-07-04 01:20:13,389 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250704T005657Z.hdf5
2025-07-04 01:20:13,394 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250704T005657Z.hdf5
2025-07-04 01:20:13,398 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250704T005657Z.hdf5
2025-07-04 01:20:13,403 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250704T005657Z.hdf5