Fri Aug 22 10:08:42 2025 INFO: Fill completed in 8min 38secs

Closes FAMIS#26550, last checked 86343

Laser Status:
    NPRO output power is 1.865W
    AMP1 output power is 69.91W
    AMP2 output power is 140.3W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 9 days, 22 hr 41 minutes
    Reflected power = 23.7W
    Transmitted power = 105.3W
    PowerSum = 129.0W

FSS:
    It has been locked for 0 days 7 hr and 57 min
    TPD[V] = 0.8324V

ISS:
    The diffracted power is around 4.0%
    Last saturation event was 0 days 12 hours and 31 minutes ago

Possible Issues:
    PMC reflected power is high

TITLE: 08/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 15mph Gusts, 10mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY:

Observing at 153Mpc and have been Locked for 6.5 hours.

TITLE: 08/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

Uneventful shift up until a M7.5 EQ took over!  Shift's almost over and I'm guessing we have another 45+min until we get out of LARGE_EQ mode.  Will be switching over to automatic operations shortly and gave TJ a status text earlier tonight.  Picket Fence continues to flash yellow.
LOG:

• Tony noticed the Teamspeak server was down at the beginning of the shift and all other servers were down except virgo's--so we switched to using the virgo Teamspeak for the night.
• 00:09-00:15 shuttering shutters in the PCal Lab (tony)
• 01:04:58 - 01:05:00 Big glitch on H1 (but nothing out of the ordinary seen on other FOMs)
• 02:36 LOCKLOSS due to Big EQ

H1's been down about 45min so far due to a M7.5 EQ....waiting for the earth to calm down, but the R-Waves are barely rolling through now.

Jeff, Oli

Today we tested out the SR3 estimators for both Pitch and Yaw (86491). The ASC loops where we see a difference are DHARD, MICH, SRC1, and SRC2, since these all go through the SRC to their output ports. As expected, we don't see any effect on CHARD, PRC, or INP.

I've plotted comparisons of the ASC control and error signals during those times along with a reference time of earlier that morning.

The ultimate conclusion is that the SR3 P and Y estimators do work to make some of the ASC noise better, and the good thing is that in the places where we see that the estimator makes the noise worse, they all seem like easy improvements/fixes! The amount of improvement that we see doesn't look like much, but that's also expected since it's just SR3 that has the estimator out of the several suspensions in each ASC path. We expect that as we add more estimators along these paths, we will keep picking away at the suspension noise. We already see really impressive broadband improvement between 1-5 Hz on SRC1 and SRC2!

Main areas of concern:
    - For all ASC loops and both P and Y, we see heightened SR3 resonances on around 0.7 Hz when the SR3 P estimator is on. This is because the OSEM P blend filter was made without including the 0.7-0.8 Hz mode. That is being added in and that should solve that issue
    - Between 0.1 and 0.2 Hz for some loops, turning on the estimators puts in some extra noise from the GS13s, which aren't as sensitive at those lower frequencies. To solve this, we will be adding a high pass filter above those frequencies
    - A few peaks aren't being damped as well with the estimator as they were with normal damping; however, now that we've shown that the estimator decreases our noise(86455, 86503), we are hoping to be able to increase gain somewhere in the estimator system (possibly in SR3_M1_EST_Y_FUSION_MEAS_BP) to better damp our resonances while still seeing improvements in noise as compared to normal damping

Here are the times used to grab the traces:
Estimator ON for SR3 P and Y (RED) 2025-08-21 16:35:00 UTC
Estimator ON for SR3 Y (BLUE) 2025-08-21 15:34:06 UTC
Estimator ON for SR3 P (GREEN) 2025-08-21 16:05:00 UTC
Estimator OFF (PINK) 2025-08-21 10:27:00 UTC

I created an updated blend for the SR3 pitch estimator. These are in the SUS SVN next to the first version. (see LHO log 84452)

The design script is blend_SR3_pitchv2.m

the Foton update script is make_SR3_Pitch_blend_v2.m

these are both in {SUS_SVN}/HLTS/Common/FilterDesign/Estimator/  - revision 12608

The update script will install the new blends into FM2 of SR3_M1_EST_P_FUSION_{MEAS/MODL}_BP with the name pit_v2. pit_v1 should still be in FM1. Turn on FM2, turn FM1 off. 

Jeff and Oli tried the first one, and see that the first 2 modes (about 0.65 and 0.75 Hz) are seeing more motion with the estimator damping than the normal damping. To correct this, _v2 add OSEM signal to the estimator for those modes. See plots below - First 2 are the _v2 blend and a zoom of the _v2 blend. figure 3 shows the measured pitch plant vs. OSEM path - the modes line up pretty well. There is a bit of shift because the peaks are close together. I expect hope this will not matter. Figure 4 shows the plant vs. the model path. Now all 4 modes are driven by the measured OSEM signal instead of the model. 

It is interesting to see that the model was not doing a good job of predicting the motion at the first 2 peaks. This is (I guess) because either (a) the model and the plant are different - or - (b) there are unmodeled drives pushing the plant (the suspension) that the model doesn't know about. 

I'm guessing the answer is (b - unmodeled drives) and is likely from DAC noise. I think this because
1 - The plant fit is smooth and really good.
2 - In the yaw analysis that Edgard and Ivey are doing (not yet posted) the first mode of the yaw plant can be seen with the OSEM, but the ISI motion is much too small to excite that level of motion. But the OSEM can see motion, so something is exciting that motion.
3 - The DAC noise is the only thing I can think of.

Quick chat with Jeff indicates that the DAC noise models at those frequencies are not well trusted. We'll try something anyway and see if it is close. I don't see how to use the estimator to deal with that noise - we'd need to have an accurate realtime measurement. 

At the beginning of this shift, Tony noticed that we had errors for the LHO Control Room Teamspeak.  He mentioned this to Jonathan, and they found out that all the LIGO/MIT Teamspeak servers are down and that we should use the Virgo server to maintain communications.  So---You can find the "LHO Control Room" teamspeak account at:

• server:  teamspeak.ego-gw.it
• room:  EM Follow-up

Of course you can always phone the Control Room as well.

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

H1's been locked 3.25+hrs.  TJ passed on what he needed to do for relocking earlier (I've not had to lock H1 for any of my last 6-evening shifts in a row this week...we'll see how tonight goes for my last (7th EVE) shift of the week!).  Environmentally, we had a small EQ from Japan roll through, winds are low, and µseism has slowly popped above the 50th percentile in the last 24hrs.

TITLE: 08/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Locked for 3 hours. We had one lock loss during commissioning today, which had an automated relock. The SR3 OSEM esitmators are running now, but that is the only notable change to the IFO. There have been many trips out to the OSB vertex area to escort contractors, mark utilities, and search for a valve out in the hydrant area. Times in the log.
LOG:

• 1046 GRB Short E592190
• 1533 Comissioning start
• 1825 Lock loss
• 2014 Observing

The annulus ion pump for BSC1 has railed again, this morning at ~3am PDT. There was no change in the internal pressure measured at PT120B (BSC2).

Gerardo and I had swapped the pump controller, see alog 85975, after it had railed previously.

We will continue to monitor and troubleshoot during the next Tuesday maintenance. Pump likely needs replacement.

J. Kissel, O. Patane

We tested both the P and Y GS13 state-space estimator's sensor correction to the OSEM damping loops for the M1 stage of H1SUSSR3 this morning. See LHO:86491. Here're some of the local metrics showcasing the performance differences between "P and Y estimators OFF" and "P and Y estimators ON."

This alog is intended as record keeping for a quick investigation into an out of observing mode data request for GPS time 1422964623 (Feb 7, 2025), when the LHO interferometer had just relocked, but calibration had not settled.

Relevant monitoring lines and kappa value trend can be seen on the calibration  LHO grafana page.

I picked a period 15 minutes after the gps time as well settled (although Kappa_C was trending up with thermalization) to create an estimated calibration model closer to what I think should have been applied at the GPS time.  I then took the ratio of that model's response function over the response function of the actually applied calibration model which was using the clearly frozen time dependent correction factors right after reaching low noise.

The attached plot of that ratio shows the ratio has a maximum deviation in magnitude of about 12% and 8 degrees.  I don't think this is exactly right, due to the clear trend in the kappa_C on the grafana page, but its close enough that I'd certainly be comfortable with a flat +/- 20%/20 degrees uncertainty statement.

Caused by comissioning activities.

Marc replaced the bad 18bit DAC, system was powered back up 07:57

I can see all the cards in the IO Chassis, h1iopsusex started with no problems, followed by the user models.

I reset the SWWD on SUS and SEI.

HWWD had not tripped overnight.

Marc is heading out of EX, Ryan is untripping the user model watchdogs and preparing for IFO recovery.