Matt Todd, Sheila Dwyer

We moved the OMC alignment a bit in pitch while watching for a response in kappa C. The attached screenshots show the updated pitch offsets that have been accepted in safe and observe.   The next screenshot shows us stepping this around. 

Overall, we improved the optical gain by something like 0.5 %.  We would like to return to the yaw offsets to see if we can recover the 1% optical gain that we lost during the vent.

Lockloss during commissioning at 2025-06-25 17:52UTC after over 5.5 hours Locked. Cause not known, but probably not commissioning related.

Wed Jun 25 10:12:58 2025 INFO: Fill completed in 12min 55secs

MEDM

Confusingly we have been running with two separate copies of the vacuum overview MEDM.

CDS_OVERVIEW has been using /ligo/lho/h0/ve/medm/beckhoff/H0_VAC_SITE_OVERVIEW_CUSTOM.adl (not under any version control)

SITEMAP has been using /opt/rtcds/userapps/release/vacuum/h0/medm/Target/H0_VAC_SITE_OVERVIEW_CUSTOM.adl (under git version control)

It is the second one, which is git controlled, which should be used. I took the opportunity when fixing the MEDMs to remove use of the /ligo files and move CDS_OVERVIEW over to using the Target file.

Changes made to the site overview and committed to git (see attachment) are:

RED - HAM1 now only shows the new PT100_MOD2 gauge

YELLOW - IP24,IP25 have new names

PURPLE - text to show the local git working directory and git repo information

VACSTAT

I added the new HAM1 PT100_MOD2 gauge to VACSTAT last night. Initially I also removed the temporary H1 PT100B gauge, but then remembered this has channels in H1EPICS_VACSTAT.ini which caused EDC disconnects.

So for now VACSTAT has the new H0 PT100_MOD2 (not in DAQ) and the old H1 PT100B (in DAQ, but needs to be removed)

Trip levels were returned to pre-vent values.

I just took some No SQZing time (starting at 2025-06-25 15:01 UTC (1427040078)) and compared it to the pre-vent No SQZ Time of 2025-03-26 16:01 UTC (1427040078). I used the command python3 range_compare.py 1427040078 1434898893 --span 600. I originally wanted to use a time span of half an hour instead of 10 minutes, but the March time had some sort of glitch that messed up its range calculation, and the range calculation for today's time was the same, so I went with 10 minutes. Here's the range comparison.

TITLE: 06/25 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 2mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:

Observing and have been Locked for almost 2.5 hours. Range is okay at 145Mpc, it looks like its been drifting a bit down since the lock started.

Signal railed about 5:18 PM local time, I checked trend data for PT120 and PT180 and no pressure rise noted inside the main volume.  Attached is 3 day trend of the pump behavior, very glitchy for a long while already.

System will be evaluated as soon as possible.  AIP last replaced on 2015, see aLOG 18261.

Lockloss From Nominal_Low_Noise @ 03:01:08 UTC.

I'm not exactly sure what caused this LL .

With the HAM1 ion pump performing nobly, the HAM1 turbo pump was spooled down and the associated SS-500 pump cart was disconnected from the HAM1 volume.  All mechanical sources of vacuum equipment noise should be in nominal observing mode.  

The HAM1 pressure gauge, PT-100, was connected via a standard gauge pigtail cable, directly from gauge body sub-D to supply CPC.  All of the temporary cabling was removed including the breakout board and analog voltage readout pigtail, so PT-100 is solely on Ethercat communication.  

Famis 28411 Weekly In-Lock SUS Charge Measurement.

This command is very useful to determine if the SUS charge measurements ran in the last week:
ls /opt/rtcds/userapps/release/sus/common/scripts/quad/InLockChargeMeasurements/rec_LHO  -lt | head -n 6

Coherence for bias_drive_bias_off is 0.06426009151210332, which is below the threshold of 0.1. Skipping this measurement
Cannot calculate beta/beta2 because some measurements failed or have insufficient coherence!
Cannot calculate alpha/gamma because some measurements failed or have insufficient coherence!
Something went wrong with analysis, skipping ITMX_13_Hz_1434811847

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

Currently Observing at 150Mpc and have been Locked for just over 2 hours. Relocking went pretty smooth, with the only issue being DRMI/PRMI taking very long to catch still. During maintenance today, the auxiliary pumps around HAM1 were turned off, and the jitter noise that we had been seeing around 550-600Hz is basically almost fully gone.

LOG:

14:30 Observing at 145Mpc and have been Locked for almost 4 hours
14:45 Out of Observing to run SUS Charge measurements
15:00 Lockloss during SWAP_BACK_ETMX
    - It doesnt look like it was due to anything that was happening with the swap

19:31 Started relocking
    - Initial alignment
    - Lockloss from MOVE_SPOTS
22:33 NOMINAL_LOW_NOISE
22:34 Observing

Range comparison plot:
Command Ran:  python3 range_compare.py 1396833438 1434842418 --span 1800
time 1 is April 11th 2024
time 2 is today at 23:20 UTC June 24th 2025
 

Ansel, Sheila, Camilla

Last week, Ansel noticed that there is a 2Hz comb in DARM since the break, similar to that that we've seen from the HWS camera sync frequency and power supplies and fixed in 75876.  The cabling has not been changed since, the camera sync frequency has been changed.

Our current camera sync frequencies are: ITMX = 2Hz, ITMY = 10Hz. We have typically seen these combs in H1:PEM-CS_MAG_LVEA_OUTPUTOPTICS_Y_DQ. With a 0.0005Hz BW on DTT I can't easily see these combs, see attached.