TITLE: 08/24 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
H1 has been locked for 17+ hours.
All systems are still running smoothly.
No events to report.
LOG:
No Log
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 14mph Gusts, 9mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.15 μm/s
QUICK SUMMARY:
H1 has been locked for 12 + Hours.
All systems seem to be running smoothly.
Secondardy useism looks to be falling & Wind forcasting is single digit wind speeds for the night, so it looks like a good night for Observing.
TITLE: 08/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: We're Observing at 153 Mpc and have been Locked for almost 12 hours. Besides going out of Observing for the calibration measuremnts, I haven't had to do anything for the ifo. We had a GRB-Short alert come in at 20:11 UTC for E592892
LOG:
14:30 UTC Observing and have been Locked for almost 3 hours
18:30 Dropped Observing to run calibration
19:02 Back into Observing
20:11 GRB-Short E592892
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 17:09 | EPO | Sam + tour | Overpass | n | Passing over | 17:39 |
Calibration suite run with IFO fully thermalized, having been Locked for over 6.5 hours.
Broadband
2025-08-23 18:31:57 - 18:37:08 UTC
/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250823T183157Z.xml
Simulines
2025-08-23 18:38:37 - 19:01:56 UTC
/ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250823T183838Z.hdf5
/ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250823T183838Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250823T183838Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250823T183838Z.hdf5
/ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250823T183838Z.hdf5
Sat Aug 23 10:08:18 2025 INFO: Fill completed in 8min 14secs
TITLE: 08/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 2mph 3min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY:
Observing at 150Mpc and have been Locked for almost 3 hours
TITLE: 08/23 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
H1 has been locked for 21+ Hours.
Dropped from observing during an earthquake but stayed locked.
Handful of small earthquakes and survived them.
Nothing else to report.
LOG:
No Log
At 00:42:03 UTC Verbals announced an incoming 5.5M Earthquake from Tonga.
At 00:56:16:UTC H1 dropped from Observing due to a SQZr Unlock that was very likely caused by the increased ground motion.
We went back to Observing at 01:01:39 UTC after the SQZ Man relocked itself.
I did put the OPS mode into earthquake for that moment.
At 01:02:10 UTC Earthquake mode was activated.
TITLE: 08/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 16mph Gusts, 9mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY:
I inherited a 15+ hour lock from the day shift operator.
Everything looks like its running well.
Wind forcast looks great as well.
TITLE: 08/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Observing at 155Mpc and have been Locked for over 15 hours. Nothing happened during my shift at all.
LOG:
14:30 UTC Observing and have been Locked for 6.5 hours
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 15:37 | FAC | Kim | OpticsLab | n | Tech clean | 15:56 |
| 17:17 | SPI | Jeff | OpticsLab | n | SPI Inventory | 21:06 |
Leo, Camilla, Jennie W.
Over the summer, a robust mode-matching simulation for the SQZ beam to the OMC was built using the a la mode library. This report serves to summarize the current state of the simulation and the relevant information one can extract from it.
Link to git code: https://git.ligo.org/leendert.schrader/alm-beam-simulation-for-sqz/-/tree/main SQZ_simulation_v4.m is currently the most recent version.
#1 A detailed description of the squeezed beam path.
Distances, curvature radii, incidence angles, refractive indices, etc. are all within the code file with comments on where they were obtained. This includes all information necessary to propagate the beam starting at the SQZ output (BM4), through ZM4-6, the OFI, SRM, and into the OMC.
These can also be found in the google doc in T2500228, though the curvature radii for ZM4/5 are not what are used in the simulation.
Related aLogs: 85282, 85339
#2 The beam characteristics between ZM5 and ZM6.
Using the beam profiling data from SQZT7 one can plot a "q manifold" which assigns a q parameter with respect to strain gauge values for ZM4 and ZM5.
That is, if one knows the strain gauge for ZM4/5, they can know the beam after ZM5.
Attached is a sample of the q manifold obtained by fitting the horizontal beam width data.
Related aLogs: 85917, 86365, 86519, 85775
#3 Simulated and experimental mode-matching at the OMC.
Simulated: By Propagating the q manifold forward to the OMC using the beam path constructed in a la mode, we can simulate mode-matching with respect to ZM4/5 strain gauge values. The simulation was found to be accurate for high mode-matching, but underestimates matching on the fringes of the strain gauge ranges (compared to collected data).
Experimental: Multiple OMC scans for mode-match were obtained, which allows us to characterize mode-matching across any strain gauge values for ZM4/5.
Attached is a picture of both the simulated and experimental matches against each other. The surface with a grid fits the experimental data, while the surface without grid is the simulated data.
Related aLogs: 86445, 86467, 86520
#4 ZM4 and ZM5 curvature estimates.
We estimate ZM4 curvature by interpolating data in E2100289. Note that preload was increased from 46 in lb to 75 in lb, hence why we had to "interpolate."
We predict the curvature of ZM4 acts as
R_ZM4 = 2/(-0.026296*V_ZM4 - 0.310465)
where V_ZM4 is the strain gauge value for ZM4.
This equation is achieved by assuming a linear voltage - to - optical power relationship (hence the '2 divided by a linear term'). The q manifold is then used to predict the ZM5 curvature values.
Therefore, by ranging the strain gauge in the simulation GUI, one can find simulated ranges for ZM4 and ZM5 curvature.
Note: ZM4 was selected for the above estimate, as we found it behaved "more linearly" than ZM5.
Miscellaneous: the simulation contains the unique SRM ray transfer matrix in the M_SRM variable (see the first interim progress report in T2500228 for details on computation).
For all reports and presentations related to the summer project, see the main DCC document T2500228.
We have now been Locked for almost 13 hours and have been in Observing since I got in this morning. Nothing to report.
Fri Aug 22 10:08:42 2025 INFO: Fill completed in 8min 38secs
Closes FAMIS#26550, last checked 86343
Laser Status:
NPRO output power is 1.865W
AMP1 output power is 69.91W
AMP2 output power is 140.3W
NPRO watchdog is GREEN
AMP1 watchdog is GREEN
AMP2 watchdog is GREEN
PDWD watchdog is GREEN
PMC:
It has been locked 9 days, 22 hr 41 minutes
Reflected power = 23.7W
Transmitted power = 105.3W
PowerSum = 129.0W
FSS:
It has been locked for 0 days 7 hr and 57 min
TPD[V] = 0.8324V
ISS:
The diffracted power is around 4.0%
Last saturation event was 0 days 12 hours and 31 minutes ago
Possible Issues:
PMC reflected power is high
TITLE: 08/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 15mph Gusts, 10mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY:
Observing at 153Mpc and have been Locked for 6.5 hours.
Our normal LVK teamspeak is back up, so I've moved us back over!
I created an updated blend for the SR3 pitch estimator. These are in the SUS SVN next to the first version. (see LHO log 84452)
The design script is blend_SR3_pitchv2.m
the Foton update script is make_SR3_Pitch_blend_v2.m
these are both in {SUS_SVN}/HLTS/Common/FilterDesign/Estimator/ - revision 12608
The update script will install the new blends into FM2 of SR3_M1_EST_P_FUSION_{MEAS/MODL}_BP with the name pit_v2. pit_v1 should still be in FM1. Turn on FM2, turn FM1 off.
Jeff and Oli tried the first one, and see that the first 2 modes (about 0.65 and 0.75 Hz) are seeing more motion with the estimator damping than the normal damping. To correct this, _v2 add OSEM signal to the estimator for those modes. See plots below - First 2 are the _v2 blend and a zoom of the _v2 blend. figure 3 shows the measured pitch plant vs. OSEM path - the modes line up pretty well. There is a bit of shift because the peaks are close together. I expect hope this will not matter. Figure 4 shows the plant vs. the model path. Now all 4 modes are driven by the measured OSEM signal instead of the model.
It is interesting to see that the model was not doing a good job of predicting the motion at the first 2 peaks. This is (I guess) because either (a) the model and the plant are different - or - (b) there are unmodeled drives pushing the plant (the suspension) that the model doesn't know about.
I'm guessing the answer is (b - unmodeled drives) and is likely from DAC noise. I think this because
1 - The plant fit is smooth and really good.
2 - In the yaw analysis that Edgard and Ivey are doing (not yet posted) the first mode of the yaw plant can be seen with the OSEM, but the ISI motion is much too small to excite that level of motion. But the OSEM can see motion, so something is exciting that motion.
3 - The DAC noise is the only thing I can think of.
Quick chat with Jeff indicates that the DAC noise models at those frequencies are not well trusted. We'll try something anyway and see if it is close. I don't see how to use the estimator to deal with that noise - we'd need to have an accurate realtime measurement.
Updated make_SR3_Pitch_blend_v2.m to r12610 after fixing the filter name and the subblock it writes to. Will be loading these in the next time we lose lock.
Thanks Oli!
Also - as a note to myself - I've attached 1 sec of drive signal from the SR3 outputs at the time when both estimators were on (2025-08-21 16:40 UTC, see LHO log 86491 ). The pitch drive is about 30 to 50 counts pk-pk, and not particularly high frequency, compared to the 16384 model rate. This suggests that the low frequency DAC noise is worth following up, and also that it could theoretically be improved with whitening filters. However, since the DC levels are ~ 10k counts to hold the alignments, a simple gain probably wont work. plz note - I am NOT suggesting any changes here, just logging some observations for followup.
Leo, Jennie, Camilla
Followed setup instructions from 80010, with 75mW injected in the SEED beam, we had 1mW on OPO_IR_PD_DC slightly lower than last time. Also took SQZ_FC to FC_MISALIGNED. And opened SQZ beam divertor and fast shutter. Have counts of ~60 on ASC-AS_A and B and 7e-4 on ASC-OMC-A and B NSUMs. Jennie took the OMC PZT down to zero to start and then ran a template userapps/../omc/h1/templates/OMC_scan_sqz_beam.xml.
Repeated mode scans with different ZM PSAMs offsets, the DC centering loops could account for the pitch change for PSAMs, for the extreme PSAMS values, I increased the servo limiter from 85 to 95.
Jennie and Leo have the data to analyze.
See the ndscope with the channels we used to monitor attached.
This template is saved in /ligo/home/jennifer.wright/Documents/OMC_scan/20250819_SQZ_beam_scan_with_ZM_changes.yaml
Following up on these OMC scans: attached is the table with all computed mode-mismatch values.
Leo, Jennie W., Camilla
Below is a plot of the OMC scans fitted with a surface polynomial.
The plot is from the presentation in T2500228, so the labels on axes will be different.
This can be plotted on Matlab simply using the following code block (requires Curve Fitting Toolbox to use fit()).
OMCX = [5.5, 4, 2.3, 3, 8.1, 2.3, 2.3, 6, 9.5, 6, 6, 9, 3, 8, 4, 9.5, 9.5];
OMCY = [-0.8, 0.34, 0.2, 0.85, -0.4, -0.1, 0.2, -0.4, -0.6, -4.5, -5.3, 2, 2, -2, -2, -5, -0.6];
OMCdata = [1-4.048/100, 1-3.412/100, 1-3.074/100, 1-3.234/100, 1-5.073/100, ...
1-3.176/100, 1-2.884/100, 1-2.174/100, 1-3.343/100, 1-9.490/100, 1-11.865/100, 1-6.282/100, 1-2.313/100, ...
1-3.013/100, 1-3.021/100, 1-9.179/100, 1-3.243/100];
omc = fit([transpose(OMCX), transpose(OMCY)], transpose(OMCdata), 'poly22');
p = plot(omc);
Leo, Jennie, Camilla, WP 12694
Jennie followed instructions for set up in 85775. We removed the SQZ beam iris at the bottom of the LPM (added for alignment capture during OFI vent work). Then took beam profiles in this SQZ path of the SEED beam with various PSAMS settings, adjusted PSAMS settings as in 85775 and used the servo for nominal settings. All data is attached. Jennie then reverted settings back to nominal.
Leo, Jennie W., Camilla The attached pdf contains all the beam q parameters fitted to the collected beam width data. Only the 13.5% data was fitted, as the D4S data was too inconsistent to obtain confident q values. Fitting was performed with the a la mode beamPath.fitBeamWidth function. The attached q parameters were individually plotted using a la mode and verified for their data-fitting accuracy. As mentioned in the document, all q parameters are located immediately after the interaction with ZM5 (through the view of BM4 -> ZM4 -> ZM5 beam travel).
Leo, Jennie W., Camilla Attached is a plot of the q manifold from the q parameter data, which allows for characterizing the beam smoothly with respect to ZM4/5 strain gauge voltage values. The image is taken from the presentation uploaded to T2500228. The real plot will likely have slightly different labels to axes. Link to git code for plotting: https://git.ligo.org/leendert.schrader/alm-beam-simulation-for-sqz/-/tree/main
