FAMIS 31113
Jason's FSS RefCav alignment tweak last week is clearly seen. Since then, the ISS diffracted power has dropped slightly and both PMC reflected and transmitted powers have risen sightly. No other major events of note this week.
TITLE: 11/24 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 11mph Gusts, 8mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.29 μm/s
QUICK SUMMARY:
Locked for 30 minutes.
Editing: TJ found my mistake, I should say ezca['TCS-ITMX_CO2_LASERPOWER_COMMAND'] = 2 to go to the requested power, not 1. 1 is search for home. Thank you TJ.
Lasty night I added some lines to Kevin's script that I hoped would make the CO2 powers step down from 1.7W to 0.9W at midnight.
As the screenshot shows the CO2 powers ended up at 7.8W for ITMX and 5 W if ITMY, which caused the PRG to drop and a lockloss.
The first attachment shows the requested and measured powers for the ITM CO2 in the power up step they normally do as we power up the IFO power. We can read off these plots that to adjust the power from 1.7W to 0.9W we should request an angle of 47 degrees from ITMX or 72 degrees from ITMY.
Next is the same plot for the time when I requested 0.9W. From this plot we can read off the information we would need to update the rotation stage calibration, for ITMX the power in should be 7.9W (it's set to 9W) and the minimum power angle (H1:TCS-ITMX_CO2_LASERPOWER_B) should be 35.5 degrees (it's set to 36.8deg). For ITMY power in should be 6.4W, (it's 6.5W), min power angle should be 58 degrees (it's 60 now).
Based on the calibration it has, the calculated angle for both ITMX and ITMY was very close to what I think it should have been. I don't understand why the angle didn't go to that angle but kept moving. It looks to me like what my script did is the same as what the guardian does to request a power change.
Since we're in-between measurements, I've set the Observing bit.
Sun Nov 23 10:06:34 2025 INFO: Fill completed in 6min 30secs
STATE of H1: Planned Engineering
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 4mph Gusts, 2mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.43 μm/s
QUICK SUMMARY:
After Robert stoped for the day, I set up another round of sqz scanning scripts, which should finish in less than 2 hours from now.
I've also modified Kevin's script to allow me to schedule it to start at midnight, and added some lines that will attempt to step down the ITM CO2 powers to 0.9W from 1.7W. This is a repeat of a test we tried a few times in June, we had locklosses that might have been unrelated 85335. If the IFO stays locked for 1 hour after stepping down the CO2s, the script should run the ADF scan again. I didn't test any of my modifications to the script.
Here's the log of times for the first sqz angle scan tonight:
log of times :
nonlinear gain measurement, unamplified seed scan: 1447904771, amplified seed time: 1447904933 nosqz : 1447904755.0
starting angle scan for FIS with zm4 psams at 6.2, zm5 psams at -5.3:
169.8 : 1447906635.0
159.8 : 1447906876.0
149.8 : 1447907115.0
139.8 : 1447907356.0
129.8 : 1447907596.0
119.8 : 1447907836.0
109.8 : 1447908076.0
99.8 : 1447908316.0
89.8 : 1447908556.0
79.8 : 1447908796.0
79.8 : 1447909036.0
59.8 : 1447909276.0
39.8 : 1447909516.0
19.8 : 1447909757.0
0.0 : 1447909997.0
-30.0 : 1447910237.0
-60.0 : 1447910477.0
-90.0 : 1447910717.0
-120.0 : 1447910957.0
-150.0 : 1447911197.0
Edited to add: the scan for FIS with nominal psams also completed:
starting angle scan for FIS with zm4 psams at 6.2, zm5 psams at -0.4
188.2 : 1447912973.0
178.2 : 1447913213.0
168.2 : 1447913453.0
158.2 : 1447913694.0
148.2 : 1447913933.0
138.2 : 1447914174.0
128.2 : 1447914413.0
118.2 : 1447914654.0
108.2 : 1447914894.0
98.2 : 1447915134.0
78.2 : 1447915374.0
58.2 : 1447915614.0
38.2 : 1447915854.0
18.2 : 1447916094.0
0.0 : 1447916334.0
-30.0 : 1447916575.0
-60.0 : 1447916814.0
-90.0 : 1447917054.0
-120.0 : 1447917295.0
-150.0 : 1447917534.0
For these two measurements, the nonlinear gain measurement was 24.4
was amplified, 7.07e-3, minimum 9.8e-5, unamplified 2.9e-4 NLG
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
The no sqz time for this set of measurements started at 1447822825 and lasted 11 minutes. During this time the nlg measurements were partially done: amplified seed: 7.06e-3, minimum 1e-4, unamplified seed measurement was missed, but it should be the same as in 88223, 2.9e-4, giving an NLG of 24.3
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.
The HAM 1 floor accelerometers appear to have been moved on or around April 18, 2025 during the HAM1 work during the break between O4c.1 and O4c.2. The coherence between the two signals dramatically changes character after that date. I attach some plots of the coherence between accelerometers the day after you repositioned them, as well as data from 0000-0100 UTC on a few example days. I'm not sure that it was moved exactly on April 18, but the coherence data begins to differ from the reference on that date.
Fri Nov 21 10:08:26 2025 INFO: Fill completed in 8min 22secs
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.
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.
PRMI OLGs
PRCL and MICH filter banks while PRMI is locked before PRMI ASC is turned on.
