At the time of starting these measurements, we had only been Locked for 1.5 hours, so we were not fully thermalized
CALIBRATION_MONITOR screen and pydarm report are attached

Broadband
2025-08-13 16:13:34 - 16:18:45 UTC
/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250813T161334Z.xml

Simulines
2025-08-13 16:19:57 - 16:43:04 UTC
/ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250813T161958Z.hdf5
/ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250813T161958Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250813T161958Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250813T161958Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250813T161958Z.hdf5

At the time of starting these measurements, we had only been Locked for 1 hour (1hr10min since MAX_POWER), so we were not fully thermalized
CALIBRATION_MONITOR screen and pydarm report are attached

Broadband
2025-08-13 15:31:30 - 15:37:02 UTC
/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250813T153151Z.xml

Simulines
2025-08-13 15:38:19 - 16:01:22 UTC
/ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250813T153820Z.hdf5
/ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250813T153820Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250813T153820Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250813T153820Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250813T153820Z.hdf5

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

Currently Observing at 153 Mpc and have been Locked for 10 minutes

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

Nice shift with H1 locked 6hrs15min.  We did have 3 drop-outs due to TCS ITMy CO2 (all quick and automatic recoveries).  ~45min after the 3rd drop, ther was superevent S250813k.  Ended the night checking out peak Perseids just before the moon was rising.
LOG:

• 0032 Turned off turbo at MY (janos)
• Observing DROPs:  TCSy Laser unlocked, but found a new locking point and came back automatically.
  • 0048-0050
  • 0055-0056
  • 0135-0136
• 0212 S250813k
• 0426-0452 Drove out to the Y-arm +1km spot to look at Perseids (saw 6 meteors [and 6 satellites]).  Moon was barely rising (about 3-diameters) as I drove back to the Control Room. 

Just had a couple of drops from Observing due to TCS_ITMY_CO2 guardian saying laser is unlocked and needed to find a new locking point.  (Attached are the two occurrences thus far).

TITLE: 08/12 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 143Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Currently Observing at 145 Mpc and have been Locked for 50 minutes. Relocking went pretty well today with the only concern being the fast shutter not firing during the last lockloss (86324), but luckily it seems like we were okay and that was expected in that situation.
LOG:

14:30UTC Locked for 5.5 hours and running magnetic injections
    14:40 Back into Observing
    14:45 Out of Observing for SUS charge measurements
14:57 Lockloss
19:18 Started relocking
    - Initial alignment - BS ADS convergence took 16+ minutes (86320)
20:47 NOMINAL_LOW_NOISE
    20:55 Observing
21:12 Lockloss
22:44 NOMINAL_LOW_NOISE
    22:46 Observing                                                                                                                                                                                                                                                                                                    

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

Got the hand-off from OIi which was standard other than their mention of the Fast Shutter note after a lockloss they had from their first locking attempt post-Maintenance.  H1 has currently been locked for almost an hour. 

(oh and Oli did also mention on leaving that they & Elenna noticed there was a Verbal Alarm for a PR3 saturation which happened about 20min after being in observing---they mentioned this is an odd thing for PR3.)

Operator Checksheet NOTES:

• FOM wall scan: 
  • CDS Overview has: 
    • (1) CDS Server Room Environment is YELLOW for MY due to Light Level being at ~65% (vs sub-5%),
    • (2) CDS ALARM box is red due to an MY VAC pressure signal (was also red yesterday) and looking at the screen for this, I'm guessing texts have already been sent to "system's engineers"
  • Calibration ndscope (nuc26):  Elenna noted it looked odd (all signals were flat), and she logged in to see it was paused, so she hit the Start Online button to bring it back.
  • Ran the "check_dust_monitors_are_working" script and have had the usual notifications for LVEA5 & LAB2 dust monitors.
• Access System "flashing doors" at:  VPW LDAS entry, VPW dirty shop entry, & EY mechanical room person door.
• Control Room Screenshots:  "H1 Glitches" (nuc27) not updating (has trouble screen for browser, which has been case for a while)

Ivey, Edgard, and Brian have created new estimator fits (86233) and blend filters (86265) for the SR3 Y estimator, and we have new rate channels (86080), so we were excited to be able to take new estimator measurements (last time 85615).

Unfortunately, there were issues with installing the new filters, so I had to make do with the old filters: for the for the estimator filters, I used the fits from fits_H1SR3_2025-06-30.mat, and the blend filters are from Estimator_blend_doublenotch_SR3yaw.m, aka the DBL_notch filter and not the new skinny notch. These are the same filters used in the testing from 85615.

So the only difference between the last estimator test and this one is that the last test had the generic satamp compensation filters (85471), and this measurement has the more precise 'best possible' compensation filters (85746). Good for us to see how much of a difference the generic vs best possible compensation filters make.

Unfortunately, due to the filter installation issues as well as still trying to re set up the estimator channels following the channel name changes, I also didn't have much time to run the tests, resulting in the actual test with the estimator being only 5 minutes. Hopefully this is okay enough for at least a preliminary view of how it's working and then next week we can run a full test with the more recent filters. Like last time, the transition between the OSEM damping and the estimator damping was very smooth and the noise out of the estimator was visibly smaller than with the regular damping (ndscope1).

Measurement times
SR3 Y damp -0.1
2025-08-12 18:28:00 - 18:44:00 UTC

SR3 Y damp -0.1, OSEM damp -0.4
2025-08-12 18:46:46 - 19:03:41 UTC

SR3 Y damp -0.1, Estimator damp -0.4
2025-08-12 19:09:00 - 19:16:51 UTC

Oli told me that the TCS CO2Y Chassis Tripped off during Maintenance this morning. This is not surprising as there was alot of craning work going on near that rack and the CO2 chassis are known to be fussy, see FRS 6639.

When I went to untrip it both indicator lights were red on it but after key-ing off/on, it turned on with no issues. 

Lockloss at 2025-08-12 21:12UTC after 25 minutes locked

Sheila, Jennie, Matt, Camilla. WP#12750

Followed what we did in 82881, but did not need to adjust alignment through the EOM. 

Starting with:

• 89mW into EOM, 85mW out of EOM.
• With 5V on ISS AOM controlmon: 22mW in 0th order and 9mW in first order beam.
• With 0V on ISS AOM controlmon: 33mW after AOM

Then with 0V on ISS AOM controlmon, increased to 73mW (85% throughput). Then put 5V on controlmon and started to maximize the 1st order beam. We decided to not completely maximize 1st order as this reduces overall throughput and our current aim is to increase total green throughout, not ISS AOM range.

Ended with:

• With 5V on ISS AOM controlmon: 40mW in 0th order and 13mW in first order beam.

Sheila then adjusted the alignment into the fiber and maximized H1:SQZ-OPO_REFL_DC_POWER from 1.55 to 2.8. 

This allowed us to have an OPO setpoint of 80uW with 20mW going into the fiber, wirth 5 on the controlmon and a spare 20mW that we could give to the fiber.  Note that after ~1hour when we got to NLN, the controlmon had decreased from 5 to 2.5. So the power to the AOM may need to be increased next time we loose lock. Maybe with SQZT0 temperature changes now doors are on and fans are off. 

There was a high pitched noise in SQZT7, close to the -Y side of the table, we couldn’t figure out what it was and maybe will have someone from EE help us with it another week. 

I ran the SCAN_OPOTEMP guardian state (twice as it was far off) once we wer close to NLN.

WP12746 h1omc0 Low Noise ADC Autocal Test

EJ, Jonathan, Dave:

For a first test we restarted h1iopomc0 three times to run an autocal on the low-noise ADC -- each time the autocal Failed. Next test will be to power cycle existing card leading to possible replacement.

WP12755 TW1 Raw Minute Trend Offload

Dave:

h1daqtw1 was configured to write it raw minutes into a new local directory to isolate the last 6 months of data from the running system. The NDS service on h1daqnds1 was restarted to serve these data from this location while the file transfer progresses.

Restarts

Tue12Aug2025
LOC TIME HOSTNAME     MODEL/REBOOT
09:06:26 h1omc0       h1iopomc0   <<< three ADC AUTOCAL tests
09:08:12 h1omc0       h1iopomc0   
09:08:58 h1omc0       h1iopomc0   
09:09:12 h1omc0       h1omc       <<< start user models
09:09:26 h1omc0       h1omcpi     
11:51:19 h1daqnds1    [DAQ] <<< reconfigure for TW1 offload
 

Unplugged an unused extension cord by the PSL racks. 

High bay and LVEA and entrance lights turned off, paging system off. Oli checked WAP is off.

Everything else looked good.

Yesterday, we installed the BTRP (Beam Tube Roughing Pump) adapter flange on the 13.25" gate valve just to the -X side of GV13.  This included installing a 8" GV onto the roughing pump port of the adapter, moving the existing gauge tree onto the new adapter, and installing a 2.75" blank on an unused port.  All of the new CF joints were helium leak tested and no signal was seen above the ~9e-11 torrL/s background of the leak detector. 

The assembly is currently valved out of the BT vacuum volume via the 13.25" GV, and is being pumped down via small turbo and aux cart.  Therefore, the PT-343 gauge reading is only reporting on the BTRP assembly pressure, not the main BT pressure, so it can be ignored until further notice of it being vavled back in.  This system has been pumping via aux cart or leak detector since ~2pm yesterday, and will continue to be pumped until it is in the pressure range of the BT volume.  The aux cart is isolated by foam under the wheels, but some noise may be noticed by DetChar folks, hence the DetChar tag on this report.

3:47:39 UTC unknown Lockloss