Sheila, Camilla

We ran a couple of squeezing angle scans to check the settings of the ADF servo. 

One thing that we realized is that the ADF Q demod signal is divided by H1:SQZ-ADF_OMC_TRANS_Q_NORM rather than mulitplied which is what we had thought.  We changed the coefficent from 0.18 to 5.8. The first png attachment shows that this transforms the blue ellipse into the orange one.  It would be a bit better if we first adjusted the demod phase to maximize the Q signal, so that the ellipse would be aligned along the axis, and the rescaled version would be more like a circle.  However you can see in the right side plot that this gives us a reasonably linear readback of sqz angle as we change the RF6 demod angle (which is actually cabled up to RF3 phase) about 150 degrees where our best squeezing is.

Camilla turned the servo back on in sqzparams. 

For future reference, a slightly better way to do this would be to move the demod phase to maximize Q, do a scan and set H1:SQZ-ADF_OMC_TRANS_Q_NORM to the ratio (max of Q)/ (max of I).  Then you can do a smaller scan around the point with the best squeezing, and in sqzparams set sqz_ang_adjust_ang to the readback angle that you think is best.

Thu Jul 17 10:07:21 2025 INFO: Fill completed in 7min 17secs

Just some quick directions on how to run a script to get the full 524 kHz DCPD data, and then save it in a useful file format.

The script to save this is in /ligo/home/elenna.capote/OMC_DCPD/H1OMCDPCD_HF.py

Right now it is set to collect data from these two channels (line 62 of the code):

channels = ["H1:OMC-DCPD_A0_OUT", "H1:OMC-DCPD_B0_OUT"]

The amount of time to collect data is set on line 66:

duration = 600  # seconds

To run the code:

> conda activate labutils

> python H1OMCDPCD_HF.py

The files will be saved in /ligo/home/elenna.capote/OMC_DCPD in a new folder labeled with a datetime and "xcorr_data" since I have traditionally used this script to collect data for cross correlation measurements. However, you can change the label on line 71, label="xcorr_data"

The output is a set of 1 second HDF5 frames for each second of data collection (so 600 seconds = 600 files). To put this data into a single .gwf format of the full data length, which can easily be read in with GWPY, use the combine.py script. Copy combine.py into the new directory with the frames and run it. The code generates a file for each OMC DCPD channel at the full rate, and at a decimated 64 kHz rate.

This is a bit odd the way it is set up, but the way this works ensures that even if you have to quit the script early, you don't lose all the data, since it saves each file by the second.

We were locked for over 6.5 hours when the measurements were started.

Simulines start:

PDT: 2025-07-17 08:07:30.859380 PDT
UTC: 2025-07-17 15:07:30.859380 UTC
GPS: 1436800068.859380
 

Simulines end:

PDT: 2025-07-17 08:30:47.210989 PDT
UTC: 2025-07-17 15:30:47.210989 UTC
GPS: 1436801465.210989
 

Files:

2025-07-17 15:30:47,050 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_
SS/DARMOLG_SS_20250717T150731Z.hdf5
2025-07-17 15:30:47,058 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DA
RM_SS/PCALY2DARM_SS_20250717T150731Z.hdf5
2025-07-17 15:30:47,062 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L1_SS/SUSETMX_L1_SS_20250717T150731Z.hdf5
2025-07-17 15:30:47,067 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L2_SS/SUSETMX_L2_SS_20250717T150731Z.hdf5
2025-07-17 15:30:47,073 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_
L3_SS/SUSETMX_L3_SS_20250717T150731Z.hdf5
 

TITLE: 07/17 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.18 μm/s
QUICK SUMMARY: We've been locked for 6.5 hours, range steady around 150Mpc. Looks like the earth has finally calmed down after the large earthquake and aftershocks in Alaska yesterday. Planned calibration and commissioning today (1500-1930UTC).

State of H1: Observing at 154Mpc

Following the power supply replacement at EX earlier tonight, Oli and I were able to recover H1 and run an initial alignment (only ETMX needed some adjustment). Lock acquisition afterwards went without issue and fully automatically and H1 began observing as of 08:16 UTC.

One thing that needed attention after rebooting the EX frontends is a restart of the ALS_XARM Guardian to reinitialize its awg connections; something we've encountered before after frontends are rebooted. I also restarted PEM_MAG_INJ and ESD_EXC_ETMX while I was at it, as I think these are the only nodes that need an awg connection to EX.

TITLE: 07/16 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Ryan S is currently working to get the detector back up through running an initial alignment after Dave and Fil helped fix the power supply failure at EX (85805).

After getting back up after the earthquake, there were some sdf diffs relating to the Big Red Button:

-  On ISIHAM2/3/4/5 saying that there were filter diffs for ISI-HAM{2,3,4,5}_GS13INF. I called Jim and he let me know that those were because of SPM diffs on each HAMs' ISI_HAM{2,3,4,5} guardian and that all I needed to do was INIT each of the guardians. I did that and they cleared.

- On SEIPROC - Jim fixed those somehow (sdf)

LOG:

23:00UTC Unlocked and waiting for the ground to calm down from the huge earthquake
00:31 Started trying to relock
    - Ran an initial alignment
01:52 NOMINAL_LOW_NOISE
    - Had SDF diffs from ISIHAM2/3/4/5 saying that there were filter diffs for ISI-HAM{2,3,4,5}_GS13INF. I called Jim and he let me know that those were because of SPM diffs on each HAMs' ISI_HAM{2,3,4,5} guardian and that all I needed to do was INIT each of the guardians. I did that and they cleared.
    There were also a few sdf diffs on SEIPROC that Jim fixed somehow
02:16 Observing
    03:49 GRB-Short E581446 - Observing
04:11 Lockloss due to power supply failure
    - ETMX M0/R0 suspension WD tripped
    - ETMX and TMSX OSEMs in FAULT
    - ETMX HWWD tripped (I put SEI_ETMX in ISI_OFFLINE_HEPI_ON beforehand)
    05:02 GRB-Short E581463 - not locked
06:39 Started trying to relock

Lockloss at 2025-07-17 04:11 UTC due to a power issue with ETMX and TMSX. Currently in contact with Dave and Fil is on his way in.

ETMX M0 and R0 watchdogs tripped

ETMX and TMSX OSEMs are in FAULT

ETMX ESD off

ETMX HWWD notified that it would trip soon, so SEI_ETMX was preemptively put into ISI_OFFLINE_HEPI_ON to keep ISI from getting messed up when it trips

Based on noise budget injections that we have been running since the vent recovery, I put together a low frequency LSC and ASC sub-budget, and made a total budget.

The results show that the noise that limits DARM from 10-20 Hz is very well understood by LSC and ASC noise. Above 20 Hz, ASC noise drops quickly to be more than a factor of 10 below DARM. LSC noise first drops to a factor of 3 below DARM at 20 Hz and then closer to a factor of 5 by 40 Hz.

For the ASC subbudget, I focused on the "usual suspects", choosing to show the HARD loops as well as the MICH ASC. During vent recovery, both MICH ASC loops were put into a higher bandwidth state to counter various instabilities. I'd like to try to put them back in a lower noise control design, which may directly lower DARM noise to at least the level of DHARD Y in the ASC budget. This budget incorporates the slightly lower noise DHARD that I implemented yesterday. Since the vent, CHARD P noise has been the lowest it has been for O4 due to the improved isolation of the HAM1 chamber. Notably missing here is CSOFT P, which I haven't been able to measure yet, but tends to strongly couple to DARM from about 10-15 Hz. The other soft loops couple less, and are not very likely to have a significant effect on this result.

If we can achieve some reduction of the ASC noise, we will reach the LSC noise limit, which is limited by our ability to fit the feedforward well at low frequency.

This noise budget does not include DAC noise or OSEM noise, although we've previously shown those to be smaller than the LSC and ASC noise, especially above 20 Hz.

These budgets were made using excess power projections. The DARM trace and ambient noise levels were chosen from an observing time last night, and the coupling functions were measured recently in June.

TITLE: 07/16 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: RyanC
CURRENT ENVIRONMENT:
    SEI_ENV state: EARTHQUAKE
    Wind: 13mph Gusts, 5mph 3min avg
    Primary useism: 0.52 μm/s
    Secondary useism: 0.45 μm/s
QUICK SUMMARY:

We are currently in DOWN still waiting out the huge earthquake from Alaska that came through a bit ago (85799). Ground motion is still pretty elevated, so it mgiht be another couple of hours at least  until we can start trying to recover the ifo

TITLE: 07/16 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Oli
SHIFT SUMMARY: We stayed lock for most of the shift, a large earthquake struck soon after losing lock. We're still ringing down as of 23:30UTC.
LOG:                                                                                                                                                                                                                                                                        

• 18:21 - 18:25 UTC We dropped Observing to try and improve SQZing as LLO was also out of observing
• 20:03 - 20:08 UTC We dropped Observing as the SQZer lost lock and relocked itself
• 20:29 UTC Lockloss from an ETMX glitch
  • 20:43 UTC 7.3 EQ from the Aleutians, I hit the big red button alog85799
  • Ground motion was so high picket-fence was registering it as a glitch