TITLE: 08/01 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 21mph Gusts, 14mph 3min avg
Primary useism: 0.07 μm/s
Secondary useism: 0.05 μm/s
QUICK SUMMARY:
Observing reached at 23:43:12 UTC But only after spending 13 min trying to determine why there is are SEI SDF Diffs.
We, (TJ, Oli, Me) decided to just accept them and hope for the best.
TITLE: 08/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Currently in NLN, but waiting to go into Observing after we figure out some weird SDF diffs with ISIHAM2/3/4/5.
LOG:
14:30UTC Relocking and in ACQUIRE_PRMI
15:23 NOMINAL_LOW_NOISE
15:25 Observing
18:06 Out of Observing due to SQZ unlock
18:12 Back into Observing
18:12 Out of Observing due to SQZ unlock
18:14 Back into Observing
18:15 Out of Observing due to SQZ unlock
18:45 Lockloss
- sat in DOWN for a bit due to high ground motion and wind
- ALSX was unlocking 10 seconds into LOCKING_ALS
21:59 NOMINAL_LOW_NOISE
- Needed to INIT HAM 2/3/4/5 ISI guardians to remove SPM (and SDF) differences - caused a lockloss
22:02 Lockloss
22:54 NOMINAL_LOW_NOISE
- Adjusted OPO temp and that got FC to lock
- Issues with ISIHAM2/3/4/5 sdf diffs for GS13INF V1/2/3
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 15:05 | FAC | Nelly | OpticsLab | n | Tech clean | 15:17 |
| 18:51 | VAC | Gerardo | FCES | n | Moving power supply | 19:51 |
| 20:02 | Ibrahim | CER | n | Grabbing laptop | 20:04 | |
| 20:03 | FAC | Eric | EY | n | Checking on chiller alarm | 20:27 |
| 20:23 | Ibrahim | CER | n | Getting another laptop | 20:26 | |
| 22:33 | VAC | Gerardo | FCES, FCET | n | Putting a couple labels on | 22:49 |
(Jordan V., Tony S., Gerardo M.)
Late entry
To get the gauge working at the filter cavity tube cross C7 we pulled the EtherCAT cable from cross C7 to cross D1, this allowed us to daisy chain the gauges at both crosses. To land the EtherCAT cable both ends were terminated, thanks Tony. To get power to the gauge we used one of the outlets in the filter cavity enclosure and a small din rail mountable power supply, the supply provides 24 VDC. Patrick took care of the software, see his aLOG here.
Currently we have the following items valved out along the filter cavity, two ion pumps;IPFCC6, IPFCC8, and the gauge PTCC7. We plan to incorporate them to the main vacuum volume on the next couple of weeks. Pressure at the gauge is low, thus we need to pump its volume down using an aux cart and a small turbo pump.
Last tuesday I was able to valve in the last two ion pumps into the filter cavity tube envelope, two of the 10" isolation valves at section C were closed to achieve this, then as the internal pressure of the filter cavity tube settle the isolation valves were opened.
Something to note with the performance of the HV cable for IPFCC8 (ion pump a the filter cavity cross 8) is a bit noisy, I noticed that the controller got noisy when I touched the HV cable, but will check both at a later time, maybe cable, grounding and/or controller issue.
(Anna I., Jordan V., Gerardo M.)
Last tuesday we valved in a gauge to the filter cavity tube vacuum volume.
We pumped the dead volume down until the pressure reached high 10^-07 torr, then introduced the gauge to the "short" volume of the filter cavity tube, we had closed two isolation valves, we waited about 10 minutes, then the isolation valves were opened. No issues to report.
Lockloss at 2025-08-01 22:02 UTC after 3 minutes in NLN. We couldn't go into Observing because of SPM differences causing SDF diffs in the guardians for ISIHAM2/3/4/5. Last time we had this, I asked Jim what to do and he said to just INIT the guardians, and it caused a glitch, but we did not lose lock, and he said INITing them should not cause glitches or locklosses (85809). Today, I did the same thing and went to INIT the guardians, but when doing it for the first one, ISIHAM2, it caused a glitch and we lost lock from it.
I don't see anything fishy going on on the guardian side of things here. When the ISI_HAM2 node had rerun the HIGH_ISOLATED state, after running through INIT, it changed a bunch of the GS13INF gains. See the end of the guardian log for the ISI_HAM2 and SEI_HAM2 nodes in the attached txt file. We then saw these changes later as well in SDF (alog84140), so the large earthquake script button might be conflicting with this.
Lockloss at 2025-08-01 18:45UTC due to earthquake
We are holding in DOWN due to the earthquake
Fri Aug 01 10:11:21 2025 INFO: Fill completed in 11min 17secs
Closes FAMIS#26433, last checked 86020
Everything is looking good besides the PMC reflected power being a bit high - it looks like it's been increasing over the past month.
Laser Status:
NPRO output power is 1.866W
AMP1 output power is 69.95W
AMP2 output power is 140.6W
NPRO watchdog is GREEN
AMP1 watchdog is GREEN
AMP2 watchdog is GREEN
PDWD watchdog is GREEN
PMC:
It has been locked 2 days, 2 hr 18 minutes
Reflected power = 23.73W
Transmitted power = 105.5W
PowerSum = 129.3W
FSS:
It has been locked for 0 days 2 hr and 47 min
TPD[V] = 0.7741V
ISS:
The diffracted power is around 3.8%
Last saturation event was 0 days 2 hours and 47 minutes ago
Possible Issues:
PMC reflected power is high
Closes FAMIS#26504, last checked 85571
T240 (channels averaged between 2025-08-01 15:08:44 - 15:08:54 UTC)
Averaging Mass Centering channels for 10 [sec] ...
2025-08-01 08:08:54.266493
There are 12 T240 proof masses out of range ( > 0.3 [V] )!
ETMX T240 2 DOF X/U = -1.424 [V]
ETMX T240 2 DOF Y/V = -1.323 [V]
ETMX T240 2 DOF Z/W = -0.982 [V]
ITMX T240 1 DOF X/U = -2.045 [V]
ITMX T240 1 DOF Z/W = 0.443 [V]
ITMX T240 3 DOF X/U = -2.17 [V]
ITMY T240 3 DOF X/U = -0.963 [V]
ITMY T240 3 DOF Z/W = -2.619 [V]
BS T240 1 DOF Y/V = -0.351 [V]
BS T240 3 DOF Z/W = -0.431 [V]
HAM8 1 DOF Y/V = -0.541 [V]
HAM8 1 DOF Z/W = -0.871 [V]
All other proof masses are within range ( < 0.3 [V] ):
ETMX T240 1 DOF X/U = -0.121 [V]
ETMX T240 1 DOF Y/V = -0.125 [V]
ETMX T240 1 DOF Z/W = -0.158 [V]
ETMX T240 3 DOF X/U = -0.094 [V]
ETMX T240 3 DOF Y/V = -0.182 [V]
ETMX T240 3 DOF Z/W = -0.111 [V]
ETMY T240 1 DOF X/U = -0.015 [V]
ETMY T240 1 DOF Y/V = 0.105 [V]
ETMY T240 1 DOF Z/W = 0.155 [V]
ETMY T240 2 DOF X/U = -0.123 [V]
ETMY T240 2 DOF Y/V = 0.156 [V]
ETMY T240 2 DOF Z/W = 0.02 [V]
ETMY T240 3 DOF X/U = 0.163 [V]
ETMY T240 3 DOF Y/V = 0.004 [V]
ETMY T240 3 DOF Z/W = 0.071 [V]
ITMX T240 1 DOF Y/V = 0.244 [V]
ITMX T240 2 DOF X/U = 0.164 [V]
ITMX T240 2 DOF Y/V = 0.252 [V]
ITMX T240 2 DOF Z/W = 0.218 [V]
ITMX T240 3 DOF Y/V = 0.104 [V]
ITMX T240 3 DOF Z/W = 0.117 [V]
ITMY T240 1 DOF X/U = 0.038 [V]
ITMY T240 1 DOF Y/V = 0.096 [V]
ITMY T240 1 DOF Z/W = -0.0 [V]
ITMY T240 2 DOF X/U = 0.022 [V]
ITMY T240 2 DOF Y/V = 0.244 [V]
ITMY T240 2 DOF Z/W = 0.089 [V]
ITMY T240 3 DOF Y/V = 0.044 [V]
BS T240 1 DOF X/U = -0.08 [V]
BS T240 1 DOF Z/W = 0.162 [V]
BS T240 2 DOF X/U = 0.068 [V]
BS T240 2 DOF Y/V = 0.161 [V]
BS T240 2 DOF Z/W = 0.027 [V]
BS T240 3 DOF X/U = -0.161 [V]
BS T240 3 DOF Y/V = -0.294 [V]
HAM8 1 DOF X/U = -0.216 [V]
STS (channels averaged between 2025-08-01 15:09:20 - 15:09:30 UTC)
Averaging Mass Centering channels for 10 [sec] ...
2025-08-01 08:09:30.264056
There are 2 STS proof masses out of range ( > 2.0 [V] )!
STS EY DOF X/U = -4.662 [V]
STS EY DOF Z/W = 2.344 [V]
All other proof masses are within range ( < 2.0 [V] ):
STS A DOF X/U = -0.46 [V]
STS A DOF Y/V = -0.752 [V]
STS A DOF Z/W = -0.633 [V]
STS B DOF X/U = 0.163 [V]
STS B DOF Y/V = 0.96 [V]
STS B DOF Z/W = -0.374 [V]
STS C DOF X/U = -0.762 [V]
STS C DOF Y/V = 0.795 [V]
STS C DOF Z/W = 0.575 [V]
STS EX DOF X/U = -0.135 [V]
STS EX DOF Y/V = -0.089 [V]
STS EX DOF Z/W = 0.05 [V]
STS EY DOF Y/V = 1.196 [V]
STS FC DOF X/U = 0.198 [V]
STS FC DOF Y/V = -1.143 [V]
STS FC DOF Z/W = 0.603 [V]
TITLE: 08/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 9mph Gusts, 6mph 3min avg
Primary useism: 0.06 μm/s
Secondary useism: 0.05 μm/s
QUICK SUMMARY:
Currently relocking and in ACQUIRE_PRMI. Looks like the last lockloss at 2025-08-01 12:34UTC was probably from an earthquake
ndscope showing when we lost lock relative to the ground motion.
15:25 UTC Back to Observing
TITLE: 08/01 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Straightforward shift with calibration sweeps run opportunistically and just one lockloss, which H1 is still relocking from due to ground motion. Currently relocking and up to ACQUIRE_PRMI.
Lockloss @ 03:36 UTC after 7 hours locked - link to lockloss tool
Possibly an ETM glitch? Hard to say, but the ground was mostly calm at the time, although it's shaking more now as H1 attempts to relock.
It looks like all the QUADs suddenly moved a lot and caused the lockloss, but their movement doesn't look like it was caused by the ETMX glitch. I'm not sure what would have caused it if the ground was calm at the time? ASC and LSC channels all look fine and I couldn't find any other evidence of an excursion.
This morning I changed the matrix that sends DCPD ADC channels to the 524 kHz test channels that Jeff set up and described in 82686, hoping that this might be useful for following up on some of investigations that Kiet has done on violin mode contamination. 85026
Right now, I've set them up to send the 4 individual ADC channels for DCPD A to all 4 filters, so that A CH0 is A1, A CH1 is B1, A CH2 is A2, and A CH3 is B2.
One striking thing in the first look I've taken at these spectra is that the rms is dominated by high frequency lines (and somewhat the 1kHz violin modes), 10215.3 Hz (f1) is the loudest followed by 10436.9 Hz (f2) and 8154.8 Hz (f3). We have been wondering if a quadratic response of the ADC could explain the violin mode contamination, so I checked the 6 combinations of these frequencies, at this resolution I only see a peak at f2 + f3 = 18591 Hz.
Since there was a lockloss during the regularly scheduled calibration measurement time this morning, with Jenne's permission I dropped H1 out of observing and ran them this afternoon after H1 had been locked for 3 hours. Calibration monitor screenshot and report attached.
Broadband PCal: 23:39:04 to 23:44:14 UTC
Simulines: 23:44:56 to 00:08:12 UTC
2025-08-01 00:08:11,966 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250731T234457Z.hdf5
2025-08-01 00:08:11,973 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250731T234457Z.hdf5
2025-08-01 00:08:11,978 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250731T234457Z.hdf5
2025-08-01 00:08:11,983 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250731T234457Z.hdf5
2025-08-01 00:08:11,987 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250731T234457Z.hdf5
This is a look at the data that Camilla and TJ took in 85957, motivated by some modeling work that Kevin and Dan have been doing. We took data to look at the squeezing rotation around the arm higher order modes, to compare to measurements that Kevin took using the ADF. We borrowed Jeff's DCPD test matrix to create a DCPD sum channel at 524kHz, and used a modified version of Elenna's script to save 5 minutes of no squeezing data from the individual DCPDs. 85937
Process details:
The first plot here shows the spectra and cross correlation, subtraction and rebinning that I did. We took 5 minutes of data for each of these traces, and 1 second FFTs, so we have 300 averages and the cross correlation asd should be a factor of 300^1/4 = 4 below the no squeezing asd. (Thanks to Elenna for pointing out that I was doing this ratio for the PSD). This is not far below the squeezing level, so when we do the subtraction of the cross correlation the squeezing data becomes noisy. We could do this with shorter FFTs to get the cross correlation lower where the noise is uncorrelated between the two DCPDs, but we want to subtract some fairly narrow features from the spectra, so our best option if we are bothered by this noisy subtracted squeezing data would be to take a longer no squeezing time. After doing the subtraction I rebinned the data to 3 Hz bins.
Looking at higher order mode frequencies:
The next plot shows this data plotted in dB of squeezing, you can identify the higher order modes most clearly from looking at the mid squeezing data where the higher order modes cause a rotation of the squeezing angle. Zooming in on 10 kHz you can identify the higher order mode frequencies as roughly 10615+/5 Hz and 10565+/- 10Hz from the X arm modes (see 84172 for ID with X arm), with the uncertainty based on what I can place as limits by eye, which is worse for the lower mode. The separation of these into different peaks means that there is some astigmatism in the X arm. The y arm mode has much more correlated noise to subtract, and is sitting right under the forest of accoustic modes, but you can still see evidence of a rotation starting around 10.25kHz. This data isn't clear enough to estimate if there is similar evidence of astigmatism in the y arm.
Zooming in around 5kHz, we can see that there do seem to be two modes with rotations, one of them is sitting on top of a set of lines, but seems to be narrower than the other. The broad mode is at 5345+/- 15 Hz Hz and the narrower one is at 5184+/- 4Hz . Assuming that the second one is from the X arm based on the identification of the 2nd order modes, the second order mode frequency is 98.8+/- 0.3% of twice the first order mode frequency for the lower mode, and 99.3% +/-0.3% for the upper mode. This ratio is not 1 because the beam size of the 2nd order modes is slightly bigger than for the 1st order mode, since the mirror is non spherical its curvature is sightly different for the larger sized beam, so these ratios contain some information about how non spherical the mirrors are.
Squeezing loss and rotation estimates:
We can use this data to estimate a loss an rotation expirienced by the squeezing at these higher order modes. Using the mean squeezing data, where the squeezing angle is completely uncontrolled, and Camilla's measurement of the nonlinear gain of 13.8 we can estimtae the total squeezing efficiency (using the notation from Aoki):
Using this estimate we can predict the anti-squeezing level, which is mostly insensitive to squeezing angle, this prediction is plotted in the dark blue on the dB plot, where it agrees nicely with the measured anti-squeezing.
We can also make an estimate of the rotation using the mid squeezing data where we have about 5dB of anti-squeezing. To do this, I first fit the average squeezing angle for these measurements using data from 6.3kHz to 7.8kHz, using the Aoki equation:
We got three good sets of ADF measurements targeting the two X arm modes. One was taken before the ETMY ring heater was changed (85514) and two were taken after. The gps start times of the upper sideband sweeps for each of these measurements are
pre-RH change 1433785394
post-RH change 1 1436198864
post-RH change 2 1436809945
There are difficulties in calculating all of the squeezing metrics described in the ADF paper (PhysRevD.105.122005), but the squeeze angle is relatively straightforward to calculate using equations (26), (33), and (34) of that paper. (All of the lower sidebands in those equations should be the conjugates of the lower sidebands.) The first plot shows the inferred squeeze angle for these three measurements along with the DCPD spectra for those times. These are consistent with what you would expect for the rotation generated from an astigmatic arm cavity and can probably be fit with a bit more work. The flat line above 10.6 kHz in the post-RH change 2 rotation is because we lost lock at the end of that measurement. The rotation is fairly constant which isn't surprising since the Y arm modes were mainly changed by the ETMY RH change. The change in the DCPD is likely due to a change in the laser noise coupling independent of any squeezing effects.
The second plot compares these measurements with the ones that Sheila measured above. The data is noisy and there's about a 10 deg variation between the rotation inferred from mid SQZ + and mid SQZ - around the second peak but the mid-SQZ + magnitude and the mid-SQZ- frequency dependence are fairly consistent with the ADF measurements. Uncertainty in the NLG will propagate to uncertainty in the magnitude of the rotation in both cases.
These plots can be made by running the following in the aligoNB environment
pytest /ligo/gitcommon/squeezing/sqzutils/analysis/T_10kHz_ADF.py -s -k T_compare_10kHz
Last year we found that a problem with the H1 GS13 was causing a .375hz feature in the motion of the table which showed up in the filter cavity. The root issue was a GS13 having a low gain compared to the other sensors. I was able to compensate by adding a digital gain of 2. During the vent, this gain got reverted at some point and the sdf accepted. I didn't fix this when I found it because it didn't seem to be causing the same issue, but it seems the feature has now returned. Doesn't seem to be causing problems for the filter cavity that I've heard of, but the ISI and SUS definitely see this feature.
First image are the side osems for FC2 while the IFO was locked, the crosshair is at .375hz, similar to what we saw in the past.
Second image is the HAM8 summary page for today, the .375hz feature is clearly visible while the ISI is isolated.
Third image are l2l tfs for each co-located gs13/cps pair, the red trace shows the magnitude of this tf is almost exactly half the other 2 gs13/cps pairs, above 1 hz.
I will try to fix this next Tuesday, but if the filter cavity is having problems, caput H1:ISI-HAM8_GS13INF_H1_GAIN 2 in a terminal and then accepting the sdf diff should fix the issue.
The filter cavity has been having locking issues, the operators were tieing sometimes to high wind 85169 or low green power 85395:
After running calibration sweeps this evening and while H1 was still out of observing, I updated the GS13 gain as Jim describes above. The filter cavity saw some motion after I did this, but after a minute or two, things settled back out. I then accepted the SDF diff (screenshot attached) and took H1 back to observing.