Sat Nov 22 10:03:07 2025 INFO: Fill completed in 3min 5secs
Quick fill, ended when TC-A saw a spurt of LN2 and its delta-T exceeded the trip limit, the full overflow followed shortly after.
STATE of H1: Planned Engineering
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 5mph Gusts, 2mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.40 μm/s
QUICK SUMMARY:
We've been locked for 11:45, Sheila has a SQZ script running which I can see by the SQZ_MANAGER complaining about the ANG_ADJ_SERVO not being on. Secondary microseism is still elevated.
The sqz angle scan ran overnight. It did no squeezing and an NLG measurement at the start but those times are not included in the log of times for some reason, I will have to find the times manually.
It looks like the alignment degraded overnight. The script runs AS42 WFS while it moves the psams, but that must not have worked well enough. I'm running scan_alignment: results here, angle scan following here.
It looks like the squeezing angle servo based on the 322 Hz ADF was on while we were in frequency independent squeezing, this will not work well so I've added it SQZ_MANAGER to turn that off when it misaligns the filter cavity.
Ran scan alignment a second time, as well as scan sqz angle, set guardian to FDS, turned off ADF servo and started Kevin's script at 6:55, it should finish around 8:30.
Edited to add: I think the first two scans here are good data, so FDS nominal psams and FIS ZM4 at 4, ZM5 at -0.4. This should also have teh nlg measurement for Kevin's script that I'll have to go find the times for by hand.
log of times :
starting angle scan for FREQ_DEP_SQZ with zm4 psams at 6.2, zm5 psams at -0.4184.8 : 1447823586.0
174.8 : 1447823826.0
164.8 : 1447824067.0
154.8 : 1447824306.0
144.8 : 1447824547.0
134.8 : 1447824787.0
124.8 : 1447825027.0
114.8 : 1447825267.0
104.8 : 1447825507.0
94.8 : 1447825747.0
94.8 : 1447825987.0
74.8 : 1447826227.0
54.8 : 1447826467.0
34.8 : 1447826707.0
14.8 : 1447826948.0
0.0 : 1447827187.0
-30.0 : 1447827428.0
-60.0 : 1447827668.0
-90.0 : 1447827908.0
-120.0 : 1447828148.0
-150.0 : 1447828388.0
starting angle scan for FREQ_INDEP_SQZ with zm4 psams at 4.0, zm5 psams at -0.4182.1 : 1447829109.0
172.1 : 1447829349.0
162.1 : 1447829589.0
152.1 : 1447829829.0
142.1 : 1447830069.0
132.1 : 1447830309.0
122.1 : 1447830549.0
112.1 : 1447830789.0
102.1 : 1447831029.0
92.1 : 1447831269.0
92.1 : 1447831510.0
72.1 : 1447831749.0
52.1 : 1447831990.0
32.1 : 1447832229.0
12.1 : 1447832470.0
0.0 : 1447832710.0
-30.0 : 1447832950.0
-60.0 : 1447833190.0
-90.0 : 1447833430.0
-120.0 : 1447833670.0
-150.0 : 1447833910.0
starting angle scan for FREQ_INDEP_SQZ with zm4 psams at 6.2, zm5 psams at -4.5175.0 : 1447835290.0
165.0 : 1447835530.0
155.0 : 1447835770.0
145.0 : 1447836010.0
135.0 : 1447836250.0
125.0 : 1447836490.0
115.0 : 1447836730.0
105.0 : 1447836970.0
95.0 : 1447837210.0
85.0 : 1447837450.0
84.9 : 1447837690.0
64.9 : 1447837930.0
44.9 : 1447838171.0
24.9 : 1447838410.0
4.9 : 1447838651.0
0.0 : 1447838891.0
-30.0 : 1447839131.0
-60.0 : 1447839371.0
-90.0 : 1447839611.0
-120.0 : 1447839851.0
-150.0 : 1447840092.0
starting angle scan for FREQ_INDEP_SQZ with zm4 psams at 6.2, zm5 psams at -5.3173.6 : 1447840601.0
163.6 : 1447840841.0
153.6 : 1447841081.0
143.6 : 1447841321.0
133.6 : 1447841561.0
123.6 : 1447841801.0
113.6 : 1447842041.0
103.6 : 1447842281.0
93.6 : 1447842521.0
83.6 : 1447842761.0
83.6 : 1447843001.0
63.6 : 1447843242.0
43.6 : 1447843481.0
23.6 : 1447843722.0
3.6 : 1447843962.0
0.0 : 1447844202.0
-30.0 : 1447844442.0
-60.0 : 1447844682.0
-90.0 : 1447844922.0
-120.0 : 1447845162.0
-150.0 : 1447845402.0
starting angle scan for FREQ_INDEP_SQZ with zm4 psams at 6.2, zm5 psams at -0.4183.6 : 1447846542.0
173.6 : 1447846782.0
163.6 : 1447847022.0
153.6 : 1447847263.0
143.6 : 1447847502.0
133.6 : 1447847743.0
123.6 : 1447847983.0
113.6 : 1447848223.0
103.6 : 1447848463.0
93.6 : 1447848703.0
93.6 : 1447848943.0
73.6 : 1447849183.0
53.6 : 1447849423.0
33.6 : 1447849663.0
13.6 : 1447849904.0
0.0 : 1447850143.0
-30.0 : 1447850384.0
-60.0 : 1447850624.0
-90.0 : 1447850864.0
-120.0 : 1447851104.0
-150.0 : 1447851344.0
Got one more scan with good alignment for ZM5 psams at -4.5. There was a no sqz time when the nlg was measured a few minutes before this, but times aren't recorded in the log so I'll have to go find the times later.
starting angle scan for FIS with zm4 psams at 6.2, zm5 psams at -4.5169.4 : 1447867479.0
159.4 : 1447867659.0
149.4 : 1447867839.0
139.4 : 1447868019.0
129.4 : 1447868199.0
119.4 : 1447868379.0
109.4 : 1447868559.0
99.4 : 1447868739.0
89.4 : 1447868919.0
79.4 : 1447869099.0
79.4 : 1447869279.0
59.4 : 1447869459.0
39.4 : 1447869640.0
19.4 : 1447869819.0
0.0 : 1447870000.0
-30.0 : 1447870180.0
-60.0 : 1447870360.0
-90.0 : 1447870540.0
-120.0 : 1447870720.0
-150.0 : 1447870900.0
TITLE: 11/22 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
Got H1 relocked at 04:09 UTC.
Sheila is running a script that will take many hours and will wait for the IFO to be relocked.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 18:18 | PEM | Robert, Geneveive | LVEA | n | Moving cable | 21:18 |
| 22:36 | PEM | Robert Sam Genevive | EY & MY | N | Setting up PEM injection? | 23:26 |
Ham 6's fast shutter seemed to have an issue.
I noticed on the OPS overview screen that HAM6 fast shutter was bright red.
I checked the details and noticed an Error:
Protection in Fault; Power Interlock is
I took ISC_lock to IDLE.
Went to AS Port Protection screen. I didn't get a screen shot of it but it looked like this screen shot from alog 87915
Got it working again,
The Fast Shutter Guardian was in fault with an init and got back to locking.
TITLE: 11/22 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 6mph Gusts, 3mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.52 μm/s
QUICK SUMMARY:
The IFO is currently unlocked and attempting to lock DRMI. Secondary microseism seems elevated but it's low enough to lock.
Flashes look good.
Pushed to PRMI early. DRMI locked!... Nice.
TITLE: 11/22 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Trying to lock DRMI, and we've been having some issues locking for the past four hours, but I think it might be a combo of the high secondary microseism and a medium sized earthquake that passed through? Hard to tell for sure.
LOG:
15:30UTC Initial alignment running
15:40 Relocking
16:36 NOMINAL_LOW_NOISE
20:51 Lockloss
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 16:33 | PEM | Robert | LVEA | n | Checking on equipment | 16:40 |
| 18:18 | PEM | Robert, Geneveive | LVEA | n | Moving cable | 21:18 |
| 18:47 | KarMeng | OpticsLab | y(local) | OPO work | 19:09 | |
| 20:21 | Corey | OpticsLab | n | Cleaning optics | 23:06 | |
| 20:48 | Sheila, KarMeng | OpticsLab | y(local) | OPO work | 21:30 | |
| 21:58 | CDS | Erik | Remote | N | RCG upgrade | 22:08 |
| 22:36 | PEM | Robert Sam Genevive | EY & MY | N | Setting up PEM injection? | 23:26 |
| 23:25 | PCAL | Tony | PCAL Lab | y(local) | Caps on spheres | 23:53 |
| 00:17 | JAC | Jennie | JOAT Lab | n | Just bringing in parts for the table | 00:24 |
At some point within the last year, both the X and Y-axis accelerometers (PEM-CS_ACC_LVEAFLOOR_HAM1_X and Y) were kocked off (pictured here) the small metal cube they were mounted to. I reattached them as of Nov 11, 2025. I believe the capacitor position sensor box was pushed back into the accelerometers which knocked them off. Image 3 shows where the CPS box is in relation to HAM1 (circled in red) and image 4 shows where it is in relation to the accelerometers.
Additionally, two other accelerometers have been remounted with epoxy in August: PEM-CS_ACC_BEAMTUBE_SRTUBE_X (remounted August 5, 2025) and PEM-CS_ACC_BEAMTUBE_YMAN_X (remounted August 12, 2025). Both had fallen off the beamtube and had been hanging in the air for an unknown amount of time until someone noticed.
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 |
I took another round of No BRD vs. BRD measurements for the BBSS BRDs, this time with a higher resolution.
Plots attached, including a comparison slide, on which the damped configuration (BRD installed) is the bottom picture.
Note that in the BRD-installed Roll screenshot, the line at the mode is just the cursor.
Zoomed comparison
Updated Zoomed BRD measurement with a higher excitation of the bounce mode with BRD installed which shows the characteristic mechanical damping of the BRD (broad peak).
Some DRMI locking info
MICH, PRCL, SRCL filter banks during the "acquire DRMI 1f" state before the lock is grabbed.
OLGs for MICH, PRCL, SRCL after 1F acquisition, DRMI ASC engaged.
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!
