A follow up on Patrick's new video server code he installed on h1digivideo3 during Tuesday maintenance this week. The attached 7 day minute-trend plot shows h1digivideo3's available memory percentage. The leak can be clearly seen on the left up to Tuesday, and has now been fixed.
TITLE: 09/07 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY: Locked for almost 13 hours, range has been trending upward a bit for the last ~4 hours.
CDS overview OK, No alarms.
TITLE: 09/07 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
IFO is in NLN and OBSERVING since 02:19 UTC (5 hr lock). Most of the action happened during the midshift update (alog 72726), We havce been locked since then.
There were 4 more EQs after Chile (from 4.7 to 5.2 mag) but we stayed locked throughout
BRS temperature is now at 22.0C (Screenshot 3 below); now only 0.1C away from nominal.
LOG:
None
IFO is in NLN and OBSERVING as of 02:19 UTC
Lockloss at 00:01 UTC (alog 72723) and Acquisition
ISI Sensor Correction (BRS Temp - alog 72709)
Before anyone worries we are boiling our brs's, that temp channel is .1 C, so 220=22.0C.
Edited wrong units (you'd have to ask my subconcious how that passed my sanity check).
Naoki, Vicky
During the commissioning window today, we reset the AS42 offset and measured the SQZ ASC sensing matrix after 4 hours into NLN. The last time we measured the sensing matrix was only 40 minutes into NLN in alog72500 and the measured sensing matrix is quite different for thermalized/non-thermalized IFO. We updated the SQZ ASC input matrix as shown in the first and second attached figures (first: new, second: old).
The third attached figure shows the comparison of SQZ ASC input matrix (left: before 20230828, middle: after 20230828, right: after 20230906). The new input matrix after 20230906 looks more similar to one before 20230828. The input matrix before 20230828 was probably thermalized one and we may have changed it to non-thermalized one on 20230828.
Lance, Genevieve, Robert
Today during the commissioning period we made shaker injections at EX, as part of the redo of the formal pre-run PEM injections because of the reduced vibration coupling at 60W. We are getting near the end of these re-dos. We also made some injections at EX and LVEA to understand coupling of the EX water pump to DARM and to investigate the dewar fill noise at the Y-manifold cryopump.
Lockloss due to 6.2 mag Chile earthquake. With alog 72709 BRS out of range (so sensor config off), this made us more susceptible to this type of lockloss.
Lately we've been having better range at the beginnings of our locks. I wondered if that was due to the ADS handing off to the camera servos early in the lock, whereas we'd set the ADS setpoints after the IFO was thermalized. Spoiler alert: I don't think this explains things.
I turned on the ADS lines for a little while, while Vicky and Naoki were working on some sqz things ('Lines on' time in first attachment). I also turned on the ITMY dither line (even though we'd been setting the ITMY A2L values lately based on CHARD dithers, not ITMY dithers).
When Vicky and Naoki were done, I turned on the ADS servos to converge their error signals closer to zero, then turned back on the camera servo (which resets the camera setpoints to the current values).
The second attachment shows the camera centroids over the same time span (and the setpoints in white, which change after the camera servo is cycled on). I cycled the camera servo on twice, which is why the setpoint is changed twice in this screenshot. The ADS servos have been on and converged around the -20min mark on this x-axis, but there's not a very major change in the spot centroid as seen by the cameras.
I don't think there was a very noticeable change to the sensitivity. Here are 2 spectra, each 30 avgs. Yellow is before I turned on the ADS servos (but the ADS lines were on), starting at 22:53:20 UTC. Red is after the ADS servos have converged, starting at 23:00:29 UTC.
I'm not really convinced that this has anything to do with the change in sensitivity over the first few minutes of each lock, so I'm not going to make any changes to any locking sequence things based on this. We just lost lock due to an earthquake, so the IFO will relock with all its normal process next time around.
TITLE: 09/06 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 141Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 13mph Gusts, 10mph 5min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.11 μm/s
QUICK SUMMARY:
IFO is in NLN (as of 22:34 UTC) and OBSERVING (as of 23:06 UTC)
TITLE: 09/06 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: One lock loss at the beginning of the shift, with an automatic relock. We started commissioning at12PT and just got back to Observing.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
14:56 | FAC | Randy | MX | n | Attending to the HEPI piers | 16:56 |
15:00 | FAC | Karen | MY | n | Tech clean | 16:49 |
16:40 | FAC | Tyler | OSB AHR | n | Check drains for AHU1 | 16:58 |
17:30 | SEI | Jim, Randy | EX | n | Check on BRSX | 18:35 |
18:39 | FAC | Karen | MY | n | Drop off | 19:39 |
19:05 | PEM | Robert, Genevieve, Lance | EX | n | PEM injections | 21:40 |
21:34 | PEM | Lance | LVEA | n | Turn on amp | 21:41 |
22:02 | CAL | TJ | CR | n | Calibration sweep | 22:32 |
22:02 | SQZ | Vicky, Naoki | CR | n | SQZ tuning | 23:02 |
Ran a broadband and simulines measurement during commissioning time today following the usual instructions at this wiki.
Simulines start:
PDT: 2023-09-06 15:08:49.141468 PDT
UTC: 2023-09-06 22:08:49.141468 UTC
GPS: 1378073347.141468
End:
PDT: 2023-09-06 15:30:56.446222 PDT
UTC: 2023-09-06 22:30:56.446222 UTC
GPS: 1378074674.446222
2023-09-06 22:30:56,070 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20230906T2
20850Z.hdf5
2023-09-06 22:30:56,087 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_2023
0906T220850Z.hdf5
2023-09-06 22:30:56,096 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_2023
0906T220850Z.hdf5
2023-09-06 22:30:56,107 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_2023
0906T220850Z.hdf5
2023-09-06 22:30:56,117 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_2023
0906T220850Z.hdf5
(Jordan V., Gerardo M.)
Today at 18:50 UTC, we vented the turbo header line very slow, we did that at the mechanical room side using a bottle of nitrogen gas, total time to vent the line was 15 minutes. The turbo header line travels from the mechanical room into the LVEA via the East bay north wall area, and travels to under the main vacuum tube via the bridge over the squeezer tables, and gets very close to HAM5, then it takes a 90 degree turn on the +Y direction to travel under HAM4 and BSC2, under BSC2 the pipe takes a 90 degree turn on the +X direction, to travel under BSC3, then under BSC7, then the pipe (4 inch OD) stops about +32 feet from BSC7, the pipe is sitting on the ground. This turbo header line was pumped down during last maintenance period, and remained under vacuum since, we vented the line to remove a component that we need to take a closer look at. Another time to note is the final vent while removing a component of the turbo header, time this took place was at 20:10 UTC, for about 5 seconds.
Times summary of possible noise: vent of turbo header line, 18:50 UTC, ended at 19:05 UTC. A second vent took place at 20:10 UTC ending 5 seconds later.
We will be out of observing for planned commissioning and a calibration measurement from 19-23UTC (12-16PT)
No obvious cuase yet, and no lock loss tool still. Oli noticed that the lights in the control room flickered about the same time as the lock loss, but we checked the H1:PEM-CS_MAINSMON_EBAY_{1,2,3}_DQ and end station equivalent channels and didn't see anything suspicious.
Back to Observing at 1827 UTC. Automated relocked, but we paused for 10 minutes Jim to swap an ITMY CPS card.
Yesterday Jim and Fil peeked into the BRSX thermal enclosure and since then the BRS has drifted out of range (see attached). Based on the thermocouple readbacks, it looks like the enclosure has cooled down. Jim thinks that he might not have closed up the enclosure well enough and the heater is already at 9V out of its max of 10V, so he cant add too much more heat. The current plan is to recenter the BRS during our commissioning break today and maybe try to get the heater in a more central voltage location to allow for more future adjustment.
In the mean time, we will have no BRS sensor corrected signal for EX. DIAG_MAIN and the SEI guardians have notifications from this automated process, but we might be more vulnerable to earthquakes during this time.
After the lockloss this morning, I went to ex to look at the enclosure and we didn't completely seal up one of the seams when we shut the box. I fixed that, temps should normalize over the next day. I've bumped the voltage on the heater up, but will probably return that to it's previous value this evening, so we don't overshoot.
After regenerating the NonSENS c-code and restarting the h1bos and h1oaf models yesterday, I tried some new cleaning during our commissioning time this afternoon. Now I can get all 3 of LSC, Jitter, and Laser noise subtraction all to work, with no mysterious minus signs needed.
Attached is my DTT 'NonSENS budget' from a time when we were still in commissioning. The blue is the CALIB_STRAIN_NOLINES channel, and red is CALIB_STRAIN_CLEAN. The black is the sum of all the other colors' noise estimates. This LSC subtraction was from a time before the MICH FF was retuned, so it may not have as big an effect were I to turn it on now that MICH FF was updated.
Today I turned on the Jitter and Laser noise subtraction during commissioning (without having retrained it), and it performed at a similar level to this plot from last week. The LSC subtraction was not as effective as this plot, but that's because the LSC in-loop feedforward was tuned later in the week last week, and so there just was less that needed to be subtracted.
Elenna, Sheila
We got data today to rerun our noise budget with the current noise (150Mpc). We got quiet time with no squeezing for 10 minutes starting at 1375723813, with no large glitches. We ran excitations for LSC, laser noise, and ASC. We had quiet time with squeezing injected from the previous night of observing, I choose 1375695779 as a time with high range and no large glitches. This is commit 50358cda
Elenna, Sheila
We ran the noise budget code for this no squeezing time.
This is all commited as 0f9ffe0e
Sheila, Vicky - we have re-run the noise budget for following times:
Noise budget with squeezing. Changes here: using GDS instead of CAL-DELTAL, closer thermalized FDS time to no-sqz, using updated IFO gwinc parameters related to quantum noise calculation.
(Edit: was a glitch in the old time; updated to an FDS time without glitches. All plots updated.)
PDT: 2023-08-10 08:45:00.000000 PDT
UTC: 2023-08-10 15:45:00.000000 UTC
GPS: 1375717518.000000
PDT: 2023-08-10 09:35:52.000000 PDT
UTC: 2023-08-10 16:35:52.000000 UTC
GPS: 1375720570.000000
Noise budget with no squeezing. Same time as above, now calculates using gwinc quantum noise calculation instead of semiclassical calculation used previously.
PDT: 2023-08-10 10:18:11.000000 PDT
UTC: 2023-08-10 17:18:11.000000 UTC
GPS: 1375723109.000000
Both sqz & no-sqz noise budgets now use the correlated quantum noise calculation from gwinc, instead of semiclassical calculations for SN & QRPN. The gwinc budget parameters related to quantum noise calculation are consistent with the recent sqz data set (8/2, alog 72565), with readout losses evenly split between IFO output losses that influence optical gain (20%) and SQZ injection losses (20%), parameters in plot title here. This is high on SQZ injection losses, and slightly conservative on IFO output losses. This updated FDS time is thermalized and closer to the No-SQZ time; the time used previously was several hours earlier near the start of lock, w/ ifo not yet thermalized.
Unlike before, both budgets now show GDS-CALIB STRAIN, which on 8/10 was more accurately calibrated (see Louis's alog on Aug 8, LHO:72075, comparing CAL-DELTAL and GDS vs. PCAL sweep, and his record from 72531). CAL-DELTAL was previously overestimating range due to calibration inaccuracies. We got GDS-CALIB_STRAIN data from nds servers, and at first weren't able to get input jitter data from nds, due to the sampling rate change of IMC-WFS channels from 2k to 16k, 71242. Jonathan H. helped us fix this issue, so we can now pull GDS data and input jitter data from nds.ligo-wa.caltech.edu:31200 -- thank you Jonathan!! With this, the input jitter sub-budget is kind of interesting, looks to be mostly IMC-WFS in YAW.
A quick thought on discrepancy between expected and measured DARM between below several hundred Hz-- I don't know if this could be related to the recent update to gwinc CTN parameters (high/low index loss angles), related to quantum noise, or mystery noise. The recent gwinc CTN update seemed to have dropped the calculated CTN level slightly (maybe 10-15% or so). In April 2023, Kevin helped update CTN parameters LHO:68499 to reconcile H1 budget with the official gwinc parameters, while Evan made a correlated noise measurement 68482 where noise in the bucket seems more consistent with the older CTN estimate from gwinc (or very slightly higher). Another idea is that it could be related to quantum noise, such as SRCL detuning or sqz angle which could've changed since the sqz dataset, as quantum noise can also affect the noise in this region.
All pushed as git commit 28cf2664.
Edit: All pushed again as git commit 33ffd60b.
Added noise budgets with squeezing for HVAC off time on August 17 from alogs 72308, 72297.
When comparing this HVAC off time on Aug 17 with the noise budget from above on Aug 10, it's interesting to note the broadband difference in input jitter (Aug 10 vs Aug 17, HVAC off). Between these times, worth noting that I think there were several additional improvements (like LSC FF or SUS-related) as well.
Edit: updated 8/10 input jitter budget to the less glitchy noise budget time.
Much of the gap between expected DARM (black traces) and measured DARM (red traces) in the noise budget looks compatible with elevating the CTN trace. Budget plots with 100 Hz CTN @ 1.45e-20 m/rtHz are attached below for the no-HVAC times. This is almost 30% higher than the new gwinc nominal CTN at 100 Hz (i.e., 1.128e-20 m/rtHz --> 1.45e-20 m/rtHz). Compared to the old gwinc estimate of 1.3e-20, this is ~11% higher. Quantum noise calculation unchanged here.
This CTN level is similar to the 30% of excess correlated noise that Evan H. observed in April 2023, see LHO:68482. His cross-correlation measurement sees ~30% excess correlated noise around 100 Hz after subtracting input jitter noise, where that "30%" is using the newer gwinc CTN estimate of 1.128e-20 m/rtHz @ 100 Hz. This elevated correlated noise, if attributed to CTN, corresponds to CTN @ 100 Hz of about 1.3*1.128 = 1.46e-20 m/rtHz. See this git merge request for the gwinc CTN update ; this update lowered the expected CTN at 100 Hz by ~15%, from 1.3e-20 (old) to 1.1e-20 m/rtHz (new), based on updated MIT measurements.
For reference, I have plotted these various CTN levels as dotted traces in the thermal sub-budget.
To elevate CTN levels by 30% in the budget code, I scaled both high+low index loss angles by a factor of 1.8, specifically Philhighn 3.89e-4 --> 7e-4 ; Phillown 2.3e-5 --> 4.14e-5. It seems like much higher than this level ~1.45e-20 might be difficult to reconcile with the full budget.
Noteworthy w.r.t. squeezing: from the laser noise sub-budget, laser frequency noise looks within 33% of squeezed shot noise with ~3.7dB of squeezing. By contrast, the L1 noise budget from Aug 2023 (LLO:66532) shows laser noise at the ~20% level of squeezed shot noise with 5.3 dB of squeezing -- i.e. a lower laser noise floor past shot noise.
The following plots can be found in /ligo/gitcommon/NoiseBudget/aligoNB/out/H1/lho_all_noisebudgets_081723_noHVAC_elevatedCTN, and not yet commited to the git repo.
Plots with higher CTN are attached here for the SQZ / no-SQZ proper noise budget times from 8/10, when injections were run.
Comparing the sqz vs. no-sqz budgets suggests there might be more to understand here, to tease apart the contributions from coating thermal noise (CTN) vs. quantum noise in the bucket. In particular, something disturbing that stands out, is that I imagined that if elevated CTN is the physical effect we're missing, it would reconcile both NBs with and without squeezing. However, there is still some discrepancy in the un-squeezed budget, which was not resolved by CTN, and seems to have a consistent shape. I'm wondering if this is related to the IFO configuration as it affects the quantum noise without squeezing. I think this could result from a non-zero but small SRCL detuning since it looks like elevated noise, with a clear shape, that increases below the DARM pole. Simply elevating CTN to match the no-sqz budget would put us in conflict with squeezed darm, so I don't think it makes sense to elevate CTN further. The budget currently has 0 SRCL detuning as it "seems small-ish", but this parameter is somewhat unconstrained in the quantum noise models.
In models, the readout angle is upper-bounded by Sheila's contrast defect measurement, though in principle it could probably be anything lower than that too, which could be worth exploring. It might be helpful to have an external measurement of the thermalized physical SRCL detuning, or in the models allowing the SRCL detunings to vary, to explore how it fits or is constrained by the fuller noise budget picture.
Plots with squeezing can be found in /ligo/gitcommon/NoiseBudget/aligoNB/out/H1/lho_all_noisebudgets. No squeezing plots are in /ligo/gitcommon/NoiseBudget/aligoNB/out/H1/lho_darm_nosqz_noisebudget.
I pushed to git commit 70ca191c without elevated CTN and the associated extra traces. The relevant parameters are left commented out at the bottom of the QuantumParams file, and relevant code to plot the extra traces is commented out in the lho_all_noisebudgets script.
Sheila, Naoki, Vicky -- SQZ data with FIS and FDS.
NLG~11.0 (Gen SQZ=14.7dB), according to calibration from OPO_TRANS = 80 uW (this calibration is reasonably accurate).
Started 8:05 hours into lock. 3-4 hour set of measurements. Data times in bold.
sqz_config |
DTT reference |
gps_start |
clf_phase |
duration |
Notes |
No SQZ |
Ref 0 |
1375027288 |
-- |
1800 |
8:05 hours into lock. Start @ 16:01:10 UTC |
-- misalign FC |
--16:33:32 UTC |
--1375029230 |
-- |
-- |
ADF ON @ 16:36:37 UTC. There is 1.3 kHz ADF line in the data. |
Start in FIS & check if AS42 |
|
(opened bdiv @ 1375029851) |
→ we offloaded + froze ASC. Sheila walked ZM5/6 to optimize ASQZ alignment. |
||
FIS test asc ref |
Ref 3 |
1375029757 |
145.20 |
250 |
End = 1375030007. |
FIAS |
Ref 2 |
1375030889 |
234.06 |
900 |
Start @ 17:01:11 UTC, End = 1375031821, 17:16:44 |
FIS |
Ref 4 |
1375032085 |
150.21 |
900 |
Start @ 17:21:07 UTC, End @ 1375033006, 17:36:28 |
FIS +mid sqz |
Ref 5 |
1375033520 |
196.94 |
900 |
Start @ 17:21:07 UTC, End @ 1375033006, 17:36:28 |
FIS -mid sqz |
Ref 6 |
1375034605 |
0 |
900 |
Start @ 18:03:07 UTC, End @ 1375035601 |
-- relock FC |
-- |
Using FIS, sqz looks like CLF demod phase @ 150.76 deg |
|||
FDAS |
Ref 7 |
1375036671 |
239.07 |
900 |
Start @ 18:37:33 UTC, End = 1375037577, 18:52:39 |
FDS +mid |
Ref 8 |
1375037596 |
196.94 |
900 |
Start @ 18:52:58 UTC, End = 1375038540, 19:08:42 |
FDS -mid |
Ref 9 |
1375038782 |
0 |
900 |
Start @ 19:12:44 UTC, End = 1375039746, 19:28:48 |
FDS (no asc) |
Ref 10 |
1375040208 |
150.21 |
~5min |
Start @ 19:36:30 UTC, End = 1375040749, 19:45:31 |
FDS (with asc ON) |
Ref 11 |
1375041161 (sqz asc has settled) |
150.21 |
900 |
Start @ 19:52:23 UTC, End = 20:07 |
Total change in squeezer configuration: SQZ angle has changed from 145.2 --> 150.2 deg.
Attached the data times as a .py, for easier analysis.
Kevin, Sheila, Daniel, Vicky
Here is the squeezing dB data from this time, which shows the quantum noise reduction with squeezing, relative to a model of quantum noise without squeezing. To sanity check IFO parameters, here is the no-sqz quantum noise model (dashed purple) is plotted alongside the full budget (solid red), plotting CTN (the -. and -- green lines), and the technical non-quantum noise estimate (grey), using the no-sqz times taken in this dataset. IFO & SQZ parameters used for modelling are shown in the title.
Note: this squeezing subtraction (estimated quantum noise w/sqz - quantum noise model w/o sqz) is model-dependent. We are still working to use a cross-correlation estimate of the technical noise, so we can calculate the quantum noise without squeezing w/o relying on a shot noise model (b/c the model depends on optical gain / ifo readout losses). In this analysis, the method this is reversed: we use the quantum noise model to get an estimate of technical noise, then subtract that technical noise estimate from squeezed darm, to see the quantum noise reduction with squeezing. Specifically, in PSD here we do the following:
- tech noise = (meas darm no sqz) - (qn model no sqz) --> this is better to get it from the dcpds correlated noise (but correlated noise includes QRPN, need to account for that accurately)
- quantum noise w/sqz = (meas darm w/sqz - tech noise)
- sqz dB = 10*log10( (quantum noise w/sqz) / (gwinc qn model no sqz) )
How I set the IFO modeling parameters:
1) Homodyne / readout angle = - 10.7 degrees. This is constrainted to < -10.7deg from sheila's recent contrast defect measurement 71913.
2) SRCL detuning =0. It is likely small, though possibly non-zero; anyways, setting it to 0 for this analysis, while working with Louis to see the SRCL detuning from calibration measurements.
3) IFO readout efficiency - based on sqz wiki, expect ~13% broadband optical readout losses of the IFO signal, without squeezing. Based on no-sqz measured DARM, circulating arm powers in the 370-380kW range, homodyne angle < -10.7 deg, and negligible SRCL detuning -- here it is estimating 73% output efficiency (27% loss) to reconcile shot noise sensitivity with measured DARM at 1 kHz. With the no-sqz quantum noise model and 73% output efficiency, the estimated technical noise level is ~0.9e-20 m/rtHz at 1 kHz. This 1kHz technical noise estimate lands somewhere between Craig's correlated noise estimate 71333 (like 0.5-1e-20 m/rtHz @ 1kHz), Sheila's measurement of correlated dcpd noise 70891 (like 1.2e-20 m/rtHz @ 1kHz), recent noise budget projections, 72245, and a lil higher than Jenne's NonSENS noise budget 72578 (considering laser frequency noise ~0.3e-20m/rtHz at 1kHz). Given that subtracting the shot noise model suggests technical noise within a factor of 2-3 of other metrics, it lends at least some some confidence to the no-sqz quantum noise model w/excess output losses that impact optical gain.
Next question: How well constrained is the breakdown between readout / injection losses? Not all the IFO readout losses that affect optical gain have to be SQZ readout losses (two beams could have different alignments/mode-matchings through the IFO / AS port). But to look for sqz losses, it'd be helpful to have a hint of where to look, if we can find whether losses are IFO side or else SQZ side. I don't see a clear sign in our measurements either way.
--> I considered 3 scenarios:
1) Equal IFO readout losses 20% + SQZ injection losses 20%,
2) Using same IFO readout losses (71%) for SQZ, then rest is SQZ injection losses (9%),
3) All SQZ injection losses (35%) and perfect readout efficiency (100%).
Noticeable features that could distinguish between the two scenarios (high readout losses vs. high injection losses) are mostly the low frequency QRPN SQZ rotation+gain from the arm cavities optomechanics. If more quantum noise is injected to the IFO (so injection losses * gen sqz dB are higher), then the arm cavities have more sqz to rotate, and so we see the squeezing efficiencies increase at low freqencies as a result. Kevin has nice plots that show this (squeezing efficiency within the arm cavity bandwidth decreases w/injection losses but not with readout losses; or like Kevin says, injection losses source QRPN and shot noise, while readout losses only source shot noise.
Some next steps to understand in the analysis/models:
1) How is the squeezing relatively flat given the known mode-mismatches of both IFO-OMC and SQZ-IFO/OMC? It seems that hot OM2 curvature leads to ~10% IFO-OMC mode mismatch, while the SQZ PSAMS are railed without yet optimizing SQZ-OMC mode-matching, so SQZ-OMC is clearly not perfectly mode-matched either. What is the scenario where we get flat squeezing given the known mode mismatch?
2) Use cross-correlation to calculate squeezing dBs. Is the squeezing definitely flat, or is that an artifact of how we compare to a quantum noise model?
Small notes about this analysis:
-- for 8/2 data: for calibration, I am using GDS-CALIB_STRAIN_CLEAN, with the text-file magnitude correction from Vlad's alog 71787.
-- for no-sqz noise budgeting, I am plotting both what gwinc has as CTN, and a trace that is 1.3e-20m/rtHz at 100 Hz. Reminder of this alog from Kevin K. and Evan H. regarding the CTN gwinc noise budget update 68499, which dropped the CTN estimate from ~1.3e-20 m/rtHz previously (green -. trace) to the ~1.13e-20 m/rtHz calculated in gwinc now (green, -- dashed line).