aLIGO LHO Logbook

H1 General - SEI seismometer mass position check - Monthly

anthony.sanchez@ligo.org — Fri, 21 Feb 2025 19:18:18 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82969

Averaging Mass Centering channels for 10 [sec] ...
2025-02-21 19:13:29.266265

There are 16 T240 proof masses out of range ( > 0.3 [V] )!
ETMX T240 2 DOF X/U = -0.872 [V]
ETMX T240 2 DOF Y/V = -1.013 [V]
ETMX T240 2 DOF Z/W = -0.359 [V]
ETMY T240 3 DOF X/U = 0.313 [V]
ITMX T240 1 DOF X/U = -1.715 [V]
ITMX T240 1 DOF Y/V = 0.441 [V]
ITMX T240 1 DOF Z/W = 0.52 [V]
ITMX T240 2 DOF Y/V = 0.337 [V]
ITMX T240 3 DOF X/U = -1.779 [V]
ITMY T240 3 DOF X/U = -0.723 [V]
ITMY T240 3 DOF Z/W = -2.288 [V]
BS T240 1 DOF Y/V = -0.325 [V]
BS T240 3 DOF Z/W = -0.397 [V]
HAM8 1 DOF X/U = -0.307 [V]
HAM8 1 DOF Y/V = -0.421 [V]
HAM8 1 DOF Z/W = -0.687 [V]

All other proof masses are within range ( < 0.3 [V] ):
ETMX T240 1 DOF X/U = 0.091 [V]
ETMX T240 1 DOF Y/V = 0.038 [V]
ETMX T240 1 DOF Z/W = 0.101 [V]
ETMX T240 3 DOF X/U = 0.107 [V]
ETMX T240 3 DOF Y/V = 0.05 [V]
ETMX T240 3 DOF Z/W = 0.051 [V]
ETMY T240 1 DOF X/U = 0.129 [V]
ETMY T240 1 DOF Y/V = 0.217 [V]
ETMY T240 1 DOF Z/W = 0.287 [V]
ETMY T240 2 DOF X/U = -0.034 [V]
ETMY T240 2 DOF Y/V = 0.248 [V]
ETMY T240 2 DOF Z/W = 0.096 [V]
ETMY T240 3 DOF Y/V = 0.168 [V]
ETMY T240 3 DOF Z/W = 0.19 [V]
ITMX T240 2 DOF X/U = 0.229 [V]
ITMX T240 2 DOF Z/W = 0.295 [V]
ITMX T240 3 DOF Y/V = 0.172 [V]
ITMX T240 3 DOF Z/W = 0.164 [V]
ITMY T240 1 DOF X/U = 0.13 [V]
ITMY T240 1 DOF Y/V = 0.166 [V]
ITMY T240 1 DOF Z/W = 0.083 [V]
ITMY T240 2 DOF X/U = 0.054 [V]
ITMY T240 2 DOF Y/V = 0.286 [V]
ITMY T240 2 DOF Z/W = 0.192 [V]
ITMY T240 3 DOF Y/V = 0.123 [V]
BS T240 1 DOF X/U = -0.126 [V]
BS T240 1 DOF Z/W = 0.193 [V]
BS T240 2 DOF X/U = -0.002 [V]
BS T240 2 DOF Y/V = 0.106 [V]
BS T240 2 DOF Z/W = -0.047 [V]
BS T240 3 DOF X/U = -0.099 [V]
BS T240 3 DOF Y/V = -0.283 [V]

Assessment complete.

Averaging Mass Centering channels for 10 [sec] ...

2025-02-21 19:16:03.265814
There are 1 STS proof masses out of range ( > 2.0 [V] )!
STS EY DOF X/U = -2.336 [V]

All other proof masses are within range ( < 2.0 [V] ):
STS A DOF X/U = -0.46 [V]
STS A DOF Y/V = -0.842 [V]
STS A DOF Z/W = -0.555 [V]
STS B DOF X/U = 0.251 [V]
STS B DOF Y/V = 0.955 [V]
STS B DOF Z/W = -0.313 [V]
STS C DOF X/U = -0.86 [V]
STS C DOF Y/V = 0.793 [V]
STS C DOF Z/W = 0.694 [V]
STS EX DOF X/U = 0.016 [V]
STS EX DOF Y/V = -0.038 [V]
STS EX DOF Z/W = 0.123 [V]
STS EY DOF Y/V = -0.066 [V]
STS EY DOF Z/W = 1.362 [V]
STS FC DOF X/U = 0.192 [V]
STS FC DOF Y/V = -1.1 [V]
STS FC DOF Z/W = 0.662 [V]

Assessment complete.

H1 General - Friday Eve Shift report

anthony.sanchez@ligo.org — Fri, 21 Feb 2025 16:35:04 -0800

Author: anthony.sanchez@ligo.org

Report ID: 82968

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

H1 Is currently Locked and Observing for 1.5 hours.
Our plan is to continue to Observe for the rest of the night.
I am told I likely need to keep an eye on PI mode 8, and Violin mode IY Mode 5 as it may require non-nominal settings.
Pi Mode 8 channel name to watch = H1:SUS-PI_PROC_COMPUTE_MODE8_NORMLOG10RMSMON

Since the Ring Heater settings were changed, I'll likely have to do an Initial Alignment after each Lockloss.

Everything else seems to be functioning normally.

LHO General - Fri Ops DAY Shift Summary

corey.gray@ligo.org — Fri, 21 Feb 2025 16:31:10 -0800

Author: corey.gray@ligo.org

Report ID: 82952

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

H1 Glitches continues as noted by Sheila here.
Ring Heater was adjusted to address the new PI24 issues (as well as the glitches above). Because this is a slow aligment change, we may have to run Initial Alignments after locklosses for the next few days.
Finally, there is the ITMy Mode 5 & 6 which are rung up and Rahul has been finding the best settings to damp it down. Don't have anything ready to update lsc_params with yet, but until we do, this is the current preferred settings (alog) for ITMy Mode 5: FM6 + FM8 + FM10 Gain +0.01 (+30deg phase) <----this needs to be entered by hand!

LOG:

1719-1750 Dust Mon FAMIS checks (mitch)
1754, 1813 PI 24 ring-up
- Around this time we begin to see the range drop and glitchiness again.
1756 Rahul taking a look at ITMy violin modes
1829-1851 Optics Lab cleaning (kim)
1816 PI24 takes us out of OBSERVING as H1 is very glitchy and overall range takes a step down
- 1829 LOCKLOSS (after 4.5hr lock)
- 1835 INITIAL ALIGNMENT (green arms didn't look great/stable)
- Sheila made a Ring Heater change to address PI24 (& hopefully our new H1 glitches as well).
  - OPS NOTE: This will take a couple days to "normalize", so Alignments may be needed after every lockloss until H1 stabilizes from this change.
- For DRMI, it was taking a while to lock, so went for a PRMI which took about 5-min to lock, and then after this DRMI was able to finally lock within a min.
1958 NLN....2002 OBSERVING
2127 Lockloss due to M5.1and sounds north of Vancouver, BC
- Taking H1 to IDLE to wait out the rumbling for 30min first.
- 2142 Initial Alignment
- 2247 back to NLN & 2250 back to OBSERVING

H1 DetChar - Comment to H1 glitches continue

sheila.dwyer@ligo.org — Fri, 21 Feb 2025 16:09:31 -0800

Author: sheila.dwyer@ligo.org

Report ID: 82966

Within the glitchy periods, there seem to be correlations between MODE8 (TMS X QPDs bandpassed from 10kHz-10.8kHz) and MODE24 (DCPDs) monitors and the rnage drops that are somewhat regular during these glitchy periods (see screenshot).

We don't have an equivalent monitor set up for TMS Y QPDs.

Daniel and I looked at this time in a dtt watching exponetial averages, and it does seem that the mode at 10432 Hz is going up and down by a few orders of magnitude, at least once this seems to happen after the glitch that shows up in the GW band. The mode directly below it is also going up and down. Watching this with exponetial averaging tends to crash dtt, but some screenshots are attached.

Images attached to this report

H1 CDS - Offload of raw minute trends from TW1 complete

david.barker@ligo.org — Fri, 21 Feb 2025 16:08:49 -0800

Author: david.barker@ligo.org

Report ID: 82967

WP12339

Dave:

The offload of the past 6 months of raw minute trend files from h1daqtw1's SSD-RAID to permanent storage is complete (disk usage was reduced from 92% to 2%).

H1 CDS - New CDS digital video camera MEDM

david.barker@ligo.org — Fri, 21 Feb 2025 16:02:10 -0800

Author: david.barker@ligo.org

Report ID: 82965

To test the new h1digivideo4 server we moved four production cameras from servers running the old software to the new server. This required changes to the camera overview MEDM, which up to this time had been hand edited.

I took this opportunity to write a python program to generate the camera overview MEDM (see attached).

The main changes are:

. cameras are sorted alphabetically by name, not by camera number.

. cameras are not grouped by the server machine they run on.

. camera data is stored in a yaml database. Camera details can be viewed by pressing the INFO buttons.

. process control buttons are provided for each camera (VID0 = h1digivideo0, etc). Servers running the new code have green text (VID3 and VID4)

SITEMAP.adl has been upgraded to use the new overview. To open the old overview there is a "Traditional Overview" button provided in the bottom right corner.

Paths for the generator code and the yaml database file are shown at the bottom of the window.

Images attached to this report

H1 SUS - Comment to New settings for ITMY mode 05/06

rahul.kumar@ligo.org — Fri, 21 Feb 2025 15:26:12 -0800

Author: rahul.kumar@ligo.org

Report ID: 82964

We lost lock and then during the next lock Corey applied the above settings (in bold fonts) and it seems to be working fine. Hence, I will continue with this for the next few lock stretches. Not committing it to lscparams yet since things can still change.

H1 SUS - New settings for ITMY mode 05/06

rahul.kumar@ligo.org — Fri, 21 Feb 2025 13:15:37 -0800

Author: rahul.kumar@ligo.org

Report ID: 82963

FM6 + FM8 + FM10 Gain +0.01 (+30deg phase) looks to be working for now - see attached screenshot.

The other settings which I tried and it didn't work are listed below,

zero phase Gain 0.01 (IY05 increasing, IY06 decreasing).

-30deg phase gain 0.01 (IY05 increasing, IY06 decreasing).

SUS

Images attached to this report

H1 ISC - EY RH power steped up

sheila.dwyer@ligo.org — Fri, 21 Feb 2025 12:14:39 -0800

Author: sheila.dwyer@ligo.org

Report ID: 82962

We lost lock because of PI 24 in our last lock. We are also seeing a correlation between PI channels and loud glitches in H1 (Derek made some nice plots in 82961).

We've stepped up the EY ring heater both upper and lower segements from 1.2W to 1.3W. This has been stepped up in Decmeber 81890 81891 and September 80320.

We did the step after Corey had the IFO locked with all ASC on, to deal with the alignment shift after this lockloss we will probably need an initial alignment.

H1 DetChar - Comment to H1 glitches continue

derek.davis@ligo.org — Fri, 21 Feb 2025 11:54:36 -0800

Author: derek.davis@ligo.org

Report ID: 82961

Following up Sheila's investigation, I've made a set of slides comparing the glitching seen in the strain channel against the 10.4 kHZ PI channel for many of the times highlighted above. We can see a clear correlation between this channel and the presence of the glitching in strain.

DetChar

Non-image files attached to this report

February2025PIGlitching.pdf

LHO VE - Fri CP1 Fill

david.barker@ligo.org — Fri, 21 Feb 2025 10:32:56 -0800

Author: david.barker@ligo.org

Report ID: 82960

Fri Feb 21 10:10:02 2025 INFO: Fill completed in 9min 59secs

Jordan confirmed a good fill curbside. TCmins [-77C, -75C] OAT (+1C, 33F) DeltaTempTime 10:10:05

Images attached to this report

H1 DetChar - H1 glitches continue

sheila.dwyer@ligo.org — Fri, 21 Feb 2025 10:18:53 -0800

Author: sheila.dwyer@ligo.org

Report ID: 82959

There have been a few other alogs about this already:

82924
82944

H1's range is slighty improved after the initial drop (possibly due to PRCL and A2L tuning in the commissioning window), but the large glitches are still present. They were not present in the early part of yesterday's lock, but re-appeared after TJ took a calibration measurement around 22 UTC (were present all night and caused a retraction of a GW alert), and they are not present so far in the current lock, which was automatic. Looking at the summary page plots, the glitches that come and go are those with SNR between 10 and 30, at 60 and just below 50 Hz. (I can't read the precise frequency from the summary page plot, to know if these glitches line up with the PR3 roll mode well or not). When the glitches are on, they have a rate of something like 2e-2 Hz (between SNR of 10-20), which means roughly a glitch every 50 seconds, more if we include the SNR 20-30 glitches. Hveto doesn't identify an auxillary channel that can veto these glitches.

Looking at the range plot, there seem to be pretty regular drops in range when the glitches at 50 + 60 Hz are present, zooming in the spacing between these range drops is 5-6 minutes, although I'm using a channel that only updates every minute. Looking at DCPD sum or ESD drive channels time series don't show an obvious way to get a better handle on the timing of these larger, less frequent glitches.

The correlation with 82944 the PI channel found by Jane's Lasso run seems to continue where the PI channel keeps being rung up in the time periods when the range has these drops every 5 minutes.

Editing to add:

It looks like the MODE8 channel got elevated like this for the first time on Feb 5th, and there have been a number of incidences where this channel was elevated with glitches at 60 Hz and just below 50:

Feb 5 4-7 UTC
Feb 5 21 UTC - Feb 6 8:30 UTC
Feb 6 15-16:50 UTC
Feb 7 21 UTC -8
4-9 UTC on Feb 10th when there is a hint of glitches but not as loud or frequent as in the last two days,
Feb 11th when there seems to be a problem with the glitch summary page or with omicron
on Feb15th (glitches appeared at 60 and just below 50Hz)

DetChar

Images attached to this report

H1 DetChar - Comment to Step down + noise in range bleeding into PI channels

derek.davis@ligo.org — Fri, 21 Feb 2025 10:10:49 -0800

Author: derek.davis@ligo.org

Report ID: 82958

The glitching related to this range drop appears to have subsided in the most recent lock. Comparison of glitchgrams from

Yesterday, showing the glitching starts when the range drop occurred
Today, showing the glitching is not present in the most recent lock

When these glitches were occurring, they appeared on roughly a 6-minute cadence.

DetChar

Images attached to this report

H1 AOS - Hepi Pump Stations

mitchell.robinson@ligo.org — Fri, 21 Feb 2025 10:04:07 -0800

Author: mitchell.robinson@ligo.org

Report ID: 82957

Hepi pump stations are running smoothly, no new leaks.

EX Trip is 6-7/8 running at 7

EY Trip is 8-1/8 running at 8-3/16 will adjust level Monday with Jim

Corner Trip is 5-5/16 running at 5-5/8

SEI

H1 SUS - Comment to ITMy Mode 05 & 06

rahul.kumar@ligo.org — Fri, 21 Feb 2025 10:01:41 -0800

Author: rahul.kumar@ligo.org

Report ID: 82956

Since IY06 was growing consistently, hence I have switched off damping for some time and will look for another setting.

I tried the following settings this morning and none of them worked,

-60 deg phase gain -0.01 (IY05 decreasing, IY06 increasing)

-30 deg phase gain -0.01 (IY05 increasing, IY06 increasing)

+30 deg phase gain -0.01 (IY05 increasing, IY06 increasing)

H1 PSL - PSL Status Report (FAMIS #26363)

corey.gray@ligo.org — Fri, 21 Feb 2025 08:23:35 -0800

Author: corey.gray@ligo.org

Report ID: 82954

Laser Status:
    NPRO output power is 1.847W
    AMP1 output power is 71.66W
    AMP2 output power is 141.6W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 16 days, 20 hr 5 minutes
    Reflected power = 23.88W
    Transmitted power = 105.7W
    PowerSum = 129.6W

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

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

Possible Issues:
PMC reflected power is high

PSL

H1 SUS - ITMy Mode 05 & 06

corey.gray@ligo.org — Fri, 21 Feb 2025 08:06:09 -0800

Author: corey.gray@ligo.org

Report ID: 82953

Now that I have seen in alogs () that ITMy Mode 5 & 6 have returned to causing grief, doing a morning check after 2hrs of lock. Currently, ITMy Mode 05 was taken to the following via guardian:

ITMy Mode 05 settings via Guardian: FM5 + FM6 + FM10 Gain -0.01 (phase -60 degrees)
This is in contrast to the settings Rahul notes in his alog yesterday: FM5 + FM6 + FM10 Gain 0.01 (phase -60 degrees)
The attached screenshot shows IY Mode-5 slightly decreasing and Mode-6 slightly increasing

Will continue monitoring.

SUS

Images attached to this report

LHO General - Fri Ops Day Transition

corey.gray@ligo.org — Fri, 21 Feb 2025 07:38:32 -0800

Author: corey.gray@ligo.org

Report ID: 82951

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

After the 18+hr lock, there was a lockloss a few hours ago (which needed help from Oli to get us back to Observing) with a decently quick recovery. Environmentally, secondary microseism has mostly been below the 95th percentile (but may be inching toward it in the last 5hrs), winds are calm and it is a foggy 30degF out.

H1 General - OWL Intervention

oli.patane@ligo.org — Fri, 21 Feb 2025 06:15:36 -0800

Author: oli.patane@ligo.org

Report ID: 82950

We were in NLN but couldn't go into Observing due to some SDF diffs that I had been warned about. I accepted the diffs and we went right into Observing!

Images attached to this report

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Thu, 20 Feb 2025 22:00:16 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82949

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

IFO is in NLN and OBSERVING as of 22:01 UTC (12 hr lock!)

Extremely calm shift with no loklosses. Of note:

violin modes IY5_6 have both been steadily going down for the last 7 hours
PI24 still ringing up every few minutes

LOG:

None

H1 DetChar - Step down + noise in range bleeding into PI channels

oli.patane@ligo.org — Thu, 20 Feb 2025 16:37:46 -0800

Author: oli.patane@ligo.org

Report ID: 82944

TJ, Oli

Starting around 02/20 at 11:30 UTC, the range had a step down, where it stayed for the rest of the lock. After this step down, the range was also much noisier than it had been before the step (ndscope1). Jane Glanzer ran Lasso for us during this lock stretch (lasso), and the top channel that came back with the highest correlation to this range drop was H1:SUS-PI_PROC_COMPUTE_MODE8_NORMLOG10RMSMON, with the other channels all having much lower correlation coefficients. This was weird to us because we bandpass and downconvert to monitor mode 8 but we don't monitor or damp it, and we don't even turn on its PLL. When you plot the correlated channel along with related PLL channels (SUS-PI_PROC_COMPUTE_MODE8_PLL_AMP_FILT_OUTPUT, SUS-PI_PROC_COMPUTE_MODE8_PLL_LOCK_ST, and SUS-PI_PROC_COMPUTE_MODE8_PLL_ERROR_SIG), you can see there was some weird noise in multiple of these channels that started when the range dropped (ndscope2).

I tried plotting a series of PI_PROC_COMPUTE_MODE channels for every mode (there are 32 in total), and out of all of them, only mode 8 and mode 24 showed any change in any of their respective channels around the time of the range drop(ndscope3). It only being these two channels is very interesting. PI mode 8 comes from the TRX QPD and has a bandpass between 10 and 10.8 kHz. Like I mentioned earlier, we do not actively do anything to this channel. Mode 24 on the other hand, we definitely monitor and are damping it a lot of the time. Mode 24 is read in from the DCPDs and has a bandpass of, and the PI is centered around 10.431 kHz. It is damped by using the ESD on ETMY. Mode 24 actually has more channels that correlate better and have larger amplitudes than mode 8, but Mode 8 NORMLOG10RMSMON correlated better with lasso over the entire lock stretch.

Zooming into when the range drop started yesterday, we actually see that the large drop in range happened about 12 minutes before we see the huge error signals in the mode 24 PLL, and it is at the very beginning of the rise in mode 8 and 24 NORMLOG10RMSMON (ndscope4).

Zooming out, this excess noise in those PI channels seems to have started early on February 5th, aka after relocking after the February 4th maintenance day(ndscope5). On other days, the range doesn't seem to have been affected by this noise though, at least nowhere near the amount that it was affected yesterday. Sometimes during these periods of noise, the range won't be very good (below 155), but other times we'll see this noise in modes 8 and 24 and still be right around or above 160.

Since it looks like the range drop yesterday started before the PI channels really started changing, we're pretty sure the issue is somewhere else and is just bleeding into these two downconverted channels. Because these two PI channels go through bandpasses in the 10kHz regime, there might be something in that frequency range. It is interesting though that although another PI channel we actively monitor, Mode 31, is also in the same frequency area (centered at 10.428 kHz), is read from the OMC DCPDs, and is damped using ETMY, all just like PI24, there doesn't seem to be any coupling into its channels.

Either way, pretty good leads were made this morning towards finding the actual cause of this range drop. TJ and Camilla looked into the many glitches that appeared then at 60 and 48 Hz, as well as noting that the line at 46.1 Hz had grown, which is a known PR3 roll mode (82924).

SUS

Images attached to this report

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Thu, 20 Feb 2025 16:32:24 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82948

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

IFO is in NLN and OBSERVING as of 18:02 UTC (6hr 20 min lock)

EY 5_6 Violins are still elevated. Rahul is trying out new settings.

H1 SUS - Comment to Violin mode damping- new settings for ITMY 05/06

rahul.kumar@ligo.org — Thu, 20 Feb 2025 16:24:15 -0800

Author: rahul.kumar@ligo.org

Report ID: 82947

Current damping using FM6 + FM7 + FM10 Gain 0.01 (-30degree phase) - not sure if this is working yet. Will keep an eye on it tonight.

LHO General - Ops Day Shift End

thomas.shaffer@ligo.org — Thu, 20 Feb 2025 16:18:17 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82934

TITLE: 02/21 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Lock loss at the start of the shift again, this one caused but , followed by a commissioning period and a calibration measurement. ITMY modes 5&6 rang up slowly overnight and continue to be an issue to damp (82940). As of right now, I'm not sure we've found a setting that is actually damping these modes. We've been locked for 6.5 hours, observing for 2.5 of those.
LOG:

2004 Observing
2129-2201 Out of observing to run calibration measurement

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
19:34	SAF	Laser Haz	LVEA	YES	LVEA is laser HAZARD!!!	06:13
17:55	FAC	Tyler	MY	n	Fire panel check	18:55
17:56	PEM	Robert	LVEA	yes	Turn on amps	19:22
18:15	ISC	Sheila, Mayank, Matt	LVEA	yes	ISCT table work with POP	18:43
18:28	FAC	Kim	MY, MX	n	Tech clean	19:31

H1 ISC - Comment to POP AIR path power measurements

sheila.dwyer@ligo.org — Thu, 20 Feb 2025 15:55:28 -0800

Author: sheila.dwyer@ligo.org

Report ID: 82946

The large beam size coming off the periscope meant it was difficult to use the power meter until downstream of the lens. That's why the first measurement was directly after the 90/10 BS.

H1 TCS - TCS Chiller Water Level Top-Off

thomas.shaffer@ligo.org — Thu, 20 Feb 2025 15:25:09 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82945

FAMIS27809

I didn't add any water to either chiller as they both looked near the max. Both filters looked good and the leak detection Dixie cup was dry. The T2200289 was updated.

H1 ISC - A2L Measurements and Coherence Monitor

matthewrichard.todd@ligo.org — Thu, 20 Feb 2025 15:05:13 -0800

Author: matthewrichard.todd@ligo.org

Report ID: 82943

Matthew Sheila

I ran a2l measurements using TJ and Sheila's a2l_min code, and I've attached the new settings below.

python userapps/isc/h1/scripts/a2l/a2l_min_multi_pretty.py -a

I've also attached plots of the coherence checks with lsc and asc channels and darm.

Results of the A2L measurement

*************************************************
RESULTS
*************************************************
ETMX P
Initial: 3.6
Final: 3.34
Diff: -0.26

ETMX Y
Initial: 4.92
Final: 4.9
Diff: -0.02

ETMY P
Initial: 5.64
Final: 5.56
Diff: -0.08

ETMY Y
Initial: 1.35
Final: 1.28
Diff: -0.07

ITMX P
Initial: -0.64
Final: -0.66
Diff: -0.02

ITMX Y
Initial: 3.0
Final: 2.97
Diff: -0.03

ITMY P
Initial: -0.03
Final: -0.06
Diff: -0.03

ITMY Y
Initial: -2.53
Final: -2.51
Diff: 0.02

Images attached to this report

H1 ISC - POP AIR path power measurements

matthewrichard.todd@ligo.org — Thu, 20 Feb 2025 14:55:57 -0800

Author: matthewrichard.todd@ligo.org

Report ID: 82942

Matthew Mayank Sheila

We went out to ISCT1 to measure the power coming to the POP AIR port, components are labeled in Sheila's alog. It seems the 50/50 beamsplitter is acting appropriately.

2025-02-20 10:28:11.348428 PST:
H1:ASC-POP_X_DC_NSUM_OUT16 = 1.1193946024467205
H1:LSC-POP_A_LP_OUT16 = 39.499373468859446

BS9010 power: 3.6 mW
POPX power: 1.8 mW

2025-02-20 10:35:24.229534 PST
H1:ASC-POP_X_DC_NSUM_OUT16 = 1.1307608842849726
H1:LSC-POP_A_LP_OUT16 = 39.88992869059245

These average power measurements were taken using

cdsutils avg +30 H1:ASC-POP_X_DC_NSUM_OUT16 H1:LSC-POP_A_LP_OUT16

H1 SUS - Comment to Violin mode damping- new settings for ITMY 05/06

rahul.kumar@ligo.org — Thu, 20 Feb 2025 14:52:55 -0800

Author: rahul.kumar@ligo.org

Report ID: 82941

Looks like IY05 is now increasing (as per narrow filter, broad filter shows decreasing) and mode 06 is decreasing. Since mode 06 is higher than mode 05, I will let the current settings damp it for now.

H1 SUS - Violin mode damping- new settings for ITMY 05/06

rahul.kumar@ligo.org — Thu, 20 Feb 2025 14:37:31 -0800

Author: rahul.kumar@ligo.org

Report ID: 82940

TJ, Rahul

ITMY mode 05 and mode 06 have been rung-up since morning and TJ and I have tried several settings to bring them down. The settings which is currently working is listed below in bold font,

New settings for ITMY 05/06 (not yet committed to lscparams file):-

FM5 + FM6 + FM10 Gain 0.01 (phase -60 degrees)

The other settings which I unsuccessfully tried as follows,

-60deg phase -0.01 gain - increase

zero phase -0.01 gain - increase

+30degree phase -0.01 gain - increase

Similarly TJ efforts (from morning to noon) are also given below,

Settings tried for this lock below. There was commissioning going on during this time, so I worry that a few of the ones I tried were made worse by measurements.

Phase, gain - result

-30deg , -0.01 - Slow increase

-60deg. -0.01 - Slow increase

-90deg, +0.01 - very slow increase

+30deg, +0.01 - no increase, no decrease

+60deg, +0.01 - maybe no increase or decrease?

Commissioning measurement might have confused this one 0deg, +0.01 - increased

SUS

Images attached to this report

H1 CAL - Calibration Sweep 2129UTC

thomas.shaffer@ligo.org — Thu, 20 Feb 2025 14:01:22 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82939

Ran a calibration measurement using an older version of simulines that the CAL group updated in the wiki. We were locked for about 3.5 hours when I started the broad band.

Simulines start:

PST: 2025-02-20 13:36:12.224035 PST
UTC: 2025-02-20 21:36:12.224035 UTC
GPS: 1424122590.224035

Simulines end:
PST: 2025-02-20 14:00:14.443589 PST
UTC: 2025-02-20 22:00:14.443589 UTC
GPS: 1424124032.443589

Files:

2025-02-20 22:00:14,365 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250220
T213613Z.hdf5
2025-02-20 22:00:14,373 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20
250220T213613Z.hdf5
2025-02-20 22:00:14,378 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20
250220T213613Z.hdf5
2025-02-20 22:00:14,383 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20
250220T213613Z.hdf5
2025-02-20 22:00:14,388 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20
250220T213613Z.hdf5

Images attached to this report

H1 ISC - HAM6 loss estimate remeasured with OMC ASC off

jennifer.wright@ligo.org — Thu, 20 Feb 2025 12:58:59 -0800

Author: jennifer.wright@ligo.org

Report ID: 82938

Jennie W, Sheila

Today I got a chance to redo some of my output chain measurements (alog #82555) that gave us a confusing result when we were heating up and cooling down the OM2 heater. The confusiong was that our optical gain got better for cold OM2 compared to hot, but the loss through HAM6 predicted by stepping the DARM offset and comparing it to the power at the anitsymmetric port predicted that the loss was worse with cold OM2 and gave us unreasonably low (~65 %) throughput estimate for the fundamental TM00 mode through HAM6. We realised that the OM3 and OMC alignment are being changed by the ASC during this time so that could be affecting the comparison.

Steps:

Turn off OMC ASC at 18:43:00 UTC.

Run auto_darm_offset_step.py from /ligo/gitcommon/labutils/darm_offset_step at 18:45:01 UTC.

Results: P_AS = 62.996 mW + 1.162 * P_DCPD

This makes the throughput estimate for the TM00 mode through HAM6 to the DCPDs to be 86.0 % of the power at the AS port. Which seems more reasonable than the 65% we got last time. We need to do this measurements again when we have improved kappa C somehow to check it gives us the same loss estimate between two times.

We were then going to purposely change kappa C as a comparison to the estimate the DARM offset step gives us, byt changing the QPD offsets based on this measurement 82383(I got the sign wrong last time I did this).

I turned the OMC ASC back on before doing this, however when I changed the H1:ASC-OMC_A_PIT_OFFSET to 0.45 this saturated the OM3 suspension so this was set back to nominal.

I think I got signs wrong yet again so we will try what we now think are the correct ones another commissioning period but maybe do it slowly so as not to cause saturations.

SQZ

Non-image files attached to this report

all_plots_plot_darm_optical_gain_vs_dcpd_sum_1424112323_Feb_20thth__cold_OM2__40_mins_into_lock.pdf

H1 SQZ - Comment to SQZ_ANG_SERVO set to False

camilla.compton@ligo.org — Thu, 20 Feb 2025 12:35:14 -0800

Author: camilla.compton@ligo.org

Report ID: 82937

Daniel, Sheila, Camilla

This morning we set the SQZ angle to 90deg and scanned to 290deg using 'ezcastep H1:SQZ-CLF_REFL_RF6_PHASE_PHASEDEG -s '3' '+2,100''. Plot attached.

You can see that the place with the best SQZ isn't a good linear range for H1:SQZ-ADF_OMC_TRANS_SQZ_ANG, which is why the SQZ angle servo has ben going unstable. We are leaving the SQZ angle servo off.

Daniel noted that we expect the ADF I and Q channels to rotate around zero, which they aren't. So we should check that the math calculating these is what we expect. We struggles the find the SQZ-ADF_VCXO model block, it's in the h1oaf model (so that the model runs faster).

Images attached to this report

H1 CAL - Calibration debugging

joseph.betzwieser@ligo.org — Thu, 20 Feb 2025 12:31:31 -0800

Author: joseph.betzwieser@ligo.org

Report ID: 82935

[Vlad, Louis, Jeff, Joe B] So while exercising the latest pydarm code with an eye towards correcting the issues noted in LHO alog 82804, we ran into a few issues which we are still trying to resolve. First, Vlad was able to recover all but the last data point from the simulines run on Feb 15th, which lost lock at the very end of the sweeps. See his LHO alog 82904 on that process. I updated the pydarm_H1.ini file to account for the current drive align gains and point at the current L1SUSETMX foton file (saved in the calibration svn as /ligo/svncommon/CalSVN/aligocalibration/trunk/Common/H1CalFilterArchive/h1susetmx/H1SUSETMX_1421694933.txt ). However, I had to also merge some changes for it submitted from offsite. Specifically https://git.ligo.org/Calibration/ifo/H1/-/commit/05c153b1f8dc7234ec4d710bd23eed425cfe4d95, which is associated with MR 10 which was intended to add some improvements to the FIR filter generation. Next, Louis updated the pydarm install at LHO from tag 20240821.0 to tag 202502220.0. We then generated the report and associated GDS FIR filters. This is /ligo/groups/cal/H1/reports/20250215T193653Z. The report and fits to the sweeps looked reasonable, however, the FIR generation did not look good. The combination of the newly updated pydarm and ini changes was producing some nonsensical filter fits. This is the first attachment. We reverted the .ini file changes, and this helped to recover more expected GDS filters, however, there's still a bit of a small ~1% change visible around 10 Hz (instead of being a flat 1.0 ratio) in the filter response using the new pydarm tag versus the old pydarm tag which we don't understand quite yet, and would like to before updating the calibration. I'm hoping we can do this in the next day or two after going through the code changes between the versions. Given the measured ~6 Hz SRC detuning spring frequency (as seen in the reports), we will need to include that effect in the calcs front end to eliminate a non-trivial error when we do get around to updating the calibration. I created a quick plot based off the 20250215T193653Z measured parameters, comparing the full model over a model without the SRC detuning included. This is the attached New_over_nosrc.png image.CAL

Images attached to this report

Non-image files attached to this report

bad_ini_H1_calibration_report_20250215T193653Z.pdf

H1_calibration_report_20250215T193653Z.pdf

H1 General - Small improvements to DARM BLRMS

camilla.compton@ligo.org — Thu, 20 Feb 2025 12:20:00 -0800

Author: camilla.compton@ligo.org

Report ID: 82930

Attached is the DARM BLRMS before and after some filters were edited and added to remove some lines, all changes are attached apart form another adjustment to RBP_2 notch 33.375Hz.

Images attached to this report

H1 ISC - Comment to More PR2 spot moves, getting full model of scraper baffle

mayank.chaturvedi@ligo.org — Thu, 20 Feb 2025 12:13:41 -0800

Author: mayank.chaturvedi@ligo.org

Report ID: 82932

We modeled the PR2Baffle beam clipping

Matt Jennie Mayank TJ Sheila Keita

We extracted the beam path and geometry for the PRM-PR2Baffle-PR2-PR2Baffle-PR3 leg of the input light from the following documents, D1200573, D1102451 (cookie cutter), D0901098, D020023 etc.

The angle of PRM-PR2Baffle beam with respect to X axis was changed from about -0.1 radian to 0.1 radian (over and above the existing value of 0.339 Degrees) such that the
PR2 Beam spot moves from approximately -25mm to 25 mm. The PR2 yaw was adjusted such that the PR2-PR3 beam always hits the same spot on PR3.
This ensures that the beam spot on PRM and PR3 remain unchanged while the beam spot on PR2 changes.

Attachment 1: Shows the overall modelled geometry

Attachment 2: Zoom view around PR2Baffle along with the beam paths.

Attachment 3: Python script.

Attachment 4: Experiment_Data_ 19Feb2025.

Attachment 5: Experiment_Data_ 5July2025.

Plot 1 shows the PR2 beam spot motion with respect to the angle.

Plot 2 shows that following distances vs the PR2 beam spot location
a) PRM-PR2 beam and the Lower edge of the PR2Baffle (D1 distance)
b) PR2-PR3 beam and the Upper edge of the PR2Baffle (D2 distance).

Plot 3 shows the transmission of the beam with respect PR2 beam spot (As the beam comes closer to the baffle edge, some of the beam power is blocked by the baffle edge and hence the transmission decreases)

Plot 4 shows the net transmission for the beam (multiplication of Upper edge and Lower edge transmissions)
It also shows the experimentally measured data above.

The two curves do not match exactly however they differ in position by around 2 mm. It seems PR2_Baffle is approximately at the right place. It may not be necessary to move the PR2_Baffle.

Images attached to this report

Non-image files attached to this report

PR2SpoMoveModel.py

CleanExptData_19_Feb_2025.txt

PR2SpotVsCircPower5July2025.txt

H1 General - Observing 2004

thomas.shaffer@ligo.org — Thu, 20 Feb 2025 12:06:02 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82936

Back to observing at 2004 after a lock loss and commissioning period. We are not thermalized yet, so we will have to run a calibration measurement later.

H1 CAL - Comment to Calibration sweeps losing lock.

vladimir.bossilkov@ligo.org — Thu, 20 Feb 2025 12:03:04 -0800

Author: vladimir.bossilkov@ligo.org

Report ID: 82933

How to salvage data from any failed attempt simulines injections:

simulines siletently dumps log files into this directory: /opt/rtcds/userapps/release/cal/common/scripts/simuLines/logs/{IFO}/ for IFO=L1,H1
navitating there you will be greeted by a log the outputs of simulines every single time it has ever been run. The one you are interested in can be identified by the time, as the file name format is the same as the measurement and report directory time-name format.
running the following will automagically populate .hdf5 files in the calibration measurement directories that the 'pydarm report' command searches in for new measurements:
- './simuLines.py -i /opt/rtcds/userapps/release/cal/common/scripts/simuLines/logs/H1/{time-name}.log'
- for time-name resembling 20250215T193653Z
- where './simuLines.py' is the simulines exectuable and can have some full path like the calibration wiki does: './ligo/groups/cal/src/simulines/simulines/simuLines.py'

CAL

H1 ISC - PRCL feedforward gain increased

elenna.capote@ligo.org — Thu, 20 Feb 2025 11:46:38 -0800

Author: elenna.capote@ligo.org

Report ID: 82931

I ran a PRCL feedforward injection since the PRCL to DARM coherence has increased. Indeed, the injection showed the PRCL feedforward was doing worse around 30 Hz. I found that by increasing gain of the feedforward from 0.6 to 0.9 this improved the subtraction again.

You will notice that below about 15 Hz, PRCL coupling is still not great. That would probably require a more "invasive" adjustment of the feedforward fit, but maybe it's not worth it since it doesn't seem that it's causing much noise.

In the first attachment, blue trace shows and old coupling measurement with no feedforward, green was the "as found" previous feedforward fit measurement. Brown was the measurement today before I started adjusting the gain and red is what I got after increasing the feedforward gain. Second attachment shows the SDF accept. I also updated the gain in lscparams.

Images attached to this report

LHO VE - Thu CP1 Fill

david.barker@ligo.org — Thu, 20 Feb 2025 10:13:34 -0800

Author: david.barker@ligo.org

Report ID: 82929

Thu Feb 20 10:07:47 2025 INFO: Fill completed in 7min 43secs

Gerardo confirmed a good fill curbside. TCmins [-51C, -50C] OAT (0C, 32F) DeltaTempTime 10:07:47

Images attached to this report

H1 SEI - HEPI Pump Trends Monthly FAMIS

oli.patane@ligo.org — Thu, 20 Feb 2025 09:45:10 -0800

Author: oli.patane@ligo.org

Report ID: 82928

Closes FAMIS#, last checked 82369

HEPI pump trends looking as expected. The lines 23 days ago in all the plots are from a DAQ restart done during Tuesday Maintenance on January 28th(82498).

Images attached to this report

H1 ISC - POP LF calibration to Watts moved,

sheila.dwyer@ligo.org — Thu, 20 Feb 2025 09:40:51 -0800

Author: sheila.dwyer@ligo.org

Report ID: 82927

I've moved Elenna's calibration (82656) of the LSC POP diode DC power to the POP_A_LP filter. I tried to engage it while we were relocking after the EQ and unlocked the IFO, because this is in the IFO trigger matrix.

I've moved it and turned it on now, accepted in SDF safe and will accept in OBSERVE when we are in low noise.

H1 ISC - More PR2 spot moves, getting full model of scraper baffle

matthewrichard.todd@ligo.org — Thu, 20 Feb 2025 09:40:45 -0800

Author: matthewrichard.todd@ligo.org

Report ID: 82918

Matt Jennie Mayank TJ Sheila

We wanted to estimate whether we were clipping on the scraper baffle of PR2 so we moved the PR3 YAW sliders during single bounce quite a bit to get an idea of when were clipping, using the AS_C_NSUM to gauge whether we were starting to clip.

Most of the steps are the same in Sheila's previous alog, expect we are in single bounce and we are therefore not looking for the ALS beatnotes, instead we are looking at the AS_C_NSUM value. You want to take ISC_Lock to PR2_SPOT_MOVE so that the guardian will adjust the IM4, PR2 yaw sliders while you adjust PR3 sliders so that most everything stays aligned. You will have to adjust the pitch every once in awhile due to the cross couplings in IM4 and PR2.

Steps taken in this measurement:

Turned ISC_Lock to PR2_SPOT_MOVE
Move PR3 yaw using the slider (steps of 10 urad seemed to work for me) or using

cdsutils step -s .66 H1:SUS-PR3_Y_OPTICALIGN_OFFSET -- -1,10

We think the yaw offset value that puts the spot on the center of PR2 is around -230 urad (we started here around 09:00 PST)

3. By going in steps to -900 in yaw offset, while pitching PR3 every so often to keep everything centered, we were able to move across PR2 to the left edge of the baffle, clipping about 10% of the power at the ASC-AS_C QPD (finished 09:45 PST).
4. Then we reset the sliders to their starting values and follwed the above steps going to the right (we stopped at +440 yaw offset). Here we recorded around a 10% loss on the right edge of the baffle (finished 10:44 PST).

Mayank has some plots he will comment analyzing the results of this.

Useful ndscopes

ndscope-dev /ligo/home/matthewrichard.todd/ndscope/pr2_spot_move.yaml

LHO General - Comment to Ops Day Shift Start

camilla.compton@ligo.org — Thu, 20 Feb 2025 09:29:49 -0800

Author: camilla.compton@ligo.org

Report ID: 82925

TJ, Camilla. No extra noise in the channels that usually show our low frequency non-stationary noise 82728, see plot. Comparing DARM before and after, there is very subtle changes <100Hz. TJ found the summary pages show more glitches at 60Hz and ~48Hz.

Additionally, we see the line at 46.09Hz or 46.1Hz grow, see plot . Georgia noted this line in 2019 47447 and Evan piont us to O4aH1lines list where this apears to be the PR3 roll mode.

Images attached to this report

LHO General - Comment to Ops Day Shift Start

thomas.shaffer@ligo.org — Thu, 20 Feb 2025 09:19:57 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82926

Running the range comparison scripts for a few different times and spans around the range step. There looks to be a slight bit more noise all the way below 100Hz, and the 60Hz is very slightly higher.

The range step happened at 330am almost exactly and since the 60Hz line got worse, I'm wondering if there is something that turned on or updated right then.

Non-image files attached to this report

compare_darm_1424082258_1424090900.pdf

compare_darm_1424082258_1424090241.pdf

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Thu, 20 Feb 2025 07:46:56 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82924

TITLE: 02/20 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Relocking
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.42 μm/s
QUICK SUMMARY: Just lost lock from a nearby earthquake. Barely saw it on the picket fence before we lost lock, but our control signals were moving. For the 8 hour lock that just ended, 4 hours ago there was a step down in the range and then less stable range. DARM looks to have more noise in the 80-200Hz area, my screenshot doesn't show it completely. Violin mode 6 was slowly ringing up overnight.

Images attached to this report

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Wed, 19 Feb 2025 22:00:02 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82923

TITLE: 02/20 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

IFO is LOCKING at LOCKING_ALS (Once again, we lose lock in the last few mins of shift...)

IFO is in NLN and OBSERVING as of 03:07 UTC.

Overall very calm shift in which we seem to have improved squeeze locking, improving range to what it was before last weekend.

We had one Lockloss seemingly caused by oscillations in PRCL in the seconds before the losing lock - alog 82916. According to the first OLG PRCL measurements from alog 82920, Elenna found that the PRCL2 gain was low by about 30-40%. Following this, she made a change to up the gain from 1 to 1.4 (alog 82917). Accepted SDF attached.

While 1.4 was a bit too high and caused a PRCL ring-up and a LL at LOWNOISE_LENGTH_CONTROL (where the gain switches on), the next setting of 1.2 worked! We were able to fully automatically re-lock and get to NLN and OBSERVING. Before I went into OBSERVING, I took another OLG PRCL measurement, which is the second measurement in alog 82920.

Other than this, the infamous IY Mode 5_6 Violin has been ringing up, visible in the top right screen of the attached screenshot, which shows mode 6 as slowly increasing since Lock. New settings may be needed for this.

Just as I was about to submit, we had a LL, though there wasn't the characteristic PRCL ring-up from the last few LLs. It also doesn't look environmentally caused since wind is low, there are no EQs and microseism is high, but unchanged mostly from the beginning of the day. Currently experiencing known ALS lock issues.

LOG:

None

Lockloss

Images attached to this report

H1 ISC - Comment to PRCL Open Loop Gain Measurements

elenna.capote@ligo.org — Wed, 19 Feb 2025 20:19:42 -0800

Author: elenna.capote@ligo.org

Report ID: 82922

Just a note that we are trying for a UGF of about 30 Hz here. Right after lock, this is clearly a bit too high, but hopefully with the 20% gain boost after thermalization it will settle closer to 30 Hz.

H1 ISC - Comment to Lockloss 00:41 UTC

ibrahim.abouelfettouh@ligo.org — Wed, 19 Feb 2025 19:14:40 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82921

H1 Back to OBSERVING 03:07 UTC

H1 ISC - PRCL Open Loop Gain Measurements

ibrahim.abouelfettouh@ligo.org — Wed, 19 Feb 2025 19:14:10 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82920

TJ, Ibrahim, Sheila, Elenna

Measured PRCL OLG at 2 different times during NLN - both attached.

First (done by TJ) at 3hrs into NLN - Screenshot 1.

Second at 15 minutes into seperate NLN. This one was done after a PRCL-related lockloss (alog 82916) at which point Elenna changed the PRCL2 Gain from 1 to 1.2 (alog 82917) - Screenshot 2.

Images attached to this report

H1 ISC - Comment to PRLC2 Gain increased

elenna.capote@ligo.org — Wed, 19 Feb 2025 18:02:36 -0800

Author: elenna.capote@ligo.org

Report ID: 82919

This was too high and caused a 70 Hz ring up in PRCL. I put in a gain of 1.2 now.

H1 ISC - PRLC2 Gain increased

elenna.capote@ligo.org — Wed, 19 Feb 2025 17:05:12 -0800

Author: elenna.capote@ligo.org

Report ID: 82917

I increased the PRCL2 gain that is set in lownoise length control from 1.0 to 1.4 to increase the overall PRCL loop gain by 40%. We have been seeing locklosses with 11 Hz oscillations that are probably due to marginal stability in PRCL. I changed line 5577 of the ISC_LOCK guardian, saved, and loaded. Ibrahim will post an alog with more info and open loop gain plots.

H1 ISC - Lockloss 00:41 UTC

ibrahim.abouelfettouh@ligo.org — Wed, 19 Feb 2025 16:45:15 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82916

Lockloss that matches the ones from over the weekend, where PRCL becomes unstable and oscillates at 11Hz in the seconds before the Lockloss.

Lockloss

LHO General - Ops Day Shift End

thomas.shaffer@ligo.org — Wed, 19 Feb 2025 16:31:10 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82914

TITLE: 02/20 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: The shift started out with a lock loss just before commissioning time. We took this opportunity to move PR2 spot while out of lock to find the baffle edges. We then relocked and Sheila and Oli fixed and issue we had causing lock losses at transition from ETMX (alog82912). We went back to observing for a few hours before stepping out to tune the SQZ angle and run a quick PRCL OLG. Results on the latter will be posted by Ibrahim later after he takes another to compare.
LOG:

1556 Lock loss
2133 Observing
0007 Out of observing to tune SQZ and run PRCL OLG
0018 Observing

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
19:34	SAF	Laser Haz	LVEA	YES	LVEA is laser HAZARD!!!	06:13
19:12	FAC	Les Schwab	Xarm	n	Truck tire repair	21:07
20:39	FAC	Eric	EX mech	n	Serial numbers	20:45
21:24	-	Betsy	Opt Lab	n	Parts and more parts	21:52

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Wed, 19 Feb 2025 16:12:11 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82915

TITLE: 02/20 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: USEISM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.60 μm/s
QUICK SUMMARY:

IFO is in NLN and COMISSIONING

The plan is to optimize SQZ via SQZ angle adjustment followed by a PRCL Open Loop Gain Measurement since there is some evidence that PR is experiencing noise at certain problem frequencies. Then, we go back to OBSERVING

H1 General - Back to Observing 2133 UTC

thomas.shaffer@ligo.org — Wed, 19 Feb 2025 14:17:20 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82913

Back to observing after a lock loss, some commissioning time, and trying to fix the transition from etmx lock losses.

useism is still high and our range is a bit low at 145Mpc. If the range doens't improve with more thermalization, we will take it out for some tuning.

H1 ISC - transition to ETMX low noise DARM control causing too low a light level on DCPDs with microseism high

sheila.dwyer@ligo.org — Wed, 19 Feb 2025 13:45:19 -0800

Author: sheila.dwyer@ligo.org

Report ID: 82912

Oli, TJ, Sheila

There have been several locklosses over the last day from the LOWNOISE_ESD_ETMX state, which happened while the gain was ramping down ITMX darm control and ramping up ETMX control. This is similar to what Elenna was trying to avoid by adjusting ramp times in 81260 and 81195, which was also at a time when the microseism was high.

Oli and I found that the problem with some of our transitions today was that the power on the DCPDs was dropping too low during the initial transition, we lost lock when it got to less than 1mA, in one of the sucsesful transitions it was as low as 4mA. We edited the guardian to not turn off the darm boost (DARM1 FM1) before making the transition, and instead we are turning it off directly after transitioning control back to ETMX, before the other filter changes that happen in this state.

This is the boost that we thought was causing locklosses when ramping off, 81638 which motivated Erik's quadratic ramping change 82263 which was then reverted 82284 82277. Today Oli and I increased the ramp time on this filter from 10 to 30 seconds. We have make the guardian wait the full 30 seconds for this ramp time, so this is making us wait longer in this state.

The attached screenshot shows the transition with the boost on on the left, and off on the right, the wiggle in the DCPD sum is about 1 mA rather than 15mA.

Oli is thinking about adding a check for DCPD sum dropping low to the lockloss tool.

Images attached to this report

H1 SEI - FAMIS ISI CPS check

ryan.crouch@ligo.org — Wed, 19 Feb 2025 12:19:49 -0800

Author: ryan.crouch@ligo.org

Report ID: 82911

HAM7 & 8 look less noisy at high frequency, same with the BSCs especially ETMY.

Non-image files attached to this report

CPS_spectra_12:04-02_19_2025.pdf

H1 CDS - Comment to EY timing error tracked to bad timing fanout port

david.barker@ligo.org — Wed, 19 Feb 2025 11:57:26 -0800

Author: david.barker@ligo.org

Report ID: 82910

FRS33349

H1 General - Comment to OPS OWL report SDF diffs

camilla.compton@ligo.org — Wed, 19 Feb 2025 11:18:22 -0800

Author: camilla.compton@ligo.org

Report ID: 82909

H1:SQZ-LO_SERVO_IN1GAIN was left at -15 by accident, reverted to -12 and saved in sdf.

SQZ

H1 SQZ - SQZ pico controller has been on

sheila.dwyer@ligo.org — Wed, 19 Feb 2025 11:00:21 -0800

Author: sheila.dwyer@ligo.org

Report ID: 82908

Nutsinee pointed us to this 66765 where the squeezer pico was left on and caused a large line.

Indeed, the HAM7/SQZT7 pico has been on since Jan 7th, when we were making homodyne measurements 82153 . This must have been accepted in SDF, but I don't see any alog about it on the 7th.

LHO General - Comment to OPS Eve Shift Summary

david.barker@ligo.org — Wed, 19 Feb 2025 10:16:32 -0800

Author: david.barker@ligo.org

Report ID: 82907

Lockloss is coincident with a vacuum glitch at the X-arm beamtube ion pump at X6 (100m from EX).

Images attached to this report

LHO VE - Wed CP1 Fill

david.barker@ligo.org — Wed, 19 Feb 2025 10:11:45 -0800

Author: david.barker@ligo.org

Report ID: 82906

Wed Feb 19 10:05:46 2025 INFO: Fill completed in 5min 43secs

TCmins [-62C, -60C] OAT (+1C, 34F) DeltaTempTime 10:05:47

Images attached to this report

H1 CAL - Comment to Calibration locklosses

vladimir.bossilkov@ligo.org — Wed, 19 Feb 2025 09:17:16 -0800

Author: vladimir.bossilkov@ligo.org

Report ID: 82905

Tagging CAL properly

CAL

H1 CAL - Comment to Calibration sweeps losing lock.

vladimir.bossilkov@ligo.org — Wed, 19 Feb 2025 09:08:27 -0800

Author: vladimir.bossilkov@ligo.org

Report ID: 82904

Despite the lockloss, I was able to utilise the log file saved in /opt/rtcds/userapps/release/cal/common/scripts/simuLines/logs/H1/ (log file used as input into simulines.py), to regenerate the measurement files.

As you can imagine the points where the data is incomplete are missing but 95% of the sweep is present and fitting all looks great.
So it is in some way reassuring that in case we lose lock during a measurement, data gets salvaged and processed just fine.

Report attached.

Non-image files attached to this report

H1_calibration_report_20250215T193653Z.pdf

H1 General - Lock loss 1556UTC and commissioning start

thomas.shaffer@ligo.org — Wed, 19 Feb 2025 08:33:49 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82903

We had a lock loss at 1556UTC (1424015786) tagged as an ETM glitch. We are going to take this "opportunity" to start moving the spot on PR2 in the direction to find the other edge of clipping. After this we will try to lock again and work on PRCL OLG, SQZ, and other issues we can address within the commissioning window of 1700-2000UTC (9-12PT).

H1 CDS - CDS Maintenance Summary: Tuesday 18th February 2025

david.barker@ligo.org — Wed, 19 Feb 2025 08:19:17 -0800

Author: david.barker@ligo.org

Report ID: 82902

WP12321 Add FMCSSTAT channels to EDC

Erik, Dave:

Recently FMCS-STAT was expanded to monitor FCES, EX and EY temperatures. These additional channels were added to the H1EPICS_FMCSSTAT.ini file. DAQ and EDC restart was required

WP12339 TW1 raw minute trend file offload

Dave:

The copy of the last 6 months of raw minute trends from the almost full SSD-RAID on h1daqtw1 was started. h1daqnds1 was temporarily reconfigured to serve these data from their temporary location while the copy proceeds.

A restart of h1daqnds1 daqd was needed, this was done when the DAQ was restarted for EDC changes.

WP12333 New digivideo server and network switch, move 4 cameras to new server

Jonathan, Patrick, Fil, Dave:

A new Cisco POE network switch, called sw-lvea-aux1, was installed in the CER below the current sw-lvea-aux. This is a dual powered switch, both power supplies are DC powered. Note, sw-lvea-aux has one DC and one AC power supply, this has been left unchanged for now.

Two multimode fiber pairs were used to connect sw-lvea-aux1 back to the core switch in the MSR.

For testing, four relatively unused cameras were moved from h1digivideo1 to the server h1digivideo4. These are MC1 (h1cam11), MC3 (h1cam12), PRM (h1cam13) and PR3 (h1cam14).

The new server IOC is missing two EPICS channels compared with the old IOC, _XY and _AUTO. To green up the EDC due to these missing channels a dummy IOC is being ran (see alog).

The MC1, MC3, PRM and PR3 camera images on the control room FOM (nuc26) started showing compression issues, mainly several seconds of smeared green/magenta horizontal stripes every few minutes. This was tracked to maximizing CPU resources, and has been temporaily fixed by stopping one of these camera viewers.

EY Timing Fanout Errors

Daniel, Marc, Jonathan, Erik, Ibrahim, Dave:

Soon after lunchtime the timing system started flashing RED on the CDS overview. Investigation tracked this down to the EY fanout, port_5 (numbering from zero, so the sixth physical port). This port sends the timing signal to h1iscey's IO Chassis LIGO Timing Card.

Marc and Dave went to EY at 16:30 with spare SFPs and timing card. After swapping these out with no success, the problem was tracked to the fanout port itself. With the original SFPs, fiber and timing card, using port_6 instead of port_5 fixed the issue.

For initial SFP switching, we just stopped all the models on h1iscey (h1iopiscey, h1iscey, h1pemey, h1caley, h1alsey). Later when we replaced the timing cards h1iscey was fenced from the Dolphin fabric and powered down.

The operator put all EY systems (SUS, SEI and ISC) into a safe mode before the start of the investigation.

DAQ Restart

Erik, Dave:

The 0-leg restart was non-optimal. A new EDC restart procedure was being tested, whereby both trend-writers were turned off before h1edc was restarted to prevent channel-hopping which causes outlier data.

The reason for the DAQ restart was an expanded H1EPICS_FMCSSTAT.ini

After the restart of the 0-leg it was discovered that there were some naming issues with the FMCS STAT FCES channels. Erik regenerated a new H1EPICS_FMCSSTAT.ini and the EDC/0-leg were restarted again.

Following both 0-leg restarts, FW0 spontaneously restarted itself after running only a few minutes.

When the EDC and the 0-leg were stable, the 1-leg was restarted. During this restart NDS1 came up with a temporary daqdrc serving TW1 past data from its temporary location.

Reboots/Restarts

Tue18Feb2025
LOC TIME HOSTNAME MODEL/REBOOT
09:45:03 h1susauxb123 h1edc[DAQ] <<< first edc restart, incorrect FCES names
09:46:02 h1daqdc0 [DAQ] <<< first 0-leg restart
09:46:10 h1daqtw0 [DAQ]
09:46:11 h1daqfw0 [DAQ]
09:46:12 h1daqnds0 [DAQ]
09:46:19 h1daqgds0 [DAQ]
09:47:13 h1daqgds0 [DAQ] <<< GDS0 needed a restart
09:52:58 h1daqfw0 [DAQ] <<< Sponteneous FW0 restart

09:56:21 h1susauxb123 h1edc[DAQ] <<< second edc restart, all channels corrected
09:57:44 h1daqdc0 [DAQ] <<< second 0-leg restart
09:57:55 h1daqfw0 [DAQ]
09:57:55 h1daqtw0 [DAQ]
09:57:56 h1daqnds0 [DAQ]
09:58:03 h1daqgds0 [DAQ]

10:03:00 h1daqdc1 [DAQ] <<< 1-leg restart
10:03:12 h1daqfw1 [DAQ]
10:03:13 h1daqnds1 [DAQ]
10:03:13 h1daqtw1 [DAQ]
10:03:21 h1daqgds1 [DAQ]
10:04:07 h1daqgds1 [DAQ] <<< GDS1 restart

10:04:48 h1daqfw0 [DAQ] <<< Spontaneous FW0 restart

17:20:37 h1iscey ***REBOOT*** <<< power up h1iscey following timing issue on fanout port
17:22:17 h1iscey h1iopiscey
17:22:30 h1iscey h1pemey
17:22:43 h1iscey h1iscey
17:22:56 h1iscey h1caley
17:23:09 h1iscey h1alsey

DAQ

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Wed, 19 Feb 2025 07:33:48 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82901

TITLE: 02/19 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 141Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 1mph Gusts, 0mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.68 μm/s
QUICK SUMMARY: Rough night for locking. We are currently in a 45 min lock, range trending down. useism is peaking above 1 um/s, so we might have a rough day as well. There is planned commissioning time today from 1700-2000UTC (9-12PT).

H1 General - Comment to OPS OWL assistance

ryan.crouch@ligo.org — Wed, 19 Feb 2025 07:04:31 -0800

Author: ryan.crouch@ligo.org

Report ID: 82900

There's been a high stage lockloss between the last 2 acquisitions, at state 558.

H1 General - OPS OWL assistance

ryan.crouch@ligo.org — Wed, 19 Feb 2025 06:56:28 -0800

Author: ryan.crouch@ligo.org

Report ID: 82899

H1 called for help again at 14:50 UTC, from the TO_NLN timer expiring. By the time I logged in we were ready to go into Observing.

14:53 UTC Observing

H1 General - OPS OWL report SDF diffs

ryan.crouch@ligo.org — Wed, 19 Feb 2025 01:28:14 -0800

Author: ryan.crouch@ligo.org

Report ID: 82898

To get in Observing I had to accept some SDF diffs for SQZ, and PCALY. There was also still a PEM CS excitation point open as well. There was a notification about PCALY OFS servo malfunction so I looked at it and it was railed at -7.83, so I toggled it off and back on and it brought it back to a good value. I also did not receive a call, a voicemail just appeared.

09:21 UTC observing

CAL, SQZ

Images attached to this report

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Tue, 18 Feb 2025 22:07:37 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82897

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

IFO is in MAINTENANCE and LOCKING_ALS

Locking has been near-impossible due to microseism and oppurtunistic earthquakes.

Essentially been dealing with the same issues the whole shift. IFO alignment is actually quite good since we have caught DRMI over 10 times automatically and very quickly but we end up losing lock due to clear instability as a cause of EQs that are exacerbated by over 1 micron/sec secondary microseism.

3 of this shift's EQs have been over 5.0 and we have lost lock around the arrival of the S or R waves each time, with 2 of those being at TRANSITION_FROM_ETMX, around an hour into acquisition, resulting in the long lock acquisitions we're experiencing. Other than TRANSITION, we've lost lock at or before DRMI with ASC and LSC signals oscillating a lot.

As I type this, we just lost lock for the 3rd time at around LOWNOISE_ESD_ETMX so there is potentially something wrong with this state specifically, despite CPS signals showing noise at the same time as the lockloss. The good news is I haven't been experiencing ALS issues at all this shift.

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
19:34	SAF	Laser Haz	LVEA	YES	LVEA is laser HAZARD!!!	06:13
15:57	FAC	Kim, Nelly	EY, EX, FCES	n	Tech clean	18:40
17:27	CDS	Jonathan, Fil, Austin	MSR, CER	n	Move temp switch and camera server	20:10
17:28	VAC	Ken	EY	n	Disconnect compressor electrical	19:49
17:35	VAC	Travis	EX	n	Compressor work	18:33
17:46	VAC	Gerardo, Jordan	MY	n	CP4 check	19:16
17:49	SQZ	Sheila, Camilla	LVEA	YES	SQZ table meas.	19:39
18:19	SUS	Jason, Ryan S	LVEA	YES	PR3 OpLev recentering at VP	21:05
18:19	SUS	Matt, TJ	CR	n	ETMX TFs for rubbing	21:21
18:37	FAC	Tyler	Opt Lab	n	Check on lab	19:03
18:39	CDS	Erik	CER	n	Check on switch	19:16
18:41	FAC	Kim	LVEA	yes	Tech clean	19:51
18:56	VAC	Travis	Opt Lab	n	Moving around flow bench	19:03
18:58	PEM	Robert	LVEA	yes	Check on potential view ports	19:51
19:04	FAC	Tyler	Mids	n	Check on 3IFO	19:25
20:21	VAC	Gerardo	LVEA	yes	Checking cable length on top of HAM6	20:50
20:27	CDS	Fil	EY	n	Updating drawings	22:14
20:46	PEM	Robert	LVEA	yes	Viewport checks	21:26
20:51	VAC	Janos	EX	n	Mech room work	21:25
21:18	OPS	TJ	LVEA	-	Sweep	21:26
21:19	FAC	Chris	X-arm	n	Check filters	22:54
22:44	PEM	Robert	LVEA	yes	Setup tests	00:06
22:46	SQZ	Sheila, Camilla, Matt	LVEA	yes	SQZ meas at racks	00:06
00:19	CDS	Dave, Marc	EY	N	Timing card issue fix	01:19

H1 CDS - Dummy IOC running to

david.barker@ligo.org — Tue, 18 Feb 2025 21:39:50 -0800

Author: david.barker@ligo.org

Report ID: 82896

Jonathan, Patrick, Dave:

Following the move of MC1, MC3, PRM and PR3 cameras from the old h1digivideo1 server to h1digivideo4 running the new EPICS IOC, two channels per camera were no longer present. This meant the EDC has been running with 8 disconnected channels

To "green up" the EDC until such time as we can restart the DAQ, I am running a dummy IOC on cdsws33 which serves these channels.

These cameras have sequentially numbers, CAM[11-14], and the eight channels in question are:

H1:VID-CAM11_AUTO
H1:VID-CAM11_XY
H1:VID-CAM12_AUTO
H1:VID-CAM12_XY
H1:VID-CAM13_AUTO
H1:VID-CAM13_XY
H1:VID-CAM14_AUTO
H1:VID-CAM14_XY

H1 CDS - EY timing error tracked to bad timing fanout port

david.barker@ligo.org — Tue, 18 Feb 2025 21:34:02 -0800

Author: david.barker@ligo.org

Report ID: 82895

Daniel, Patrick, Jonathan, Erik, Fil, Ibrahim, Marc, Dave:

Starting around lunchtime and getting more frequent after 2pm the Timing system was showing errors with EY's fanout port_5 (the sixth port). This port sends timing to h1iscey's IO Chassis timing card.

At EY, Marc and I replaced the SFPs in the fanout port_5 and h1iscey's timing card. At this point we could not get port_5 to sync. We tried replacing the timing card itself, but no sync was possible using the new SFPs. Installing the original SFPs restored the sync, but the timing problem was still there. Moving to the unused port_7 (seventh port) of the fanout fixed the problem. We put the original timing card back into the IO Chassis, so at this point all the hardware was original and the fanout SFP had been moved from port_5 to port_6.

H1 SQZ - Comment to Something in SQZ Oscillating at 14kHz

sheila.dwyer@ligo.org — Tue, 18 Feb 2025 21:04:48 -0800

Author: sheila.dwyer@ligo.org

Report ID: 82894

1st photo, CLF OLG

2nd photo, LO OLG

3rd photo, OPO OLG

4th photo, spectrum of LO loop I Mon. We also looked at OPO and SHG demod spectra and saw 14kHz in those as well.

Images attached to this report

H1 General - OPS Midshift Update

ibrahim.abouelfettouh@ligo.org — Tue, 18 Feb 2025 19:27:35 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82893

We're having locking troubles due to Microseism and EQs.

After failing to get past DRMI and experiencing ~10 LLs, we finally did it and got all the way to powering up. Then a 5.6 EQ hit and we lost lock at TRANSITION_ETMX, with clear seismic signs in the few seconds leading up to the Lockloss (similar to the last LL). Lock reacquisition has been as rocky as pre-EQ. Meanwhile, Microseism has continued to increase, with traces now passing the 1 micron threshold, making lock reacquisiton harder yet.

We've just gotten back to PRMI post EQ so hoping this will be a successful reacquisition.

H1 SQZ - Something in SQZ Oscillating at 14kHz

camilla.compton@ligo.org — Tue, 18 Feb 2025 17:01:37 -0800

Author: camilla.compton@ligo.org

Report ID: 82892

Sheila, Matt, Daniel, Camilla.

We went to the SQZ racks to check the loops, all (LO, OPO, CLF) looked stable, the OPO looked peaky but stable. Once we opened beamdiv and were squeezing there was the large oscillation in ndscopes which SR785 showed to be at 14kHz.

Issues seen:

Yesterday AM: 82874 and plot attached, issue started when IFO unlocked and Beam divertor closed, continued once IFO re-locked and SQZ injected.
Today while we were measuring SQZ loops. plot attached, issues worse and OPO_TRANS_POWER bad when in FDS with beam div open (POISTION = 0) and LO locked, issues less when beamdiv closed.

We think it could be FSS or PMC or laser going multi mode. Can see EOMRMSMON gets worse when this noise appears. Will continue to investigate tomorrow.

Tagging OpsInfo, if you see this oscillation i.e. SQZ is injected but DARM looks terrible like NO SQZ, try taking SQZ out and in again, if this doesn't help, go to Observing with NO SQZ tonight, using Ryan's wiki Instructions.

OpsInfo

Images attached to this report

H1 SQZ - SQZ_ANG_SERVO set to False

camilla.compton@ligo.org — Tue, 18 Feb 2025 16:32:15 -0800

Author: camilla.compton@ligo.org

Report ID: 82891

Due to so much SQZ strangeness over the weekend, Sheila set the sqzparams.py use_sqz_ang_servo to False and I changed the SQZ_ANG_ADJUST nominal state to DOWN and reloaded SQZ_MANAGER and SQZ_ANG_ADJUST.

We set the H1:SQZ-CLF_REFL_RF6_PHASE_PHASEDEG to a normal good value of 190. If the operator thinks the SQZ is bad and wants to change this to maximize the range AFTER we've been locked 2+ hours, they can. Tagging OpsInfo.

OpsInfo

LHO General - Ops Day Shift End

thomas.shaffer@ligo.org — Tue, 18 Feb 2025 16:30:56 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82890

TITLE: 02/19 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Maintenance day. Notable tasks from today's maintenance are below. We recently had another lock loss, we have started initial alignment and will start main locking shortly.

Some squeezer table work
MC1,MC3, PRM, PR3 camera server change
Timing card at EY started to show signs of failing in the past few hours. Dave and others are currently investigating this.
DAQ and NDS1 restart
Heater element swap, 3A

LOG:

2244 Back to low noise, but some squeezer work needs to happen
2357 Lock loss

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
19:34	SAF	Laser Haz	LVEA	YES	LVEA is laser HAZARD!!!	06:13
15:33	FAC	Kim, Nelly	Opt Lab	n	Tech clean	15:57
15:51	VAC	Ken	EX	n	Compressor electrical	17:19
15:52	VAC	Janos, contractor	EX	n	Compressor work	17:35
15:57	FAC	Kim, Nelly	EY, EX, FCES	n	Tech clean	18:40
15:59	FAC	Eric	Mech room	n	Heater 3a replacement	17:27
16:58	-	Christina, truck	VPW	n	Large truck delivery to VPW	16:59
17:27	CDS	Jonathan, Fil, Austin	MSR, CER	n	Move temp switch and camera server	20:10
17:28	VAC	Ken	EY	n	Disconnect compressor electrical	19:49
17:35	VAC	Travis	EX	n	Compressor work	18:33
17:46	VAC	Gerardo, Jordan	MY	n	CP4 check	19:16
17:49	SQZ	Sheila, Camilla	LVEA	YES	SQZ table meas.	19:39
17:50	SUS	Jason	LVEA	yes	PR3 OpLev alignment	18:04
18:19	SUS	Jason, Ryan S	LVEA	YES	PR3 OpLev recentering at VP	21:05
18:19	SUS	Matt, TJ	CR	n	ETMX TFs for rubbing	21:21
18:37	FAC	Tyler	Opt Lab	n	Check on lab	19:03
18:39	CDS	Erik	CER	n	Check on switch	19:16
18:41	FAC	Kim	LVEA	yes	Tech clean	19:51
18:56	VAC	Travis	Opt Lab	n	Moving around flow bench	19:03
18:58	PEM	Robert	LVEA	yes	Check on potential view ports	19:51
19:04	FAC	Tyler	Mids	n	Check on 3IFO	19:25
20:21	VAC	Gerardo	LVEA	yes	Checking cable length on top of HAM6	20:50
20:27	CDS	Fil	EY	n	Updating drawings	22:14
20:46	PEM	Robert	LVEA	yes	Viewport checks	21:26
20:51	VAC	Janos	EX	n	Mech room work	21:25
21:18	OPS	TJ	LVEA	-	Sweep	21:26
21:19	FAC	Chris	X-arm	n	Check filters	22:54
22:44	PEM	Robert	LVEA	yes	Setup tests	00:06
22:46	SQZ	Sheila, Camilla, Matt	LVEA	yes	SQZ meas at racks	00:06
00:19	CDS	Dave, Marc	EY	N	Timing card issue fix	01:19

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Tue, 18 Feb 2025 16:28:56 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 82889

TITLE: 02/19 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT_USEISM
    Wind: 9mph Gusts, 5mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.77 μm/s
QUICK SUMMARY:

IFO is in INITIAL_ALIGNMENT and MAINTENANCE

We're still recovering from maintenance today with a few key issues:

Dave and Marc working on EY CDS Timing, potentially needing us to go down
SQZ Team says the Squeezer is "as ready to go as it has been all weekend"
ALS Locking issues still prevalent

Given all that, we shall begin locking when initial alignment is done.

LHO VE - Comment to Corner RGA Non Responsive

jordan.vanosky@ligo.org — Tue, 18 Feb 2025 16:14:41 -0800

Author: jordan.vanosky@ligo.org

Report ID: 82888

2/18/25

Today, Erik was able to reconfigure the IPs of the RGAs. Able to ping all three RGAs currently connected to network, and corner monitoring scans have resumed. Filaments are turned on for all three RGAs, Corner, HAM6 and EX. Reminder, both HAM6 and EX have 10 l/s pumps on RGA volume.

H1 SUS - Comment to Checking SUS TFs for rubbing

thomas.shaffer@ligo.org — Tue, 18 Feb 2025 14:58:34 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82887

PRM LPY, and BS LPY. I had to turn off the BS OpLev damping, which is mentioned in the Jeff K TF instructions wiki.

Images attached to this report

LHO VE - New EX clean air supply is installed

janos.csizmazia@ligo.org — Tue, 18 Feb 2025 14:56:28 -0800

Author: janos.csizmazia@ligo.org

Report ID: 82886

The new clean air supply (compressor, tank, dryer and a series of extra filters), which was received in the end of 2024, was installed in the EX mechanical room as a replacement for the old system. The installation work was carried out in the last few weeks, the last step - the startup by Rogers Machinery - happened today. This new system has a 69 cfm air delivery operating with 3 pcs. of 7.5 HP motors (in sum 22.5 HP). In comparison, the old system had a 50 cfm air delivery, operating with 5 pcs. of 5 HP motors (in sum 25 HP). Moreover, the new system (unlike the old one) has an automatic dew point monitor, and a complete pair of redundant dryer towers. So, this new system is a major improvement. The reason for this 69 cfm limit (and not more) is that the cooling of the compressor units in the MER is still feasible, moreover, the filters and the airline do not need any upgrades, they can still accommodate the airflow. Both the new and old systems are able to produce at least -40 deg F dew point air on paper. During the startup, the new system was however able to produce much better than this - it was ~-70 deg F (and dropping) - as you can see in the attached photo. Last but not least, a huge congratulations to the Vacuum team for the installation, as this was the first instance, when the installation of a clean air system was carried out by LIGO staff, so this is indeed a huge achievement. Also, big thanks to Chris, who cleaned some parts for the compressor, to Tyler, who helped a lot in the heavy lifting, and to Richard & Ken, who did the electrical wiring. From next week on, we repeat this same installation at the EY station.

Images attached to this report

H1 SUS - Checking SUS TFs for rubbing

matthewrichard.todd@ligo.org — Tue, 18 Feb 2025 14:29:53 -0800

Author: matthewrichard.todd@ligo.org

Report ID: 82884

[ Matt, TJ ]

We looked at the transfer functions of the suspensions of the Test Masses, SR3 and PRM (top stage of each), to see if we could see signs of rubbing. This is a limited number of transfer functions; however, it does seem like there is some peak shifting in the ITMY-P.

Images attached to this report

H1 General - LVEA Swept

thomas.shaffer@ligo.org — Tue, 18 Feb 2025 14:27:50 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82885

I swept the LVEA after maintenance activities today. I unplugged one power strip in the CER, and heard a UPS in one of the vacuum racks going off. I silenced the alarm and talked to Gerardo and Richard, but we should keep an ear out.

H1 AOS - WP 12333 Installed sw-lvea-aux1 in the CER, moved 4 cameras to the switch and to h1digivideo4

jonathan.hanks@ligo.org — Tue, 18 Feb 2025 14:02:38 -0800

Author: jonathan.hanks@ligo.org

Report ID: 82882

As per WP 12333 we installed a POE switch (sw-lvea-aux1) in the CER, moved four cameras onto the switch and migrated them to h1digivideo4. This is to expand and test our infrastructure to host more digital cameras. Jonathan H. and Austin F. moved the switch from its test location in the MSR to the CER. As part of the work we moved sw-lvea-aux up 1 space in the rack to make more room and installed a cable management bar beneath the switches to provide some strain relief. Fil C. setup the DC power for the switch. We had wanted to also convert sw-lvea-aux to full DC power, but Fil would like us to split the load between the two switches more before removing the 1 AC power supply from sw-lvea-aux. Patrick worked to migrate the cameras from h1digivideo1 to h1digivideo4.

H1 AOS - PR3 Optical Lever

jason.oberling@ligo.org — Tue, 18 Feb 2025 13:29:32 -0800

Author: jason.oberling@ligo.org

Report ID: 82883

J. Oberling, R. Short

After the recent PRC alignment work (moving PR3 to better center the beam on PR2) the OpLev beam had fallen off of its QPD, so today I attempted to re-center the QPD. Using only the translation stages, I could not re-center the QPD since the horizontal translation stage hit its max travel limit well before the beam was back on the QPD (SUM counts went from ~700 to ~850, well short of the usual ~22k). I enlisted Ryan S. to help and we set out to adjust the OpLev beam alignment from the transmitter. Turns out that the beam gets clipped before we can get it centered on the QPD. We first tried to move the translation stage away from its limit but could only get the beam on 2 of the QPD segments (segments 1 and 3) before the SUM counts started dropping; at no point could we get the beam onto QPD segments 2 and 4 in this configuration. We then moved the horizontal stage to its limit and tried to align the beam onto the QPD; this worked a little better, but still not great. The best SUM counts we could get and have a "centered" QPD was ~17k, roughly 75% of the total SUM counts for this OpLev, so still some significant clipping. We decided to unclip the beam to make the OpLev more trustworthy (we've had questions about this OpLev in the past). Max SUM counts were ~22.7k, and this gives a Yaw reading of roughly -12.5 µrad; any closer to zero and the beam begins to clip again. We left the OpLev in this configuration and will investigate the clipping at a later date.

Tagging OpsInfo: Around -12.5 µrad is the current "yaw zero" for the PR3 OpLev until we can figure out and alleviate the clipping.

As for the clipping, my best guess at this point is we're clipping somewhere on/in the ~4' long tube that runs from the exit viewport for the OpLev receiver and the OpLev's QPD. We'll have to climb on top of HAM3 to check this, which we will do at a later date.

This closes WPs 12336 and 12341.

Edit: Fixed typo in yaw reading in bolded sentence (12.7 to 12.5).

OpsInfo

H1 SQZ - SHG EOM, AOM and fiber pointing realigned, powers measured.

camilla.compton@ligo.org — Tue, 18 Feb 2025 12:33:27 -0800

Author: camilla.compton@ligo.org

Report ID: 82881

Shiela, Camilla, Sheila and Vicky moved the AOM and realigned in 80830.

Summary: Today we measured the powers on SQZT0, see attached photo. Aimed to understand where we were loosing our green light as we had to turn down the OPO setpoint last week 82787. Adjusted SHG EOM, AOM and fiber pointing are dramatically increased available green light. OPO setpoint back to 80uW with plenty of extra green avaible.

After taking the attached power measurements we could see we the SHG conversion was fine, 130mW green out of SHG for 360mW of IR in.

We were loosing a lot of power through the EOM 96mW in to 76mW out (expect ~100%). We could see this clipping in yaw by taking a photo. Sheila adjusted the EOM alignment increasing the power out to 95mW.

Then AOM and fiber aligned following 72081:

1) set the ISS drive point at 0V to make only 0th order beam and check 90% of AOM throughput with power meter. Started with 95mW in, 50mW out. Improved to 95mW in 80mW out = 84%.

2) set the ISS drive point at 5V and align the AOM to maximize the 1st order beam (which is left side of 0th order beam looking from the laser side of SQZT0). After the AOM alignment, the 1st order beam was 27.5 mW and the 0th order beam was 49 mW. We measured again the AOM throughput including both 0th and 1st order beam. The AOM throughput was 77.5mW/93mW = 83%.

3) set the ISS drive point at 5V and align the fiber by maximizing the H1:SQZ-OPO_REFL_DC_POWER. I needed to adjust the SHG waveplate to reduce power to stop PD saturating

After this alignment, the SHG output is 42.7 mW, the pump going to fiber is 20.5 mW, and the rejected power is 2.7 mW. The ISS can be locked with OPO trans of 80uW while the ISS control monitor is 7.0. Also checked the OPO temperature.

Note that depending on the SHG PZT voltage, the power does change. Maybe cause by an alignment change form the PZT.

As ISS control monitor is 7.0 is a little high with 26.5mW SHG launched (OPO unlocked), I further turned the SHG launch power down to 20mW and adjusted the HAM7 rejected light. ISS control monitor left at 5.4 which is closer to the middle of the 0-10V range.

Non-image files attached to this report

SQZT0_18Feb.pdf

LHO VE - Tue CP1 Fill

david.barker@ligo.org — Tue, 18 Feb 2025 10:44:40 -0800

Author: david.barker@ligo.org

Report ID: 82880

Tue Feb 18 10:08:06 2025 INFO: Fill completed in 8min 3secs

Gerardo confirmed a good fill curbside. TCmins [-51C, -48C] OAT (+2C, 36F) DeltaTempTime 10:08:06.

missing data in plot is due to DAQ restart at that time.

Images attached to this report

H1 ISC - Comment to MICH, PRCL, SRCL displacments in long vs short locks

elenna.capote@ligo.org — Tue, 18 Feb 2025 10:35:45 -0800

Author: elenna.capote@ligo.org

Report ID: 82879

I'm comparing plots that Oli made in this alog to a plot I added to this alog from early O4a where we were having frequent locklosses due to marginal stability in PRCL. The ring up looks very similar and I would guess that we should measure the PRCL OLG and adjust the gain. Just scrolling back the last few days on the summary pages, I don't visually see the excess noise around 11 Hz for a long time before the locklosses, like we saw in O4a, but that doesn't mean much since I could be fooled by the color scale.

H1 CAL - Calibration sweeps losing lock.

vladimir.bossilkov@ligo.org — Tue, 18 Feb 2025 10:03:32 -0800

Author: vladimir.bossilkov@ligo.org

Report ID: 82878

I reviewed the weekend lockloss where lock was lost during the calibration sweep on Saturday.

I've compared the calibration injections and what DARM_IN1 is seeing [ndscopes], relative to the last successful injection [ndscopes].
Looks pretty much the same but DARM_IN1 is even a bit lower because I've excluded the last frequency point in the DARM injection which sees the least loop suppression.

It looks like this time the lockloss was a coincidence. BUT. We desperately need to get a successful sweep to update the calibration.
I'll be reverting the cal sweep INI file, in the wiki, to what was used for the last successful injection (even though it includes that last point which I suspected caused the last 2 locklosses), out of abundance of caution and hoping the cause of locklosses is something more subtle that I'm not yet catching.

CAL

Images attached to this report

H1 ISC - MICH, PRCL, SRCL displacments in long vs short locks

camilla.compton@ligo.org — Tue, 18 Feb 2025 09:26:18 -0800

Author: camilla.compton@ligo.org

Report ID: 82877

The operator team have been finding 11Hz oscillation locklosses. Attached is the spectrum of MICH, PRCL and SRCL from one of our last long (2 day) locks to a more recent 6 hour lock. There is a debatable PRCL bump around 10-11Hz.

Images attached to this report

H1 CDS - Comment to H1 Wake Up Due To: Due to BS Camera No Longer Updating & Taking CAMERA_SERVO Out Of Nominal

corey.gray@ligo.org — Tue, 18 Feb 2025 09:06:27 -0800

Author: corey.gray@ligo.org

Report ID: 82876

Forgot once again to note timing for this wake-up. This wake-up was at 233amPDT (1033utc), and I was roughly done with this work in about 45min after phoning Dave for help.

H1 AOS - Comment to H1 Wake Up Call Due to ALS EY Diffs

corey.gray@ligo.org — Tue, 18 Feb 2025 08:58:28 -0800

Author: corey.gray@ligo.org

Report ID: 82875

Here's the lockloss that preceded this 1253amPDT (853utc) Wake-up call (the one where I happened to still be up at 1115pmPDT); and it does not have an EQ tag, but I could have sworn I remembered hearing Verbal going to EQ Mode a few min before the lockloss---this is why I stayed up to run an alignment! Since I was up, this is the one where I tried to help H1 by running an alignment before trying to go to bed, but ended up fighting H1_MANAGER with the alignment attempts. Then I was awakened just before 1am for the SDF diffs noted above.

This wake-up call was only me getting out of bed for a few minutes to ACCEPT the ALS SDF diffs (which might have been due to me and my errant alignments).

H1 SQZ - SQZ_ANG_SERVO strangeness

camilla.compton@ligo.org — Tue, 18 Feb 2025 08:56:13 -0800

Author: camilla.compton@ligo.org

Report ID: 82873

After Ryan S and I changed the SQZ ang servo H1:SQZ-ADF_OMC_TRANS_PHASE yesterday, the SQZ was unhappy overnight, plot, and the servo failed to work for a few hours, should be keeping H1:SQZ-ADF_OMC_TRANS_SQZ_ANG at zero but from the attached plot, clearly wasn't.

On the positive, the SHG power has now increased to 130mW and is more stable since the LVEA temperatures are stable again.

Images attached to this report

H1 SQZ - Comment to Trouble with SQZ FC this AM.

camilla.compton@ligo.org — Tue, 18 Feb 2025 08:55:22 -0800

Author: camilla.compton@ligo.org

Report ID: 82874

Attaching the plot from after Corey got the SQZ locked and it was bad, you can see it looks like one of the loops was oscillating, plot attached. Compare to normal SQZ plot.

Images attached to this report

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Tue, 18 Feb 2025 07:34:37 -0800

Author: thomas.shaffer@ligo.org

Report ID: 82872

TITLE: 02/18 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 2mph Gusts, 1mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.47 μm/s
QUICK SUMMARY: Lost lock at 1507 UTC (0707 PT). Maintenance day today. No active alarms.

H1 CDS - workstations updated

erik.vonreis@ligo.org — Tue, 18 Feb 2025 07:05:37 -0800

Author: erik.vonreis@ligo.org

Report ID: 82871

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

H1 General - Ops Eve Shift End

oli.patane@ligo.org — Mon, 17 Feb 2025 22:02:52 -0800

Author: oli.patane@ligo.org

Report ID: 82870

TITLE: 02/18 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Currently Observing and have been Locked for almost 1 hour.

Two locklosses during my shift, and they both had that weird oscillation in DARM right before the lockloss (see 82847). Relocking went okay as long as I ran an initial alignment.

First relocking:
At the start of the initial alignment during green arms, I did get the ALSX issue where it's locked but the WFS won't turn on. I Forced the auto-centering for the WFS and that was all it needed.
Once we got back up to NLN we were having issues with the filter cavity losing lock (similar to the issues from the rest of this weekend). It was losing lock at different places in the locking process (FIND_IR, GR_VCO_LOCKING, TRANSITION_IR_LOCKING, etc). I tried just running SQZ_MANAGER through DOWN and back up but that didn't work. I then tried moving FC1&2 a bit to get them back to where they were during our last lock but that also didn't work. I then just tried what Ryan S did yesterday (82840) - I paused SQZ_MANAGER in LOCK_CLF and adjusted the OPO temp. That worked well and we were then able to lock the filter cavity, start squeezing, and get back into Observing. Tagging sqz
Second relocking:
I just made sure to immediately run an initial alignment and there were no issues getting back to NLN and Observing.
LOG:

00:06 Lockloss
    - started an inital alignment
        - ALSX was locked (but oscillating weirdly) around 1 but the WFS wouldn't turn on - the auto-centering was off (we've been seeing this recently sometimes). I Forced the auto-centering and the WFS turned on and took ALSX up to 1.2 right away
    - Lockloss from TURN_ON_BS_STAGE2
    - Lockloss from PRMI_ASC

02:20 NOMINAL_LOW_NOISE
    - FC losing lock during different stages in the locking process (FIND_IR, GR_VCO_LOCKING, TRANSITION_IR_LOCKING, etc.)
    - Ran SQZ_MANAGER through DOWN and back up - didn't work
    - Adjusted FC1&2 a bit to get them back to where they were during our last lock - didn't work (did not revert these changes)
    - Did what Ryan S did yesterday (82840) - paused SQZ_MANAGER in LOCK_CLF and adjusted OPO temp. We were then able to lock the filter cavity, start squeezing, and get back into Observing
03:05 Observing
    03:36 Popped out of Observing to reset the sqz angle since we had a message about it and sqz was slowly getting worse
    03:36 Back into Observing

03:47 Popped out of Observing to reset the sqz angle since we had a message about it and sqz was slowly getting worse
03:48 Back into Observing

04:00 Lockloss
- Ran initial alignment

05:16 NOMINAL_LOW_NOISE
05:19 Observing

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
00:19	PEM	Robert	LVEA	YES	Putting viewport cover back on	00:29

ISC, SQZ

Images attached to this report

H1 AOS - Prevalence of ETMX Glitch Locklosses throughout O4

oli.patane@ligo.org — Mon, 17 Feb 2025 21:57:31 -0800

Author: oli.patane@ligo.org

Report ID: 82869

In our ongoing quest to figure out what causes the ETMX glitch locklosses, I've rerun all O4 NLN locklosses with our most up-to-date locklost code to see if we can pinpoint when it started and how/if it comes and goes.

To do this I made a histogram plot for all of O4 showing the amount of locklosses we had each day in blue, and then over that plotted the number of those locklosses that have ETMX glitches right before the lockloss (plot). Basically, it looks like it's been with us since the start of O4. There are times where we go a week or maybe almost a whole month without getting locklosses from them, but they're still pretty regular and we see them every few days otherwise. In O4b, it looks like we saw them very often between end of August to early October and then saw less of them in December, but it's also hard to quantify because we had less locklosses in December, but that could've been either due to more time locked, or due to more time when the detector was down (same with November - that was when we had all the NPRO stuff).

I also have this plot as a pdf, and here's the link to my lockloss tool in case anyone wants to peruse the early O4 ETM glitch locklosses. Also keep in mind that a few ETMX glitch locklosses will have been missed being tagged by the lockloss tool - our code relies on the glitch surpassing a threshold and then going back down and staying below another threshold for a set amount of time, but in a few cases the glitch leads right into the lockloss, meaning it doesn't stay below that threshold long enough for the lockloss tool to realize it was an ETM glitch and thus not tagging it. This doesn't happen very often but it's still important to note that there are more ETM glitch locklosses than we have plotted on this histogram.

Images attached to this report

Non-image files attached to this report

etm_glitch_locklosses.pdf