david.barker@LIGO.ORG - posted 10:14, Friday 21 November 2025 (88197)
Fri CP1 Fill
Fri Nov 21 10:08:26 2025 INFO: Fill completed in 8min 22secs
Images attached to this report
Fri Nov 21 10:08:26 2025 INFO: Fill completed in 8min 22secs
Starting at 08:38 PST this morning the 1PPS signal from EY CNS-II clock, as seen by the comparitor, started dropping from is nominal range of -200 to -700 nS.
This had been seen before and was coming and going about every month about a year ago to the point where Erik installed a Rb clock under the computer rack at EY as a second independent clock and ran its 1PPS BNC into the next port on the comparitor, at which point the problem went away for 8 months until today.
The timeline for the past year is:
07dec2024 CNS dropped to -700 for a few hour
16jan2025 ditto
25feb2025 ditto
04mar2025 Rb clock installed
21nov2025 problem reappeared 8 months since last one
The Rb clock signal is a linearly varying time difference and it does not show any jump this morning confirming the CNS-II signal itself is the problem, not the comparitor or the local timing fanout.
In the trend posted CNS-II is BLUE, Rb-clock is ORANGE
Closes FAMIS#27540, last checked 88125
Everything is looking good.
Laser Status:
NPRO output power is 1.855W
AMP1 output power is 70.55W
AMP2 output power is 139.7W
NPRO watchdog is GREEN
AMP1 watchdog is GREEN
AMP2 watchdog is GREEN
PDWD watchdog is GREEN
PMC:
It has been locked 21 days, 18 hr 27 minutes
Reflected power = 24.49W
Transmitted power = 106.8W
PowerSum = 131.3W
FSS:
It has been locked for 0 days 0 hr and 40 min
TPD[V] = 0.5491V
ISS:
The diffracted power is around 3.9%
Last saturation event was 0 days 9 hours and 3 minutes ago
Possible Issues:
PMC reflected power is high
TITLE: 11/21 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 4mph Gusts, 3mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.53 μm/s
QUICK SUMMARY: Just finished an initial alignment and working on getting DRMI. Looks like we have been unlocked for the past 8 hours. We last lost lock at 07:05 UTC, it then tried relocking until at 08:05 UTC it left CHECK_MICH_FRINGES and took itself to DOWN to run an initial alignment. However, it got stuck in READY (probably because the IMC was stuck at 10W), but it stayed there for four hours, then it looks like a couple earthquakes came in so it probably then just stayed there because the ground may have been moving too much. However, it wasn't until TJ fixed the 10W issue that it was able to start an initial alignment at 15:17 UTC. I know we don't have an actual OWL set, but I am surprised it didn't at least say in the log that assistance was required.
Last night we were stuck at 10W with the IMC unlocked because H1_MANAGER requested ISC_LOCK run an initial alignment while ISC_LOCK was already powering up to 10W to run check MICH. In the DOWN state of ISC_LOCK, it requests LASER_PWR to 2W, BUT ALIGN_IFO repeatedly requests LASER_PWR to 10W while the power is still adjusting. I have no idea why this would be necessary, and Sheila and I agreed that we should take it out. I've removed that portion of code and reloaded that node. If we run into whatever issue someone was trying to fix again, we will come up with a different solution.
TITLE: 11/21 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: PEM measurements were going well until a lockloss @ 01:27 UTC; PEM team was out in the LVEA at the time but were not doing anything particularly noisy. Ran an initial alignment then started relocking, but had a lockloss for some reason in LOWNOISE_ESD_ETMY; this didn't happen on the second relock attempt.
After relocking, I started testing Sheila's SQZ angle stepper script to make sure it's okay to run automatically tonight, but I ran into a few issues, so at this point it is not set to run overnight. After the last test run I did of the script, I accidentally just reverted the ZM4 PSAMs voltage from 15.2 back to its nominal 6.7 (I know now this is MUCH too quick of a change and could have caused a lockloss), so squeezing doesn't look great. Even still, H1 is observing and is set to relock automatically as usual overnight.
LOG:
The squeezing angle stepper script is now in /ligo/gitcommon/squeezing/sqzutils/automate_dataset/
I've set it to go taking the longer data sets overnight tonight. I modified the script this morning to check that the IFO is locked and thermalized before it starts, which is working with some debugging from Ryan and TJ during breaks in the PEM work today. It doesn't handle locklosses part way through the data set well, there are places where it will wait for the squeezing manager to go to the requested state and get hung up there if the IFO is unlocked.
I've set up the first script (SQZ_ANG_stepper.py) to start with no squeezing time, and scan the demod phase for FDS with nominal psams(6.2V ZM4, -0.4V ZM5), then move ZM4 to 4 V and scan with FIS, this is going now.
I've also set up a second script to start again at 1:30 pacific, this should only start if we are locked for at least an hour at that time. This one will scan FIS for two different values of ZM5 psams, and if all goes well will finish around 4 am.
Edit: this didn't complete because the IFO unlocked, I've stopped both scripts now. This is what the log says:
log of times :
starting angle scan for FREQ_DEP_SQZ with zm4 psams at 6.2, zm5 psams at -0.4176.2 : 1447740288.0
166.2 : 1447740528.0
156.2 : 1447740768.0
146.2 : 1447741008.0
136.2 : 1447741248.0
126.2 : 1447741489.0
116.2 : 1447741728.0
106.2 : 1447741969.0
96.2 : 1447742209.0
86.2 : 1447742449.0
86.1 : 1447742689.0
66.1 : 1447742929.0
46.1 : 1447743169.0
26.1 : 1447743409.0
6.1 : 1447743649.0
0.0 : 1447743889.0
-30.0 : 1447744129.0
-60.0 : 1447744370.0
-90.0 : 1447744609.0
-120.0 : 1447744849.0
-150.0 : 1447745090.0
H1:SQZ-CLF_REFL_RF6_PHASE_PHASEDEG => 156.17385
H1:GRD-SQZ_ANG_ADJUST_REQUEST => ADJUST_SQZ_ANG_ADF
log of times :
starting angle scan for FREQ_DEP_SQZ with zm4 psams at 6.2, zm5 psams at -0.4176.2 : 1447740288.0
166.2 : 1447740528.0
156.2 : 1447740768.0
146.2 : 1447741008.0
136.2 : 1447741248.0
126.2 : 1447741489.0
116.2 : 1447741728.0
106.2 : 1447741969.0
96.2 : 1447742209.0
86.2 : 1447742449.0
86.1 : 1447742689.0
66.1 : 1447742929.0
46.1 : 1447743169.0
26.1 : 1447743409.0
6.1 : 1447743649.0
0.0 : 1447743889.0
-30.0 : 1447744129.0
-60.0 : 1447744370.0
-90.0 : 1447744609.0
-120.0 : 1447744849.0
-150.0 : 1447745090.0
H1:GRD-SQZ_MANAGER_REQUEST => FREQ_INDEP_SQZ
TITLE: 11/20 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 13mph Gusts, 10mph 3min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.55 μm/s
QUICK SUMMARY: H1 has been locked for 14 hours and PEM measurements continue with other opportunistic tests happening in between.
TITLE: 11/20 Day Shift: 1530-2330 UTC (0730-1530 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Locked for 13.5 hours. PEM characterization continues. The useism has been on the rise the last few hours.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 15:47 | FAC | Nellie | Opt lab | n | Tech clean | 16:09 |
| 15:48 | FAC | Randy | Yarm | n | Y1 beam tube sealing | 23:01 |
| 18:45 | FAC | Kim, Nellie | OSB | n | Rolling up roll up door | 19:05 |
| 18:50 | PEM | Robert, Genevieve | LVEA | n | Move the speaker cable | 19:27 |
| 19:30 | PEM | Robert, Genevieve | LVEA | n | Readjusting the shaker rod | 19:43 |
| 20:05 | IO | Corey | Opt Lab | n | JAC optics cleaning | 22:05 |
| 21:05 | PEM | Robert, Genevieve, Carlos | LVEA | N | Moving shaker to BSC3 | 21:29 |
| 21:22 | SQZ | Sheila, Kar Meng | Opt Lab | LOCAL | OPO testing | 21:50 |
| 21:24 | CDS | Marc | MY | n | Grabbing parts | 23:22 |
| 22:51 | SUS | Oli | CER | n | Writing down a number | 22:55 |
| 23:05 | PEM | Robert, Genevieve, Sam | LVEA | n | Look at and alter the shaker | 23:13 |
| 23:23 | SQZ | Sheila, Kar Meng | Opt Lab | - | Looking for tool pan in area past card reader, then going to optics lab for more OPO work | 01:23 |
Thu Nov 20 10:09:15 2025 INFO: Fill completed in 9min 11secs
TITLE: 11/20 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 6mph Gusts, 4mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.30 μm/s
QUICK SUMMARY: Locked for 6 hours but it looks like the squeezer has an issue. Working on it now. Dust alarm in the diode room, but other than that, no alarms overnight.
Notifications from the SQZ suite of guardians:
SQZ_MANAGER - request Reset_SQZ_ASC_FDS
SQZ_OPO_LR - "pump fiber rej power in ham7 high, nominal 35e-3, align fiber pol on sqzt0."
SQZ_LO_LR - "LOW OMC_RF3 power < -22! Align SQZ-OMC_RF3, or more CLF power if aligned."
This seems like a similar situation as alog87361
I ended up doing these things:
Since I saw H1 was locked, I started the full magnetic injection suite (49 injections total over the 7 coils across site) at 05:40 UTC using the PEM_MAG_INJ Guardian. This dropped H1 out of observing, but it should return to observing once the injections finish. The suite will finish in roughly 2 hours or if the IFO loses lock, whichever comes first. I'll check things later tonight in case this poses any issues.
Injection suite finished at 08:00 UTC and H1 returned to observing.
TITLE: 11/20 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: PEM measurements were running smoothly until a lockloss @ 01:28 UTC. Since H1 is having a bit of trouble getting relocked (locklosses during LASER_NOISE_SUPPRESSION and DRMI) for reasons I'm unsure of, I've set things to run overnight the same as last night, with H1_MANAGER attempting to keep H1 up but not call for help. I've also set Sheila's SQZ angle stepper script to start at 09:00 UTC (01:00am PST) running on cdsws39 with the hope that H1 is locked.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 01:13 | CAL | Tony | PCal Lab | N | Changing spheres | 01:21 |
| 01:40 | PEM | Robert, Sam, Genevieve | EX -> LVEA | N | Moving shaker | 02:50 |
| 02:12 | VAC | Gerardo | LVEA | N | Checking AIP controller | 03:02 |
IFO locked and was in NLN, but not observing, because I'd left a pico controller enabled and it was causing an SDF diff. I disabled it and now we are in observing.
TITLE: 11/20 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 9mph Gusts, 6mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.33 μm/s
QUICK SUMMARY: H1 has been locked for about 30 minutes and PEM measurements are ongoing.
TITLE: 11/20 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Currently at low noise, PEM characterization all day and one SQZ measurement started. There was one lock loss during the shift caused by us trying to move the corner station sensor correction off while in lock to allow Robert and a UW visitor look at the ITMY seismometer. Didn't work. Relocking was an initial alignment and then waiting at DRMI while we still had SC off, but all auto.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 16:25 | PEM | Robert, Sam, Genevieve | CR/LVEA | n | PEM measurements, in and out of the LVEA all day | 22:05 |
| 17:07 | FAC | Kim, Nellie | OSB | n | Opening receiving roll up door | 17:22 |
| 17:48 | PEM | Robert, Sam | EX | n | Setup measurement | 19:33 |
| 19:34 | SEI | Richard, UW | desert | n | Checking on the vault seismometers | 20:25 |
| 19:42 | SYS | Betsy | Opt Lab | n | Check on lab | 19:47 |
| 20:22 | IO | Corey | Prep lab | n | JAC table enclosure | 22:58 |
| 20:57 | SQZ | Sheila | CR | n | SQZ meas. | 22:07 |
| 21:40 | VAC | Travis | EY | n | Check in mech room | 22:04 |
| 21:56 | SQZ | Sheila, Kar Meng | Opt Lab | n | OPO unboxing | 23:00 |
| 22:04 | PEM | Sam, Genevieve, Jennie | LVEA | n | Move speaker | 22:40 |
| 22:06 | PEM | Robert, UW Paul | LVEA | n | Look at seismometer | 23:21 |
| 22:13 | PEM | Richard | LVEA | n | Join Robert and Paul | 22:39 |
| 23:22 | pem | Robert, Sam, Genevieve | EX | n | Set up shaker | 00:11 |
I've made a fresh start on the noise budget code, using much of the work and many of the functions from aligoNB, but in a code that should be overall simpler for us to work with. This exists in a repo here: simplenb.
Noises estimated using the excess power method can be read in either using gps times or from a dtt template. .xml files are tracked using git lfs and read in by dttxml. If a list of gps times is provided then the code will download the data using gwpy and save asds as a .pkl file, so that the data doesn't need to be downloaded each time the budget is run. Deleteing the pkl file from the local copy will cause it to redownload the data if the user wants to change times or resolution. The excess power projection is done using the frequency resolution of the dtt file, or right now it is hard coded to an fft length of 3 seconds for those made using a list of gps times. The noises are rebinned to a frequency vector specified for the budget after the projections are made.
Thermal noises are imported from gwinc. Quantum noises are also calculated using gwinc, which is why this code needs to be run in an environment that uses Kevin's superQK branch of gwinc. I've added a function save_quantum_params to my quantum noise modeling repo that takes a template of a yaml file including all the parameters you think are important for modeling quantum noise, and a ifo struct, which saves a yaml file with the current parameters. This function is also available in the quantum_utils.py function in this repo, so that people can use it with any method they like of generating a gwinc model of quantum noise to incorporate into this noise budget. I think it is best to leave the quantum noise budgeting separate from this repo for now, because the code for that is still evolving. For now I've used the quantum parameters where all the missing squeezing is explained by frequency dependent loss from 85942, the next step is to add mode mismatches to that model.
Running the budget.py script will generate noise budget plots, you can choose how many layers deep to go in plotting sub-budgets by setting that parameter in the make_all_plots function call in the final lines. The plots attached were made using the injections that Camilla made this morning (86550), and a reference time of 20:00 UTC.
Still to do:
We used the simplenb code to make a plot for the the Stanford seismic NSF proposal, I've attached it below for reference. Some things which we found along the way getting this to run properly as someone offsite who doesn't have a lot of experience with cds * We struggled with LFS and eventually manually downloaded the files needed, we couldn't get them to download via git for some reason * superQK environment is a branch of pygwinc https://git.ligo.org/gwinc/pygwinc * The aligoNB repo is also needed * If working offsite some lines in excess_power_utils under def import_dtt_calib should be edited to the correct directory Hope this is useful for anyone trying to do the same offsite!
