Closes FAMIS 26551. Last checked in alog 86515
Laser Status:
NPRO output power is 1.873W
AMP1 output power is 70.19W
AMP2 output power is 141.3W
NPRO watchdog is GREEN
AMP1 watchdog is GREEN
AMP2 watchdog is GREEN
PDWD watchdog is GREEN
PMC:
It has been locked 16 days, 0 hr 26 minutes
Reflected power = 23.93W
Transmitted power = 105.2W
PowerSum = 129.1W
FSS:
It has been locked for 0 days 0 hr and 39 min
TPD[V] = 0.8058V
ISS:
The diffracted power is around 4.2%
Last saturation event was 0 days 0 hours and 39 minutes ago
Possible Issues:
PMC reflected power is high
Today we pushed calibration report 20250823T183838Z, which updates the calibration model after changes to the actuation (ESD bias change) and sensing (SRC alignment offset change).
These are the steps I took (and two mistakes I made):
pydarm report --regen 20250823T183838Z
with the ESD bias and drivealign L3 L2L gains updated in the ini file. I checked to make sure the results were sensible. There is a change in the sensing function at low frequency, probably from an L2A2L related change.
pydarm report --regen 20250823T183838Z
to get the GDS filters, checked the GDS filters to ensure they looked normalpydarm commit 20250823T183838Z --valid --message 'new calibration push, new ESD bias and SRC ASC offsets'
pydarm export --push 20250823T183838Z
pydarm upload 20250823T183838Z
pydarm gds restart
H1:CAL-CS_DARM_FE_ETMX_L3_DRIVEALIGN_L2L_GAIN
had not been updated with the new drivealign gain. Once I updated it, CAL DELTA L then looked correct
The attached plot compares the before and after PCAL broadband to GDS CALIB STRAIN. Tony will post the usual alog about the simulines measurement once it is complete.
Sadly, we lost lock mid-simulines measurement. However, the broadband pcal measurement showed success, so we are happy to keep this calibration and we will (hopefully) get simulines Saturday.
Here is the same plot as above, except with PCAL/GDS instead of GDS/PCAL.
We've had two locks since this push, and it appears the systematic error during thermalization is even lower than it was before. We updated the SRCL offset during thermalization, partially because it reduces the systematic error. It appears we do not need to update the thermalization servo, as the systemic error of the 33 Hz line is 2% or less during thermalization.
J. Kissel After this Tuesday's maintenance day, when I installed the H1 SUS PR3 pitch and yaw estimators (LHO:86578), I'd thought I'd turned them OFF. I'd accidentally left the pitch estimator ON. Whoops! I've turned them OFF this morning -- if only to get some data with *just* the improved SR3 estimators (i.e. that the SR3 pitch estimator now includes longitudinal sus point to M1 contributions; see LHO:86567 and LHO:86589). The first nominal low noise and subsequent observation segment with SR3 P & Y (P with improved Sus Point L to M1 P contribution) and PR3 P (also with Sus Point L to M1 P contribution includes) was right after maintenance, 2025-08-26 21:16 UTC, but really it had been on from 2025-08-26 17:44 UTC. I turned the PR3 pitch estimator off by 2025-08-28 15:15 UTC. For reference, assuming everything upstream of the switch is on and functional, you can look at the "use estimator or use OSEM" switch status to check if the estimators are on. The current status is H1:SUS-PR3_M1_EST_P_SWITCH_NEXT_CHAN 2.0 H1:SUS-PR3_M1_EST_Y_SWITCH_NEXT_CHAN 2.0 H1:SUS-SR3_M1_EST_P_SWITCH_NEXT_CHAN 3.0 H1:SUS-SR3_M1_EST_Y_SWITCH_NEXT_CHAN 3.0 i.e. (as stated above) the PR3 estimators are OFF = NEXT_CHAN = 2, and the SR3 estimators are ON = NEXT_CHAN = 3. At superficial glance, i.e. "we've been in nominal low noise observing since they've been on," the IFO doesn't seem to mind AT ALL. And we have a data point of 1.0 that says that we can make it through initial alignment and lock acquisition with it on as well. We'll post some more quantitative metrics in a bit.
TITLE: 08/28 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 3mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.07 μm/s
QUICK SUMMARY:
H1 Has been Locked for 41+ continuous hours without any drops from observing.
Expected drops from Observing:
Today the Comissioning time starts at 1500 -1900 UTC
Calibration:
Target of opportunity:
TITLE: 08/27 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:
Smooth and easy shift with H1 locked for 31.75hrs.
LOG:
TITLE: 08/27 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
GRB-Short E594495 15:35:48 UTC
Vacuum MidX PT 343B Press sensor caused a Verbals Alarm due to phone interfierence with cold cathode gauge. @ 20:44 UTC
Vac Team said this may take a few days to start working properly again, so it may be red for a while.
SuperEvent S250827fo candidate @ 22:50 UTC !!
H1 has been Locked and Observing for 25+ hours.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
17:15 | SPI | Jeff | Optics Lab | N | SPI Inventory | 19:00 |
17:59 | ISS | Rahul | Optics lab | N | Looking for parts | 18:06 |
20:14 | VAC | Janos | MidX MidY | N | Lock out tag out equipment. | 22:14 |
20:20 | SPI | Jeff | Optics Lab | N | SPI Inventory | 20:47 |
20:37 | SPI | Marc | Optics lab | N | Helping Jeff | 20:47 |
22:06 | SPI | Rick | PCAL Lab | Yes | Testing SPI setup for AR & HR coatings measurements | 00:06 |
TITLE: 08/27 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 7mph Gusts, 4mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.06 μm/s
QUICK SUMMARY:
H1's been locked for almost 26.5hrs. Environmentally, microseism is low, as well as low winds, and there was recently some light rain!
Sheila, Tony, Camilla
Sheila and Tony noticed that we had a ~30 minute 10MPc range drop last night with related extra low-freq glitches, from the range BLRMs this is most clear in th 20-34Hz band. This noise is broadband 15-100Hz looking at DARM, plot. And trending the common range drop channels form last year, plot, we see a slight increase in FC2_M3_NOISEMON, plot, confirmed as the cause by the dtt spectrum. Sheila is proposes the cause could be FC backscatter into the IFO. There is no increase in FC1 noise apart from small regions at 80Hz, 160Hz, 190Hz, plot.
There is slighly more noise 8-20Hz in HAM8 in the low range time and 3 peaks at 7-9Hz are gone, plot.
We see the same increased noise in H1:SUS-FC2_M3_NOISEMON_LL_OUT16 in the early morning range drop, see attached.
Running the same template as yesterday, attached yellow traces, there is increased noise in the FC2 and FC LSC control channels, more noise in HAM8 ISI, and a ISI peak at 3.3Hz (there was an earthquake 45mins before but the FC noise started before the EQ), however, the noise in DARM is actually less than yesterday so the coupling isn't constant.
Jim and I had a look at the HAM8 motion and although it increases at times when the ground motion increases, these times do not seem correlated with the FC excess movement and range drops, attached. Maybe the 3.3Hz ISI peak is related to the noisier ground motion times.
Wed Aug 27 10:09:46 2025 INFO: Fill completed in 9min 43secs
Joe B, Elenna
Since the ETMX ESD bias was changed, kappa TST has been trending upwards. This could be due to charging. Kappa TST has increased nearly 3%.
The following packages were added to the default CDS Conda environment on workstations.
- hws (Hartmann Wavefront Sensor)
- epics-striptool
- mypy, a linter and type checker for python programs
TITLE: 08/27 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 6mph Gusts, 4mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY:
H1 Has been Locked in Nominal Low Noise for 17.5 + hours.
All Sub Systems seem to be running well.
J. Kissel After today's H1 SUS SR3 Pitch Estimator's inclusion of the Sus. Point L to M1 P feed forward from the HAM5 ISI GS13s (where we had mistakenly only installed Sus. Point P to M1 P) -- see LHO:86567, I now compare the times of ASC signals (using 0.02 Hz binwidth, 64 sec FFT chunks, 30 averages, and a Hanning window with 50% overlap): 2025-08-20 18:29 UTC - Both P and Y Estimators are OFF 2025-08-24 18:18 UTC - Both P and Y Estimators are ON, but for the P estimator, only the Sus. Point P to M1 P contribution is included in the GS13 FF 2025-08-26 22:00 UTC - Both P and Y Estimators are ON, and for the P estimator, both P to P and L to P contributions are included in the GS13 FF. I'm showing only the control signals, and only the ASC DOFs which are impacted by SR3: DHARD, MICH, SRC1, and SRC2; both pitch and yaw. In All DOFs, the 0.64 and 0.75 Hz modes that had been made worse with only the P to P model of suspension point contribution have now been restored to no-estimator levels. In some DOFs, the 1-10 Hz broadband motion is just barely improved, but enforces the conclusion that SR3 is only partially, if not 'not the dominate contribution' to the ASC signals. Here's a fun one for you -- look at SRC2 Y CTRL -- and look at how much the SRC2 *yaw* motion has changed from including the *longitudinal* suspension point contribution to M1 *pitch* top mass. #ThrowsHandsInAir But -- overall -- with the improvements and all design intent included -- the SR3 P and Y estimators slightly improve the ASC noise from 1 to 10 Hz. Great! As Oli notes in LHO:86551 comparing all of these different configurations from totally different days and times is dubious. We'll get "official" versions of all of these ON vs. OFF configurations on Thursday 8/28. I also attach the local estimator metrics for pitch described in LHO:86553, comparing "only Sus Point P to M1 P modeled contribution" against "P to P and L to P sus point to M1 contribution." That similarly shows that L to P contribution forms a good fraction of the signal needed for damping.
Great to see that the inclusion of the SUSpoint L to M1 P block makes a difference.
Unfortunately, the P2Y coupling is a wierd non-reciprocal coupling we were seeing on the measurements [See page 21 about the SR3 measurements from june after an OSEM calibration test]. The Pitch to Yaw transfer function is consistent with the conversion of pitch motion to observed yaw signals on the LF and RT OSEMs, this apparent motion gets turned into yaw feedback drive and creates the transfer function you see in the measurements linked.
Brian and I discussed it before and we had decided against adding a cross-term in the estimator to address it because it is both not well understood (at least we don't know why the LF and RT OSEMs see Pitch signals) , and because it is possible that we might only be able to address it if we commission the estimators in a fully serialized way, which would be even more time consuming for (probably) minimal benefit.
Depending on schedule, we can figure out if it is worth adding an M1 drive P to M1 Y estimator path, and probably commission a baby version of it with the measurements that Oli already took to see if it makes a difference.
I've confirmed in 86784 that the excess noise seen in the red trace between 1-3 Hz is not due to the SR3 Estimator having L2P compensation
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.
/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.
Similar to alog 86227, the BTRP adapter flange and GV were installed on Tuesday at the MY station. Leak checking was completed today with no signal seen above the ~e-12 torrL/s background of the leak detector.
Pumping on this volume will continue until next Tuesday, so some additional noise may be seen by DetChar. This volume is valved out of the main volume, so the pressure readings from the PT-243 gauges can be ignored until further notice.
Here are the first and the last pictures of the leak detector values. The max was 3.5 * 10-12. 90% of the time it stayed at <1 *10-12.
As of Tuesday, August 19, the pumps have been shut off and removed from this system, and the gauge tree valved back in to the main volume. Noise/vibration and pressure monitoring at MY should be back to nominal.
The pumping cart was switched off, and the dead volume was valved back in to the main volume. The pressure dropped rapidly to ~5E-9 within a few minutes, and it continues to drop. Also, we (Travis & Janos) added some more parts (an 8" CF to 6" CF tee; CF to ISO adapters, and an ISO valve) to the assembly, and also added a Unistrut support to the tee; see attached photo. Next step is to add the booster pump itself, and anchor it to the ground.
LOTO was applied now both to the handlers of the hand angle valve and the hand Gate Valve.
Yesterday, we installed the BTRP (Beam Tube Roughing Pump) adapter flange on the 13.25" gate valve just to the -X side of GV13. This included installing a 8" GV onto the roughing pump port of the adapter, moving the existing gauge tree onto the new adapter, and installing a 2.75" blank on an unused port. All of the new CF joints were helium leak tested and no signal was seen above the ~9e-11 torrL/s background of the leak detector.
The assembly is currently valved out of the BT vacuum volume via the 13.25" GV, and is being pumped down via small turbo and aux cart. Therefore, the PT-343 gauge reading is only reporting on the BTRP assembly pressure, not the main BT pressure, so it can be ignored until further notice of it being vavled back in. This system has been pumping via aux cart or leak detector since ~2pm yesterday, and will continue to be pumped until it is in the pressure range of the BT volume. The aux cart is isolated by foam under the wheels, but some noise may be noticed by DetChar folks, hence the DetChar tag on this report.
A before - after pair of photos. As the conductance is very bad in this complex volume, we're aiming to pump it until next Tuesday. The estimated pressure rise of the main volume after valving in this small volume next Tuesday is less than E-12 Torr (after equalizing) - in other words, negligible.
Some backstage snapshots of the great teamwork of Travis, Janos, and me on installing these: Pic. 1 - "before"; 2,3 - 90% complete.
As of Tuesday, August 12, the pumps have been shut off and removed from this system, and the gauge tree valved back in to the main volume. Noise/vibration and pressure monitoring at MX should be back to nominal.
LOTO was applied now both to the handlers of the hand angle valve and the hand Gate Valve. Also, components have been added to the header, only 1 piece away from the booster pump.
Andrei, Naoki, Sheila
Following the research of aLOG 78125 and aLOG 78262, we aimed to quantify the value of backscattering from the ZM2 and ZM5. We performed backscattering measurements under the assumption that modulation of the optical path between scatterer and interferometer would introduce additional noise in the DCPD spectrum [1-4].
We used data from the H1:OMC-DCPD_SUM_OUT_DQ channel (calibrated to mA of photocurrent) for the times of aLOG 78125. We've then calculated RIN with correction for the DARM control loop. Using Eq. 25 from [1], we performed manual fit. Although we couldn’t perfectly fit within the range from 15 Hz to 21 Hz (probably because of the chosen Welch's transform parameters), we were still able to obtain meaningful results for the backscattering coefficients (see Fig. Backscattering_meas.png). The resulting coefficients are below:
rZM5 ≈ 4 x 10-4
rZM2 ≈ 0.1 x 10-4
Also note, that the amplitude of the excitation used for fit is several times larger than that we've measured from the H1:SUS-ZM#_M1_DAMP_L_INMON channel (1.2 μm unstead of 0.4 μm).
Code that was used for this calculation is attached to this report. OM1_fringewrapping_test.m (Sheila's code) was used to calculate RIN, main.nb was used for manual fit and plotting.
[1] Martynov, D. V., Hall, E. D., Abbott, B. P., Abbott, R., Abbott, T. D., Adams, C., ... & McIver, J. (2016). The sensitivity of the Advanced LIGO detectors at the beginning of gravitational wave astronomy. Physical Review D, 93(11), 112004.
[2] Ottaway, D. J., Fritschel, P., & Waldman, S. J. (2012). Impact of upconverted scattered light on advanced interferometric gravitational wave detectors. Optics express, 20(8), 8329-8336.
[3] Nguyen, P., Schofield, R. M. S., Effler, A., Austin, C., Adya, V., Ball, M., ... & Moreno, G. (2021). Environmental noise in advanced LIGO detectors. Classical and Quantum Gravity, 38(14), 145001.
[4] Fricke, T. T. (2011). Homodyne detection for laser-interferometric gravitational wave detectors. Louisiana State University and Agricultural & Mechanical College.
Camilla, Elenna, Sheila
We wanted to compare this to the design requirement for the filter cavity, table 1 on page 11 T1800447. We are operating with about 47mW of carrier going to the AS port, and the r's above should be amplitude reflectivities. So, this means that we should have 47mw *(1e-5)^2 = 5 pW. This is a factor of 10 less than the assumption in the document.