Tue Aug 19 10:07:37 2025 INFO: Fill completed in 7min 33secs
Gerardo confirmed a good fill curbside. He also knocked some ice from the end of the discharge line.
I moved DM10 to the working platform on the +X+Y corner of BSC2 so we can get some dust readings up at that level in preparation for dome removal post O4. I was hoping to get it further away from the edge of the clean room, but the RS232 cable was stretched to its max. I velcrostripped and zip tied the unit as well as the cabled to keep things from falling off and to relieve stress. I also verified that the unit was still getting 2.8L/min since I had to disconnect and reconnect the vacuum hose. It looks to be running well and we can connect to it in epics.
Ops: Please note if this monitor starts to alarm.
WP12755 TW1 offload.
TJ, Erik, Dave:
Following the file copy to permanant storage last week, this morning at 08:15 (inbetween PEM mag injection and PCAL work) I restarted nds1 with its new daqdrc file. It is now no longer using the files on TW1 which frees them for deletion.
TJ tested the script which restarts the FOM ndscope processes, as previously reported we found that the nuc25 and nuc26 restarts did not work. Doing the restarts manually on the operator machines does work, running the full script on opslogin0 also works, investigation continues.
An attempt was made to swap the split whitening chassis that is currently used for the ASC-AS_C QPD (serial S1101627 in slot U26) with a standard whitening chassis. The current chassis is a split whitening chassis that needs to be modified back to a standard whitening chassis in support of BHD/JAC. While swapping the chassis, I noticed that cable ISC_445 was connected to old OMC PD inputs. I seem to have forgotten that one of these channels is now used for the OMC-REFL PD. The new whitening chassis cannot accommodate this without a new custom cable, so the changes were reverted. However, the new standard whitening chassis, serial S2101199, is now mounted in slot U26, whereas the split whitening has moved to slot U29.
TITLE: 08/19 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 2mph Gusts, 1mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY: Locked for 3 hours. Magnetic injections are running to start our maintenance for the day.
Fire pumps are running for hydrant testing, bypassing cell phone alarms for this morning.
Bypass will expire:
Tue Aug 19 02:38:40 PM PDT 2025
For channel(s):
H0:FMC-CS_FIRE_PUMP_1
H0:FMC-CS_FIRE_PUMP_2
H0:VAC-MY_Y1_PT243B_PRESS_TORR
The Norco truck came onsite early today while we are still Observing and dropped our range by up to 20 Mpc as it went around the corner station. The truck arrived onsite at 13:58 UTC, and then passed through the gate and proceeded around the corner station at 14:01 UTC (ndscope).
Workstations were updated. This was an OS packages update. No conda packages were updated.
H1 had lost lock at 06:54 UTC (after 56:57 locked!) from an ETMX glitch. It later called for assistance at 09:53 UTC because it was unable to lock DRMI quick enough after having run an initial alignment. On the next attempt, PRMI was able to lock almost immediately, and I touched up PRM pitch alignment to make buildups look as good as possible while MICH ASC was running and before PRMI ASC offloaded. That seemed to be all it needed as DRMI locked very quickly after that.
I needed to fix a typo in LOWNOISE_ASC related to new SRC ASC offsets (alog86422) that caused a channel connection error when we got there, and accept these offsets in SDF (screenshot).
H1 returned to observing at 11:33 UTC.
This typo must have been some copy-paste error I made. Looking at the code now, it does not turn the offsets on, so I must have made a mistake in the ezca.switch command that Ryan undid (sorry!). The SDF diff was accepting that the offsets were OFF instead of ON (see this alog where I had accepted them ON). I want to clarify that the SRC1 offsets were OFF for this subsequent lock. I will make sure the error is fixed during maintenance today.
Fixed. We will have an SDF diff again when we relock to properly engage the offset.
TITLE: 08/18 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 22Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
Notable news H1 has now been locked 55+hrs.
For those keeping track:
LOG:
H1 just hit 50hrs with the current lock!! (at about the same time a M5.6 Tonga earthquake passed by to add some drama! See the cyan colored trace in the attached photo.) :)
TITLE: 08/18 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: SEISMON_ALERT
Wind: 10mph Gusts, 5mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
H1 is minutes away from a 50hr lock (just as a M5.6 EQ is rolling in....we look like we are fine). Other than that, environmentally continues to get better with microseism coming down and winds also being low.
TITLE: 08/18 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: We're still locked! 49.5 hours now, high frequency SQZing was a little worse after commissioning.
LOG:
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 18:49 | LASER | LVEA is LASER HAZARD | LVEA | YES | LVEA IS LASER HAZARD | 09:49 |
| 17:13 | ISC | Betsy | Optics lab | N | Check for parts/tools | 17:38 |
| 17:14 | VAC | Travis | MidY | N | Check on pumps | 17:27 |
| 17:19 | CAL | Tony | PCAL lab | LOCAL | Start a measurement | 18:22 |
| 18:55 | CAL | Tony | PCAL lab | LOCAL | Look at beamspots | 19:11 |
| 19:22 | CAL | Rick, Dripta | PCAL lab | LOCAL | Checks | 20:15 |
| 20:01 | CAL | Tony | PCAL lab | LOCAL | Join team | 20:15 |
| 20:13 | ISC | Betsy | Optics lab | LOCAL | Parts/tools checks | 21:15 |
| 20:14 | ISC | Camilla | Optics lab | LOCAL | Join Betsy | 21:15 |
| 20:31 | ISC | Keita | Optics lab | LOCAL | Housekeeping, ISS array | 21:24 |
| 20:46 | ISC | Rahul | Optics lab | LOCAL | ISS Array work | 22:30 |
| 20:51 | ISC | Jennie | Optics lab | LOCAL | ISS array work | 22:30 |
| 21:26 | VAC | Travis | Ends | N | Moving equipment for tomorrow | 23:02 |
| 23:18 | CAL | Rick, Dripta, Tony | PCAL lab | LOCAL | Finish measurement | Ongoing |
15:36 - 18:33 UTC Comissioning
Last Tuesday, Oli took some pitch transfer functions for the pitch estimator (see LHO: 86203).
The fits were added to the SVN and live inside '~/SusSVN/sus/trunk/HLTS/Common/FilterDesign/Estimator/Clean_fits_H1SR3_P-08-05.mat'. They are already calibrated to work on the filter banks for the estimator and can be installed using 'make_SR3_pitch_model.m', which is in the same folder.
Attached below are three images of the pitch estimator fits.
The first attachment shows the Suspoint P to M1 DAMP P fit. The zpk for this fit is:
'zpk([-1.573-2.997i,-1.573+2.997i,-0.363-8.909i,-0.363+8.909i,-0.086-5.793i,-0.086+5.793i,-0.012-21.983i,-0.012+21.983i,0.391-14.449i,0.391+14.449i,1.12-1.455i,1.12+1.455i],[-0.421-1.748i,-0.421+1.748i,-0.193-10.021i,-0.193+10.021i,-0.145-13.141i,-0.145+13.141i,-0.115-4.125i,-0.115+4.125i,-0.093-4.667i,-0.093+4.667i,-0.061-21.579i,-0.061+21.579i],-0.001)'
The second attachment shows the M1 drive P to M1 DAMP P fit. The zpk for this fit is:
'zpk([-0.226-4.432i,-0.226+4.432i,-0.008-5.377i,-0.008+5.377i,-0.001-20.571i,-0.001+20.571i],[-0.161-13.126i,-0.161+13.126i,-0.126-4.077i,-0.126+4.077i,-0.111-4.709i,-0.111+4.709i,-0.061-21.603i,-0.061+21.603i],75.096)'
The third attachment shows the Suspoint L to M1 DAMP P fit. We tried to fit the zero at 3 Hz as best as possible without compromising the rest of the fit. The zpk for this fit is:
'zpk([-1.395-60.783i,-1.395+60.783i,-0.941-7.056i,-0.941+7.056i,0.685-18.736i,0.685+18.736i,0.887-6.92i,0.887+6.92i,0,0],[-0.198-10.004i,-0.198+10.004i,-0.141-13.133i,-0.141+13.133i,-0.095-4.093i,-0.095+4.093i,-0.083-4.646i,-0.083+4.646i,-0.06-21.579i,-0.06+21.579i],0)'
13:49:12 PDT power glitch. Lights flickered in OSB.
No UPS emails regarding this event. Attached CS mains mon trend shows issues with all 3 phases.
Closes FAMIS#37208, last checked 85791
HEPI pump trends looking as expected.
Broadband:
Start: 2025-08-18 18:53:06 UTC
Stop: 2025-08-18 18:58:16 UTC
Files:
/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250818T175306Z.xml
Simulines:
Start: 2025-08-18 18:00:44.516123 UTC // GPS: 1439575262.516123
Stop: 2025-08-18 18:24:10.038319 UTC // GPS: 1439576668.038319
Files:
2025-08-18 18:24:09,876 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250818T180045Z.hdf5
2025-08-18 18:24:09,884 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250818T180045Z.hdf5
2025-08-18 18:24:09,889 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250818T180045Z.hdf5
2025-08-18 18:24:09,894 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250818T180045Z.hdf5
2025-08-18 18:24:09,900 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250818T180045Z.hdf5
Just adding some notes that this calibration measurement was taken with SRC ASC offsets, as detailed in this alog.
This report pulled a very old report for comparison, which is an error that Joe B is trying to work on fixing in the code. I regenerated the report so it could pull the most recent valid report, and the results are attached.
/ligo/home/camilla.compton/Documents/sqz/templates/dtt/20250819higher_order_modes.xml screenshot attached. Elenna opened POP beamdiv.| Type | Time (UTC) | Angle | DTT Ref | Notes |
| SQZ | 15:30:00 - 15:35:00 | (-)133 | ref 0 | |
| FDS Mid - SQZ | 15:37:00 - 15:39:00 | (-)111 | ref 1 | At 4dB ASQZ |
| FDS Mid SQZ, SRM YAW -1urad (offset -0.3) | 15:47:00 - 15:49:00 | (-)108 | ref 2 | Made better today and in 86363 |
| Mid SQZ, , SRM YAW -1urad, +8cts DHARD YAW | 15:51:30 - 15:53:30 | (-)108 | ref 3 | No change at 5 or 10kHz |
| Mid SQZ, , SRM YAW -1urad, CAM3Y -1count | 16:04:30 - 16:06:30 | (-)108 | ref 4 | Loop takes ~5 minutes to converge, buildups worse. No change at 5 or 10kHz. |
| Mid SQZ, , SRM YAW -1urad, CAM3Y +1count | 16:15:30 - 16:16:30 | (-)108 | not taken | Builds-ups same as normal. No change at 5 or 10kHz. |
| Mid SQZ, , SRM YAW -1urad, SRM PIT +2urad (offset +0.6) | 16:23:00 - 16:25:00 | (-)110 | ref 5 | Buildups worse, saw 5kHz was a little worse at 5kHz with +0.3 so went further. DHARD PIT started to grow at 1Hz. |
| Mid SQZ, , SRM YAW -1urad, SRM PIT -1urad (offset -0.3) | 16:27:00 - 16:29:00 | (-)107 | ref 6 | 5kHz better |
| Mid SQZ, SRM YAW -1urad, SRM PIT -2urad (offset -0.6) | 16:30:00 - 16:32:00 | (-)106 | ref 7 | 5kHz slightly worse |
| Mean SQZ | 16:35:00 - 16:37:00 | N/A | ref 8 |
camilla.compton/Documents/sqz/templates/dtt/20250818_SQZdata.xml and attached.| Type | Time (UTC) | SRCL Offset | Angle | DTT Ref |
| FIS SQZ | 16:42:30 - 16:45:30 | -382 | (-)124 | ref 1 |
| FIS SQZ | 16:48:30 - 16:51:30 | -200 | (-)153 | ref 2 |
| FIS SQZ | 16:58:30 - 17:01:30 | 0 | (-)224 | ref 3 |
| No SQZ | 17:02:30 - 17:05:30 | -382 | N/A | ref 0 |
Took above data at NLG of 16.0, checked and improved the NLG after data taken 76542.
| OPO Setpoint | Amplified Max | Amplified Min | UnAmp | Dark | NLG | Note |
| 80 | 0.108523 | 0.00199724 | 0.0067894 | -1.22e-5 | 16.0 | Without Optimizing Temp |
| 80 | 0.154115 | 0.00199724 | 22.7 | After Optimizing Temp |
I think we like these SRC ASC offsets, so I set up the guardian to keep them. While the overall effect is minimal, there was a small increase in the buildups that was repeatable: we switched these offsets on and off a few times as we were commissioning today and the buildups got slightly worse when they went off and slightly better when they went on. I tried to process the FIS data, and I think it shows that the overall change in the SRCL offset is minimal, but maybe someone else can confirm. Similarly, the calibration report show the fit of the sensing function is very good in the current model.
Now the guardian engages these SRC ASC offsets in the LOWNOISE_ASC state.
I have attached the results (plot one and plot two) from the FIS measurement, and the fit indicates that our current SRCL offset is fine (I think that's the correct interpretation here).
Here is a trend of the buildups and SRC ASC offsets (pitch and yaw are right on top of each other in the bottom plot). The plot shows that the buildups increase when we add these offsets and decrease when we disengage these offsets.
The calibration report is linked in this alog, and shows that the calibration model is still very good. (There are some strange errors in the report generation, but they are unrelated to this change).
Here is a more to-the-point executive summary of what these results today are indicating:
A large positive SRM pitch offset caused a growing 1 Hz oscillation in DHARD pitch as well. I'm not sure what to make of that yet, but I wanted to re-emphasize for future moves.
Since we are seeing an improvement in the buildups when adding SRM offsets, I think some of the prevalence of these modes could be related to some uncontrolled AS 72 offset which is changing the SRM alignment offset. We reran dark offsets when coming back from the vent, so the dark offset change on AS 72 could be effecting the SRM alignment in some way.
In a follow up discussion, Sheila and I referring Matt's slides regarding the HOMs here.
Based on Matt's work, we think that the lower frequency mode is the Y-arm mode, and the higher frequency mode is the X arm mode.
Therefore, this indicates that the SRM yaw alignment offset effected the Y arm mode and the SRM pitch alignment offset effected the X arm mode.
Also, as a follow up test, we should try CAM2 offsets, which is the X arm soft degree of freedom.
We could also try MICH alignment offsets.