aLIGO LHO Logbook

LHO General - Sun DAY Ops Transition

corey.gray@ligo.org — Sun, 09 Mar 2025 07:49:52 -0700

Author: corey.gray@ligo.org

Report ID: 83247

TITLE: 03/09 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 10mph Gusts, 6mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.45 μm/s
QUICK SUMMARY:

Happy Spring Forward Morning (& 1-hr less sleep)!

H1 just went down (after a 3h51m lock, and a 1435utc lockloss w/ an ETMx Glitch tag). Taking H1 immediately into Initial Alignment to skip Locking ALS locklosses.

The one Owl 932utc lockloss (also an ETMx Glitch tag) was fully automatic (after about 22min of 7 Locking ALS attempts) & no Alignment was needed.

Looks like secondary microseism hit the 95th percentile about 10hrs ago and has stayed there. Winds are under 10mph.

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Sat, 08 Mar 2025 22:00:01 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 83246

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

IFO is in NLN and OBSERVING as of 01:36 UTC (~4hr 30 min lock).

Extremeley calm IFO that stayed locked for majority of shift.

Lock acquisition after the EQ lockloss (alog bla bla) went fully automatically.

Since then, we've been locked with the microseism steadily increasing. However, the wind has died down.

PSL Dust has been fluctuating a lot (swapping between red, yellow and no alerts) this shift, despite wind calming down.

LOG:

None

LHO General - Sat DAY Ops Summary

corey.gray@ligo.org — Sat, 08 Mar 2025 16:30:02 -0800

Author: corey.gray@ligo.org

Report ID: 83239

TITLE: 03/08 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:

Two locklosses today which were straightforward to recover from. One happened at the waning minutes of the calibration suite of measurements which is sad (EQ inbound, higher winds, and microseism increasing); this was tagged as a WIND + Calibration lockloss.

Also had 5-tours for our 2nd Saturday Tour day.
LOG:

H1 was recovering from an ETMx glitch lockloss at beginning of shift.
1638 Back to Observing
1700-1715 Picked up around the Control Room before Saturday Tour visitors arrive (mainly putting lots of used scratch paper in the "data archive" (aka recycling bin), one coffee cup in dishwasher, one battery in battery recycling container, and organized chairs.
1815-1832 930am Saturday tour (cassidy)
- 1955-2010 1030am Saturday tour (janos)
- 2040- 1130am Saturday tour (mike)
- 2125-2156 1230pm Saturday tour (amber)
- 2245-2314 1:30 Saturday Tour (fred)
1911 Incoming EQ alert for M5.7 from southern japan
1930 Out of Observing for Saturday Calibration
- Lockloss (presumably due to incoming EQ) during the last few minutes of the simulines measurement at 1958utc :(
- Had WINDY + Calibration tags for this lockloss.
1952 Noticed nuc25 PI Mode ndscope was not running for last 4-days---restarted it.
1958 LOCKLOSS (right before the Saturday Calibration measurement)
- 2004-2024 Initial Alignment
- 2122 OBSERVING....could have been a few minutes sooner, but for some reason a GRD_IFO in "AUTOMATIC OPERATION" failed to take us in automatically which is odd.
0002 EQ alert for another one south of Japan
0017 Lockloss....guessing it is EQ related since we had an alert for one, but we also have high microseism and winds
- Proactively went for an Initial Alignment and now handing off to Ibrahim!
- Late NOTE: This lockloss has a WINDY tag with winds passing the 20mph threshhold, but we also had the earth moving with that incoming EQ from South Japan and rising usiesm...so, still think it's a toss-up. Both locklosses with the South Japan EQ never had the picket fence go yellow, did not see any movement on ndscopes and really didn't look bad on seismometer bands, so chalking it up to a comedy of seismic noise teaming up to be an H1 foe.

H1 SEI - Lockloss 00:17 UTC

ibrahim.abouelfettouh@ligo.org — Sat, 08 Mar 2025 16:27:46 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 83245

Lockloss due to EQ, exacerbated by a 5.9 EQ (which interestingly didn't trigger EQ mode).

IFO is relocking now.

Lockloss

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Sat, 08 Mar 2025 16:11:32 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 83244

TITLE: 03/09 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT
    Wind: 26mph Gusts, 21mph 3min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.41 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 21:22 UTC (3 hr lock).

Unfortunately, we have a 5.9 EQ arriving in a few minutes. If microseism was lower, we could probably ride it out but seeing as we lost lock due to a lower mag EQ with lower microseism just 4ish hrs ago, I would say chances are low.

Calibration sweep did not run today due to an EQ so I can run one pending thermalization (and green light from comissioners/run coord).

H1 PSL - Comment to PMC Duty Cycle from July 1 2022 to July 1 2024

jeffrey.kissel@ligo.org — Sat, 08 Mar 2025 12:06:55 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 83243

The data used in the above aLOG was gathered by ndscope using the following template, /ligo/svncommon/SeiSVN/seismic/Common/SPI/Results/ alssqzpowr_July2022toJul2024_trend.yaml and then exported (by ndscope) to the following .mat file, /ligo/svncommon/SeiSVN/seismic/Common/SPI/Results/ alssqzpowr_July2022toJul2024_trend.mat and then processed with the following script to produce these plots /ligo/svncommon/SeiSVN/seismic/Common/SPI/Scripts/ plotpmcuptime_20250224.m rev 9866 ndscope have become quite an epically powerful data gathering tool! CDS, CSWG, SEI, SUS, SYS

LHO VE - Sat CP1 Fill

david.barker@ligo.org — Sat, 08 Mar 2025 10:18:59 -0800

Author: david.barker@ligo.org

Report ID: 83242

Sat Mar 08 10:08:10 2025 INFO: Fill completed in 8min 7secs

Images attached to this report

H1 SEI - H1 ISI CPS Noise Spectra Check - Weekly (Famis 26033)

corey.gray@ligo.org — Sat, 08 Mar 2025 08:15:18 -0800

Author: corey.gray@ligo.org

Report ID: 83240

FAMIS Link: 26033

Only CPS channels which look higher at high frequencies (see attached) would be the following:

ITMx St1 V1
ETMy St2 V2

SEI

Non-image files attached to this report

CPS_spectra_08:11-03_08_2025.pdf

LHO General - Sat DAY Ops Transition

corey.gray@ligo.org — Sat, 08 Mar 2025 07:45:07 -0800

Author: corey.gray@ligo.org

Report ID: 83238

TITLE: 03/08 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: 8mph Gusts, 3mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.31 μm/s
QUICK SUMMARY:

H1 had a lockloss about 70min ago due to an ETMx Glitch, due to trouble locking ALS, automation finished up an alignment 10min ago and continues locking (H1 had a pretty quick automated acquisitioon overnight in about 90min for comparison). Secondary microseism has a slow increase over the last 12-ish hours and it has been a little breezy the last 24hrs (w/ gusts going over 20mph at various points). Today is Saturday Tour day & Calibration is scheduled for 1830utc/1130amPST.

H1 General - Friday Eve Shift Report.

anthony.sanchez@ligo.org — Fri, 07 Mar 2025 22:09:43 -0800

Author: anthony.sanchez@ligo.org

Report ID: 83237

TITLE: 03/08 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT
    Wind: 9mph Gusts, 6mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.26 μm/s
SHIFT SUMMARY:
Had a lockloss just before my shift.
Did some SQZr changes while relocking : Corey's alog: 83225 , My alog about this: 83236
Once Relocked H1 has stayed locked and Observing for 3 hours.

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
18:34	isc	myank.siva	optics.lab	y	iss array hardware	01:50
01:26	ISS	Matt	Optics Lab	Yes	Taking pics of Fiber Lasers	01:32

H1 General - Friday Ops Eve Shift Starting report.

anthony.sanchez@ligo.org — Fri, 07 Mar 2025 20:21:27 -0800

Author: anthony.sanchez@ligo.org

Report ID: 83236

TITLE: 03/08 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 15mph Gusts, 11mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY:

00:14 UTC H1 Aquired a Lockloss of unknown cause.
There was a request to load the SQZ_SHG Guardian, but there was a syntax in the code that caused the Guardian node to go into error. Simple fix took me a few minute to find and fix.
SQZ_SHG Guardian node is running smoothly now.

Corey then took H1 into Initial_Alignment, while I edited the sqzparams.py.
Line 18 was take from 75 to 80:
opo_grTrans_setpoint_uW = 80 #reload OPO guardian for this to take effect
I then took SQZ_OPO_LR Guardian to LOCKED CLF_DUAL_NO_ISS, Then reloaded the Guardian code.
Once reloaded I took SQZ_OPO_LR back to LOCKED_CLF_DUAL.

Then tried to adjust the OPO_TEC_TEMP, this was a mistake. I could tell that something wasnt correct because I couldn't get the SQZ-CLF_RFEL_RF6_ABS_OUTPUT back to the same hieght it was before while adjusting the OPO_TEC_TEMP. Contacted Sheila.
She informed me that the SQZ_CLF_LR should be locked when doing this.

Once locked the SQZ-CLF_RFEL_RF6_ABS_OUTPUT went up and Looked much better.

Relocking notes.
Initial_Alignment is finished and I'm trying to relock and I have not had success past DRMI. But the night is stil young.

Update:
NOMINAL_LOW_NOISE reached at 2:50 UTC
Observing reached at 3:02 UTC

Lockloss

Images attached to this report

LHO General - Fri Ops DAY Shift Summary

corey.gray@ligo.org — Fri, 07 Mar 2025 17:02:00 -0800

Author: corey.gray@ligo.org

Report ID: 83225

TITLE: 03/07 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

edit: h1 had a lockloss minutes before the end of the shift, so Tony and I started addressing SQZ To-Dos (see below in the log)

Ops To Do At Next Opportunity (next H1 lockloss, or L1 goes down. See sheila alog 83227):

Load SQZ_SHG (this can be done with H1 in any state)
Restore opo_grTrans_setpoint_uW back to 80 (was set to 75 this morning), and re-tune the OPO TEC setpoint . This can be done with H1 in any state.

LOG:

At the beginning of the shift, H1 was at NLN, but not Observing due to issues with the SQZ_SHG (alog83224)
1758 Dave TeamSpeak-ed in saying we have a red FMCS Stat for the EX VEA temperature---he mentioned this is normal when we get warmer days and the sun on the building. No changes were made, so will leave this FMCS Stat red as a heads up for a temperature increase in the EX VEA.
1831-2035 ISS Array work in optics lab (myank, siva)
- 2209 hardware work (myank)
- 2319 siva joining
1855-1914 Optics Lab clean (kim)
1921-2005 y-arm walk (ibrahim)
2155-2213 Packing sensor in PCal lab (tony)
- 2222-2226 changing shutter status (tony)
0014 Lockloss toward end of shift. Took this opportunity to do the (2) SQZ items listed above.
(1) SQZ_SHG node was LOADed, but came up with this error:
- 2025-03-08_00:15:52.522971Z File "/opt/rtcds/userapps/release/sqz/h1/guardian/SQZ_SHG.py", line 39
- 2025-03-08_00:15:52.522971Z elif ezca['SQZ-SHG_TRANS_RF24_PHASE_ERROR_FLAG'] != 0:
- 2025-03-08_00:15:52.522971Z ^ 2025-03-08_00:15:52.522971Z SyntaxError: invalid syntax
- In SQZ_SHG.py, here is the fix Tony made to fix the error above:

def in_hardfault():
#if ezca['SQZ-LASER_IR_DC_ERROR_FLAG'] != 0:
# notify('Squeezer laser PD error')
# return True
#elif ezca['SQZ-PMC_TRANS_DC_ERROR_FLAG'] != 0:
# notify('Squeezer PMC not locked')
# return True
if ezca['SQZ-SHG_TRANS_RF24_PHASE_ERROR_FLAG'] != 0:
notify('SHG Trans phase shifter error')
return True
#elif ezca['SQZ-SHG_TRANS_RF24_DEMOD_ERROR_FLAG'] != 0:
# notify('SHG Trans Demod error')
# see comment to alog 83224 for why this was commented out
# return True

(2) Restored opo_grTrans_setpoint_uW back to 80 (from 75).
- Then Tony tried adjusting OPO TEC TEMP to maximize CLF_REFL_RF6_ABS_OUTPUT, but it was not totally clear it was working. Granted H1 is not at NLN (does H1 need to be at NLN to do this?)
- At any rate, Tony got a hold of Sheila and they are chatting on the phone now.

H1 PSL - PMC Duty Cycle from July 1 2022 to July 1 2024

jeffrey.kissel@ligo.org — Fri, 07 Mar 2025 16:37:21 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 83230

J. Kissel I've been looking through the data captured about the PMC in the context of the two years of observatory use between July 2022 and July 2024 where we spanned a few "construction, commission, observe" cycles -- see LHO:83020. Remember the end goal is to answer the following question as quantitatively as possible: "does the PMC have a high enough duty cycle in the construction and commissioning phases that the SPI does *not* need to buy an independent laser?" Conclusions: - Since the marked change in duty cycle after the PMC lock-loss event on 2023-05-16, the duty-cycle of the PMC has been exceptionally high, either 91% during install/commissioning times or 99% during observing times. - Most of the down time is from infrequent planned maintenance. - Recovery time is *very* quick, unless the site loses power or hardware fails. - The PMC does NOT lose lock when the IFO loses lock. - The PMC does NOT lose lock just because we're vented and/or the IMC is unlocked. - To-date, there are no plans to make any major changes to the PSL during the first one or two O4 to O5 breaks. So, we shouldn't expect to lose the SPI seed light frequently, or even really at all, during the SPI install or during commissioning. And especially not during observing. This argues that we should NOT need an independent laser from an "will there even be light?" "won't IFO construction / commissioning mean that we'll be losing light all the time?" duty-cycle stand point. Only the pathfinder itself, when fully functional with the IFO, will tell us whether we need the independent laser from a "consistent noise performance" stand-point. Data and Historical Review To refresh your memory, the major milestones that happened between 2022 and 2024 (derived from a two year look through all aLOGs with the H1 PSL task): - By Mar 2022, the PSL team had completed the complete table revamp to install the 2x NeoLase high-power amps, and addressed all the down-stream adaptations. - 2022-07-01 (Fri): The data set study starts. - 2022-09-06 (Tue): IO/ISC EOM mount updated, LHO:64882 - 2022-11-08 (Tue): Full IFO Commissioning Resumes after Sep 2022 to Dec 2022 vent to make FDS Filter Cavity Functional (see E2000005, "A+ FC By Week" tab) - 2023-03-02 (Thu): NPRO fails, LHO:67721 - 2023-03-06 (Mon): NPRO and PSL function recovered LHO:67790 - 2023-04-11 (Tue): PSL Beckhoff Updates LHO:68586 - 2023-05-02 (Tue): ISS AOM realignment LHO:69259 - 2023-05-04 (Thu): ISS Second Loop Guardian fix LHO:69334 - 2023-05-09 (Tue): "Something weird happened to the PMC, then it fixed itself" LHO:69447 - 2023-05-16 (Tue): Marked change in PSL PMC duty-cycle, nothing specific PSL team did with the PMC, but the DC power supplies for the RF & ISC racks we replaced, 69631, while Jason tuned up the FSS path LHO:69637 - 2023-05-24 : O4, and what we'll later call O4A, starts, we run with 75W requested power from the PSL. - 2023-06-02 (Fri): PSL ISS AA chassis it was replaced, but PMC stays locked through it LHO:70089 - 2023-06-12 (Sun): PMC PDH Locking PD needs threshold adjustment, LHO:70352, for "never found out why" reason FRS:28260 - 2023-06-19 (Mon): PMC PDH Locking PD needs another threshold adjustment, LHO:70586, added to FRS:28260, but again reasons never found. - 2023-06-21 (Wed): Decision made to reduce requested power into the IFO to 60W LHO:70648 - 2023-07-12 (Wed): Laser Interlock System maintenance kills PSL LHO:71273 - 2023-07-18 (Tue): Routine PMC / FSS tuneup, with quick PMC recovery LHO:71474 - 2023-08-06 (Sun): Site-wide power glitch takes down PSL LHO:72000 - 2023-09-22 (Fri): Site-wide power gltich takes down PSL LHO:73045 - 2023-10-17 (Tue): Routine PMC / FSS tuneup, with quick PMC recovery LHO:73513 - 2023-10-31 (Tue): Jeff does a mode scan sweeping the PMC FSR LHO:73905 - 2023-11-21 (Tue): Routine PMC / FSS tuneup, with quick PMC recovery LHO:74346 - 2024-01-16 : O4A stops, 3 months, focused on HAM567, no PSL work (see E2000005, "Mid-O4 Break 1" tab) O4A to O4B break lock losses: 7 2024-01-17 (Wed): Mid-vent, no IFO, no reported cause. 2024-01-20 (Sat): Mid-vent, no IFO, no reported cause. 2024-02-02 (Fri): Mid-vent, no IFO, no reported cause. 2024-02-08 (Thu): Mid-vent, no IFO, no reported cause. During HAM6 close out, may be related to alarm system 2024-02-27 (Tue): PSL FSS and PMC On-table Alignment LHO:76002. 2024-02-29 (Thu): PSL Rotation Stage Calibration LHO:76046. 2024-04-02 (Tue): PSL Beckhoff Upgrade LHO:76879. - 2024-04-10 : O4 resumes as O4B start O4B to 2024-07-01 lock losses: 1 2024-05-28 (Tue): PSL PMC REFL tune-up LHO:78093. - 2024-07-01 (Mon): The data set study ends. - 2024-07-02 (Tue): The PMC was swapped just *after* this data set, LHO:78813, LHO:78814 By the numbers Duty Cycle (uptime in days / total time in days) start_to_O4Astart: 0.8053 O4Astart_to_O4Aend: 0.9450 O4Aend_to_O4Bstart: 0.9181 O4Bstart_to_end: 0.9954 (Uptime in days is the sum on the values of H1:PSL-PMC_RELOCK_DAY just before lock losses [boxed in red] in the attached trend for the given time period) Lock Losses (number of times "days" goes to zero) start_to_O4Astart: 80 O4Astart_to_O4Aend: 22 O4Aend_to_O4Bstart: 7 O4Bstart_to_end: 1 (Number of lock losses is mere the count of red boxes for the given time period) Lock Losses per calendar days start_to_O4Astart: 0.2442 O4Astart_to_O4Aend: 0.0928 O4Aend_to_O4Bstart: 0.0824 O4Bstart_to_end: 0.0123 (In an effort to normalize the locklosses over the duration of the time period to give a more fair assessment.) I also attach a histogram of lock durations for each duration, as another way to look at how the duty cycle dramatically changed around the start of O4A. CSWG, ISC, Lockloss, SEI, SQZ, SYS

Non-image files attached to this report

2025-03-07_alssqzpowr_July2022toJul2024_trendannotated.pdf

2025-03-07_alssqzpowr_July2022toJul2024_hist.pdf

H1 DetChar - Comment to Possible Scattered Light ~28 Hz

sheila.dwyer@ligo.org — Fri, 07 Mar 2025 15:03:16 -0800

Author: sheila.dwyer@ligo.org

Report ID: 83235

Ryan found this alog from Oli: 83093 about this noise. Looking back through the summary pages, it does seem that this started turning off and on Feb 20th, before the 20th this blrms was constantly at the level of 200 nm/s.

Comparing the EX ground BLRMS to the optical lever spectra, whenever this ground noise is on you can see it in the optical lever pitch and yaw, indicating that the optical lever is sensing ground motion. Feb 22nd is a nice example of the optical lever getting quieter when the ground does. However, at this time we don't see the glitches in DARM yet, and hveto doesn't pick up the optical lever channel until yesterday. I'm having a hard time telling when this ground motion started to line up with glitches in DARM, it does for the last two days.

H1 TCS - TCS Monthly Trends - FAMIS 28458

ibrahim.abouelfettouh@ligo.org — Fri, 07 Mar 2025 14:29:14 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 83234

Closes FAMIS 28458. Last checked in alog 82659.

CO2 IY and IX PD_OUT signals are constant rather than offset at week intervals compared to last month. I assume this is due to changes between Tuesdays.
HWS SLEDPOWERMON signals for both IX and IY are continuing to go down very gradually as last month's trend showed.

TCS

Images attached to this report

H1 DetChar - Comment to Possible Scattered Light ~28 Hz

derek.davis@ligo.org — Fri, 07 Mar 2025 13:06:06 -0800

Author: derek.davis@ligo.org

Report ID: 83233

In recent weeks (every day after Feb 26), there have been large jumps in the amplitude of ground motion between 10-30 Hz at ETMX during the night. A good example of this behavior is on March 1 (see the relevant summary page plot from this page). This jump in ground motion occurs around 3 UTC and then returns to the lower level after 16 UTC. The exact times of the jumps change from night to night, but the change in seismic state is quite abrupt, and seems to line up roughly with the time periods when this scattering appears.

DetChar

Images attached to this report

H1 DetChar - Comment to Possible Scattered Light ~28 Hz

sheila.dwyer@ligo.org — Fri, 07 Mar 2025 12:42:28 -0800

Author: sheila.dwyer@ligo.org

Report ID: 83232

Ryan Short and I have been looking through the summary pages to see what we could learn about this.

Our range has been shaggy and low since Tuesday, this does seem to line up well with Tuesday maintence. Comparing the glitch rate before and after Tuesday isn't as easy, Iara Ota pointed me to the DMT omega glitch pages to make the comparison for Wed when omicron wasn't working. DMT omega pages don't show the problem very clearly, but the omicron based ones do show more glitches SNR 8 and higher since Tuesday maintence, we can compare Monday to Thursday.

Hveto does flag something interesting, which is that the ETMX optical lever vetos a lot of these glitches, both the pitch and yaw channels are picked by hveto, and they don't seem related to glitches in other channels. The oplev wasn't appearing in hveto before Tuesday.

H1 ISC - Comment to New in-vac POP WFS (HAM1) assembly is ready for testing

corey.gray@ligo.org — Fri, 07 Mar 2025 12:28:39 -0800

Author: corey.gray@ligo.org

Report ID: 83231

This WFS Assembly (D1102002) has been given the dcc-generated Serial Number of: S1300637 (with its electronics installed & sealed with 36MHz & 45MHz detection frequencies). As Keita notes, this s/n is etched by hand on the WFS Body "part" (D1102004 s/n016).

Here is ICS information for this new POP WFS with the Assembly Load here: ASSY-D1102002-S1300637

(NOTE: When this WFS is installed in HAM1, we should also move this "ICS WFS Assy Load" into the next Assy Load up: "ISC HAM1 Assembly" (ICS LINK: ASSY-D1000313-H1)

H1 PSL - PSL Status Report (FAMIS #26370)

corey.gray@ligo.org — Fri, 07 Mar 2025 11:49:15 -0800

Author: corey.gray@ligo.org

Report ID: 83229

This is for FAMIS #26370.
Laser Status:
    NPRO output power is 1.853W
    AMP1 output power is 70.51W
    AMP2 output power is 140.0W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 30 days, 23 hr 28 minutes
    Reflected power = 22.36W
    Transmitted power = 106.5W
    PowerSum = 128.8W

FSS:
It has been locked for 0 days 5 hr and 18 min
TPD[V] = 0.7969V

ISS:
The diffracted power is around 3.5%
Last saturation event was 0 days 5 hours and 18 minutes ago

Possible Issues: None reported

PSL

H1 SEI - SEI ground seismometer mass position check - Monthly (#26499)

corey.gray@ligo.org — Fri, 07 Mar 2025 11:42:37 -0800

Author: corey.gray@ligo.org

Report ID: 83228

Monthly FAMIS Check (#26499)

T240 Centering Script Output:

Averaging Mass Centering channels for 10 [sec] ...
2025-03-07 11:28:08.262570
There are 15 T240 proof masses out of range ( > 0.3 [V] )!
ETMX T240 2 DOF X/U = -0.975 [V]
ETMX T240 2 DOF Y/V = -1.02 [V]
ETMX T240 2 DOF Z/W = -0.554 [V]
ITMX T240 1 DOF X/U = -1.776 [V]
ITMX T240 1 DOF Y/V = 0.392 [V]
ITMX T240 1 DOF Z/W = 0.484 [V]
ITMX T240 3 DOF X/U = -1.843 [V]
ITMY T240 3 DOF X/U = -0.789 [V]
ITMY T240 3 DOF Z/W = -2.313 [V]
BS T240 1 DOF Y/V = -0.351 [V]
BS T240 3 DOF Y/V = -0.311 [V]
BS T240 3 DOF Z/W = -0.432 [V]
HAM8 1 DOF X/U = -0.317 [V]
HAM8 1 DOF Y/V = -0.434 [V]
HAM8 1 DOF Z/W = -0.712 [V]
All other proof masses are within range ( < 0.3 [V] ):
ETMX T240 1 DOF X/U = -0.006 [V]
ETMX T240 1 DOF Y/V = -0.014 [V]
ETMX T240 1 DOF Z/W = 0.009 [V]
ETMX T240 3 DOF X/U = 0.029 [V]
ETMX T240 3 DOF Y/V = -0.068 [V]
ETMX T240 3 DOF Z/W = -0.005 [V]
ETMY T240 1 DOF X/U = 0.082 [V]
ETMY T240 1 DOF Y/V = 0.171 [V]
ETMY T240 1 DOF Z/W = 0.24 [V]
ETMY T240 2 DOF X/U = -0.067 [V]
ETMY T240 2 DOF Y/V = 0.216 [V]
ETMY T240 2 DOF Z/W = 0.073 [V]
ETMY T240 3 DOF X/U = 0.26 [V]
ETMY T240 3 DOF Y/V = 0.114 [V]
ETMY T240 3 DOF Z/W = 0.146 [V]
ITMX T240 2 DOF X/U = 0.181 [V]
ITMX T240 2 DOF Y/V = 0.294 [V]
ITMX T240 2 DOF Z/W = 0.245 [V]
ITMX T240 3 DOF Y/V = 0.13 [V]
ITMX T240 3 DOF Z/W = 0.133 [V]
ITMY T240 1 DOF X/U = 0.082 [V]
ITMY T240 1 DOF Y/V = 0.123 [V]
ITMY T240 1 DOF Z/W = 0.04 [V]
ITMY T240 2 DOF X/U = 0.04 [V]
ITMY T240 2 DOF Y/V = 0.263 [V]
ITMY T240 2 DOF Z/W = 0.132 [V]
ITMY T240 3 DOF Y/V = 0.08 [V]
BS T240 1 DOF X/U = -0.161 [V]
BS T240 1 DOF Z/W = 0.156 [V]
BS T240 2 DOF X/U = -0.031 [V]
BS T240 2 DOF Y/V = 0.072 [V]
BS T240 2 DOF Z/W = -0.092 [V]
BS T240 3 DOF X/U = -0.139 [V]
Assessment complete.

STS Centering Script Output:

Averaging Mass Centering channels for 10 [sec] ...
2025-03-07 11:37:12.263138
There are 1 STS proof masses out of range ( > 2.0 [V] )!
STS EY DOF X/U = -2.334 [V]
All other proof masses are within range ( < 2.0 [V] ):
STS A DOF X/U = -0.503 [V]
STS A DOF Y/V = -0.757 [V]
STS A DOF Z/W = -0.603 [V]
STS B DOF X/U = 0.235 [V]
STS B DOF Y/V = 0.954 [V]
STS B DOF Z/W = -0.319 [V]
STS C DOF X/U = -0.862 [V]
STS C DOF Y/V = 0.801 [V]
STS C DOF Z/W = 0.681 [V]
STS EX DOF X/U = -0.041 [V]
STS EX DOF Y/V = -0.05 [V]
STS EX DOF Z/W = 0.102 [V]
STS EY DOF Y/V = -0.065 [V]
STS EY DOF Z/W = 1.318 [V]
STS FC DOF X/U = 0.195 [V]
STS FC DOF Y/V = -1.104 [V]
STS FC DOF Z/W = 0.659 [V]
Assessment complete.

SEI

H1 SQZ - Comment to SQZ SHG TEC Set Temperature Increased (+ opo_grTrans_setpoint lowered to 75)

sheila.dwyer@ligo.org — Fri, 07 Mar 2025 11:09:05 -0800

Author: sheila.dwyer@ligo.org

Report ID: 83227

During this time that the SHG guardian was cycling through it's states, that was happening because of the hard fault checker, which checks for errors on the SQZ laser, PMC transdiode, SHG demod, phase shifter.

The demod had an error because the RF level was too high, indeed this was above this threshold in this time and dropped back to normal allowing Corey to lock the squeezer.

The second screenshot shows a recent time that the SHG scaned and locked sucsesfully, in this case as the PZT scans the RF level goes up as expected when the cavity is close to resonance, and also goes above the threshold of 0dBm for a moment, causing the demod to have an error. This must have happened not at the moment when the guardian was checking this error, so that the guardian allowed it to continue to lock.

It doesn't make sense to throw an error about this RF level when the cavity is scanning, so I've commented out the demod check from the hardfault checker.

Also, looking at this hardfault checker, I noticed that it is check for a fault on the PMC trans PD. It would be prefferable to have the OMC guardian do whatever checks it needs to do on the PMC, and trust the sqz manager to correctly not ask the SHG to lock when the PMC is unlocked. Indeed, SQZ manager has a PMC checker when it is asking the SHG to lock, so I've commented out this PMC checker in the SHG guardian. This same logic applies to the check on the squeezer laser, leaving us with only a check on the SHG phase shifter in the hardfault checker.

Editing to add: I wondered why Corey got the message about the pump ISS. DIAG_MAIN has two checks for the squeezer, first that SQZ_MANAGER is in the nominal state, then second that the pump ISS is on. I added an elif to the pump ISS one, so if the sqz manager isn't in the nominal state this will be the only message that the operator sees, Ryan Short and I looked at the SQZ_MANAGER and indeed it seems that there isn't a check for the pump ISS in FREQ_DEP_SQZ.

SQZ_SHG guardian and DIAG_MAIN will need to be reloaded at the next oppurtunity.

Images attached to this report

Non-image files attached to this report

SHG_log_cycling.txt

LHO VE - Fri CP1 Fill

david.barker@ligo.org — Fri, 07 Mar 2025 10:22:32 -0800

Author: david.barker@ligo.org

Report ID: 83226

Fri Mar 07 10:09:56 2025 INFO: Fill completed in 9min 52secs

Jordan confirmed a good fill curbside.

Images attached to this report

H1 SQZ - SQZ SHG TEC Set Temperature Increased (+ opo_grTrans_setpoint lowered to 75)

corey.gray@ligo.org — Fri, 07 Mar 2025 09:45:44 -0800

Author: corey.gray@ligo.org

Report ID: 83224

SUMMARY: Back To OBSERVING, but got here after going in a few circles.

H1 had a lockloss before the shift, but when I arrived H1 was at NLN, BUT SQZ had issues.

I opened up the SQZ Overview screen and could see that the SQZ_SHG guardian node was bonkos (so I had this "all node" up the whole time...it was crazy because it was frantically moving through states to get LOCKED, but could not), BUT also I saw.....

1) DIAG_MAIN

DIAG_MAIN had notifications flashing which said: "ISS Pump is off. See alog 70050." So, this is where I immediately switched focus.

2) Alog70050: "What To Do If The SQZ ISS Saturates"

Immediately followed the instructions from alog70050 which were pretty straightforward. Remember: H1's not Observing, so I jumped on the alog instructions and wanted to get back to Observing ASAP.) I took the opo_grTrans_setpoint_uW from 80 to 50, and tried to get SQZ back to FDS, but no go (SQZ Manager stuck....and SQZ_SHG still bonkos!).

At this point, I saw that there were several other sub-entries with updated instructions and notes. So I went through them and took opo_grTrans_setpoint_uW to 60 (no FDS + SQZ_SHG still crazy), and finally set opo_grTrans_setpoint_uW = 75 (but still no FDS + SQZ_SHG still crazy).

At this point, I'm assuming DIAG_SDF sent me on a wild goose chase. Soooooo, I focused on the erratic SQZ_SHG......

3) Alog search: "SQZ_SHG" ---> H1:SQZ-SHG_TEC_SETTEMP Taken to 33.9

This did the trick! And this search took me to early Feb2025 alogs from (1) RyanS alog82599 which sounded what I had and then (2) Ibrahim's alog82581 which laid out instructions for what to do for adjusting the SHG TEC Set Temperature (went from 33.7 to 33.9; see attachment #1). AND---during these adjustments the infamous SQZ_SHG finally LOCKED!!

After this it was easy and straightforward taking the SQZ Manager to FDS and get H1 back to Observing.

NOTE: I wanted to see the last time this Set Temperature was adjusted and it was Feb 17, 2025. Doing an alog search on just "SHG" + tag: SQZ took me to when it was last adjusted: By ME! During an OWL wake-up call, I adjusted this set point from ~35.1 to 33.7 on 02172025 at 1521utc/72amPST (see attachment #2).

The only SDF to ACCEPT was the H1:SQZ-SHG_TEC_SETTEMP = 33.7 (see attachment #3). BUT: Remember other changes I made (when I erroneously thought I had to adjust the OPO TEC TEMP which are not in SDF:

opo_grTrans_setpoint_uW = 75 (was 80)
H1:SQZ-OPO_TEC_SETTEMP = 30.937 (was 30.941)

Hindsight is 20/20, but if I addressed the "bonkos SQZ_SHG" via instructions from an alog search first, I would have saved some time! :)

OpsInfo, SQZ

Images attached to this report

LHO General - Fri Ops Day Transition

corey.gray@ligo.org — Fri, 07 Mar 2025 07:46:28 -0800

Author: corey.gray@ligo.org

Report ID: 83223

TITLE: 03/07 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: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY:

H1's just made it to NLN .after a 7.75hr lock overnight (lockloss), but has a SQZ ISS Pump Off issue. microseism are low and winds are as well.

H1 General - Thursday Eve Shift Summary

anthony.sanchez@ligo.org — Thu, 06 Mar 2025 22:07:34 -0800

Author: anthony.sanchez@ligo.org

Report ID: 83222

TITLE: 03/07 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: ->Ryan S.<-
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 8mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.20 μm/s
SHIFT SUMMARY:
H1 was locked for 7 Hours and 17 minutes.
Until a sudden and Unknown lockloss struck at 5:24 UTC, Screenshots of lockloss ndscopes attached.

I took the last half hour of my shift to run an Initial_alignment before the start of Ryans Shift.
H1 is currently just past at CARM_TO_TR.

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
00:32	WFS	Keita	Optics Lab	Yes	Parts for WFS	01:36

Lockloss

Images attached to this report

H1 SEI - BRS Drift Trends--Monthly

anthony.sanchez@ligo.org — Thu, 06 Mar 2025 21:52:02 -0800

Author: anthony.sanchez@ligo.org

Report ID: 83221

BRS Dift Trends --Monthly FAMIS 26452

BRSs are not trending beyond their red thresh holds.

Images attached to this report

H1 ISC - New in-vac POP WFS (HAM1) assembly is ready for testing

keita.kawabe@ligo.org — Thu, 06 Mar 2025 18:26:16 -0800

Author: keita.kawabe@ligo.org

Report ID: 83220

I assembled the 45MHz WFS unit in the optics lab. Assembly drawing: D1102002.

BOM:

1x Pre-assembled WFS body (D1102004 s/n016 Main Body, sealed & scribed as "S1300637" according to Corey's email)
1x Alumina spacer (D1102007)
1x Baseplate (D1102003)
1x Q3000 QPD
1x QPD hood (D1102006)
2x SHCS 1/4-20 X .75" 18-8 VENTED for the baseplate
2x 1/4" PEEK washer (D1102010) for the baseplate
4x SHCS 4-40 X 3/16" 18-8 Vented for the QPD hood (spec is BSHCS but SHCS works fine)

I confirmed that the baseplate and the WFS body are electrically isolated from each other.

There were many black spots on the WFS body (2nd pic) as well as the aluminum foil used for wrapping (3rd pic). It seems that this is a result of rubbing of aluminum against aluminum. I cannot wipe it off but this should be aluminum powder and not some organic material.

QPD orientation is such that the tab on the can is at 1:30 o'clock position seen from the front (4th pic). You cannot tell it from the picture but there's a hole punched to the side of the can.

Clean SMP - dirty SMA cables are in a bag inside the other clean room in the optics lab. DB25 interface cable is being made (or was made?) by Fil.

ISC

Images attached to this report

H1 General - Thursday Eve Shift login

anthony.sanchez@ligo.org — Thu, 06 Mar 2025 16:41:28 -0800

Author: anthony.sanchez@ligo.org

Report ID: 83219

TITLE: 03/07 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 21mph Gusts, 16mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.25 μm/s
QUICK SUMMARY:

H1 has been locked and Observing for 2 hours and 23 minutes.
All systems are running well, though the range seems a bit low.

H1 General - Ops Day Shift End

oli.patane@ligo.org — Thu, 06 Mar 2025 16:38:20 -0800

Author: oli.patane@ligo.org

Report ID: 83218

TITLE: 03/07 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Currently Observing at 147 Mpc and have been Locked for 2.5 hours. Relocking after the lockloss during the calibration measurements was fully automatic and went relatively smoothly.
LOG:

20:35UTC Lockloss during calibration measurements

22:07 NOMINAL_LOW_NOISE
22:10 Observing

23:25 Three military jet planes flew overhead at a very low altitude (tagging Detchar)

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
16:02	FAC	Nelly	Opt lab	n	Tech clean	16:14
19:21	SQZ	Sheila, Mayank	LVEA - SQZ	n	SQZ rack meas.	19:52
21:05	TOUR	Sheila, Nately	LVEA	N	Tour	21:29
21:53	ISC	Matt, Siva, Mayank	OpticsLab	n	ISS Array Alignment	22:48
23:55	VAC	Jordan, Fifer reps	Mids	n	Vacuum work	00:39
00:32	WFS	Keita	Optics Lab	Yes	Parts for WFS	02:32

DetChar

H1 DetChar - Possible Scattered Light ~28 Hz

elenna.capote@ligo.org — Thu, 06 Mar 2025 16:23:02 -0800

Author: elenna.capote@ligo.org

Report ID: 83217

I found evidence of possible scattered light while looking at some data from a lock yesterday. Attached is a whitened spectrogram of 30 minutes of data starting at GPS 1425273749. It looks like the peaks are around 28, 38, and 48 Hz, but they are broad and it's hard to tell the exact frequency and spacing. Sheila thinks this may have appeared after Tuesday maintenance. Tagging detchar request so some tests can be run to help us track down the source!

DetChar-Request

Images attached to this report

H1 SUS - Comment to cross-coupling and reciprocal plants

brian.lantz@ligo.org — Thu, 06 Mar 2025 15:10:09 -0800

Author: brian.lantz@ligo.org

Report ID: 83216

If this is a gain error in 1 of the L osems, how big is it? - about 15%.

Move the top mass, let osem #1 measure a distance m1, and osem #2 measure m2.

Give osem #2 a gain error, so it's response is really (1+e) of the true distance.
Translate the top mass by d1 with no rotation, and the two signals will be m1= d1 and m2=d1*(1+e)
L is (m1 + m2)/2 = d1/2 + d1*(1+e)/2 = d1*(1+e/2)
The angle will be (m1 - m2)/s where s is the separation between the osems.

I think that s=0.16 meters for top mass of HLTS (from make_sus_hlts_projections.m in the SUS SVN)
Angle measured is (d1 - d1(1+e))/s = -d1 * e /s

The angle/length for a length drive is
-(d1 * e /s)/ ( d1*(1+e/2)) = 1/s * (-e/(1+e/2)) = -0.85 in this measurement
if e is small, then e is approx = 0.85 * s = 0.85 rad/m * 0.16 m = 0.14

so a 14% gain difference between the rt and lf osems will give you about a 0.85 rad/ meter cross coupling. (actually closer to 15% -
0.15/ (1 + 0.075) = 0.1395, but the approx is pretty good.
15% seem like a lot to me, but that's what I'm seeing.

LHO FMCS - Mid station chilled water temperature trends

eric.otterman@ligo.org — Thu, 06 Mar 2025 14:50:38 -0800

Author: eric.otterman@ligo.org

Report ID: 83215

I ran each chilled water pump at the Mid Stations in order to exercise their seals and bearings since these pumps are currently off for the season. This will cause the temperature trending of the loop water to show an decrease for a brief period. The Mid Stations chillers are currently shut down and will remain off until late Spring.

H1 SUS - Summary aLOG for Hardware/Sotware Changes in Support of In-coming POP WFS Steering Mirror HTTS, PM1

jeffrey.kissel@ligo.org — Thu, 06 Mar 2025 14:13:34 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 83214

F. Clara, D. Barker, J. Kissel, O. Patane, D. Sigg ECR E1700228 (0) Confirm the analog cabling plan implicit in D0902810-v10 -- see LHO:83168. (1) Move PR3 optical lever from h1sush2b over to h1sush2a to make room for PM1 on h1sush2b, WP 12370 Front-end Model Prep work: LHO:83194 (2) Add new POP WFS controls path to ASC front-end model for driving PM1, WP: 12374 Front-end Model Prep work: LHO:83195 (3) Add PM1 as an "HSSS_FF_MASTER.mdl" into the h1sushtts.mdl, following the other HTTS in HAM1, RM1 and RM2 WP: 12375 Front-end Model Prep work: LHO:83196 and LHO:83211 Note, as Oli mentions in LHO:83196, we'll likely need one more model change to h1sushtts.mdl and the future h1isiham1.mdl model to send up some fresh-and-better ISI feed-forward signals to the RMs and PM1, but this will come in due time. The goal is to execute all of this prep work and work-permits during upcoming maintenance period, Mar 11 2025 (with a back-up date of Mar 18 2025 if needed).CDS, ISC

H1 CAL - Comment to Calibration Sweep 2006UTC, Lock loss near end

oli.patane@ligo.org — Thu, 06 Mar 2025 14:11:02 -0800

Author: oli.patane@ligo.org

Report ID: 83213

22:10UTC Back to Observing after lockloss

H1 SUS - Comment to Addition of PM1 to h1sushtts simulink model

jeffrey.kissel@ligo.org — Thu, 06 Mar 2025 13:59:03 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 83212

Just few "slept on it, and remembered we should" things to add: (1) Attached is the DAQ channel list that comes with the installation of PM1. We didn't cover it explicitly above because it comes standard with the /opt/rtcds/userapps/release/sus/common/models/ HSSS_FF_MASTER.mdl library part, but as it is new (small) weight on the DAQ, it's worth calling out. 4x new channels stored at 512 Hz, and 13x at 256 Hz. (2) Also, the oft-forgotten coil driver output voltage monitor channels, the so-called VMONs needed to be absorbed by the h1susauxh2 front-end too, so we've now done the model prep that as well -- see LHO:83211.CDS

Images attached to this report

H1 SUS - Model Prep for PM1 (New POP WFS HTTS in HAM 1): Added Coil Driver VMONs to h1susauxh2 model

jeffrey.kissel@ligo.org — Thu, 06 Mar 2025 13:05:59 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 83211

J. Kissel ECR E1700228 One last thing in prep for PM1 from the simulink model perspective: in addition to the "controls" model that Oli and I prepped yesterday (LHO:83196, LHO:83194), we need to add the HAM-A coil driver voltage monitors, the "VMONs" to the h1susauxh2 model. Currently the HAM12 wiring diagram D0902810-v10 is in conflict, indicating that these VMON channels are to be piped in (1) on page 12 to "IN25-28" of the SUS-C4 AA chassis at U11, (2) on page 14 to "IN25-28" of the SUS-C3 AA chassis at U31 which either way feed into ADC0 of the h1susauxh2 IO chassis/computer. I'm 100% confident that (2) is right, and will redline the drawing. As such, I've populated the new PM1 VMON filters with the ADC0 channels 24-27. See attached screenshots. I've tested that the model compiles successfully on the h1build machine. The updates to the model have been committed to the userapps repo as /opt/rtcds/userapps/release/sus/h1/models/ h1susauxh2.mdl rev 30909. No library parts were used or impacted.

Images attached to this report

H1 CAL - Calibration Sweep 2006UTC, Lock loss near end

thomas.shaffer@ligo.org — Thu, 06 Mar 2025 12:38:08 -0800

Author: thomas.shaffer@ligo.org

Report ID: 83210

Following the usual Cal meas wiki instructions , I ran a calibration broadband and simulines measurement, but the IFO lost lock near the very end of simulines. All test points were cleared with the script wrapup.

Simulines start:

PST: 2025-03-06 12:12:00.699516 PST
UTC: 2025-03-06 20:12:00.699516 UTC
GPS: 1425327138.699516

Simulines output near end:

2025-03-06 20:35:04,501 | INFO | Drive, on DARM_OLGTF, at frequency: 1083.3, and amplitude 1e-09, is finished. G
PS start and end time stamps: 1425328503, 1425328518
2025-03-06 20:35:04,502 | INFO | Scanning frequency 1200.0 in Scan : DARM_OLGTF on PID: 861436
2025-03-06 20:35:04,502 | INFO | Drive, on DARM_OLGTF, at frequency: 1200.0, is now running for 23 seconds.
2025-03-06 20:35:05,621 | INFO | Drive, on L2_SUSETMX_iEXC2DARMTF, at frequency: 43.6, and amplitude 0.40648, is
finished. GPS start and end time stamps: 1425328503, 1425328518
2025-03-06 20:35:05,622 | INFO | Scanning frequency 51.05 in Scan : L2_SUSETMX_iEXC2DARMTF on PID: 861446
2025-03-06 20:35:05,622 | INFO | Drive, on L2_SUSETMX_iEXC2DARMTF, at frequency: 51.05, is now running for 23 se
conds.
2025-03-06 20:35:06,760 | INFO | Drive, on L3_SUSETMX_iEXC2DARMTF, at frequency: 289.84, and amplitude 0.49024,
is finished. GPS start and end time stamps: 1425328503, 1425328518
2025-03-06 20:35:07,271 | INFO | 4 still running.
2025-03-06 20:35:11,138 | INFO | Drive, on PCALY2DARMTF, at frequency: 7.68, and amplitude 16534, is finished. G
PS start and end time stamps: 1425328496, 1425328523
2025-03-06 20:35:11,279 | INFO | 3 still running.
2025-03-06 20:35:11,721 | ERROR | IFO not in Low Noise state, Sending Interrupts to excitations and main thread.
2025-03-06 20:35:11,721 | ERROR | Ramping Down Excitation on channel H1:LSC-DARM1_EXC
2025-03-06 20:35:11,721 | ERROR | Aborting main thread and Data recording, if any. Cleaning up temporary file st
ructure.
Process Process-12:
Traceback (most recent call last):
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap
   self.run()
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/process.py", line 108, in run
   self._target(*self._args, **self._kwargs)
File "/ligo/groups/cal/src/simulines/simulines/simuLines.py", line 340, in checkIfLocked
   os.kill(pid,signal.SIGINT)
ProcessLookupError: [Errno 3] No such process
2025-03-06 20:35:24,341 | INFO | Drive, on L1_SUSETMX_iEXC2DARMTF, at frequency: 12.86, and amplitude 19.723, is
finished. GPS start and end time stamps: 1425328522, 1425328538
Process Process-9:
Traceback (most recent call last):
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap
   self.run()
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/process.py", line 108, in run
   self._target(*self._args, **self._kwargs)
File "/ligo/groups/cal/src/simulines/simulines/simuLines.py", line 678, in generateSignalInjection
   results[scan] = tempObj
File "", line 2, in __setitem__
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/managers.py", line 817, in _callmethod
   conn.send((self._id, methodname, args, kwds))
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/connection.py", line 206, in send
   self._send_bytes(_ForkingPickler.dumps(obj))
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/connection.py", line 411, in _send_bytes
   self._send(header + buf)
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/connection.py", line 368, in _send
   n = write(self._handle, buf)
BrokenPipeError: [Errno 32] Broken pipe
2025-03-06 20:35:30,666 | INFO | Drive, on L2_SUSETMX_iEXC2DARMTF, at frequency: 51.05, and amplitude 0.34489, i
s finished. GPS start and end time stamps: 1425328529, 1425328544
Process Process-10:
Traceback (most recent call last):
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap
   self.run()
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/process.py", line 108, in run
   self._target(*self._args, **self._kwargs)
File "/ligo/groups/cal/src/simulines/simulines/simuLines.py", line 678, in generateSignalInjection
   results[scan] = tempObj
File "", line 2, in __setitem__
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/managers.py", line 817, in _callmethod
   conn.send((self._id, methodname, args, kwds))
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/connection.py", line 206, in send
   self._send_bytes(_ForkingPickler.dumps(obj))
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/connection.py", line 411, in _send_bytes
   self._send(header + buf)
File "/var/opt/conda/base/envs/cds/lib/python3.10/multiprocessing/connection.py", line 368, in _send
   n = write(self._handle, buf)
BrokenPipeError: [Errno 32] Broken pipe
ICE default IO error handler doing an exit(), pid = 861402, errno = 32
PST: 2025-03-06 12:35:30.912878 PST
UTC: 2025-03-06 20:35:30.912878 UTC
GPS: 1425328548.912878

Images attached to this report

H1 SUS - Comment to cross-coupling and reciprocal plants

brian.lantz@ligo.org — Thu, 06 Mar 2025 11:27:28 -0800

Author: brian.lantz@ligo.org

Report ID: 83209

ah HA! There is already a SENSALIGN matrix in the model for the M1 OSEMs - this is a great place to implement corrections calculated in the Euler basis. No model changes are needed, thanks Jeff!

LHO VE - Thu CP1 Fill

david.barker@ligo.org — Thu, 06 Mar 2025 10:34:36 -0800

Author: david.barker@ligo.org

Report ID: 83208

Thu Mar 06 10:13:00 2025 INFO: Fill completed in 12min 56secs

Images attached to this report

H1 General - Lock loss 1611UTC

thomas.shaffer@ligo.org — Thu, 06 Mar 2025 09:05:30 -0800

Author: thomas.shaffer@ligo.org

Report ID: 83207

1425312692

Just before calibration and commissoining time we lost lock. Just like the lock loss before it, the only sign of anything moving beforehand is a very small wiggle in ETMY output 10's of ms before. This might be nothing, but it's the only thing I've found so far.

Once we get back we will jump straight into unthermalized commissioning followed by a calibration.

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Thu, 06 Mar 2025 07:30:27 -0800

Author: thomas.shaffer@ligo.org

Report ID: 83206

TITLE: 03/06 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 9mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.32 μm/s
QUICK SUMMARY: Currently in a stand down, we've been locked for 5.5 hours. Calm environment, no alarms.

H1 General - Wednesday Eve Shift Sign out report.

anthony.sanchez@ligo.org — Wed, 05 Mar 2025 22:09:01 -0800

Author: anthony.sanchez@ligo.org

Report ID: 83205

TITLE: 03/06 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 10mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.29 μm/s
SHIFT SUMMARY:
Once LHO H1 was relocked at the very beginning of my shift, it stayed locked for the next 4 hours and 40 minutes.
Everything has been running well.

LOG:
No Log

H1 AOS - Comment to CDS Unifi WAP update notes

anthony.sanchez@ligo.org — Wed, 05 Mar 2025 21:49:04 -0800

Author: anthony.sanchez@ligo.org

Report ID: 83204

All CDS UNIFI WAPS have been updated without issues.

H1 AOS - CDS Unifi WAP update notes

anthony.sanchez@ligo.org — Wed, 05 Mar 2025 21:48:29 -0800

Author: anthony.sanchez@ligo.org

Report ID: 83199

https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=83131

The lastest updates for these UAP-AC-HD UNIFI WAP can be found here:
https://ui.com/download/software/uap-ac-hd

I'm going to update MSR-AP-UNIFI WAP as a test to determine if we wwill run in to issues.
MSR-AP-UNIFI is currently running this version:
MAC Address xx:...:c4:04
Model   UAP-AC-HD
Version   5.43.56.12784

I will be updating to 6.6.77 which is the latest update.
Update went well, with no Issues.

The Following CDS Unifi WAPS Should also be updated.
CER-UNIFI-AP
EX-UNIFI-AP
EY-UNIFI-AP
FCES-UNIFI-AP
LVEA-UNIFI-AP
MX-UNIFI-AP
MY-UNIFI-AP

H1 SUS - ETMX glitch limiter effect on ETMX L3 MASTER_OUT

oli.patane@ligo.org — Wed, 05 Mar 2025 18:57:36 -0800

Author: oli.patane@ligo.org

Report ID: 83203

Back at the start of February, Jim put a limiter into the ETMX_L3_ESD OSEM filter banks to limit the output, hoping that it would minimize the number of ETMX glitches and subsequently locklosses(82608). To help us figure out if it did anything, I've taken a look at the amplitude distribution of the ETMX glitches that happen during our locks (the ones we don't lose lock during), comparing the amplitude distribution for the glitches we saw with the limiter on versus the ones that happened with it off.

The three time periods I compared are the following (all about 9 days long):

Limiter off:

Jan25 14:12UTC - Feb3 16:28UTC
- ~161 hours locked
- ~1,000 ETMX glitches seen (6/hour locked)
Feb12 22:45UTC - Feb22 01:46UTC
- ~137 hours locked
- ~1,000 ETMX glitches seen (7/hour locked)

Limiter on:

Feb3 16:28UTC - Feb12 22:45UTC
- ~152 hours locked
- ~1,650 ETMX glitches seen (11/hour locked)

How I got this data (ignore if you don't care about the convoluted scripts I wrote):

For each stretch of time, I used minute trends of GRD_ISC_LOCK_STATE_N to grab all lock stretches based on whether we were in NLN that entire minute (so excluding the first and last minute of the lock). I then went through the lock stretches while looking at one of the L3 MASTER_OUT channels using second trends and grabbed any time where the min or max went above a reasonably low value, low enough that it would also catch small ETMX glitches. However, this method also catches any other time the OSEM was moving a lot, such as during earthquakes, so I then grabbed the raw data for that channel, and then ran that data plus the two seconds on either side through a high pass filter. This was a method we previously implemented into the lockloss tool to help us find ETMX glitches right before locklosses. Then I looked through the high passed data with scipy's signal.find_peaks and looked for peaks over a certain threshold and at least 25ms apart. Any peaks found were logged into a txt file. In matlab I used the ecdf function to calculate the cumulative distribution and plotted the data from the three stretches of time.

Looking at the results:

The plot shows that the two stretches of time where the limiter was off have similar distributions of glitch amplitude probabilities, so that's good to know they line up with each other well. Looking at the data set for when the limiter was on, the distribution differs - there was a higher probability of glitches occurring at all amplitudes as compared to when the limiters were off. This also generally lines up with what we see when we just look at the basic stats for each data stretch - even though all three sets are similar in the amount of hours locked, there were about 50% more ETMX glitches when limiters were on.

The limiter was turned back on yesterday (83158), so it'll be interesting to see if we get a similar distribution as before.

Images attached to this report

Non-image files attached to this report

limiter_on_v_off.fig

H1 General - Wednesday Eve Shift Sign in report.

anthony.sanchez@ligo.org — Wed, 05 Mar 2025 17:27:37 -0800

Author: anthony.sanchez@ligo.org

Report ID: 83202

TITLE: 03/06 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 137Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 10mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.29 μm/s
QUICK SUMMARY:

Lockloss right at the start of my shift from a small local 3.9M earthquake.
Lockloss page says that it was caused by anthropogenic source but when we lost lock we saw UW's Picket fence ground motion increased and we had an increase in our ground motion on the H1:ISI-GND_STS_ITMY_{X,Y, Z}_BLRMS_{1_3, and 3_10}. BUT we didn't see it on the top of NUC 5. Which is strange.
This lockloss may have been first logged in Ryan C's outro alog.

I started relocking without an Initial_Alignment, H1 requested Find X-Arm by hand. I took X arm to Increase flashes, which worked great!
PRMI locked on a crazy mushroom shaped mode. I decided to see if it could lock DRIMI like that, and if it was having trouble then i'd just run an Initial Alignment if it failed. But it Actually locked pretty quickly!

Nominal Low Noise reached at 1:23 UTC
Observing Reached at 1:26 UTC

H1 General - OPS Wednesday DAY shift summary

ryan.crouch@ligo.org — Wed, 05 Mar 2025 16:30:26 -0800

Author: ryan.crouch@ligo.org

Report ID: 83190

TITLE: 03/05 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: We lost lock early in the day and struggled to get back up due to ASC issues, we've been locked for ~ 3 hours. Sheila turned off SRC1 & SRC2 in ISC_DRMI.py in ENGAGE_DRMI_ASC to help us lock.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
16:08	FAC	Kim	Optics lab & Vac prep	N	Tech clean	16:31
16:11	FAC	Nellie	H2	N	Tech clean	16:32
17:04	ISC	Sheila, TJ	ISCT1	LOCAL	Table checks/adjustments	17:20
17:16	FAC	Tyler + contractors	VAC prep lab	N	Heating checks	18:24
17:24	FAC	Kim & Nellie	MidX	N	Tech clean	18:24
18:08	FAC	Jim, Mitchell	Ends	n	Taking measurements on wind fence	19:29
18:30	FAC	Nellie	Firepump room	N	Tech clean	19:20
18:45	VAC	Travis, Gerardo	EndX MR	N	Piping, compressor work	19:53
21:41	EE	Fil, Marc	OSB Recieving	N	Bring parts from LSB to OSB recieving	21:55
21:55	CAL	Tony	PCAL lab	LOCAL	PCAL work	22:06
21:56	EE	Fil, Marc	MidY	N	Parts dropoff	22:16

16:34 UTC Lockloss
17:40 UTC We held in PRMI_LOCKED and tried to increase the buildups by adjusting some optics
- Then we tried to go up bypassing ASC, by manualing around the states. I lost it at TRANSITION_TO_3F
I'm trying to do the same in DRMI_1F, adjust optics by hand, but its keeps killing it
18:55 UTC We tried running the dark_offsets script
20:41 UTC EQ mode, from near the Galapagos islands
21:12 UTC Observing after accepting SDF diffs
00:20 UTC lockloss , there was a motion spike in the 0.3 - 1.0 Hz bandwith

Images attached to this report

H1 SUS - cross-coupling and reciprocal plants

brian.lantz@ligo.org — Wed, 05 Mar 2025 16:23:32 -0800

Author: brian.lantz@ligo.org

Report ID: 83200

I'm looking again at the OSEM estimator we want to try on PR3 - see https://dcc.ligo.org/LIGO-G2402303 for description of that idea.

We want to make a yaw estimator, because that should be the easiest one for which we have a hope of seeing some difference (vertical is probably easier, but you can't measure it). One thing which makes this hard is that the cross coupling from L drive to Y readout is large.

But - a quick comparison (first figure) shows that the L to Y coupling (yellow) does not match the Y to L coupling (purple). If this were a drive from the OSEMs, then this should match. This is actuatually a drive from the ISI, so it is not actually reciprocal - but the ideas are still relevant. For an OSEM drive - we know that mechanical systems are reciprocal, so, to the extent that yellow doesn't match purple, this coupling can not be in the mechanics.

Never-the-less, the similarity of the Length to Length and the Length to Yaw indicates that there is likely a great deal of cross-coupling in the OSEM sensors. We see that the Y response shows a bunch of the L resonances (L to L is the red TF); you drive L, and you see L in the Y signal. This smells of a coupling where the Y sensors see L motion. This is quite plausible if the two L OSEMs on the top mass are not calibrated correctly - because they are very close together, even a small scale-factor error will result in pretty big Y response to L motion.

Next - I did a quick fit (figure 2). I took the Y<-L TF (yellow, measured back in LHO alog 80863) and fit the L<-L TF to it (red), and then subtracted the L<-L component. The fit coefficient which gives the smallest response at the 1.59 Hz peak is about -0.85 rad/meter.

In figure 3, you can see the result in green, which is generally much better. The big peak at 1.59 Hz is much smaller, and the peak at 0.64 is reduced. There is more from the peak at 0.75 (this is related to pitch. Why should the Yaw osems see Pitch motion? maybe transverse motion of the little flags? I don't know, and it's going to be a headache).

The improved Y<-L (green) and the original L<-Y (purple) still don't match, even though they are much closer than the original yellow/purple pair. Hence there is more which could be gained by someone with more cleverness and time than I have right now.

figure 4 - I've plotted just the Y<-Y and Y<-L improved.

Note - The units are wrong - the drive units are all meters or radians not forces and torques, and we know, because of the d-offset in the mounting of the top wires from the suspoint to the top mass, that a L drive of the ISI has first order L and P forces and torques on the top mass. I still need to calculate how much pitch motion we expect to see in the yaw reponse for the mode at 0.75 Hz.

In the meantime - this argues that the yaw motion of PR3 could be reduced quite a bit with a simple update to the SUS large triple model, I suggest a matrix similar to the CPS align in the ISI. I happen to have the PR3 model open right now because I'm trying to add the OSEM estimator parts to it. Look for an ECR in a day or two...

This is run from the code {SUS_SVN}/HLTS/Common/MatlabTools/plotHLTS_ISI_dtttfs_M1_remove_xcouple'

-Brian

SEI

Images attached to this report

H1 General - 00:20 UTC lockloss

ryan.crouch@ligo.org — Wed, 05 Mar 2025 16:22:30 -0800

Author: ryan.crouch@ligo.org

Report ID: 83201

00:20 UTC lockloss, LSC_PR_GAIN got noisy ~20 seconds before the lockloss.

H1 SUS - Addition of PM1 to h1sushtts simulink model

oli.patane@ligo.org — Wed, 05 Mar 2025 13:40:59 -0800

Author: oli.patane@ligo.org

Report ID: 83196

Jeff, Oli

ECR E1700228

More preparation to make way for PM1 - Jeff and I went into the h1sushtts simulink model and added in PM1 and its necessary connections(h1sushtts before). It was basically a copy of the RM1 and RM2 control blocks, with the input ADC channels taking 24 - 27, and channels 8 - 11 on the DAC (h1sushtts after - PM1+output).

We also copied the RMs PCIe inputs, but the channels coming in from the TTL4C on HAM1 are going to be removed for the RMs when the ISI is installed on HAM1 and replaced with the new ISI channels, and so PM1 will never have the HAM1_TTL4C channels. Since we want to be able to compile and test the model before then, I have put in a constant 0 in place of the TTL4C channels for PM1 (h1sushtts after - IPC INP). Once we have the new ISI channels, we can add these connections in using those channels, as well as update the channels for the RMs.

Daniel just added in the new ASC channels for PM1 (83195), so I was able to successfully compile h1sushtts. It has not yet been installed.

The model file can be found in /opt/rtcds/userapps/release/sus/h1/models/, and the changes to h1sushtts.mdl have been committed to the svn as revision 30907.

AOS, CDS

Images attached to this report

H1 General - OPS Update

ryan.crouch@ligo.org — Wed, 05 Mar 2025 13:13:44 -0800

Author: ryan.crouch@ligo.org

Report ID: 83198

21:12 UTC we have recovered Observing after a long struggle with ASC, I had to accept a bunch of OFFSET SDF diffs from the dark offset script earlier.

Images attached to this report

H1 General - Monthly wind fence inspection FAMIS Request ID:24812

jim.warner@ligo.org — Wed, 05 Mar 2025 12:41:39 -0800

Author: jim.warner@ligo.org

Report ID: 83197

Inspected the wind fences today. The southmost panel at EY continues to degrade, might even save us the work of coming down on its own before the vent, when we plan to replace it. The rest of EY looks fine. EX also seems stable, unsure of when we plan to repair it, but we have replacement panels and are starting to order hardware. First pic is EX, second is EY.

Images attached to this report

H1 AOS - ASC Model Update

daniel.sigg@ligo.org — Wed, 05 Mar 2025 12:31:39 -0800

Author: daniel.sigg@ligo.org

Report ID: 83195

Preparing for an upgrade of the ASC model to add PM1 auto-centering. This includes new filter modules PM1_PIT and PM1_YAW, and IPC senders H1:ASC_PM1_PIT_SUSHTTS and H1:ASC_PM1_YAW_SUSHTTS.

For now the old auto-centering driving the MCL PZTs has been left in place.

Buttons for the the new PM1 filter modules were added to the ASC medm screen as well.

H1 SUS - Simulink Model Prep for PR3 Optical Lever Cable Move

oli.patane@ligo.org — Wed, 05 Mar 2025 12:21:12 -0800

Author: oli.patane@ligo.org

Report ID: 83194

Jeff, Oli

WP 12370

ECR E1700228

In a continuation of preparing for the addition of PM1 (83168), Jeff and I have made the necessary model changes for the PR3 OpLev. As outlined in 83168, the stuff that needed to be changed in the model (to match with the physical changes) was to move the PR3 OpLev channels. They were originally located in the top level of h1susim.mdl and sent via IPC to PR3, but we moved them over to the h1suspr3.mdl model. This means that the outgoing IPC connection from h1susim going into h1suspr3 has been removed(h1susim before, h1susim after), and the PR3 oplev channels have been directly connected from ADC1(h1suspr3 before, h1suspr3 after).

Both models were compiled successfully but have not yet been installed.

Model files can be found in /opt/rtcds/userapps/release/sus/h1/models/, and changes to h1susim.mdl and h1suspr3.mdl have been committed to the svn as revision 30905.

AOS, CDS

Images attached to this report

LHO VE - Wed CP1 Fill

david.barker@ligo.org — Wed, 05 Mar 2025 11:39:35 -0800

Author: david.barker@ligo.org

Report ID: 83193

Wed Mar 05 10:11:50 2025 INFO: Fill completed in 11min 46secs

Gerardo confirmed a good fill curbside.

Images attached to this report

H1 ISC - Comment to Dark Offsets Updated

thomas.shaffer@ligo.org — Wed, 05 Mar 2025 11:22:38 -0800

Author: thomas.shaffer@ligo.org

Report ID: 83192

More SDF shots.

Images attached to this report

H1 ISC - Dark Offsets Updated

ryan.short@ligo.org — Wed, 05 Mar 2025 11:09:46 -0800

Author: ryan.short@ligo.org

Report ID: 83191

After a lockloss while attempting to relock this morning, I ran the dark offset script (/opt/rtcds/userapps/release/isc/h1/scripts/dark_offsets/dark_offsets_exe.py) after taking the IMC offline and shuttering ALS with the hope of fixing some of our ASC troubles.

I've attached a text file of the script output showing what all was changed, as well as screenshots of these being accepted in SDF safe.snap tables (TJ has more that he will add in a comment). These will likely need further accepting once we eventually reach NLN.

OpsInfo

Images attached to this report

Non-image files attached to this report

new_dark_offsets_03052025.txt

H1 PEM - Dust monitor trend monthly - FAMIS

ryan.crouch@ligo.org — Wed, 05 Mar 2025 09:26:44 -0800

Author: ryan.crouch@ligo.org

Report ID: 83189

Closes FAMIS 37250, the first of this new task. All of the dust monitors look to be working as expected and are seeing counts, aside from LAB2 which is known.

Images attached to this report

H1 General - Comment to OPS Wednesday DAY shift start

ryan.crouch@ligo.org — Wed, 05 Mar 2025 08:50:28 -0800

Author: ryan.crouch@ligo.org

Report ID: 83188

In some more camera fallout we found ISC_LOCK sets CAM18s exposure during PREP and CLOSE_BD (H1:VID-CAM18_EXP) which does not exist anymore, ISC_LOCK turned "blood red" for a few seconds complaining it couldn't connect then just it moved on and went back to normal?

Those 2 lines have since been edited and loaded.

GRD

H1 General - Comment to OPS Wednesday DAY shift start

ryan.crouch@ligo.org — Wed, 05 Mar 2025 08:22:30 -0800

Author: ryan.crouch@ligo.org

Report ID: 83187

H1 Glitches (Omicron) plot isn't updating

CDS

H1 General - OPS Wednesday DAY shift start

ryan.crouch@ligo.org — Wed, 05 Mar 2025 07:32:44 -0800

Author: ryan.crouch@ligo.org

Report ID: 83185

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

In observing since 15:22 UTC
- 2 short locks overnight
Wind and microseism are relatively low
16:34 UTC lockloss

H1 CDS - Comment to CDS Maintenance Summary: Tuesday 4th March 2025

david.barker@ligo.org — Wed, 05 Mar 2025 07:31:08 -0800

Author: david.barker@ligo.org

Report ID: 83186

LVEA and CER CDS Wifi Problems

FRS33406

Erik reconfigured the LVEA and CER WAPs from DHCP to static IP addresses. This resolved the immediate connection problem between wap-control and these units. Details can be found in the FRS ticket.

H1 General - SDFs to get to observing

sheila.dwyer@ligo.org — Tue, 04 Mar 2025 22:24:42 -0800

Author: sheila.dwyer@ligo.org

Report ID: 83184

Timing things that I don't understand but accepted, ALS WFS turned off, which I reverted in the hopes that this will work again in the next lock, ESD limiters as expected from 83158

Images attached to this report

LHO General - Comment to OPS Eve Shift Summary

sheila.dwyer@ligo.org — Tue, 04 Mar 2025 22:18:27 -0800

Author: sheila.dwyer@ligo.org

Report ID: 83183

Ibrahim increased H1:LSC-POPAIR_B_RF18_I_GAIN which is normally 2 during lock acquisition to 4 to get DRMI to lock, as he says. Normally the guardian then adjusts this gain to 3.991 when the 9 MHz modulation depth is reduced, then it gets reset to 2 in PREP_FOR_LOCKING. We commented out the lines in prep for locking that do this reset, but then I remembered that this is also in SDF revert, so I accepted 3.991 in the safe.snap file. And I uncommented the change to ISC_LOCK so that we won't have two places to remember to undo this.

Edited to add one more comment: We also turned off SRC2 P in DRMI ASC to stop a large oscillation. This isn't in the guardian.

Images attached to this report

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Tue, 04 Mar 2025 22:02:23 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 83182

TITLE: 03/05 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

IFO is in PREVENTATIVE_MAINTENANCE and LOCKING at DARM_TO_DC_READOUT

We have been unable to lock since conclusion of maintenance. The issue concerns PRMI's ASC not improvign POP counts sufficiently for DRMI to maintain lock.

While wind and microseism was the early culprit and assumption of locking issues, both have calmed down and revealed PRMI_ASC as the problem. Since ~20:30 PT, we have been in a cycle of PRMI and DRMI where PRMI is able to lock and stay locked to move to DRMI, but then DRMI is unable to lock. When we stay at PRMI_ASC, it can stay locked indefinitely.

Elenna, Sheila and I troubleshot this quite exentsively, by moving all relevant suspensions (PRM, BS, PR2). We also ran initial alignment now a total of 3 times without needing to change anything. At the end, Sheila suggested increasing the gain of of LSC_POPAIR_B_RF18 from G = 2 to G = 4. This allowed DRMI triggering to activate a tad earlier than it usually would, which (excitingly) locked DRMI.

Relevant alog: alog 83178. The gain change fix has been commented out. It is on line 564 and 565 on ISC_LOCK.py. The plan is that it will be reverted tomorrow given a solution to the underlying PRMI_ASC not improving.

Other:

DOF2 P and Y had to be temporarily turned off because they were fighting the ALSY transmission signal, which would cause FIND_IR locklosses (due to slow signal degradation). Turning it off allowed me to get further.
Wind speeds and microseism are down.

LOG:

None.

H1 ISC - Comment to OPS Midshift Update: Locking Troubles

elenna.capote@ligo.org — Tue, 04 Mar 2025 20:38:03 -0800

Author: elenna.capote@ligo.org

Report ID: 83181

The alignment on the AS AIR camera looks very poor in PRMI, and the buildups are lower than I expect (around 60 on the fast channel). We tried moving the beamsplitter, PRM, and PR2 and nothing seems to improve the buildup or the shape of the beam on the camera. I even tried stepping PR3 in all directions (I reverted my steps!) and nothing got better. DRMI locking isn't working, we see plently of flashes but no triggers. My guess is the alignment is still poor that we are not meeting the threshhold. However, we've done multiple initial alignments and even adjusted the alignment by hand with no luck. I am stumped about what the problem could be.

H1 ISC - Comment to OPS Midshift Update: Locking Troubles

ibrahim.abouelfettouh@ligo.org — Tue, 04 Mar 2025 20:08:16 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 83180

ALSY instability was caused by DOF2 P and Y going in opposite directions slowly causing ALS to lose lock at FIND_IR. I turned them off at this point and was able to get past this state after 7 locklosses.

In other news, Elenna and I do not think this issue is environmental because we were able to hold PRMI lock for over 10 minutes but were not able to improve its counts past 60 with movements in all the relevant suspensions. DRMI is thus still failing to lock (and this is fresh after another initial alignment). The current hypothesis is that something is wrong with ASC.

H1 ISC - Comment to OPS Midshift Update: Locking Troubles

ibrahim.abouelfettouh@ligo.org — Tue, 04 Mar 2025 19:31:13 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 83179

Now unable to make it past FIND_IR since fully auto initial aligment ~7PM. Wind is just picking up and is now over 30mph again. The last 6 locklosses have been from FIND_IR, caused by ALSY slowly becoming unstably and losing lock. I will go into IDLE and attempt locking if wind improves, which forecast says is unlikely before shift end.

H1 ISC - OPS Midshift Update: Locking Troubles

ibrahim.abouelfettouh@ligo.org — Tue, 04 Mar 2025 18:53:47 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 83178

IFO is still LOCKING and not able to since MAINTENANCE ended.

At first, this was thought to be a combination of the microseism and wind speeds, but both have since gone down to since lockable states. We can also easily lock ALS and have gone through initial alignment fully automatically twice. What happens is that the PRMI_ASC alignment holds but is not high enough in counts, hovering around 50 and not improving. Then, when we attempt to lock DRMI, we lose lock every time. Elenna and I are troubleshooting the issue now. Certainly doesn't seem like the environment.

ISC

H1 CDS - PCALY_STAT Guardian node creation.

anthony.sanchez@ligo.org — Tue, 04 Mar 2025 17:37:52 -0800

Author: anthony.sanchez@ligo.org

Report ID: 83164

PCALY_STAT Guardian node was created, which is a very basic guardian node that just checks a handful of channels to be with a handfull of histoical threshholds to determine if the PCAL subsystem is functioning.
This is just a copy of PCALX_STAT which has been running well for a number of months.

TJ has also put PCALY_STAT on the GUARD_OVERVIEW screen for easy access.

Thank you Dave for fitting us into this last DAQ restart today.

CAL

Images attached to this report

H1 CDS - CDS Maintenance Summary: Tuesday 4th March 2025

david.barker@ligo.org — Tue, 04 Mar 2025 17:27:35 -0800

Author: david.barker@ligo.org

Report ID: 83176

WP12362 Upgrade h1susex to latest 5.30 RCG

To address a difference in the RCG5.3.0 running on h1omc0 and h1susex, all models on h1susex were built against the latest 5.3.0. h1susex was rebooted as part of this upgrade. No DAQ restart was needed.

WP12358 Move cameras to new AMD servers

All the cameras from h1digivideo0 and h1digivideo1 were added to the four already running on h1digivideo4. This brings the number of cameras on this server to 15. All cameras are running at 25 frames-per-second limits.

The cameras on h1digivideo3 (deb11) were moved to a new server, h1digivideo5.

The h1digivideo[0,1,3] machines were powered down. No changes were made to h1digivideo2.

A new camera MEDM was built showing the new layout.

See Jonathan's alog for details.

WP12356 Install independent 1PPS generator at EY

An independed 1PPS function generation was installed at EY and connected to the 5th port of the comparitor, next to the CNS-II clock. This will be used to invistigate when the CNS-II occassionally has a 500nS offset applied.

WP12355 Picket Fence Upgrade

Erik upgraded the picket fence system.

WP12332 BSC Temperature Monitors

Fil worked on the BSC1 (ITMY) temp monitor, it is now reading the correct temp.

DAQ Restart.

A EDC DAQ restart was needed for three changes:

H1EPICS_DIGVIDEO.ini: reflect the move of cameras from old to new software.

H1EPICS_CDSMON.ini: remove h1digivideo3's epics load mon channels, add those for h1digivideo5

H1EPICS_GRD.ini: add channels for new Guardian node PCALY_STAT

The DAQ restart followed our new EDC procedure, whereby the trend-writers were stopped before the edc was restarted with its new configuration.

No major surprises except FW1 sponteneously restarted itself after running for about seven minutes.

Images attached to this report

H1 CDS - Comment to CDS Maintenance Summary: Tuesday 4th March 2025

david.barker@ligo.org — Tue, 04 Mar 2025 17:24:10 -0800

Author: david.barker@ligo.org

Report ID: 83177

Tue04Mar2025
LOC TIME HOSTNAME MODEL/REBOOT
08:00:38 h1susex h1iopsusex <<< First we restarted h1susex models with new RCG
08:00:52 h1susex h1susetmx
08:01:06 h1susex h1sustmsx
08:01:20 h1susex h1susetmxpi
08:08:12 h1susex h1iopsusex <<< Then we rebooted h1susex
08:08:25 h1susex h1susetmx
08:08:38 h1susex h1sustmsx
08:08:51 h1susex h1susetmxpi

13:46:16 h1susauxb123 h1edc[DAQ] <<< New video, load_mon and grd ini loaded
13:47:04 h1daqdc0 [DAQ] <<<0leg start
13:47:15 h1daqfw0 [DAQ]
13:47:15 h1daqtw0 [DAQ]
13:47:19 h1daqnds0 [DAQ]
13:47:24 h1daqgds0 [DAQ]
13:48:08 h1daqgds0 [DAQ] <<< gds0 needed a second restart
13:51:17 h1daqdc1 [DAQ] <<< 1leg start
13:51:26 h1daqfw1 [DAQ]
13:51:27 h1daqtw1 [DAQ]
13:51:28 h1daqnds1 [DAQ]
13:51:35 h1daqgds1 [DAQ]

14:00:36 h1daqfw1 [DAQ] <<< spontaneous restart of fw1

H1 CDS - WP12358 digital video server work, installed h1digivideo5 and h1digivideo6, migrated cameras off of old servers

jonathan.hanks@ligo.org — Tue, 04 Mar 2025 16:44:58 -0800

Author: jonathan.hanks@ligo.org

Report ID: 83175

Jonathan, Erik, Dave, Patrick As part of WP12358 we installed two new digivideo server h1digivideo5 and h1digivideo6. These were racked in the aux rack. To make room we removed two old conlog servers. Both servers were installed with Debian 12 and are under puppet configuration and running the 0.1.16 version of the pylon-camera-server software. They are connected to the new video1 switch. We migrated cameras off of h1digivideo0, h1digivideo1, and h1digivideo3. These machines have been powered off. h1digivideo4 is running the following cameras H1-VID-CAM-ALS-X H1-VID-CAM-ALS-Y H1-VID-CAM-FC-REFL H1-VID-CAM-MC-REFL H1-VID-CAM-MC-TRANS H1-VID-CAM-MC1 H1-VID-CAM-MC2 H1-VID-CAM-MC3 H1-VID-CAM-PR2 H1-VID-CAM-PR3 H1-VID-CAM-PRM H1-VID-CAM-ISCT6-AS-AIR H1-VID-CAM-SRM H1-VID-CAM-SQZT7-OPO-GR-TRANS H1-VID-CAM-SQZT7-IR-TRANS h1digivideo5 is running the following cameras H1-VID-CAM-ETMX H1-VID-CAM-ETMY H1-VID-CAM-FC1 H1-VID-CAM-FC2 H1-VID-CAM-FCES-GREEN H1-VID-CAM-FCES-IR-TRANS-B H1-VID-CAM-SHG-TRANS H1-VID-CAM15 We did a daqd restart to remove monitoring information regarding h1digivideo3 and to reflect changes in EPICS variables due to migrating from older versions of the camera software. We still need to migrate cameras off of h1digivideo2. That will likely happen next Tuesday.

H1 AOS - TCS CO2 Cooling Pipe Inspection - Biannual

thomas.shaffer@ligo.org — Tue, 04 Mar 2025 16:31:44 -0800

Author: thomas.shaffer@ligo.org

Report ID: 83162

FAMIS27777

I didn't find any major issues with the pipes themselves, no leaks were found and the supports that were added last year (alog76528) seem to be helping. The flex joints still seem good and the plastic wrap around it also look OK. The same issues reported in the last inspection are still present (alog80015): cuts/scratches in pipes and a blocked outlet under HAM4 that also stressed the pipes there a bit from people pushing them out of the way to use the outlet. After getting Richard's approval, I moved the outlet up on its support beam and on a conduit support further down to clear the TCS pipes and relieved some of the stress on the pipes there - Pic1 Pic2

Images attached to this report

H1 General - OPS Tuesday day shift summary

ryan.crouch@ligo.org — Tue, 04 Mar 2025 16:30:18 -0800

Author: ryan.crouch@ligo.org

Report ID: 83169

TITLE: 03/04 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: DRMI/PRMI has been giving us issues in the maintenance recovery, PRMI_ASC doesn't seem to actually improve the signal or camera. The wind has been increasing over the past 4 hours and the 2ndary microseism has been decreasing. We've run 1 full IA and a 2nd with only SRC. Some yellow PSL laser room alarms, probably from the wind.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
15:37	CDS	Erik	Office	N	SUS EX restart for RCG upgrade	16:17
15:56	EE	Ken	EndY	N	Mech room compressor work	21:40
16:04	FAC	Tyler & Chris	Optics lab	N	Move stuff	17:42
16:10	FAC	Tyler	Old bake lab	N	Removing old elevator, NOISY AND DIRTY	17:42
16:11	LSC	Daniel	LVEA	N	REFL measurements	18:41
16:11	FAC	Kim & Nellie	EndY	N	Tech clean	17:11
16:12	CDS	Jonathan	Office	N	Digivideo work	16:39
16:17	CDS	Erik	CER	N	Working on broken WAPs (LVEA)	19:45
16:22	EE	Fil	LVEA	N	LY vac rack ups	16:38
16:24	IAS	Jason, RyanC	LVEA	N	FARO surveying	20:15
16:26	VAC	Jordan, Travis	EY MER	N	Mech room, compressor	21:54
16:39	SEI	Fil	CER	N	SEI rack electronics	19:17
16:50	AOS	Richard	LVEA	N	Checks	17:07
16:53	FAC	Mitchell, Jim, Betsy	LVEA	N	Checks around HAM1	19:44
16:58	CAL	Francisco	EX	YES	PCal measurement	18:12
17:03	VAC	Janos, Gerardo	EX MER	N	Compressor testing	21:54
17:14	TCS	TJ	MER/LVEA	N	Chiller piping checks	18:03
17:24	FAC	Chris (+Pest Control)	LVEA, Arms, Ends	YES (EX)	FAMIS tasks, Pest control	18:30
18:06	FAC	Tyler	MX, MY	N	3IFO checks	19:06
18:17	TCS	TJ	LVEA	N	Adjusting TCS lines	18:32
18:20	FAC	Nellie	LVEA	N	Technical cleaning	19:34
18:25	CAL	Jeff	CER/LVEA	N	Pictures at SUS racks	19:43
18:31	FAC	Chris	MER	n	Tumbleweed clearing	21:23
19:14	FAC	Tyler	All Bldgs	N	Measuring technical slabs	21:14
19:15	CDS	Erik	EY	N	Plugging in timing system	20:10
19:15	FAC	Richard	EY	N	Checking in w/ Ken	19:48
19:17	EE	Fil	LVEA	N	Table electronics documentation	20:13
19:53	AOS	Betsy, Mitchell	LVEA	N	HAM1 Checks	20:13
21:20	ALS	TJ, Sheila	LVEA, ISCT1	LOCAL	Table adjustment	22:20
21:27	OPS	RyanC	LVEA	N	Sweep	21:50
21:39	ISC	Siva, Mayank	Opt Lab	N	ISS array	Ongoing
21:53	VAC	Gerardo	Optics lab/ VAC prep	N	Find a viewport	21:59
22:02	ISC	Keita	Optics lab	N	Join ISS work	Ongoing
23:22	VAC	Janos	EndX	N	Quick measurement	23:36

Some of the maintance items completed today includes:

Tumbleweed clearing with big green
EndX compressor test and EndY compressor swap
PCAL endX station measurement
LVEA WAP work alog83159
EX RCG upgrade alog83157
EndY independent timing source alog83161
Picket Fence updated and restarted alog83171
REFL/POP cable delay measurement alog83155
TCS line adjustment
ISCT1 table alignment alog83172
LY vac rack UPS replacement alog83151
HAM1 SEI rack electronics installation alog83163
EX chiller maintanance alog83154
Digivideo upgrades
- The new camera software has lost us the ability to take screenshots of the cameras in one of the ways we used to, using the channels H1:VID-CAM##_FILE.

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Tue, 04 Mar 2025 16:07:24 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 83174

TITLE: 03/04 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: EARTHQUAKE
    Wind: 28mph Gusts, 16mph 3min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.33 μm/s
QUICK SUMMARY:

IFO is LOCKING and having issues recovering from maintenance with the following being reported from DAY Ops (Ryan C):

PRMI/DRMI Flashes are low
Wind is causing ALS to drop out
IFO was in EQ mode following Iceland EQ (that I don't think would have usually caused EQ mode). TJ just manualled to calm since the EQ was long past and low mag.
Comissioners are troubleshooting ASC issues that involve lowering thresholds for DRMI lock.

H1 ISC - ALS COMM and DIFF path tweaked on table

thomas.shaffer@ligo.org — Tue, 04 Mar 2025 15:57:58 -0800

Author: thomas.shaffer@ligo.org

Report ID: 83172

Sheila and I took a bit of time at the end of maintenance to touch up the COMM and DIFF paths on ISCT1.

We first removed one of the shims that was under the DCPD circled in light blue. This was shimmed up a few weeks ago (alog82783) to get more light on the pd without realigning the entire path since we had more PR suspension moves to do. Two shims were added at the time, and we were only able to remove the larger of the two, but it placed the beam close to center in height. The second attachment shows before the shim was removed.

The COMM path looked clearly not well coaligned viewed from before the last lens in the path. Sheila walked the two optics circled in pink to bring them closer together and ended up with a positive beatnote. At first we could increase the beatnote but visually the two beams seemed to get worse, but she ended up getting to a spot that worked for both.

The DIFF beatnote was already pretty good, but we touched it up a bit more using the optics circled in red. While here, we also added a beam dump behind the lower of the two circled optics. We ended up with a DIFF beatnote around -8.

OpsInfo

Images attached to this report

H1 SUS - Damping threshold for PI31 lowered

oli.patane@ligo.org — Tue, 04 Mar 2025 15:40:50 -0800

Author: oli.patane@ligo.org

Report ID: 83173

Since PI31 has been wanting to sit higher (83142) and has been regularly ringing up following the EY ring heater change (82962), I've lowered the threshold for turning the damping on on PI31. It previously would turn on once PI31 RMS went above 4, but I've lowered it to 3. This means starting about 4 hours into our locks, the damping on EY will be on almost continuously, but that's okay. This will hopefully stop the sudden ringups from happening every 30-45 minutes.

OpsInfo

H1 CDS - Moving PR3 Optical Lever Signal Chain to make way for PM1

jeffrey.kissel@ligo.org — Tue, 04 Mar 2025 15:30:03 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 83168

J. Kissel, D. Sigg ECR E1700228 WP 12370 The last piece of today's puzzle -- after understanding that PR3's optical lever (oplev) whitening chassis is NOT in newly labeled SUS-R1 (see LHO:83156), but in SUS-R2 (see LHO:83165, and when I first realized this in LHO:63849) -- I can now comfortably identify the physical cables that Daniel "moved" in future SUS HAM 1 2 wiring diagram to make room for PM1. In short: We need to move the D9F end of cable "H1:OP LEV_PR3_AA" or "H1:SUS-HAM2_88" - from SUS-C4 U11 AA chassis spigot "IN25-28," which is CH24-27 via ADC0 in/on the sush2b IO chassis / front-end computer (and shipped over to PR3 via IPC in the top level of h1susim.mdl) - to SUS-C4 U32 AA chassis spigot "IN29-31," which shall be CH28-31 via ADC1 in/on the sush2a IO chassis / front-end computer (and be added to the top level of h1suspr3.mdl as a direct read of ADC1) and then make model changes accordingly. Pictured are - Front view of SUS-R2 U12 ("U31" in iLIGO rack terms, as its labeled) oplev whitening chassis showing that this is indeed the PR3 optical lever, as stated in LHO:63849. - Back view of SUS-R2 U12 oplev whitening chassis showing the field end of the SUS-R2 to SUS-C4 cable, labeled "H1:OP LEV_PR3_AA" or "H1:SUS-HAM2_88" - SUS-C4 U11 AA chassis where the remote end of the cable is connected to "IN25-28" - SUS-C4 U32 AA chassis were we want to use "IN29-32." Why was this so hard? The history of drawing optical levers and SUS in HAM1 in wiring diagrams is sordid. (1) The PR3 optical lever was originally drawn in the SUS HAM 2 wiring diagram in the aLIGO era. See page 26 of D0902810-v7. However, in these aLIGO era drawings, field racks weren't defined so each site put their optical lever whitening chassis where-ever, and connected them up in a way that made sense to them. Complicating the allocation were the never-used, now-decommissioned HAM-ISI optical levers, and as drawn in D0902810-v7, the HAM2 ISI optical lever was to pair with this PR3 optical lever. (2) In the effort to, among other things, define field racks for the first time, Luis and I circa early 2023 (see 5097), we cleaned up the PR3 optical lever chain, arguably in correctly, and included PR3 and SR3 in the SUS HAM 3 4 wiring diagram D1000599-v8, see pages 5 and 7 (PR3 ADC) or 6 (SR3), respectively. (3) The "missing" PR3 optical lever continued when we, as a result of the plan to integrate SUS in O5 (G2301306), created a new BSC 2 HAM 3 4 wiring diagram, D2300383, and in doing so we left out the PR3 optical lever chain. (See discussion below about the SR3 optical lever chain). In parallel, (4) as the HAM 2 wiring diagram, D0902810, became a very quick-and-dirty D0902810-v8 circa 2017 in order to find space for the then O3 SQZ system in HAM6 -- see, e.g. LHO:38883, or other alogs where the "h1sushtts" model changes are mentioned. (5) Luis and I then, circa 2023 as the last field racks to draw, converted the drawing to the "modern" wiring diagram with D0902810-v9. Since it included the RMs, but no change for O5, we renamed it the HAM 1 2 wiring diagram. Again, because we'd put PR3 optical lever in D1000599-v8, nothing was shown in D0902810-v9. So, when Daniel comes along, perusing for spare channels, he implicitly makes the recommendation to move the PR3's AA / ADC input from sush2b to sush2a, looking to make room for the incoming PM1, and further JM1 - 3. So now it appears back again in D0902810-10, on page 10, going into the U32 AA Chassis "IN29-32" spigot! This is "necessary" and "natural," because after this change, - everything on sush2a is related to the triples in HAM2 - PR3 optical lever can be directed read out from ADC1 of sush2a, rather than having to receive it via IPC from another IO chassis (sush2b) - sush2b drives only single suspensions, even though they're split between HAM2 (the IMs) and HAM3 (RMs, PM1, and the future JMs). - that leaves us open and capable, eventually, if we mass produce LIGO 32-channel DACs and we can claw back lots of 8 channel card slots, perhaps sush2a and sush2b can naturally evolve to simply sush1 and sush2, much like sush56 is to evolve to sush5 and sush6. So -- a pretty dang simple change, but it was just tough to follow with the wiring diagrams alone. FUTURE DRAWING ACTIONS: (I) Need to update HAM 1 2 wiring D0902810-10 to include the a page for the "sensor and field" wiring for PR3 that's currently in D1000599-v8 page 5, so that the ADC input (on current page 10) doesn't appear out of "thin air" in D0902810-10. (II) (For now, we have to leave SR3 on sush34, since there're no spare ADC spigots in the sush56 ADCs' AA chassis, see page 6 of D1002740-v10) (III) When we split the sush56 computer into two, sush5 and sush6, for O5, in the sush5 drawing, currently D2300380-v3, we should include the a page for the "sensor and field" wiring for SR3 that's currently in D1000599-v8 page 5. In doing do, we can move the AA chassis end of SUS_OPLEV_SR3_AA :: from SUS-C2 sush34 HAM 34 IO chassis's AA U33 of SUS-C1 "IN17-20" spigot :: to the SUS-C8 sush5 HAM 5 IO chassis's AA U33 of SUS-C7 "IN17-20" spigot that's currently spare. There there'll be some semblance of symmetry and "final home" for SR3 optical lever. (IV) Need to update D1000599-v8 to remove all evidence of PR3 and SR3. PR3 will "already" be represented in the HAM 1 2 wiring diagram D0902810, and SR3 will be represented in the HAM 5 wiring diagram D2300380, and the HAM 3 4 wiring diagram D1000599 will be deprecated anyways in favor of the BSC2 HAM 3 4 wiring diagram, D2300383, which "correctly" only includes the Beam Splitter optical lever. BUT FOR NEXT WEEK: All we need to do is the above summarized single cable move -- and make the corresponding changes to the h1sushtts and h1suspr3 front-end models.SUS

Images attached to this report

H1 CDS - Picket Fence updated

erik.vonreis@ligo.org — Tue, 04 Mar 2025 15:00:58 -0800

Author: erik.vonreis@ligo.org

Report ID: 83171

Picket Fence wall display was updated. The update changes two of the source station channel definitions:

"US_MSO:00BHZ" changed to "US_MSO:00HHZ"

And

"IU_TEIG:00HHZ" changed to "IU_TEIG:00BHZ" (only used at LLO)

SEI

LHO FMCS - Comment to End X Chiller 1 failure

eric.otterman@ligo.org — Tue, 04 Mar 2025 14:55:08 -0800

Author: eric.otterman@ligo.org

Report ID: 83170

This has been repaired and the chiller is now running.

H1 CDS - Comment to Status of ISI HAM2 & HAM3 Optical Lever Cables and Whitening Chassis; Re-use Cables for PM1?

jeffrey.kissel@ligo.org — Tue, 04 Mar 2025 14:07:06 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 83167

Some supporting pictures from the above conversation. - 2025-03-04_SUSR1_ISIHAMOplevWhitening_FrontView_U9.jpg Front view of S1101555 Oplev Whitening Chassis in SUS-R1 U9(ish). - Zoom in on HAM3 and HAM2 cable connections at the front of the chassis in SUS-R1. - Zoom in on HAM3 and HAM2 cable connections at the back of the chassis in SUS-R1. - The disconnected end of the HAM3 cable dangling near SUS-C1 in the CER - The disconnected end of the HAM2 cable dangling near SUS-C4 in the CER. SEI, SUS

Images attached to this report

H1 CDS - Status of ISI HAM2 & HAM3 Optical Lever Cables and Whitening Chassis; Re-use Cables for PM1?

jeffrey.kissel@ligo.org — Tue, 04 Mar 2025 13:56:21 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 83165

J. Kissel, F. Clara ECR E1700123 More yak shaving, but at the end of today's kLog series you'll understand how to execute Daniel's implicit plan in D0902810-v10 for moving cables around to make room for an incoming tip-tilt, aka HTTS, to eventually be named "PM1," i.e. Pop wfs steering Mirror 1. In this kLog: There're 2x cables DB9 available for the cable run from SUS-R1 to SUS-C4 to cover the needs of that run for PM1, we may not need to buy new cables. In 2022, I inventoried all optical lever whitening chasses in LHO:63844. In that aLOG I confirmed that the never-existed / now-officially decommissioned HAM2 and HAM3 ISI optical levers were disconnected from their respective optical lever piers. Today, while poking around the racks, I identified that - The last version of a wiring diagram that had any record of these HAM ISI optical levers was :: HAM3 D1000599-v7 (it's now at -v8, and in O5 D1000599 will be superceded by D2300383). :: HAM2 D0902810-v7 (it's not at -v10). - These diagrams disagree with how H1 started cable up the ISI optical levers, which have both the HAM3 and HAM2 ISI optical levers routed to the Oplev Whitening Chassis in U9 (ish) of SUS-R1. :: According to the above -v7 drawings, the intent was to have the HAM3 ISI optical lever readout by the Oplev whitening chassis in SUS-R2 over by HAM3. - The wiring diagrams specified the 2x long DB9 cable run between the whitening chassis (in the field rack) and the AA chassis (in the CER) to be called :: (IFO):OPLEV-HAM2_AA :: (IFO):OPLEV-HAM3_AA - As H1 labeled them, they're also (respectively) :: H1:SUS_HAM2_78 :: H1:SUS_HAM3_161 - These HAM2 and HAM3 Whitening-to-AA cables *are pulled* from SUS-R1 to SUS-C4 and SUS-C1, respectively, but they're dangling unconnected to any AA. In short -- the Oplev whitening chassis S1101555 in SUS-R1 U9 *looks* full populated and in use, but every "other end" of the cables plugged into it are disconnected. This chassis, S1101555 in SUS-R1 U9 can *absolutely* be powered down and removed from the rack, pushed to our spares supply. So, interestingly to our mission, there's two D9M (at SUS-R1 end) to D9F (at CER end) available to be repurposed. Coincidentally, according to Daniel's design in D0902810-v10, PM1 needs two D9 cables... sort of. - SENSOR CABLE: The OSEM PD output of the SUS-R1 U38 Dual, 8ch satamp, D1002818 is mapped from the "PD Outputs to AA" D9F directly to the SUS-C4 U11 "IN25-28" D0902783 8x D9M input AA chassis. :: one of the above ISI oplev cables will meet this need perfectly. - DRIVE CABLE: The D1100687-v1 or v2 HAM-A coil driver, which uses the driver board D080276, sends out the four coil drive outputs on a D15F on J4. But, the 4x differential channels can absolutely fit on a DB9, as is evident by the Dual, 8ch satamp, D1002818 which accepts the Coil Drive Inputs at J1 as a D9M. In A+ circa 2021-2022, when we started regularly using this HAM-A coil driver + 8ch Dual Satamp combo, Luis drew up the cable solution to this problem, a custom D15M to D9F cable, D2200034. :: So, we "just" need to make a short version of this oft-used custom D15 to D9 cable, D2200034, and then we can use the other cable. That being said -- Daniel says he's "already ordered the cables." Ah HA! But -- I worry that the wrong cable has been ordered -- because in D0902810-v10 page 8, Daniel did the sensible thing and copied and pasted the RM1 and RM2 wiring chains from D0902810-v9 page 8 to create the PM1, and JM1-3 chains on -v10 page 9. But alas, there was a typo on the label of this DRIVE CABLE, citing that it should be D2100747, a D15M to D15F cable. It should be the D2200034 D15M to D9F mentioned above. So -- if we did end up ordering the wrong cable, here's the solution: With only one short adapter made, we can reuse these D9M to D9F cables for the OSEM PD and Coil Drive cables of PM1, if we want or need. Or anything else future that needs a long from from SUS-R1 to the SUS racks in the CER. (Future readers beware -- the plan may be to fix the typo D2100747 > D2200034 cable label typo in the D0902810-v10 drawing by keeping the same version number in the DCC but sneakily replacing the files -- so if you're reading this in 2026, the comments about the typos in -v10 may not be there...)SEI, SUS

H1 General - LVEA swept

ryan.crouch@ligo.org — Tue, 04 Mar 2025 13:54:14 -0800

Author: ryan.crouch@ligo.org

Report ID: 83166

I swept the LVEA following the conclusion of most maintenance activities, the last group in will double check their area and get the lights on their way out. Nothing really of note.

H1 SEI - H1 HAM1 SEI Electronics

filiberto.clara@ligo.org — Tue, 04 Mar 2025 13:09:26 -0800

Author: filiberto.clara@ligo.org

Report ID: 83163

WP 12366

Started installation of the required electronics (ISI Interface/AA/AA/ISI Coil Drivers/Binary Chassis) for the HAM1 ISI upgrade. IO chassis will need to be updated.

All existing electronics need to be powered down to move power cables to lower ports on the ±18V DC power strip. New electronics are installed in the upper U slots of the rack and standard power cables are not long enough. Work will be coordinated with the IO chassis upgrade.

Waiting on the in-rack and field cables to be delivered onsite.

CDS

H1 SUS - H1 SUS-R1 U-Heights Labeled

jeffrey.kissel@ligo.org — Tue, 04 Mar 2025 12:35:10 -0800

Author: jeffrey.kissel@ligo.org

Report ID: 83156

J. Kissel, F. Clara I'm yak shaving, but at the end of today's kLog series you'll understand how to execute Daniel's implicit plan in D0902810-v10 for moving cables around to make room for an incoming tip-tilt, aka HTTS, to eventually be named "PM1," i.e. Pop wfs steering Mirror 1. In this kLog: I've labeled the U heights of SUS-R1. SUS-R1 is an old iLIGO rack that was never labelled, but repurposed in aLIGO to house (mostly) HAM2 SUS satellite amps, i.e. the triples MC1, MC3, PRM, PR3, and the singles IM1, IM2, IM3, and IM4. (It also houses a CDS network switch, a PEM test panel, and a deprecated / never used HAM2 and HAM3 ISI optical lever whitening chassis.) In aLIGO, all U-slots in U42-ish height racks were "converted" to being labeled by industry standard with the top being U42, and the bottom being U1. These iLIGO racks don't have enough slots to populate all 42 U-height slots, so the compromise is to *draw* 42 U-heights, but "never use" U1. The last bit of the story: the drawing that governs the content of these racks is D0902810. However, when the aLIGO field racks were populated with stuff, (a) The sites made a custom non-standard 3.25-ish U-height "craddle" to hold the non-rack-mountable UK satamps. (b) that drawing did not cover the layout of the field racks, so each sites kinda "did what they wanted." The issue (b) was been rectified by 2023 as Louis Sanchez and I brought D0902810 up to -v9, see IIET:5097. So, that's why the U-height labels don't awesomely line up with the chassis that are installed. See - Screenshot of depiction of the rack in page 13 D0902810-v10, with the rack labeled "top down" from U42 at the top and U41 at the bottom (even though the H1 "as-built" version of this design doesn't have a U1). - single "before" picture - The rest of the attachment: pictures of the labels.CDS

Images attached to this report

H1 CDS - Rubidium clock installed at EY

erik.vonreis@ligo.org — Tue, 04 Mar 2025 12:22:25 -0800

Author: erik.vonreis@ligo.org

Report ID: 83161

In order to help narrow the cause of on-going but rare timing comparator discrepency with the CNS clock at EY, I installed a rubidium clock on port 4 of the same comparitor.

The clock is on the floor under the computer rack. A BNC cable runs from the clock under the roll up door, and over the racks in the CER to the comparator.

Port 7 of the comparator didn't work.

H1 CDS - LVEA WAP working

erik.vonreis@ligo.org — Tue, 04 Mar 2025 12:18:43 -0800

Author: erik.vonreis@ligo.org

Report ID: 83159

LVEA WAP is now working. When either the LVEA WAP or the CER WAP is toggled on or off, the toggled WAP must be pinged from the 'wap-control' server before it will reconnect and show up on MEDMs.

Other WAPs are working normally. This seems to be a networking issue and not a problem with the WAPs themselves.

H1 ISC - ETMX glitch limiters turned back on in ISC_LOCK

jim.warner@ligo.org — Tue, 04 Mar 2025 12:16:09 -0800

Author: jim.warner@ligo.org

Report ID: 83158

I talked to Sheila this morning about turning on the ETMX glitch limiters from this alog, so I've edited ISC_LOCK to turn this back on. This will cause SDF diffs on ETMX when we get to NLN, but otherwise shouldn't interfere with locking. If it's necessary to turn this off, just comment out lines 5462-5464:

log('turning on esd limits to reduce ETMX glitches')
for limits in ['UL','UR','LL','LR']:
ezca.get_LIGOFilter('SUS-ETMX_L3_ESD_%s'%limits).switch_on('LIMIT')

Still unclear if this is helping, but we turned it off ~Feb 12 after running it for almost 2 weeks.

H1 CDS - h1susex models updated

erik.vonreis@ligo.org — Tue, 04 Mar 2025 12:16:07 -0800

Author: erik.vonreis@ligo.org

Report ID: 83157

[Erik v.R., Dave]

h1susex models were re-built with the same version of the RCG as h1omc models.

git tag is 'H1_rollback_2025_01_14'

Dolphin started reporting errors while shutting down the models. We tried to reboot the front end, but it crashed, so we hard reset it.

SUS

H1 ISC - Delay Measurements of REFL/POP RF Detectors

daniel.sigg@ligo.org — Tue, 04 Mar 2025 11:20:44 -0800

Author: daniel.sigg@ligo.org

Report ID: 83155

Following T2500040-v1 the phase delays were measured for LSC REFL_A, LSC POP_A, ASC REFL_A, ASC REFL_B, and ASC POP_X. Results in the attached pdf.

Non-image files attached to this report

T2500040-v1-before.pdf

LHO FMCS - End X Chiller 1 failure

eric.otterman@ligo.org — Tue, 04 Mar 2025 10:36:17 -0800

Author: eric.otterman@ligo.org

Report ID: 83154

After replacing the chiller pump seal, I switched the lead unit to enable to chiller to run, but it failed on water flow. After troubleshooting the chiller, I found that the wiring harness for the flow switch had been chewed on by an animal. I will see about splicing the damaged wiring back together, but until that is done we are down one chiller at End X.

LHO VE - Tue CP1 Fill

david.barker@ligo.org — Tue, 04 Mar 2025 10:25:59 -0800

Author: david.barker@ligo.org

Report ID: 83153

Tue Mar 04 10:11:57 2025 INFO: Fill completed in 11min 54secs

Images attached to this report

H1 PSL - PSL Cooling Water pH Test

ryan.short@ligo.org — Tue, 04 Mar 2025 09:39:08 -0800

Author: ryan.short@ligo.org

Report ID: 83152

FAMIS 24832

pH of PSL chiller water was measured to be between 10.0 and 10.5 according to the color of the test strip.

H1 General - LY Vacuum Rack - UPS

filiberto.clara@ligo.org — Tue, 04 Mar 2025 09:01:58 -0800

Author: filiberto.clara@ligo.org

Report ID: 83151

WP 12364

The battery for the LY Vacuum Rack UPS system was replaced this morning. Unit stayed powered on during the battery replacement. Nothing had to be powered down. Noted a low memory pop window on the h0valy machine. Patrick logged in and closed visual studio and medm.

All vacuum rack UPS systems have batteries with an install date of March 2021. Manufacturer recommends batteries be replaced. Replacement batteries will be ordered.

F. Clara, G. Moreno

CDS, VE

H1 PSL - PSL 10-Day Trends

ryan.short@ligo.org — Tue, 04 Mar 2025 08:59:38 -0800

Author: ryan.short@ligo.org

Report ID: 83150

FAMIS 31075

Jason made a few tweaks last Tuesday, including a PMC alignment tweak and recalibration of amplifier pump diode monitors (alog83035), which is clearly seen in trends here. Since then, things have looked quite stable.

Images attached to this report

H1 General - OPS Tuesday day shift start

ryan.crouch@ligo.org — Tue, 04 Mar 2025 07:28:05 -0800

Author: ryan.crouch@ligo.org

Report ID: 83149

TITLE: 03/04 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 5mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.41 μm/s
QUICK SUMMARY:

We lost lock at 14:49 UTC, at DRMI as I'm coming in
2ndary microseism has risen quickly over the past 9 hours

H1 CDS - Workstations updated

erik.vonreis@ligo.org — Tue, 04 Mar 2025 06:17:23 -0800

Author: erik.vonreis@ligo.org

Report ID: 83148

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