aLIGO LHO Logbook

H1 General - Ops Eve Shift Start

oli.patane@ligo.org — Fri, 17 Jan 2025 16:24:48 -0800

Author: oli.patane@ligo.org

Report ID: 82333

TITLE: 01/18 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 10mph Gusts, 7mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:

Observing and have been Locked for over 10 hours. Range dipped a bit earlier due to unknown reasons, but looks to be slowly coming back up.

LHO FMCS - HVAC Fan Vibrometers Check FAMIS

oli.patane@ligo.org — Fri, 17 Jan 2025 15:26:22 -0800

Author: oli.patane@ligo.org

Report ID: 82332

Closes FAMIS#26354, last checked 82116

** Looking at last 2 weeks since last checked was on 01/04

Corner Station Fans (attachment1)
- All fans are looking normal and within range. There did look to be a period of extra noise following some sort of work done yesterday (Thursday 01/16) on MR FAN1 2, but that looks to have calmed down now.

Outbuilding Fans (attachment2)
- All fans are looking normal and are within range.

PEM

Images attached to this report

H1 ISC - Comment to Evidence for in-band lines caused by aliasing of lines in high-sampled frequency DCPD ADC

evan.goetz@ligo.org — Fri, 17 Jan 2025 14:34:33 -0800

Author: evan.goetz@ligo.org

Report ID: 82331

E. Goetz, L. Dartez We temporarily added extra digital AA filtering in the DCPD A1/2 B1/2 TEST banks (we are planning to revert to https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=82313 on Tuesday), to see if we can suppress the aliased artifacts. Repeating the same procedure as before: computing the ratio of the ASD of the decimated data to the ASD of the full 524 kHz band data, both with and without the extra digital AA filtering we can see a significant improvement in the low frequency artifacts. The temporary filtering is just copies of the standard 524k-65k and 65k-16k filters, but it shows significant reduction in low frequency artifacts (see especially Figure 2). This suggests that improvements to the sensing path anti-aliasing filtering would be beneficial to detector sensitivity, reducing the impacts of high frequency artifacts that are being aliased to in-band.CAL, DetChar, ISC

Images attached to this report

H1 ISC - Evidence for in-band lines caused by aliasing of lines in high-sampled frequency DCPD ADC

evan.goetz@ligo.org — Fri, 17 Jan 2025 13:18:27 -0800

Author: evan.goetz@ligo.org

Report ID: 82329

E. Goetz, J. Kissel, L. Dartez Summary: There is evidence that some of the lines found in the gravitational wave band are actually aliased lines from higher frequencies. So far it is unclear exactly how many of the lines in the run-averaged list are due to this problem and if the lines are stationary or if violin ring-ups may induce more lines in band due to aliasing artifacts. Further investigation is needed, but this investigation suggests that the current level of anti-aliasing is insufficient to suppress the artifacts at high frequency aliasing into the gravitational wave band. Details: We used the live, test-point acquisition of the 524 kHz sampled DCPD data in DTT, channel H1:OMC-DCPD_B1_OUT (equivalent to the nominal H1:OMC-DCPD_B0_OUT channel used in loop). This channel had the same 524k-65k and 65k-16k decimation digital AA filtering applied. The time series was exported from DTT and processed by stitching together the time segments into a single time series. Then one can process the time series using the scipy.signal.welch() function of 1) the full 524 kHz sampled data, 2) 524 kHz sampled data decimated (no additional AA filtering) by a factor of 32 to get the 16 kHz sampled frequency data, 3) 524 kHz sampled data decimated using additional AA filtering by using the scipy.signal.decimate() function which has a built-in anti-aliasing filter. We also plotted in DTT the individual channels against the 16k H1:OMC-DCPD_B_OUT_DQ channel, showing that some of the lines are visible in the in-loop DCPD 16 kHz channel, but not visible in the test point 524 kHz channels. Figure 1: ASD of raw 524 kHz data (blue), decimated data without any extra anti-aliasing filter applied (orange), and decimated data with additional anti-aliasing filtering (green). Orange peaks are visible above the blue and green traces above ~750 Hz. Figure 2: ASD ratio of the decimated data without anti-aliasing filtering to the raw data showing the noise artifacts Figure 3: Zoom of figure 2 near 758 Hz Figure 4: ASD computed from DTT showing DCPD B Ch 1, 5, 9, 13 and and the H1:OMC-DCPD_B_OUT_DQ channel at the same time as the 9 and 13 channels were acquired (limitations of the front end handling of 524 kHz test points to DTT) Figure 5: Zoom of figure 4 near 758 Hz We were also interested in the time-variability of these artifacts and watched the behaviour of H1:OMC-DCPD_B_OUT_DQ, and saw amplitude variations on the order of factors of a few and frequency shifts on the order of 0.1 Hz, at least for the artifacts observed near 758 Hz. Figures 4 and 5 indicate that there are more artifacts not necessarily directly caused by aliasing; perhaps these are non-linearity artifacts? This needs further study. A count of the number of 0.125 Hz frequency bins from 0 to 8192 Hz of the ratio between downsampling without additional anti-aliasing filtering and the raw 524 kHz ASD indicates that ~4900 bins are above a threshold of 1.1 (though most of those bins are above 2 kHz, as indicated by figure 2).CAL, DetChar, ISC

Images attached to this report

H1 SEI - Comment to HAM1 Summary: Beam Diverter Optic Swap, New REFL PD Prep Work, (4) L4C sensors installed inside Optics Table

corey.gray@ligo.org — Fri, 17 Jan 2025 12:57:01 -0800

Author: corey.gray@ligo.org

Report ID: 82330

Since, there has been a recent search for the D1300278 cables, and just for documentation, wanting to update this alog to note that the cable for this new REFL PD (LSC REFL B) was D1300278-V2-S1301459 (the shorter 106" long cable) and entered into ICS.

LHO VE - Fri CP1 Fill

david.barker@ligo.org — Fri, 17 Jan 2025 10:22:37 -0800

Author: david.barker@ligo.org

Report ID: 82328

Fri Jan 17 10:09:34 2025 INFO: Fill completed in 9min 30secs

Images attached to this report

H1 PSL - PSL Status Report (FAMIS #26349)

corey.gray@ligo.org — Fri, 17 Jan 2025 08:02:46 -0800

Author: corey.gray@ligo.org

Report ID: 82327

Laser Status:
    NPRO output power is 1.842W
    AMP1 output power is 70.11W
    AMP2 output power is 137.6W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 30 days, 21 hr 54 minutes
    Reflected power = 25.75W
    Transmitted power = 102.5W
    PowerSum = 128.2W

FSS:
It has been locked for 0 days 2 hr and 54 min
TPD[V] = 0.773V

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

Possible Issues:
PMC reflected power is high

PSL

LHO General - Fri Ops Day Transition

corey.gray@ligo.org — Fri, 17 Jan 2025 07:45:54 -0800

Author: corey.gray@ligo.org

Report ID: 82325

TITLE: 01/17 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY:

H1 had 2-locklosses overnight which came back automatically. Ther was a drop from 0944--0945 due to PI24. Microseism is squarely between 50th-95th percentile and winds are low. Nuc31's USGS website needed a refresh; nuc35's MC2 & PR2 cameras are offline/blue.

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Thu, 16 Jan 2025 22:01:18 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82324

TITLE: 01/17 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 22:34 UTC (7hr 30 min lock)

Smooth shift locked the whole time.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
17:16	SAFETY	LAZER HAZ (\u2310\u25a0_\u25a0)	LVEA	!!!YES!!!	LVEA = LASER HAZARD!	16:51
00:28	JOG	Camilla	Y arm	n	Improve or maintain health	01:00

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Thu, 16 Jan 2025 16:13:59 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82321

TITLE: 01/17 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: Tony
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 22:34 UTC

LOG:

None

H1 TCS - Comment to CO2Y RIN at CW and PWM

camilla.compton@ligo.org — Thu, 16 Jan 2025 15:16:10 -0800

Author: camilla.compton@ligo.org

Report ID: 82319

I misread the graph, for CW 100%

CW = 3880 counts, 49.1W laser power ~ RIN 1.5e-6 but limited by electronics noise (6e-3/3880). This is higher than the 6 x 10^-7 measured in 81863.

LHO FMCS - Increasing temperatures in Zone 2A and 5 in LVEA

eric.otterman@ligo.org — Thu, 16 Jan 2025 13:38:46 -0800

Author: eric.otterman@ligo.org

Report ID: 82318

The increase in space temperature in zones 2A and 5 in the LVEA this morning appears to be from sun exposure on the building. Both zones experienced rapid increases at the same time, at the same rate of increase. Both zones have the most sun exposure during the morning hours. The space sensors are located in the exterior walls which makes them susceptible to radiant heating during periods of direct sun exposure. These sensor locations also caused issues at the mid and end stations, when the southern exposures routinely read colder when the winds blow. I have made slight adjustments to the set points in zones 2A and 5 to accommodate for the sun exposure. If it continues to be a problem, sensor relocation will likely be needed.

H1 ISC - Optimising OMC QPD offsets

jennifer.wright@ligo.org — Thu, 16 Jan 2025 12:53:53 -0800

Author: jennifer.wright@ligo.org

Report ID: 82316

We haven't aligned the OMC ASC for while so today I did Gabriele's method where we inject lines in the four OMC ASC loops at different frequencies and then demodulate the 410 Hz PCAL line at these frequencies and then at 410Hz to look at which combination of offsets improves our optical gain the most.

The plot of BLRMS of the DCPD_SUM_OUT at 410 Hz vs. QPD offset is shown below.

The start and end times used were 17:22:40 UTC and 17:42:40 UTC.

The detector was in NLN s but squeezing was turned off.

The code is at /ligo/home/jennifer.wright/git/2025/OMC_Alignment/OMC_Alignment_2025_01_16.ipynb.

Usually the start and end times the plots use contain some times without the OMC ASC lines but that was not possivle here as we went to NLN_CAL_MEAS before I had turned off the lines.

Looking at the plot, I think we need to change

H1:ASC-OMC_A_PIT_OFFSET by -0.1

H1:ASC-OMC_A_YAW_OFFSET by 0.075

H1:ASC-OMC_A_PIT_OFFSET by -0.075

H1:ASC-OMC_A_YAW_OFFSET by 0.08

or something close to these.

Images attached to this report

H1 ISC - Reducing ETMX glitches

jim.warner@ligo.org — Thu, 16 Jan 2025 12:34:34 -0800

Author: jim.warner@ligo.org

Report ID: 82315

As a follow up to my other post about ETMX glitches, I looked at using a strategy used in DRMI locking to try to help the IFO ride through the high frequency glitches that have been causing locklosses. On the BS suspension the ISC path includes filters that whiten the high frequency ISC signal, a limit is applied to that whitened signal then it's dewhitened. Think the filters used for this are a zpk(1,200,1) and it's inverse, with a limit of 50000 in the ISC input to the BS.

I attempted to look at the impact of doing that on a couple glitches leading up to a lockloss. I got data for the ESD drive from one of the lock losses and used lsim in matlab to model the change in the ESD timeseries. The attached image shows the timeseries for each step of whitening, limit and dewhiten compared to the original glitch. It's not a proper model of the DARM loop, Sheila and I might talk about doing that, I just wanted to see if doing the simplest estimate would blow up before digging deeper into it.

Thick blue is the original ESD drive from one of the quadrants, Red is the whitened siganl, yellow is the whitened signal limited to below the saturation level for the ESD, and the thin purple line is the dewhitened, final timeseries. The thin line doesn't show crazy behavior and stays below the saturation threshold (2^19*275, which comes from some adjustments made to accomodate the new dac on ETMX).

I expect if this worked, it would inject some higher frequency junk into this segment, but the glitches already do that. The hope is this would reduce the drive from these high frequency saturations and let the IFO ride them out.

Images attached to this report

H1 ISC - Filters redone in DCPD A1, A2, and B1, B2 TEST filter banks

jeffrey.kissel@ligo.org — Thu, 16 Jan 2025 11:53:02 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 82313

J. Kissel More changes along the lines of LHO:82261. As we continue to explore the configurations of the OMC DCPD channels, probing anti-aliasing and ADC noise, we find it helpful to have all of the frequency-dependent, actual physical channel filter differences available in all four test banks. As such, I've - changed the name of gain(0.25) filter from "sum2avg" to "sum4avg." Pun intended. - Copied the DCPD A "NewV2A" and "NewAW" from A0 now called "A_V2A" and "A_AW" into FM2 and FM3, - Copied the DCPD B "NewV2A" and "NewAW" from B0 now called "B_V2A" and "B_AW" into FM4 and FM5, and - Moved all of the channel-independent gains to the bottom row, FM6: "18b_cts2V" gain of 40 / 2^18 [V/ct] FM7: "sum4avg" gain of 0.25 FM8: "A2mA" - keeping only the FM1, 1 Hz 5th order elliptic highpass and the digital AA decimation filters, Dec65K and Dec16K in FM9 and FM10 in place. This filter file change has been loaded (because we're not in observing at the moment), and committed to the userapps repo, /opt/rtcds/userapps/release/cds/h1/filterfiles/ H1IOPOMC0.txt rev 30421.

Images attached to this report

H1 General - Thursday mid shift Lockloss

anthony.sanchez@ligo.org — Thu, 16 Jan 2025 11:36:01 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82314

TITLE: 01/16 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 3mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:

Comissioning Activities:
Calibration sweep: completed
OMC ASC Alignment test : Completed
PR2 Beam spot measurement : Ongoing.
PEM CPS Slider Ghost beam investigations: ongoing
SRC Injection sweeps: Complete
Squeeze measurements: Ongoing.

Lockloss from NLN_CAL_MEAS @ 18:56 UTC

Alarm Handler:
Dust PSL 101 again.

Lockloss

Images attached to this report

H1 AOS - pause added to guardian state 557

sheila.dwyer@ligo.org — Thu, 16 Jan 2025 10:51:32 -0800

Author: sheila.dwyer@ligo.org

Report ID: 82312

Camilla, Sheila, Erik

Erik points out that we've lost lock 54 times since November in the guardian states 557 558 transition from ETMX or low noise ESD ETMX.

We thought that part of the problem with this state was a glitch caused when the boost filter in DARM1 FM1 is turned off, which motivated Erik's change to the filter ramping on Tuesday 82263, which was later reverted after two locklosses that happened 12 seconds after the filter ramp, 82284.

Today we added 5 seconds to the pause after the filter is ramped off (previously the filter ramp time and the pause were both 10 seconds long, now the filter ramp time is still 10 seconds but the pause is 15 seconds). We hope this will allow us to better tell if the filter ramp is the problem or something that happens immediately after.

LHO VE - Thu CP1 Fill

david.barker@ligo.org — Thu, 16 Jan 2025 10:10:54 -0800

Author: david.barker@ligo.org

Report ID: 82310

Thu Jan 16 10:06:15 2025 INFO: Fill completed in 6min 12secs

Jordan confirmed a good fill curbside. TCs started high around +30C so trip temp was raised to -30C for today's fill. TCmins [-55C, -54C] OAT (2C, 36F).

Images attached to this report

H1 General - Comment to Lights had been on in LVEA Since Tuesday

david.barker@ligo.org — Thu, 16 Jan 2025 09:35:38 -0800

Author: david.barker@ligo.org

Report ID: 82309

Opened FRS33087 to potentially install a Gneiss environment monitor in the LVEA to read light levels via EPICS.

H1 CDS - Comment to Single Long Range Dolphin IPC receive errors on end station models for channels sent by the h1lsc model

david.barker@ligo.org — Thu, 16 Jan 2025 09:33:51 -0800

Author: david.barker@ligo.org

Report ID: 82308

I have cleared the end station SUS errors with a DIAG_REST when H1 was out of observe.

H1 CDS - Comment to Single Long Range Dolphin IPC receive errors on end station models for channels sent by the h1lsc model

david.barker@ligo.org — Thu, 16 Jan 2025 09:19:27 -0800

Author: david.barker@ligo.org

Report ID: 82307

FRS33085 is an umbrella ticket covering any IPC errors seen during O4.

Yesterday's IPC receive error was the fourth occurence during O4, we are averaging roughly one every six months.

H1 General - Lights had been on in LVEA Since Tuesday

camilla.compton@ligo.org — Thu, 16 Jan 2025 09:18:24 -0800

Author: camilla.compton@ligo.org

Report ID: 82306

Robert and I just went into the LVEA for Commissioning activities and the lights were already on. Expect they had been left on since Tuesday.

DetChar

H1 CAL - Calibration Sweep

anthony.sanchez@ligo.org — Thu, 16 Jan 2025 09:13:56 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82305

Latest Calibration:
gpstime;python /ligo/groups/cal/src/simulines/simulines/simuLines.py -i /ligo/groups/cal/H1/simulines_settings/newDARM_20231221/settings_h1_newDARM_scaled_by_drivealign_20231221_factor_p1.ini;gpstime

notification: end of measurement
notification: end of test
diag> save /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250116T163130Z.xml
/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250116T163130Z.xml saved
diag> quit
EXIT KERNEL

2025-01-16 08:36:40,405 bb measurement complete.
2025-01-16 08:36:40,405 bb output: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250116T163130Z.xml
2025-01-16 08:36:40,405 all measurements complete.

gpstime;python /ligo/groups/cal/src/simulines/simulines/simuLines.py -i /ligo/groups/cal/H1/simulines_settings/newDARM_20231221/settings_h1_newDARM_scaled_by_drivealign_20231221_factor_p1.ini;gpstime
PST: 2025-01-16 08:40:33.517638 PST
UTC: 2025-01-16 16:40:33.517638 UTC
GPS: 1421080851.517638

2025-01-16 17:03:33,281 | INFO | 0 still running.
2025-01-16 17:03:33,281 | INFO | gathering data for a few more seconds
2025-01-16 17:03:39,283 | INFO | Finished gathering data. Data ends at 1421082236.0
2025-01-16 17:03:39,501 | INFO | It is SAFE TO RETURN TO OBSERVING now, whilst data is processed.
2025-01-16 17:03:39,501 | INFO | Commencing data processing.
025-01-16 17:03:39,501 | INFO | Ending lockloss monitor. This is either due to having completed the measurement, and this functionality being terminated; or because the whole process was aborted.
2025-01-16 17:04:16,833 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250116T164034Z.hdf5
2025-01-16 17:04:16,840 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250116T164034Z.hdf5
2025-01-16 17:04:16,845 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250116T164034Z.hdf5
2025-01-16 17:04:16,850 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250116T164034Z.hdf5
2025-01-16 17:04:16,854 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250116T164034Z.hdf5
ICE default IO error handler doing an exit(), pid = 1289567, errno = 32
PST: 2025-01-16 09:04:16.931501 PST
UTC: 2025-01-16 17:04:16.931501 UTC
GPS: 1421082274.931501

Images attached to this report

H1 General - Thursday Morning Shift report

anthony.sanchez@ligo.org — Thu, 16 Jan 2025 07:51:03 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82304

TITLE: 01/16 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 21mph Gusts, 13mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.27 μm/s
QUICK SUMMARY:
IFO Locked for 24 hours!
Planned Comissioning time today from 16:30- 19:30 UTC where we will drop from observing for comissioning and calibration activities.

Alarm handler:
PSL Dust 101 & 102

Red but not actively alarming:
Vacuum alert: H0:VAC-LX_Y0_PT110_MOD1_PRESS_TORR
Trending this channel back it looks like its been red for days, and this Alog mentions that its not currently running

H1 CDS - Single Long Range Dolphin IPC receive errors on end station models for channels sent by the h1lsc model

david.barker@ligo.org — Wed, 15 Jan 2025 22:00:34 -0800

Author: david.barker@ligo.org

Report ID: 82303

At 17:48:23 Wed 15jan2025 PST all end station receivers of long-range-dolphin IPC channels originating from h1lsc saw a single IPC receive error.

The models h1susetm[x,y], h1sustms[x,y] and h1susetm[x,y]pi all receive a single channel from h1lsc and recorded a single receive error at the same time. No other end station models receive from h1lsc.

On first investigation there doesn't appear to be anything going on with h1lsc at this time to explain this.

Images attached to this report

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Wed, 15 Jan 2025 22:00:00 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82302

TITLE: 01/16 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 14:57 UTC (15 hr lock!)

Ultra-smooth shift - nothing of note.

LOG:

None

H1 General - Wednesday Day Shift end

anthony.sanchez@ligo.org — Wed, 15 Jan 2025 16:46:48 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82301

TITLE: 01/16 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:
Great Day of Observing!
Dropped down to Commissioning twice:
Once due to an earthquake causing the SQZr to lock loss- but we stayed in NLN.
And another time due to an Xtreme PI Damping event. Once again we stayed in NLN.

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
17:45	PSL	Ryan C	PSL Chiller	N	Checking the PSL Chiller water level	18:15
17:46	FAC	Kim	Optics Lab	Yes	Tecnical cleaning	16:46
17:56	PEM	Ryan C	VAC Prep	n	Tracing Dust mon issues and wires	18:16
19:05	PCAL	Francisco & Kim	PCAL	Yes	Technical Cleaning	19:34
21:13	R&R	JC	Overpass	N	Walking over to the Overpass	21:23
22:46	VAC	Janos	EX	n	Work in maintenance room	23:09
00:28	PCAL	Francisco	PCAL Lab	Yes	PCAL measurements	01:08

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Wed, 15 Jan 2025 16:06:15 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82300

TITLE: 01/16 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.34 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 14:57 UTC (9 hr lock!)

H1 SUS - Xtreme PI Damping

anthony.sanchez@ligo.org — Wed, 15 Jan 2025 15:42:42 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82299

23:39:06 UTC Xtreme PI damping took us out of Observing.
We got back into Observing at 23:40:06 UTC

H1 SQZ - SQZr unlocked by Earthquake?

anthony.sanchez@ligo.org — Wed, 15 Jan 2025 15:18:35 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82298

TITLE: 01/15 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.35 μm/s
QUICK SUMMARY:

Dropped from Observation at 15:22:22:40 UTC due to the SQZ system got unlocked. We did not drop out of Nominal_Low_Noise.
Looking slightly more into this, It looks like a 5.7Mag Eathquake may have unlocked the SQZ system.

Images attached to this report

H1 General - Comment to Wed Morning Shift

ryan.crouch@ligo.org — Wed, 15 Jan 2025 13:36:39 -0800

Author: ryan.crouch@ligo.org

Report ID: 82297

ETMY mode1s damping wasn't going well this morning and it was slowly rising (it did this a few times over the previous weekend as well), I went from +60 of phase to +30 and flipped the sign of the gain +0.1 -> -0.1, it has been damping for the past hour and has damped past where it was turning around with the previous settings.

SUS

H1 SUS - ALL* plotallsus_tfs.m scripts now plot cross-coupling

oli.patane@ligo.org — Wed, 15 Jan 2025 12:29:06 -0800

Author: oli.patane@ligo.org

Report ID: 82296

As an update to 80919, I have finished editing all* plotallsus_tfs.m scripts to now include the plotting of cross-coupling. There is an on/off boolean along with a matrix near the top of each script that allows you to choose whether or not to plot cross coupling, and between which DOF.

This can help when we want to check for cross-coupling before vs after a period of time/vent/etc.

* When I say all I mean every sus matlab script whose name is a variation of plotallsus_tfs.m or plotallsus_tfs_M1.m. I did not update the plotallsus_spectra.m or plotallsus_tfs_{some other stage}.m since those are not used as often. All changes verified to work and committed to svn.

H1 DetChar - Comparisons of GDS-CALIB_STRAIN_CLEAN and OMC-PI_DCPD_64KHZ_AHF_DQ at times with many narrow lines near violin modes

ansel.neunzert@ligo.org — Wed, 15 Jan 2025 10:51:53 -0800

Author: ansel.neunzert@ligo.org

Report ID: 82294

This comparison was suggested to help evaluate whether the narrow line contamination seen around violin mode regions during ring-ups is related to aliasing. The idea (as I follow it) is that because the 64 kHz channel has different aliasing, the noise ought to look different in the two channels if it is aliasing-related. In fact the two channels look similar, albeit not identical, which looks like evidence against the aliasing hypothesis. However, this test may not catch all the places where aliasing could occur, so it may not be conclusive. See the associated detchar-request issue for ongoing discussion.

The first two plots are from 2023, during time periods which were previously identified as having line contamination around the violin modes (71800, 79825). The last plot is from just a few days ago, on Jan 12.

DetChar

Images attached to this report

H1 CDS - Comment to CDS Maintenance Summary: Tuesday 14th January 2025

david.barker@ligo.org — Wed, 15 Jan 2025 10:43:37 -0800

Author: david.barker@ligo.org

Report ID: 82295

Tue14Jan2025
LOC TIME HOSTNAME MODEL/REBOOT
08:06:21 h1omc0 h1iopomc0 <<< Install RCG5.31
08:06:35 h1omc0 h1omc
08:06:49 h1omc0 h1omcpi

17:30:10 h1omc0 h1iopomc0 <<< Revert back to RCG5.30
17:30:24 h1omc0 h1omc
17:30:38 h1omc0 h1omcpi

LHO VE - Wed CP1 Fill, manually cancelled due to TCmins too high

david.barker@ligo.org — Wed, 15 Jan 2025 10:24:01 -0800

Author: david.barker@ligo.org

Report ID: 82293

Wed Jan 15 10:06:29 2025 ALERT: Fill done (errors) in 6min 25sec

TCs started very high, around +40C, and therefore TCmins [-28C, -27C] did not exceed the trip temp (-60C). After the TCs had flatlined I manually cancelled the fill.

OAT (-1C, 31F) and foggy.

Images attached to this report

H1 PSL - Comment to PSL_Chiller: Check PSL chiller.

ryan.crouch@ligo.org — Wed, 15 Jan 2025 09:49:52 -0800

Author: ryan.crouch@ligo.org

Report ID: 82292

I topped off the PSL chiller with ~100mL of water.

PSL

H1 PSL - Comment to PSL_Chiller: Check PSL chiller.

anthony.sanchez@ligo.org — Wed, 15 Jan 2025 09:41:32 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82291

I just got the verbal alarms alert to Check the PSL Chiller.

H1 PSL - PSL_Chiller: Check PSL chiller.

anthony.sanchez@ligo.org — Wed, 15 Jan 2025 09:35:52 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82290

Diag Main has now got a PSL_Chiller message telling me to Check the PSL Chiller. I ran the PSL Status script to hopefully get some insight. Laser Status: NPRO output power is 1.842W AMP1 output power is 70.15W AMP2 output power is 137.0W NPRO watchdog is GREEN AMP1 watchdog is GREEN AMP2 watchdog is GREEN PDWD watchdog is GREEN PMC: It has been locked 28 days, 23 hr 15 minutes Reflected power = 25.55W Transmitted power = 102.4W PowerSum = 127.9W FSS: It has been locked for 0 days 3 hr and 32 min TPD[V] = 0.781V ISS: The diffracted power is around 4.2% Last saturation event was 0 days 3 hours and 32 minutes ago Possible Issues: PMC reflected power is high Check chiller (probably low water) PSL probably wants some water and someone to chill with. The plots below seem like it might be a little lonely. PSL

Images attached to this report

H1 General - Wed Morning Shift

anthony.sanchez@ligo.org — Wed, 15 Jan 2025 08:06:11 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82287

TITLE: 01/15 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 1mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.35 μm/s
QUICK SUMMARY:

When I walked in H1 had been locked and Observing for 33 minutes!

Unknown lockloss this morning at 13:17 UTC
H1 Manny relocked without assistance this morning and no one was even woken up.

PS: It's a little icey out in the parking lot so be prepared stepping out of your car.

Lockloss

Images attached to this report

H1 TCS - AOM Drive output now connected to CO2X table feedthrough

camilla.compton@ligo.org — Wed, 15 Jan 2025 07:59:24 -0800

Author: camilla.compton@ligo.org

Report ID: 82288

Camilla, TJ, Marc, Fil. WP#12281

We attached the AOM drive cable from the back of the D1300649 chassis to the lowest TEST point in the PEM feed through photo on the CO2X table. We used two barrel connectors (photos attached) to do this as it looks like there used to be an AOM driver on the table that the signal went into before going to the AOM.

We thought that we could use the digital filters in the h1tcscs model to create a loop with this output and feed to the Synrad UC-2000 PWM controller (needs 0-10VDC). The max of CTRL2 was capped at +/-2 (unsure why) and this was actually +/- 0.6V on the BNC via an oscilloscope. We'll need to increase this by ~x10 to get PWM to work. Reverted changed sdfs.

There was an unknown cable also labeled AOM drive coming into the table, not connected to anything photo.

Images attached to this report

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Tue, 14 Jan 2025 22:00:01 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82286

TITLE: 01/15 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 05:40 UTC (20 min lock!)

Overall, bad recovery from maintenance. Here’s what happened in 7 short stories:

Late LN2 Fill: NORCO arrived to fill CP8 at 00:34 UTC (16:34 PT) over 3 hours late while we were locking. Jim made EX as robust as possible such that we would survive their truck moving through. This worked though the BRS was all over the place as expected. Due to them driving <5mph as requested, they took 20 minutes to arrive at EX, then over 1 hr to do the fill and then another 20 minutes to get back. They left site at 02:34 UTC (18:34 PT). After NORCO left, I undid Jim’s seismic configuration changes to go back to nominal.
Changes made prevented locking: Earlier in the day, (before NORCO arrived), we lost lock at state 557/8, TRANSITION_FROM_ETMX. I was told by the DAY operator that if this happened, I was to revert Camilla’s changes in alog 82277 with regard to the DARM Boost. Since Camilla and Sheila were in the room when this happened, they decided not to do it since it could have just been bad luck. Erik had also made changes regarding ramp times that affect this state. Camilla and Sheila left for the day and then NORCO arrived. While NORCO was filling, we lost lock again at state 557, TRANSITION_FROM_ETMX. Camilla told me to revert her changes and Jenne told Erik to revert his. This was done by 1:31 UTC (17:31 PT).
Changes reverted prevented locking: We could not lock ALS until Norco left the EX area, which happened ALS locked finally at 02:10 UTC (while Norco was en route from EX). Locking then happened automatically until state 500, PREP_DC_READOUT_TRANSITION, where for 10 minutes, I was getting the error message “OMC not ready”. I then called Camilla, who didn’t answer. I then called Erik, who was still on site and came to help troubleshoot the issue (since his changes involved resetting OMs - the idea was that maybe this is related, which it is likely not). After some fiddling to no avail, I called Sheila (the first person on the call list), who walked me through the OMC troubleshooting process.
Troubleshooting with Sheila and Erik: I informed Sheila that the error was that the OMC TF was not letting guardian continue. We did a manual OMC scan while waiting at ASC_QPD_ON to see that there indeed were triplets, with 2 sidebands and one carrier with the right magnitude. We let guardian lock it and it did, yielding the expected signal magnitude for the DCPD_SUM and PZT2 Monitors. Looking closely at the error, Erik realized that it was the phase that was below the threshold (150) and was measuring at 144. Sheila, Erik and I then decided to lower the phase threshold to 140. This worked immediately until we also lost lock just as immediately when we transitioned to DARM_TO_DC_READOUT, which saturated DCPD, EX, EY, IX and HAM6. This happened at 04:13 UTC (20:42 PT). At 4:49 UTC, I reverted the phase changes to OMC_LOCK guardian, since clearly something else was awry.
“Did you try turning it off and back on?”: After the lockloss and the reversion, we went up to lock again, preparing to face the same issue, DTT template and TF in hand and then… it worked. Perhaps the lockloss from earlier was from transitioning the OMC with whitening to the OMC without whitening (which I did after achieving the full OMC lock during troubleshooting). Now our next hurdle is state 557/558 (TRANSITION_FROM_ETMX).
The DARM Boost is actually still on: It turns out that the DARM boost had to be turned off in two places, rather than just line 3058 (alog 82277), there was another later boost turn-on at line 3774. Sheila discovered this during troubleshooting at 5:15 UTC. Since we didn’t want to tempt H1 by turning off abruptly, we chose to leave it on and see what would happen at 557/558. After some anticipatory sighs, it worked! We automatically went all the way to NLN.
05:40 UTC - reached NLN! We had one node that wasn’t right, which was the FSS being in INIT and not knowing how to go to IDLE. It wasn’t on the SDF page (no other SDF diffs). Sheila manualled into IDLE, which worked. Strangely enough, we also got a “check PSL chiller” alert but since I know that this alert has some weird timing feature with respect to its thresholds, I will just tag PSL.

Big thanks to Erik and Sheila who helped a lot with troubleshooting.

LOG:

None

PSL

H1 CDS - H1OMC models were reverted

erik.vonreis@ligo.org — Tue, 14 Jan 2025 18:24:15 -0800

Author: erik.vonreis@ligo.org

Report ID: 82284

The changes here 82263 were reverted.

H1OMC models were reverted to version 5.3.0 of the RCG that uses the linear ramp. The IFO was consistently losing lock after a filter ramp down.

H1 ISC - Comment to Re-added DARM boost that was removed because of glitch after CDS filter ramping changes

ibrahim.abouelfettouh@ligo.org — Tue, 14 Jan 2025 17:26:25 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82283

Re-commented out line 3058 today at 1:25 UTC after losing lock at the same state LOWNOISE_ESD_ETMX (558).

H1 CDS - CDS Maintenance Summary: Tuesday 14th January 2025

david.barker@ligo.org — Tue, 14 Jan 2025 17:12:45 -0800

Author: david.barker@ligo.org

Report ID: 82282

WP12272 h1omc0 new RCG, quadratic filter ramping

Erik, Dave:

h1omc0 models were built against RCG 5.31 which introduces quadratic smoothing to ramped filter switching. All the models running on this frontend have the new rcg (h1iopomc0, h1omc, h1omcpi).

The overview was modified to show that h1omc0 has a different rgc than h1susex by colour coding the RCG: dark_blue=5.31(quadratic filter ramp and variable duotone frequence), light-blue-5.30 (LIGO DAC) and green = 5.14 (standard)

WP12274 h1guardian1 reboot

TJ, Erik:

TJ rebooted h1guardian1 to reload all the nodes. The hope is that this will eliminate the leap-second warnings we have been seeing on certain nodes.

Images attached to this report

H1 TCS - Added adjustable fiber collimator to HWS ETMY, SLED left off.

camilla.compton@ligo.org — Tue, 14 Jan 2025 17:10:32 -0800

Author: camilla.compton@ligo.org

Report ID: 82281

TJ, Camilla WP12277.

Started the work done in 81734 on the EX HWS at EY. Swapped the fiber collimator to a CFCS11-A adjustable SMA fiber collimator. Still need to swap to a 50um fiber, remove HWS-L3 and realign. SLED left off.

Images attached to this report

H1 TCS - CO2Y RIN at CW and PWM

camilla.compton@ligo.org — Tue, 14 Jan 2025 17:03:57 -0800

Author: camilla.compton@ligo.org

Report ID: 82262

Repeated 82151, with H1:IOP-OAF_L0_MADC{2,3}_TP_CH{10-13} 65kHz channels on CO2Y. WP# 12261.

Plots attached of the DC and AC out channels. These signals are straight from the PD in counts, before the filtering to undo the D1201111 pre-amp listed in 81868. PWM is at 5kHz, as can be seen in the spectrum.

Strangely when adding cursors to the laser on CW and PWM @50% signals plot, the DC channel has a factor of 30 difference but the AC channel has a factor of 5 difference. We would expect these to be the same.

Also the 95% PWM signal has lower broadband noise that the 25% and 50% PWM signals on the DC channel but higher on the AC channel.

CW = 3880 counts, 49.1W laser power ~ RIN 1.5e-5 but limited by electronics noise.
@50% PWM = 3500 counts, 30.0W laser power ~ RIN 5e-5
@25% PWM = 1800 counts, 14.4W laser power
@95% PWM = 3880 counts, 46.7W laser power

Images attached to this report

H1 ISC - Comment to Re-added DARM boost that was removed because of glitch after CDS filter ramping changes

camilla.compton@ligo.org — Tue, 14 Jan 2025 16:56:35 -0800

Author: camilla.compton@ligo.org

Report ID: 82280

Sheila, Camilla, Erik

We lost lock 12s after this DARM1 FM1 filter was turned off, we're not sure if the filter changes are the cause. Are trying to relock again.

We think we were a little confused and have been turning on FM1 the whole time, as it was still turning on in PREP_DC_READOUT_TRANSITION. Unsure if it was just luck that the glitch disappeared when we made the change Dec 5th. Will look into more...

H1 General - OPS Tuesday day shift summary

ryan.crouch@ligo.org — Tue, 14 Jan 2025 16:31:06 -0800

Author: ryan.crouch@ligo.org

Report ID: 82274

TITLE: 01/14 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Currently relocking, we just lost lock at LOWNOISE_ESD_ETMX.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
22:08	OPS	LVEA	LVEA	N	LASER SAFE	16:01
15:48	FAC	Kim, Nelly	EX	n	Tech clean	16:46
16:01	FAC	Chris	XARM	n	Big Green versus tumbleweeds, finished at 23:00	17:02
16:16	CAL	Sheila	CR	n	IM4 trans cal check	17:01
16:17		Camilla, Mitchell	LVEA (WB)	n	Looking for parts	16:24
16:31	VAC	Janos, Jordan, Travis, JC	MX, EX	n	Air supply replacement	22:36
16:39	PSL	Mayank, Sivananda, Rick, Rahul, Keita	LVEA (H2 PSL+tour)	n	Grabbing parts (Keita out 18:21)	18:48
16:40	PCAL	Tony	PCAL Lab	y(local)	Preparing stuff to ship	17:31
16:47	FAC	Kim, Nelly	EY	n	Tech clean	18:09
16:48	EE	Fil	CER	n	Checking for OMC0 necessities	17:05
16:52		Christina	OSB Receiving	n	Forklifting stuff into the bins	18:01
17:04	FAC	Chris, pest control	LVEA, EX, MX, EY, MY, FCES	n	Pest control	20:11
17:05	EE	Fil	EX, EY	YES, n	Checking all racks	19:56
17:26	FAC	Eric, contractor	LVEA	n	Patching wall holes	19:28
17:36	PCAL	Francisco	PCAL Lab	y(local)	Grabbing stuff for PCAL meas	17:52
17:45	PEM	RyanC	EX, FCES	n	Checking dust monitors	18:31
17:49	PCAL	Francisco	EX	YES	PCAL measurements	20:02
18:09	FAC	Kim, Nelly	LVEA	n	Tech clean	19:08
18:11	TCS	Camilla	LVEA	n	Adjusting CO2 power	18:22
18:30	SEI	Jim	CR	n	Testing filters on BSCs	20:26
18:34	IAS	RyanC	LVEA	n	Setting up FARO for next week	18:47
18:37	TCS	Camilla	LVEA	n	CO2 laser work	19:10
18:52	PCAL	Rick, Mayank, Sivananda	EX	YES	Tour	20:01
19:11	HWS	TJ, Camilla	EY	n	Adding new collimator to HWS	20:20
19:41	VAC	Janos, JC	EY, MY, LVEA	YES	Fitting new exhaust filters for roughing pipes	23:53
20:02	PCAL	Francisco	PCAL Lab	y(local)	Dropping stuff off	20:32
20:07	PCAL	Rick, Sivananda, Mayank	PCAL Lab	y(local)	tour	20:59
20:37	EE	Fil	LVEA	n	Rack checks	22:29
20:47	SEI	Jim	CR	n	Tests on ETMX	22:27
21:06	OPS	Camilla	LVEA	YES	Transitioning LVEA to HAZARD	21:27
21:27	TCS	Camilla, TJ	LVEA	Y	HWS table work	22:19
22:19	OPS	Camilla	LVEA	Y -> N	SAFE transition	22:26
22:46	TCS	Camilla	LVEA	N	TCSY adjustment	22:53
23:10	EE	Daniel	LVEA	N	HAM1 investigation	23:32

H1 SEI - Changes toSEI LARGE_EQ state

jim.warner@ligo.org — Tue, 14 Jan 2025 16:17:21 -0800

Author: jim.warner@ligo.org

Report ID: 82279

During one of the large eqs over the weekend all of the BSC-ISI tripped. I checked one of the chambers and the trip was due to large low frequency drive railing the stage 2 horizontal actuators. The earthquake was big enough SEI_ENV went LARGE_EQ, well after the IFO lost lock, but also after the ISIs started tripping. In SEI_ENV I've reduced the threshold on the peak mon to 6000, about 1.5x the largest eq we've ever ridden out, down from 10000. I've also changed the stage 2 blends used in this state to some 1.5hz blends which roll-off the gs13s at low frequency much more aggressively. I don't think these changes would have been enough to prevent the ISI trips for this particular earthquake, the ISIs started tripping while peak mon was around 4000, so there must have been a large amount of ground motion that was out of band for that channel.

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Tue, 14 Jan 2025 16:03:45 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82278

TITLE: 01/15 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 0mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.39 μm/s
QUICK SUMMARY:

IFO is LOCKING at MOVE_SPOTS

The LN2 truck is yet to arrive and so it may cause a lockloss.

H1 ISC - Re-added DARM boost that was removed because of glitch after CDS filter ramping changes

camilla.compton@ligo.org — Tue, 14 Jan 2025 15:50:49 -0800

Author: camilla.compton@ligo.org

Report ID: 82277

In 81638 we removed a DARM1 FM1 boost because of a glitch when ramping it off causing locklosses during ESD transitions in preparation to switch back to ETMX. Today the CDS team updated H1OMC0 models with an improved filter ramping: 82263. We hope this will allow us to keep the boost us which gives us more range against high microseism while relocking (it's always off by NLN).

Uncommented line 3058 from ISC_LOCK.py and reloaded: ezca.get_LIGOFilter('LSC-DARM1').turn_on('FM1'). If we have locklossses at ISC_LOCK state 557 or 558, at the operator can re-comment this line out. Tagging OpsInfo.

OpsInfo

H1 ISC - Data in OMC DCPD Test Point Readbacks Limited by Single-Point-Precision above 7kHz when IFO is in Nominal Low Noise (and NOT limited anywhere by ADC Noise)

jeffrey.kissel@ligo.org — Tue, 14 Jan 2025 15:34:50 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 82268

J. Kissel, T. Sanchez, E. Goetz, L. Dartez *EDIT* This limitation is only pulling out data with test points from the A0/B0 filter outputs due to them being recorded in single precision, not double precision. The actual data for all internal calculations is double precisions, and in fact for the final calibrated gravitational wave strain is both calculated in, and then stored in frames as, double precision. Back in July 2024 when I started to characterize the super-16 kHz-Nyquist frequency data off the OMC DCPDs with the live 524 kHz channels. See LHO:78516 for the whole story, but we got stalled when we ran into what we believed was some sort of single-precision, numerical precision noise, limited at the equivalent of 1e12 [A/rtHz] DCPD current or 1e-6 [V/rtHz] ADC voltage. In LHO:78559, we ruled out single-point precision calculation of the ASD when we ran the same DCPD signal through a special version of DTT which uses double-precision to calculate the pwelch algorithm. That version of the data proved that the high frequency limitation is still there, and NOT the precision of DTT. In that same data set, we also showed that if you ask DTT to remove the mean, i.e. large DC component of the signal, it also did NOT have any impact on this limit. And it's in removing the mean that we reveal / confirm that it is "single-point precision" limit in the test point readbacks. Check out 1st attachment which is the data from LHO:78559, but with no DTT calibration applied. That means the channels are calibrated into the units of whatever they are coming off of the front-end -- in this case milliamps, or [mA]. The DC value of the test point channel during the time of measurement was ~20 [mA]. The front-end computes all its filtering in double precision, but the readbacks of the products of those calculations are single-point precision. An IEEE 754 32-bit base-2 floating-point, single precision channel has 24 bits of significance (excluding the sign and exponent) to hold the entire frequency dependent content of the time-series that has a DC value of ~20 [mA]. The (front end filtering algorithm?) rounds the 20.43 DC component to the nearest 2^n value, i.e. 2^5 = 32 ["mA"]. Eq. 2.2 of Liquid instruments article on quantization noise suggests that the amplitude spectral density of 1 bit spread across the 0 to 2^18 Hz (f_Nyquist) frequency range over which we care is n_{ASD,RMS} = sqrt( DELTA^2 / (12 * f_Nyquist) ) = DELTA * sqrt( 1 / 12 * 1/f_Nyquist ) where - DELTA is the minimum step resolution (i.e. the peak value / number of significant bits), - the factor or 1/12 comes from the expectation value of the noise power derived from the integral of the product of instantaneous noise power and the probability that that power is distributed across one, specifically the least significant, bit (and we use the square root because we want the amplitude not the power) - the factor of 1/f_Nyquist comes from spreading out the (presumably frequency independent) power over the entire frequency range (and again, we use square root because we want the amplitude not the power) In line-by-line math, that's [[ 32 ["mA"_DC] peak value * (1/2^24) significant bits in single precision) ]] [[ 1 bit * (1/sqrt(12)) expectation value quantization noise amplitude spread across 1 bit * (1/sqrt(2^18 Hz)) quantization noise spread across 0 to Nyquist frequency range ]] = [ 32 / (2^24) ] * sqrt[ 1 / (12 * 2^18) ] = 1.07539868e-9 ["mA"/rtHz] This number *exactly* the high-frequency asymptote we see. BINGO! The next step was then to create pick-off paths of the ADC channels and high-pass -- i.e. remove the large DC component of the signal -- in the front-end. Importantly, this has to be the *first* filter, so the DC component is removed before any other calculation is done. We added the infrastructure and installed the filtering (LHO:78956, LHO:78975), but have not come back to the data until today. Today, we're finally looking at the front-end OMC DCPD data that's been high-pass filtered with a 5th order, 1 Hz high-pass, with 40 dB stop-band attenuation and a 1 dB ripple ellip("HighPass",5,1,40,1) The odd (5th) order means that DC component is completely suppressed, leaving only the remaining frequency-dependent accumulated RMS, which is 5.8901e-4 [mA_RMS] to upper limit of the dynamic range and define the precision limit. SIDE QUEST -- Fractional numbers are much less intuitive to "just round up to the nearest power of 2^n," so the equivalent of "converting 20.43 [mA] to 32 ["mA"]" for 5.8901e-4 is instead a process of, Converting 5.8901e-4 to floating point binary, # sign exponent fraction 0 01110100 00110100110110111110111 # round up the fraction part 0 01110100 01000000000000000000000 # convert back to decimal 0.00061035156 That takes the quantization limit down to = [ 6.1035156e-4 / (2^24) ] * sqrt[ 1 / (12 * 2^18) ] = 2.05e-14 ["mA"/rtHz] Take a look at 2nd attachment, which compares the normal nominal OMC DCPD data to this 1 Hz high passed data. One can see all of the AA filtered data all the way out to the 232 kHz Nyquist frequency, because that data only goes as low as 1e-13 [mA]. Finally in the last attachment, we re-cast this into ADC noise units, to show where the data against the trace we'd had as a bench mark before. Note *this* comparison is a false comparison because the digital AA filtering is applied after the ADC noise is added. So -- don't read anything into the fact that the resolved noise goes below the ADC noise -- it's just a guide to the eye and a bench mark to remind folks that the numerical precision limit is *not* ADC noise. In conclusion, if we want to investigate the OMC DCPD data above 7 kHz with test points, we need to make sure to use a version where the data is high-passed significantly. So, now we can actually begin doing that...CAL, CDS, ISC

Images attached to this report

H1 SEI - H1 ISI CPS Noise Spectra Check - Weekly

thomas.shaffer@ligo.org — Tue, 14 Jan 2025 15:26:39 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82276

FAMIS26026

Last week's report - alog82184. All spectra look good to me and agree with last week's report.

Non-image files attached to this report

CPS_spectra_15:23-01_14_2025.pdf

H1 TCS - TCS chiller sock filters replaced

thomas.shaffer@ligo.org — Tue, 14 Jan 2025 15:21:58 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82275

FAMIS31405

I replaced both sock filters for fresh ones and inspected the radiator air filters.

H1 GRD - h1guardian1 machine reboot and point back at nds0

thomas.shaffer@ligo.org — Tue, 14 Jan 2025 14:53:46 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82273

WP12274

FAMIS28946

We rebooted the h1guardian1 machine today for 3 things:

Point the machine back at nds0 as the primary nds server
- I noticed the other day that the guardian was still defining the chosen nds server as nds1 primary and nds0 as secondary. I'm not entirely sure when this was changed, but maybe 2 years ago (alog66834).
- This was done by changing the NDSSERVER definition in the /etc/guardian/local-env file
Relieve any stale processes that might latch the gps leap second data.
Quarterly machine reboot FAMIS task

All 168 nodes came back up and Erik confirmed that nds0 was seeing the traffic after the machine reboot.

CDS

H1 CAL - PCALX_STAT Guardian testing

anthony.sanchez@ligo.org — Tue, 14 Jan 2025 12:26:31 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82272

Francisco, went to End X to do a beam movement, and I asked him kindly to just block a few beams for me, as a test of the threshholds for PCALX_STAT Guardian.
Francisco blocked the beam for more than 60 seconds which should have reduced the TXPD values to their minimum values.

Conditions to be met:
CAL-PCALX_TX_PD_WATTS_OUTMON > 0.002

This minute of time where TXPD is below the minimum threshhold should have taken PCALX_STAT into A fault mode. 
But it never did.
This is because I changed the PCALX_STAT ISC_LOCK state prerequisite from 600 to 10 for this test today. But ISC_LOCK was in PREP_FOR_LOCKING[9] Instead of IDLE[10] which is what I expected to remain in for the duration of maintenance. In hind sight I should have just taken the ISC_Lock depenence out of the Guardian node completely.

Thanks goes out to Francisco for giving me a hand on a busy day.

Images attached to this report

H1 CDS - Stand down alerts service restarted

thomas.shaffer@ligo.org — Tue, 14 Jan 2025 11:09:21 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82271

I noticed on the ops overview last night that there was an orange "Stand down alerts query failure" light. Looking at the journald log located on the ext-alerts vm, looks like it crashed on Jan 11, so our automated stand downs haven't been working since then, but the incoming events were unaffected. The error was that it wasn't able to connect to the superk site after so many retries. I've restarted this for now with the hope that it was just some maintenance or similar on thier end, but if it crashes again I'll find a more robust solution.

LHO General - Comment to OPS Eve Shift Summary

thomas.shaffer@ligo.org — Tue, 14 Jan 2025 11:06:44 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82270

These should have been the -0.36 and -7.0 values that Jennie found (alog82251). We're reaccepted the new values in the safe.snap and observe.snap.

Images attached to this report

H1 CDS - Comment to H1OMC0 models were updated

david.barker@ligo.org — Tue, 14 Jan 2025 11:03:56 -0800

Author: david.barker@ligo.org

Report ID: 82269

All models on h1omc0 whose filter-modules uses ramp switching filters have the new spline ramps. The models and number of ramping filters are summarized in this table, details are in attached text file.

Model	Number of ramping filters
h1iopomc0	0
h1omc	217
h1omcpi	2

Non-image files attached to this report

h1omc0_ramping_filters.txt

LHO VE - Tue CP1 Fill

david.barker@ligo.org — Tue, 14 Jan 2025 10:26:31 -0800

Author: david.barker@ligo.org

Report ID: 82267

Tue Jan 14 10:03:25 2025 INFO: Fill completed in 3min 22secs

TCmins [-65C, -63C] OAT (0C, 32F)

Images attached to this report

H1 ISC - IM4 trans calibration check

sheila.dwyer@ligo.org — Tue, 14 Jan 2025 09:59:38 -0800

Author: sheila.dwyer@ligo.org

Report ID: 82260

Sheila, Mayank

We wanted to double check the calibration of IM4 trans into power on PRM, similar to 63812 and 62213

10 Watts, single bounce ITMY 16:24 UTC
OMC locked 16:35 UTC. Sensor correction was off so this alignment is wobbling more than it otherwise would.
sensor correction on 16:40 UTC - 16:45 UTC. 1420908058 for 300 seconds
IM4 trans and AS_C whitening gains were 18dB at the time of this measurement.
Medians:
- H1:IMC-IM4_TRANS_NSUM_OUT16 9.855005
- H1:IMC-PWR_IN_OUT16 9.997126
- H1:ASC-AS_C_SUM_OUT16 0.007815647
- H1:OMC-DCPD_SUM_OUT16 15.558
Using Craig's code here to get all the optic transmissions (he cites where the numbers came from at the top of the file), we expect 0.244% of the power incident on PRM to reach HAM6 in single bounce.
If we continue to trust the calibration of AS_C, and the known transmissions that Craig collected, we would apply a correction of 0.9566 to IM4 trans.

H1 CDS - Comment to H1OMC0 models were updated

erik.vonreis@ligo.org — Tue, 14 Jan 2025 09:31:59 -0800

Author: erik.vonreis@ligo.org

Report ID: 82266

Some plots comparing the ramps, taken from simulation of a user model switching on a filter with gain.

Images attached to this report

H1 ISC - Comment to Measuring PR2 spot position using A2L gains

thomas.shaffer@ligo.org — Tue, 14 Jan 2025 09:01:05 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82265

While Jennie was optimizing this I noticed that there weren't 30Hz notch filters in PR2s M3 ISCINF bank. As Jenne Driggers noted the last time this was done (alog77855), she wasn't sure if they would be necessary. To check I put some in for P and Y in the FM7 slot and turned them on while coordinating with Jennie. Jennie saw no difference with them on or off so it confirms Jenne D's suspicions. I believe these notches were left on for the remainder of Jennie's optimization.

H1 CDS - Comment to H1OMC0 models were updated

erik.vonreis@ligo.org — Tue, 14 Jan 2025 08:53:40 -0800

Author: erik.vonreis@ligo.org

Report ID: 82264

The ramp formula was taken from the ramp used to end excitations in awgtpman.

H1 CDS - H1OMC0 models were updated

erik.vonreis@ligo.org — Tue, 14 Jan 2025 08:51:49 -0800

Author: erik.vonreis@ligo.org

Report ID: 82263

All h1omc0 models (h1iopomc0, h1omc, h1omcpi) were restarted with version 5.3.1 of the RCG. This version changes the ramp function when turning on and off ramp-switched filters from a linear ramp to the so-called quadratic ramp.

A linear ramp has the formula r = q where q = (t - t0)/(t1 - t0), the new ramp has the formula r = -q⁴ + 2q², which has the nice property that dr/dq = 0 when q = 0 or q = 1.

This change is an attempt to address the problem described here: 81638

H1 ISC - Filters Shuffled Around in OMC DCPD Test Banks; More Clear Functionality; One more SDF Unmonitor Round

jeffrey.kissel@ligo.org — Tue, 14 Jan 2025 08:50:48 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 82261

J. Kissel, T. Sanchez, L. Dartez As we began to use the new OMC DCPD test infrastructure (LHO:78956, LHO:78975) to pick up where we left off in characterizing the new-to-O4, segregated OMC DCPD, 524 kHz low-noise ADC system (LHO:78516, LHO:78559), we found in necessary and fruitful to - shift some of the installed filters around in the A2 and B2 banks (the one's the replicate the reverse-calibration filters that turn the raw ADC counts in mA on the DCPDs; the copies of the A0 and B0 "NewV2A" and "NewAW" -- moved from FM1 and FM2 to FM2 and FM3 like they are in the A1 and B1 banks.) - add the 1 Hz 5th order elliptic high-pass as an option to the A2 and B2 filters in FM1 (like the A1 and B1 banks) and - split out "divide-by-four" gain of 1/4 that turns the sum of the four channels into an average from the "cts2V" ADC calibrating gain of 40 / 2^18 [V/ct] = 0.00015258789 [V/ct] ~ 0.0001526. The ADC gain in th previous cts2V bank was actually implemented as a typo of the 16 bit ADC calibration divided by 4. The ADC gain should be 40 / 2^16 [V/ct] = 0.00061035156 [V/ct], but was installed as 0.0006105 "[V/ct]." And then the multiplication of the gain of 1/2^2 = 1/4 = gain(0.25) to convert from 16-bit to 18-bit calibration was immediately adjacent to the gain(0.25) for turning the sum into an average. Not so clear. So, what was cts2V = gain(0.0006105)*gain(0.25)*gain(0.25) in FM4, is now two separate filter banks 18b_cts2V = gain(0.0001526) sum2avg = gain(0.25) in FM4 and FM5. The new filter banks and arrangement have been committed to the SVN under /opt/rtcds/userapps/release/cds/h1/filterfiles/ H1IOPOMC0.txt rev 30385 Also -- it appears as though the B1 and B2 filter banks didn't have their filters properly *un*monitored when I touched the SDF system last week (LHO:82155). The configuration changes (made during Monday commissioning time) thus had prevented returning to observing. I've rectified that as well, so now, *really* these A1, A2, B1, and B2 banks' EPICs records can be changed at will during observing.CAL, DetChar, ISC

Images attached to this report

H1 General - Comment to Ops Day Shift Start

oli.patane@ligo.org — Tue, 14 Jan 2025 08:09:57 -0800

Author: oli.patane@ligo.org

Report ID: 82259

Down for maintenance at 16:06 UTC

H1 General - Ops Day Shift Start

oli.patane@ligo.org — Tue, 14 Jan 2025 07:33:49 -0800

Author: oli.patane@ligo.org

Report ID: 82258

TITLE: 01/14 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 4mph Gusts, 3mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.45 μm/s
QUICK SUMMARY:

PEM and SUS charge measurements currently being taken. We've been Locked for over 5.5 hours. Today is an 8 hour maintenance day.

H1 CDS - Workstations updated

erik.vonreis@ligo.org — Tue, 14 Jan 2025 06:50:22 -0800

Author: erik.vonreis@ligo.org

Report ID: 82257

Workstations were updated and rebooted. This was an OS packages update. Conda packages were not updated.

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Mon, 13 Jan 2025 22:00:00 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82256

TITLE: 01/14 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 162Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 04:47 UTC

Smooth shift with one Lockloss caused by the ETMX glitch (alog 82254)

Per Ryan C's instruction from Ryan S, I also adjusted the PSL ISS Ref signal (attached pic) to bring the refracted power above 4.

There was one SDF Diff that I accepted (also attached).

LOG:

None

Images attached to this report

H1 ISC - Comment to Lockloss 02:39 UTC

ibrahim.abouelfettouh@ligo.org — Mon, 13 Jan 2025 19:17:56 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82255

ETM Glitch tag confirming the LL cause on Lockloss Tool.

Lockloss

H1 ISC - Lockloss 02:39 UTC

ibrahim.abouelfettouh@ligo.org — Mon, 13 Jan 2025 18:49:25 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82254

Lockloss likely caused by the ETMX glitch. EX L2 OUT channel shows erratic movement 170ms pre-lockloss (attached screenshot)

Lockloss

Images attached to this report

H1 AOS - Progress on two input arm scattering issues: ITMY CP yawing causes spot on HAM3 ballast mass baffle to move; mystery beam spot comes from ITMX direction

robert.schofield@ligo.org — Mon, 13 Jan 2025 17:49:38 -0800

Author: robert.schofield@ligo.org

Report ID: 82252

Bright beam spot on HAM3 ballast mass baffle moves with ITMY compensation plate yaw motion

We have been looking for the source of the scattering noise that varies with the ITMY compensation plate yaw setting (80499). I recently searched for beam spots in the HAM3 area that move as CPY is yawed, using movies that I took from both the MC2 camera viewport and the PR2 camera viewport near HAM2. Anamaria and I had done some of this before (77631) but this time I recorded the CP movements on the audio track of the movies for a more precise correlation. And I also modified the movies in iMovie to increase visibility of faint spots. Figure 1 shows that I did find a spot that moved precisely with CPY Yaw settings (link to movie clips: https://youtu.be/FDdNDPoQadU ). The spot appears to be on a ballast mass baffle (see Fig. 1), which is not angled as much as the scraper baffle (which I think the beam is supposed to fall on (Alena's slides)) and may thus retroreflect more light.

Mystery beam spot on HAM3 spool piece comes from ITMX direction, not HAM2 direction

I had previously misinterpreted the pattern of light on edges and bellows of the HAM3 spool piece as suggesting that the mystery beam spot (78192) was coming from the HAM2 direction . More recently I found that there was light on the HAM3 side of the MC baffle that had a similar interference pattern and was consistent with being part of the mystery beam spot (Figure 1). The light on the HAM3 side of the baffle was visible when looking through the viewport for the PRM camera at a high angle. Thus, the beam is most likely coming from the ITMX direction, travelling close to the –Y wall of the beam tube.

One possibility is that it actually comes from ITMX, either scattered light from ITMX or scattered light from the back side of MC2 reflecting off of ITMX. Figure 3 shows these suggested paths and a picture taken from the point of view of the beamspot on ITMX that shows that there is a clear path to the site of the mystery beam spot. I think that the cartoon shows that it would be worth using a real model to determine if these paths are possible.

I checked to see if the beamspot on the eye baffle moved or modulated when I actuated the compensation plates. I made movies as I moved the two compensation plates more than 600 microradions in pitch and yaw, but, unlike the spot on the ballast mass baffle, I did not see any modulation or motion of the spot on the eye baffle.

DetChar

Non-image files attached to this report

Fig1-Beamspot-Moves-With-CP.pdf

Fig2-MysterySpot-from-ITMX-direction.pdf

H1 General - OPS Monday day shift summary

ryan.crouch@ligo.org — Mon, 13 Jan 2025 16:30:16 -0800

Author: ryan.crouch@ligo.org

Report ID: 82240

TITLE: 01/13 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: The bottom monitor of NUC31 looks pretty dim today, we've also had a standdown query failure on OPS_OVERVIEW. The failure is from the last query being greater than 4 minutes from the current time, the last query was 01/11/25 15:25 UTC. We've been locked for 6 hours, range coherence check yielded.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
22:08	OPS	LVEA	LVEA	N	LASER SAFE	15:07
16:09	FAC	Kim	Optics, PCAL	N	Tech clean	16:37
16:27	CAL	Francisco	PCAL	LOCAL	PCAL work	16:39
16:43	FAC	Tyler	Xarm	N	Tumbleweeds check	17:13
17:15	CAL	Camilla	Optics lab	N	Tidying	18:41
17:58	FAC	Kim	MidY then X	N	Tech clean	18:35
17:59	VAC	Janos	MidX	N	Look for a setup, mech room	18:30
18:33	ISC	Jennie, Sheila	CR	N	A2L measurement	19:29
18:44	FAC	Kim	MidX	N	Tech clean	19:29
19:08	ISC	Elenna	Remote	N	SRCL dither meas	19:29

16:48 UTC I adjusted the OPO temp while relocking.
17:03 UTC TRANSITION_FROM_ETMX lockloss
18:29 UTC NLN and start of Commissioning
19:37 UTC SEI to CALM
19:44 UTC Observing after wrangling some SDFs

Images attached to this report

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Mon, 13 Jan 2025 16:01:11 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82253

TITLE: 01/14 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 162Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.52 μm/s
QUICK SUMMARY:

IFO is in NLN as of 19:20 UTC (5hr 30 min lock)

H1 ISC - Measuring PR2 spot position using A2L gains

jennifer.wright@ligo.org — Mon, 13 Jan 2025 15:39:36 -0800

Author: jennifer.wright@ligo.org

Report ID: 82251

Sheila, Jennie W

During commissioning window today we measured the P2L and Y2L gains for the PR2 mirror.

This is part of the work to understand how to move the beam on PR2 in order top avoid a reflection and subsquent stray beam off the PR2 scraper baffle (as found in alog #77631 by Annamaria and Robert).

The P2L gain was close to optimised and has been left at -0.36.

The commissioning window ran out before I could finish optimising the Y2L, I have left it at -7.00 which gave better A2L decpupling than the previous value.

Method:

Inject line on PR2 M3 stage pitch at 30Hz using the OSC 9 filter bank in the ADS.
- sitemap-> ASC -> Dither overview
Check the PIT9 filter bank at the bottom of the page is not being used (CLK gain = 0).
Set the matrix at the right of the row to have a 1 in the PIT9 to PR2 cell.
Check there is a ramp time in the PIT 9 filter bank.
Set the frequency to 30 and step the amnplitude to 1 in a couple of steps.
Measure a reference for DARM and PRCL. The red and blue traces show the case when injecting into pitch with nominal A2L gains.
Set the aevraging to exponential and zoom in on the line.
Change gain in HzTS->PR2-> M3 DRIVEALIGN->P2L

Do this until the line height relative to the background is minimised, allowing time for the ramp and a couple averages each step. One thing to note is that the line height above the background in the PRCL spectrum (LSC-PRCL_OUT_DQ) is much less than the relative height above the background in DARM which suggests that the noise in PRCL is not coupling strongly to DARM.

Switch off the line and set the PIT 9 amplitude to 0 counts.

Then repeat the above for the YAW 9 oscillator channel in the ADS, changing the gain in the Y2L gain filter bank in order to minimise the line height. The reference values for yaw are in the photo linked above with the green line showing DARM (we had gone into NLN cal meas with SRCL FF switched off for Elenna's SRCL tests so that is why DARM shows elevated noise). The orange line is the reference value of PRCL using the nominal Y2L gain. The same amplitude was used in the oscillator for this line but it was much higher above the PRCL background noise than for the pitch degree of freedom.

Template is at /ligo/hom,e/jennifer.wright/git/2025/A2L/20250113_A2L_PR2.xml

PEM

Images attached to this report

LHO General - DGR Storage Building Progress

tyler.guidry@ligo.org — Mon, 13 Jan 2025 14:54:04 -0800

Author: tyler.guidry@ligo.org

Report ID: 82250

Since the last report siding, insulation, roofing and doors have all been installed. In addition, a concrete transition between the asphalt and slab was poured as well as a walkway & equipment pad to/near the mandoor. With that, the building construction is complete. Keys were handed over last Thursday 1/9. I have began the process of populating the space with site equipment. Richard and I are making preparations to get basic electrical items ran to the building. T. Guidry

Images attached to this report

H1 ISC - Comment to Lockloss 02:06 UTC

camilla.compton@ligo.org — Mon, 13 Jan 2025 12:46:25 -0800

Author: camilla.compton@ligo.org

Report ID: 82249

As Ibrahim said, the OPO temp adjustment would not cause a lockloss.

However we can see a this Friday time and two days before, the SQZ angle servo and ASC seem to get into a strange ~13minute oscillation when the OPO temperature is bad and the SQZ angle is around 220deg. See attached plots. We are not sure why this is. Now we are a week from the OPO crystal move 82134, the OPO temperature is becoming more stable but will still need adjusting for the next ~week.

SQZ

Images attached to this report

H1 ISC - Notes about SRCL Dither Arm Power Measurement

elenna.capote@ligo.org — Mon, 13 Jan 2025 12:32:02 -0800

Author: elenna.capote@ligo.org

Report ID: 82248

There are not yet any results to report about the SRCL dither arm power measurement, but I have some notes about the attempts to run this measurement over the last few commissioning periods.

This measurement works by using the radiation pressure coupling of SRCL to induce differential radiation pressure in the arms, which depends on a couple factors, one being the arm power. This measurement is made by injecting into the SRCL control signal, and measuring the transfer function of of the relative intensity noise on the transmission QPDs of each arm to DARM.

Measurement requirements:

know the calibration of DARM well (must be CAL DELTA L in this case)
turn off the SRCL feedforward
Make sure the TMS QPDs are centered
ensure high coherence (>0.9) of DARM to TMS QPDs

However, I once caused a lockloss running Craig's measurement templates, so I wanted to be sure that I could drive hard enough to get the required coherence, but not break the lock.

Last week, I ran a couple of test measurements with the SRCL feedforward off, and the TMS QPDs as well centered as possible. I have a screenshot of the results below. You can see that the DARM/SRCL coherence is very good, but the DARM/TMS QPD coherence is very bad. This is true for the NSUM channels as well as the individual segments. When I tried to drive harder, I would get ETMX saturation warnings. The signal appears almost four orders of magnitude above the noise in DARM and about one order of magnitude above the noise in the TMS QPDs.

The centering loops we use center onto QPD B of both arms, but cause the beam to be off center on QPD A in both arms. However, the coherence is equally low on both the A and B QPDs, so I don't think the centering is the issue. Craig and I previously tried centering onto the A QPDs, but then you become miscentered on B, and also cause other problems, see 67066.

Today, I instead drove single lines using awggui. I was able to achieve >0.9 coherence at three different frequencies without causing any saturations anywhere, at about 70 Hz, 49 Hz and 34 Hz. Good coherence was observed with both the NSUM channels and the individual segments of the TMS QPDs. I also confirmed that we see the expected differential phase in the signal between the X and Y arm.

We were not thermalized today, so I plan to rerun this measurement on Thursday using these three points. This should be sufficient information to measure the arm power, and also confirm that we observe the predicted 1/f^2 coupling. I can also use the regularly scheduled Thursday calibration measurements to make sure we know the CAL DELTA L calibration.

Images attached to this report

H1 General - Comment to OPS Monday update

ryan.crouch@ligo.org — Mon, 13 Jan 2025 11:54:36 -0800

Author: ryan.crouch@ligo.org

Report ID: 82247

The OMC chans have been unmonitored at Jeffs behest.

H1 General - OPS Monday update

ryan.crouch@ligo.org — Mon, 13 Jan 2025 11:48:47 -0800

Author: ryan.crouch@ligo.org

Report ID: 82246

19:44 UTC we wrapped up commissioning which started late due (~18:30 UTC) to not being locked. I had to accept/revert some SDFs to get back to observing, ASC, PR2, and OMC.

Images attached to this report

H1 General - Comment to OWL Intervention

oli.patane@ligo.org — Mon, 13 Jan 2025 10:59:24 -0800

Author: oli.patane@ligo.org

Report ID: 82245

It looks like ETMY M0 and R0 tripped due to barely going over the watchdog limit, and that it was due to the ISI stages tripping (ndscope). Similar to what I did in 81668, I'll up the thresholds for M0 and R0 by a bit. Thankfully it looks like the thresholds we established for the other stages were all good guesses and are still good.

Stage	Original WD threshold	Max BLRMS reached after lockloss	New WD threshold
M0	100	106	150
R0	120	122	175
L1	170	134	170 (unchanged)
L2	270	168	270 (unchanged)

SUS

Images attached to this report

LHO VE - Mon CP1 Fill

david.barker@ligo.org — Mon, 13 Jan 2025 10:34:39 -0800

Author: david.barker@ligo.org

Report ID: 82244

Mon Jan 13 10:11:32 2025 INFO: Fill completed in 11min 28secs

Jordan confirmed a good fill curbside. TCmins [-86C, -84C] OAT (0C, 32F)

Images attached to this report

X1 SUS - Comment to BBSS Model Parameter Correction/Update

oli.patane@ligo.org — Mon, 13 Jan 2025 10:25:31 -0800

Author: oli.patane@ligo.org

Report ID: 82243

Verification that the d4 value is correct: 82138

X1 SUS - Comment to BBSS Model Parameter Exploration w/ Data from First Article H1 SUS BS (a BBSS)

oli.patane@ligo.org — Mon, 13 Jan 2025 10:25:24 -0800

Author: oli.patane@ligo.org

Report ID: 82242

Verification that the d4 value is correct: 82138

H1 PSL - PSL 10-Day Trends

ryan.short@ligo.org — Mon, 13 Jan 2025 10:22:22 -0800

Author: ryan.short@ligo.org

Report ID: 82241

FAMIS 31068

PMC REFL continues to rise. Since I didn't get a chance to bump up the ISS diffracted power last week and it's continued to fall, I'll adjust that opportunistically this week between lock stretches.

Images attached to this report

H1 GRD - Comment to OWL Intervention part 2

thomas.shaffer@ligo.org — Mon, 13 Jan 2025 08:42:52 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82239

This is a bit of a conflict from H1_MANAGER and IFO_NOTIFY. Since the IFO was able to get back to Observing on its own, even after H1_MANAGER timed out and triggered the initial Assistance_Required (H1_MANAGER state) and Alert_Active (IFO_NOITFY state), IFO_NOTIFY would clear that state when we got back to observing, but H1_MANAGER would not. Since H1_MANAGER was still in Assistance_Required, then IFO_NOTIFY would bounce between Alert_Active and Waiting. I'll add something into H1_MANAGER to also clear the alert when we get back into observing to avoid this in the future.

I have no idea why Oli wasn't called until 14UTC, as the states of both IFO_NOTIFY and H1_MANAGER definitely changed two hours earlier. I'll check with Dave to see if Twillo threw any errors.

H1 General - OPS Monday day shift start

ryan.crouch@ligo.org — Mon, 13 Jan 2025 07:36:30 -0800

Author: ryan.crouch@ligo.org

Report ID: 82238

TITLE: 01/13 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.10 μm/s
    Secondary useism: 0.47 μm/s
QUICK SUMMARY:

We lost lock at 12:31 UTC from an earthquake (6.8 from Japan), currently relocking at DRMI
2ndary microseism is decreasing, wind is low

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Sun, 12 Jan 2025 21:59:30 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82237

TITLE: 01/13 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of Jan 12 14:03 (16 hr lock!)

Very calm shift where we were locked the whole time. violins are somewhat high but don't seem to be increasing (EY1 likely needs new damping controls).

LOG:

None

H1 CDS - VACSTAT alarm, BSC PT132 Sensor glitch, restarted code to clear

david.barker@ligo.org — Sun, 12 Jan 2025 17:32:58 -0800

Author: david.barker@ligo.org

Report ID: 82236

At 16:37 Sun 12jan2025 VACSTAT detected a sensor glitch on PT132 BSC3.

I restarted the service at 17:30 to clear this alarm.

Images attached to this report

H1 General - OPS Sunday DAY shift summary

ryan.crouch@ligo.org — Sun, 12 Jan 2025 16:31:16 -0800

Author: ryan.crouch@ligo.org

Report ID: 82234

TITLE: 01/12 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: We've been locked for over 10 hours, ITMY 5/6 and ETMY1 remain elevated, I turned off ETMY1s damping after seeing it start turning around.
LOG: No log for this shift.

14:03 UTC Observing

Images attached to this report

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Sun, 12 Jan 2025 16:06:54 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82235

TITLE: 01/13 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 4mph Gusts, 3mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.64 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 14:03 UTC the previous day (10 hr lock!)

Microseism is increasing and violins are elevated.

H1 General - OPS Sunday midshift report

ryan.crouch@ligo.org — Sun, 12 Jan 2025 13:18:40 -0800

Author: ryan.crouch@ligo.org

Report ID: 82233

We've been locked and observing for over 7 hours, 2ndary microseism looks to have peaked.

LHO VE - Sun CP1 Fill

david.barker@ligo.org — Sun, 12 Jan 2025 10:20:38 -0800

Author: david.barker@ligo.org

Report ID: 82232

Sun Jan 12 10:18:16 2025 INFO: Fill completed in 18min 13secs

TCmins [-106C, -99C] OAT (3C, 38F)

Images attached to this report

H1 General - OPS Sunday DAY shift start

ryan.crouch@ligo.org — Sun, 12 Jan 2025 07:35:39 -0800

Author: ryan.crouch@ligo.org

Report ID: 82231

TITLE: 01/12 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT_USEISM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.76 μm/s
QUICK SUMMARY:

We've been locked for 1.5 hours
2ndary microseism is rising, wind is low

H1 GRD - OWL Intervention part 2

oli.patane@ligo.org — Sun, 12 Jan 2025 06:35:14 -0800

Author: oli.patane@ligo.org

Report ID: 82230

Got called at 14:15UTC due to assistance required. I *believe* the issue was that the NLN timer had run out, but by the time I logged on we were in Observing. We had been in OMC_WHITENING for about an hour presumeably damping violins. It looks like the total amount of time we were trying to relock after completing an initial alignment was almost 3.5 hours. The strange thing is that looking at the H1_MANAGER log, it looks like the NLN timer ran out at 12:42UTC, triggering H1_MANAGER to enter ASSISTANCE_REQ, but like I said, I did not get called until 14:15UTC. There was also something weird going on with the IFO_NOTIFY guardian too, when I logged on it was rapidly cycling between ALERT_ACTIVE and WAITING, although it looks like the cycling started once we got into Observing, so that might have just been due to no longer needing the alert (although I never noticed it doing that on other similar occassions but maybe that's just me missing it).

All is good and we've been Observing for 30 minutes.

Images attached to this report

H1 General - OWL Intervention

oli.patane@ligo.org — Sun, 12 Jan 2025 01:30:57 -0800

Author: oli.patane@ligo.org

Report ID: 82229

Alerted by H1_MANAGER that it needed intervention. There was a large earthquake coming through that had tripped the ISIs for the ITMs and ETMs. Also, ETMY stages M0 and R0 had tripped (not yet sure if that is just due to the ISI tripping).

There was also a notification on verbals from 08:51UTC, a minute after everything tripped, that says "ETMY hardware watchdog trip imminent", but when I checked the hardware watchdog screen everything looked normal with no countdowns. Once it looked like the worst of the earthquake had passed and the ISI values were all within range, I reset R0 and M0 for ETMY and reset all four ISI watchdogs. We are still in LARGE_EQ mode so we haven't started relocking yet, but it looks like we are close to leaving and we should be good to go for relocking.

SEI

Images attached to this report