DriptaB, TonyS, RickS
J. Kissel, quoting R. Savage: A few extra explanatory words for the uninitiated on how this measurement works / how the results were derived: The uncertainties reported are the statistical variations for the measurements we made, highlighted in the attached plots. The authors have not attempted an assessment of potential systematic errors. I suspect that the largest sources of systematic error would likely result from - deviations of the incident polarization (as defined by the plane of incidence of the beamsplitter) from pure p-pol and - deviations of the Angle of Incdence from 45 deg. I also suspect that the errors we might have in this regard are much smaller than what you will have in the SPI installation given the much longer path lengths measured here vs. the SPI in-chamber setup. The next largest source of systematic errors might be - the temperature dependence of the reflectivity of the beamsplitters. We did not attempt to quantify this. We do measure, and correct for, the temperature dependence of the power sensor responsivities and their dark levels during the measurements. I suspect these will have a negligible impact on the measurement results reported for this effort. Regarding the measurement setup and math to derive the answers: The description of the responsivity ratio measurements given in D. Bhattacharjee et al., CQG 38.1 (2020): 015009 (P2000113) -- specifically the caption and text surrounding Figure 3 -- is the gist of the measurement method - simply replace "... the square root of the product of the ratios... replaced with "... the square root of the quotient of the ratios ..." from that caption. This yields the beamsplitter ratio, T/R, rather than the responsivity ratio of the two integrating sphere PDs that the PCAL team is after. (called \alpha_{W1W2} in the caption, but could also be any two responsivities, \alpha_{WG}, \alpha_{RW}, etc). Only - laser power variations that occur over the difference between times of recording the two power sensor outputs (less than 0.1 sec) - variations of the reflectivity of the BS or the responsivities of the two power sensors that occur over the time difference between measuring in the A-B and B-A configurations (less than 40 seconds) should impact the measurements. We record four time series: the output of both power sensors (in volts) and the temperatures (in volts) recorded by sensors on the circuit boards of both power sensors. The any temperature variation in the power sensor time series is normalized out, leaving two conditioned voltage time series for a given physical arrangement of PDs -- and thus are the (power) transmission, T, and (power) reflection, R, of the beam splitter (the A path's HR steering mirror -- that reflects light 90 [deg] to be parallel with the B path -- reflectivity is measured and taken into account as well -- see details below). The responsivity of these PCAL integration sphere + photodiode assemblies -- here we'll call them \rho_1 and \rho_2 -- is known to extremely high accuracy. Each data point you see in the plot is the ratio of [[ the BS ratio (T/R) resulting from one set of (two conditioned) time series when the sensors are in one configuration ]] and [[ a second BS Ratio (T/R) when PD positions have been swapped ]], i.e. accounting for - what was the T time series (from \rho_1 PD in the B position; the "A-B" configuration) becomes the R time series (from \rho_1 PD in the A Position; the "B-A" configuration). - what was the R time series (from \rho_2 PD in the A position; the "A-B" configuration) becomes the T time series (from \rho_2 PD in the B Position; the "B-A" configuration), and conversely So the math is T/R = sqrt { [(P x T x rho_1) / (P x R x rho_2)]_{A-B} / [(P x R x rho_1) / (P x T x rho_2)]_{B-A} } = sqrt{ (T/R)^2 } where again - P is the input power (in [W]), - R and T are the beam splitter reflectivity and transmission (in power; [W]), - \rho_1 and \rho_2 are the two different working standards, and - the subscript _{A-B} and _{B-A} are the answers in the two different physical configurations of the integrating spheres. Assuming no other loss or absorption, then the (power) reflectivity, R, displayed on the plots is R + T = 1 1 + T/R = 1/R R = 1 / (1 + T/R) As noted earlier, the powers (sensor outputs) for the transmitted path are multiplied by about 1.00035 to account for the transmissivity of the the HR mirror that reflects the transmitted beam to the power sensor.
TITLE: 08/25 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
H1 has been locked for 41+ hours
All systems still running well.
No events to report.
LOG:
No Log
H1 ISI CPS Sensor Noise Spectra Famis 26545
No obvious or alarming changes from the last CPS Sensor Noise Spectra.
TITLE: 08/24 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 10mph Gusts, 4mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
H1 has been locked for 35 hours and 45 min.
All systems appear to be running smoothly.
TITLE: 08/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Observing at 152 Mpc and have been Locked for almost 37 hours. Once again nothing at all happened during my shift
LOG:
no log
Sun Aug 24 10:09:25 2025 INFO: Fill completed in 9min 21secs
TITLE: 08/24 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: 2mph Gusts, 0mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY:
Currently Observing at 150Mpc and have been Locked for almost 27 hours
Looks like there were a couple of GRB-Short alerts that came in early this morning (but no superevent candidates :( ):
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.