Fri Nov 14 10:13:11 2025 INFO: Fill completed in 13min 7secs
Jordan confirmed a good fill curbside.
In 88046 the OFI temperature slowly scanned while we were in observing, we lost lock while the temperature was still scanning but we got through the minimum of power sent to HAM7.
The first attachement shows the time series. The second shows that the AS power drifted during the test but the ratio of OFI PD A (pick off of TFP reflection towards HAM7) to AS_C (power into HAM6) shows the OFI temperature dependence nicely.
In the third attachment, the blue dots are averages of the last 10 minutes at each OFI temperature. This is fit to a model for the constant leakage, temperature coefficient and temperature that minimizes leakage: leakage ratio = constant_leakage + 1* sin^2( (pi /180 )* angle_coefficent * (temp - best_temp)
The impact of the misrotation of the OFI is sitting on top of 0.34% constant leakage that doesn't change with OFI temperture, presumably the reflection of the thin film polarizer. The OFI seems to rotate the polarization by 0.12 degrees of rotation per degrees C, which can be compared to the estimate of 0.2 deg / deg C from 57965.
Closes FAMIS#27828, last checked 87799
TCSX Chiller read 30.5, TCSY read 10.5, so I did not add any water. Filters and water flow looks good, and there is no water in the Dixie Leak Detector™
We had a couple of HAM1 vacuum glitches yesterday evening (Thursday 13th November 2025) at 18:24 and 22:24 PST. The first glitch caused a VACSTAT alarm because its slope just exceeded the 1.0e-09 torr/min trip level, the second did not reach this level.
These both look like sensor glitches (not gas releases), the pressure is a square wave with no pumpdown curve.
I restarted VACSTAT at 20:44, roughly at the mid point between the glitches, to clear the alarm.
TITLE: 11/14 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Microseism
OUTGOING OPERATOR: Anthony S.
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 15mph Gusts, 11mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.81 μm/s (peak 1.349 um/sec)
QUICK SUMMARY:
There is a H0:FMC-CS_WS_RO_ALARM on CDS_OVERVIEW
Tyler has the RO system offline at the moment, further work will be done on it today. Cellphone alarms for this channel are currently bypassed.
TITLE: 11/14 Owl Shift: 0600-1530 UTC (2200-0730 PST), all times posted in UTC
STATE of H1: Microseism
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 5mph Gusts, 3mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.86 μm/s
QUICK SUMMARY:
Eve shift had left the IFO in Idle to wait out the higher useism.
I woke up at 2am to see if the useism was low enough to lock since it was falling.
H1 went through an Initial Alignment before trying to lock, which took longer than expected locking the green Arms.
Once that was done I allowed DRMI to try to lock a handfull of times. I think when it fails this time I will leave it in idle and try again in a few more hours.
TITLE: 11/14 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Microseism
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Another shift of no observing time for H1 due to the high microseismic motion. Tony will check on things overnight to see if conditions improve, and I've re-enabled sensor correction in case he decides to give locking a try.
TITLE: 11/14 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Microseism
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: In IDLE and not currently trying to relock due to the high secondary microseism. Really nothing happened all day besides some opportunistic commissioning and out of lock work.
LOG:
15:30UTC In DOWN due to very high secondary microseism
- Decided to run an initial alignment just for fun
- Issue with FSS oscillation
16:47 Decided to take the ifo to IDLE from ACQUIRE_DRMI since it wasn't catching and we wanted to do some out of lock commissioning
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 15:48 | FAC | Randy | YARM | n | Caulking even more joints | 18:35 |
| 17:35 | ISC | Sheila, Alicia, Rene | LVEA | n | Ground ITM ESDs | 17:55 |
| 18:01 | IO | Kar Meng | Opt Lab | LOCAL | JAC alignment | 19:21 |
| 18:03 | CDS | Fil | MY | n | Parts, roll up door | 18:35 |
| 18:09 | TCS | Matt | CR | n | CO2 blast on ITMs | 19:09 |
| 19:28 | ISC | Sheila, Kar Meng | LVEA | n | Looking for optics | 19:40 |
| 19:37 | TCS | Matt | LVEA | n | Turning off side bands | 19:45 |
| 20:45 | SPI | Corey | Opt Lab | n | Optics cleaning | 00:13 |
| 21:26 | FAC | Tyler | Site | n | Moving big red to the tractor shop | 21:46 |
| 22:14 | IO | Betsy | Opt Lab | n | JAC optics | 00:13 |
| 22:14 | VAC | Gerardo, Travis, Jordan | EY | n | Purge air and pump work | 23:32 |
| 22:15 | CDS | Dave | MY, EX | n | Looking for cables and checking on equipment | 23:45 |
| 23:46 | PCAL | Tony, Oli | PCAL Lab | N | Gone fishin' | 00:32 |
TITLE: 11/14 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Microseism
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: MAINTENANCE
Wind: 3mph Gusts, 1mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 1.22 μm/s
QUICK SUMMARY: H1 has not been locked all day due to the very elevated microseismic motion and is currently holding in IDLE. If I see it come down enough, I'll try to have H1 lock, but I don't think this is forecasted to get better any time soon.
Ibrahim, Betsy
BBSS Eliptical Baffles (D2500293) were successfully installed today. Pictures from various angles are attached.
Problems - graphics regarding these are attached as slide screenshots
Remarks: I added one of those coated screw caps to the Y-Brace (D1900589) strut fasteners since I could see it shining in the head on picture. Comparison pictures for this are below.
M. Todd
From some of the modeling I've been doing, I've come up with a slew of estimates for coupling factors of TCS power settings to substrate and surface defocus. I've put them into TCS and SDF'd them, hoping that the next week or two we get some good confirmation of these numbers.
Thu Nov 13 10:13:43 2025 INFO: Fill completed in 13min 39secs
Gerardo confirmed a good fill curbside.
[Joan-Rene Merou, Alicia Calafat, Sheila Dwyer, Jenne Driggers] We have entered the LVEA and went to the Beer garden. There, we first turned off the Low Voltage ITM ESD Driver D1600092, first the 15V switch and then the medium voltage switch. In order to turn it on again, it should be reconnected in the opposite order. With the voltage request set to 0 and chassis powered off, we have unplugged the SHV cables going to the chamber and plugged into Robert's ground boxes, which we used to ground to the rack which is grounded to the chamber. This has been done at both drivers (See attached photos). Afterwards, we have changed the code at /opt/rtcds/userapps/release/isc/h1/guardian/ISC_LOCK.py in order that the LOWNOISE_COIL_DRIVERS will go to LOWNOISE_ESD_ETMY instead of TRANSITION_FROM_ETMX. This has been done by changing lines 6670 and 6674, moving the ", 15" step from line 6670 to 6674. Finally, we communicated the change to the operator and loaded the guardian.
M. Todd, S. Dwyer
We wanted to get a couple of measurements of the OMC mismatch with the SQZ beam when we changed from the nominal setting for only one of the ZMs at a time. OM2 was cold for all of these measurements.
| Measurement | Time | OMC Mismatch [%] |
| ZM4 = 6.2, ZM5 = -0.4 (nominal) | 1447088389 | 2.8 |
| ZM4 = 4, ZM5 = -0.4 | 1447088919 | 2.4 |
| ZM4 = 6.2, ZM5 = -4.5 | 1447089464 | 10.5 |
It seems the ZM4 is not a very strong actuator for changing the mode at the OMC.
During PRC Align, IMC unlocked and couldn't relock due to the FSS oscillating a lot - PZT MON was showing it moving all over the place, and I couldn't even take the IMC to OFFLILNE or DOWN due to the PSL ready check failing. To try and fix the oscillation issue, I turned off the autolock for the Loop Automation on the FSS screen, and after a few seconds re-enabled the autolocking, and then we were able to go to DOWN fine, and then I was able to relock the IMC.
TJ said this has happened to him and to a couple other operators recently.
Took a look at this, see attached trends. What happened here is the FSS autolocker got stuck between states 2 and 3 due to the oscillation. The autolocker is programmed to, if it detects an oscillation, jump immediately back to State 2 to lower the common gain and ramp it back up to hopefully clear the oscillation. It does this via a scalar multiplier of the FSS common gain that ranges from 0 to 1, which ramps the gain from 0dB to its previous value (15dB in this case); it does not touch the gain slider, it does it all in block of C code called by the front end model. The problem here is that 0dB is not generally low enough to clear the oscillation, so it gets stuck in this State 2/State 3 loop and has a very hard time getting out of it. This is seen in the lower left plot, H1:PSL-FSS_AUTOLOCK_STATE, it never gets to State 4 but continuously bounces between States 2 and 3; the autolocker does not lower the common gain slider, as seen in the center-left plot. If this happens, turning the autolocker off then on again is most definitely the correct course of action.
We have an FSS guardian node that also raises and lowers the gains via the sliders, and this guardian takes the gains to their slider minimum of -10dB which is low enough to clear the majority of oscillations. So why not use this during lock acquisition? When an oscillation is detected during the lock acquisition sequence, the guardian node and the autolocker will fight each other. This conflict makes lock acquisition take much longer, several 10s of minutes, so the guardian node is not engaged during RefCav lock acquisition.
Talking with TJ this morning, he asked if the FSS guardian node could handle the autolocker off/on if/when it gets stuck in this State 2/State 3 loop. On the surface I don't see a reason why this wouldn't work, so I'll start talking with Ryan S. about how we'd go about implementing and testing this. For OPS: In the interim, if this happens again please do not wait for the oscillation to clear on its own. If you notice the FSS is not relocking after an IMC lockloss, open the FSS MEDM screen (Sitemap -> PSL -> FSS) and look at the autolocker in the middle of the screen and the gain sliders at the bottom. If the autolocker state is bouncing between 2 and 3 and the gain sliders are not changing, immediately turn the autolocker off, wait a little bit, and turn it on again.
TITLE: 11/13 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Microseism
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: USEISM
Wind: 3mph Gusts, 0mph 3min avg
Primary useism: 0.05 μm/s
Secondary useism: 1.22 μm/s
QUICK SUMMARY:
Currently in DOWN due to excessively high secondary microseism. We're supposed to have calibration measurements and commissioning today. I'll try for a bit to get us back up, but I doubt we'll get past DRMI since it's worse now than it was last night for Ryan or TJ
I restarted VACSTAT at 08:18 to clear its alarm. Tyler resolved the RO alarm at 06:17 and now the CDS ALARM is GREEN again.
J. Kissel, C. Gray, M. Nakano, G. Billingsley We're getting started with cleaning our 1" and 2" optics for SPI. Corey uploaded *all* of our optics (50:50 BSs, 85:15 BSs, TFPs, HR mirrors, Lenses etc.) to ICS in prep, and I reviewed the work double checking that the ICS record information makes sense. For the HR mirrors, which were part of the 2025 large custom purchase order (C2500044) from FiveNine Optics (to be used by JAC, SQZ, the LLO TNT Lab, and SPI), he entered them into ICS with a key that used the DCC number that's physically etched into the barrel of the optic. HOWEVER -- the DCC number etched on the barrel of the optic is E1900393 -- E1900393. See attached picture. That drawing number is for the coating spec of 0-25 deg AOI HR mirrors. The physical coating spec we want, was provided, and bought was for 45 deg AOI, i.e. E1900392 -- E1900392 (one DCC number lower). So these HR optics, coated with E1900392 spec, bought with C2500044, which have vendor run numbers 1895 and 1897, have the incorrect DCC number for the spec etched on the barrel. If you head to the purchase order, C2500044, and look at the FNO_4787-1.pdf attachment, it clearly states (twice!) "[...] per drawing E1900392-V2. Serialization per E1900392-V2." However, if you then *read* E1900392-v2, section 8 states equally clearly "Each optic should be serialized and marked with the following code/description: 1" optics: E1900393-v2-01 S/N:01 HR1064+532 with incremental S/N: 01, 02, 03, ... 2" optics: E1900393-v2-02 S/N:01 HR1064+532 with incremental S/N: 01, 02, 03, ..." Thankfully we know the coating is the correct E1900392 coating -- (1) The PCAL team confirms via measurement at 45 deg AOI, that these have transmission at the level of ~5e-5 W/W, so these will serve excellently as HR mirrors at 45 deg AOI. See LHO:86699 (2) The vendor's data, posted to C2500186, (Even though the run numbers listed on the first page of the data for the First Batch are quoted as "V2-2895" and "V2-1897" we know the run numbers are V2-1895 and 1897 from what's written on the containers the optics came in; see attached picture) show figures with captions indicating the data is from AoIs of 38, 45, and 50 deg, a reasonable range of AoI's to test for a 45 deg AoI mirror; and conversely no measurement of anything at AoIs less than 25 deg, which would be what one would report for a coating that's spec'd with the *actual* E1900393 spec. (3) The E1900392 spec specificies a 45 deg AoI. So, now we just have to figure out how to keep track of this information when we're in the lab / in the chamber, 5 years later, and the optics are no where near their cases and a brand new person is using the optics. C'est le vie!
Bookkeeping UPDATE:
After consulting with Mitch R. & Dwayne G. about the confusion here, I asked Dwayne to DELETE the qty8 HR mirrors (etch-labeled with the INCORRECT part number of E1900393). So now the ICS permalink Jeff notes above in alog 87397 will no longer point to any parts in ICS. Dwayne made an FRS 35768 for this.
I then imported these NEW ICS parts for the qty-8 MIS-LABELED optics (new permalink list) and gave them the correct Part # they were manufactured/coated for of E1900392
-PLUS-
added a comment to all 8-parts stating they are mislabeled. (comment is: "note: this optic is etch-labeled with the --WRONG-- part number (E1900393), these are in fact E1900392 and have been tested as such. See https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=87397.").
Another bookkeeping mistake found (RyanS noticed that in ICS I marked all the 50/50 splitters with the wrong batch number. Deleted these parts from ICS and just re-uploaded with the correct batch number. We will also update their PETG containers and bags with the correct batch. (this is an easy fix unlick the errant ones which had the physical error etched on the optics themselves IRL).
Yet again, the permalink for the SPI optics has been updated. It is now this permalink.