This icalibration was requested by Sheila after today's Commissioning work.
Measurement NOTES:
I've expanded the use of the new "system" MEDM widget to the CDS section of the oveview. HW_STAT, PICKET_FENCE and CDS_SDF are now color coded blocks, replacing the related-display+LED pairs.
These blocks will turn RED in non-nominal conditions. In addition HW and PKT will turn MAGENTA if their respective servers stop updating.
Sheila D, Elenna C, TJ S
Yesterday we ran the a2l_min_multi.py script and then Elenna adjusted the ITM yaw gains by hand to see if the script was actually helping our coupling in a way we would like (alog79904). Today, we did a similar exercise but made some adjustments to the script to see if we could tune it a bit better and get it work properly. The short answer is that the script stills seems to want the ITMY Y gain to be ~0.2 different compared to where Elenna found the best CHARD Y coherence. Other quads and dofs seemed to be ok in this instance though.
This morning we were curious if the script agreed with the changes made yesterday, so we quickly ran it at the start of commissioning. Sheila and Elenna noticed that the script didn't actually have a zero crossing for a few of the dofs, ITMY was particularly far off (seen in <a href="https://alog.ligo-wa.caltech.edu/aLOG/uploads/79921_20240905113858_a2l_demod_3_tries.png">attachment 2</a>). When the script doesn't find a zero crossing within its scan range, it would just return the initial gain and stop. So, Sheila and I made some changes by hand using a pen to screen linear fit, then ran the script again. This was better but ITMY Y didn't change because the magnitude of the gain change was greater than the gain change threshold coded in. We bumped this up from 0.2 to 0.5 and tried one more time. This try had only ITMY Y gain appreciably change, and all other dofs looked much better from a perspective of all of their demod signals had zero crossings in the center of their scan range.
At this point, the script wants ITMY Y at -2.46. Elenna then moved ITM Y gains by hand and found that the previous value (from the second running of the script) of -2.2 for ITMY Y looked best. See attachment 1. The -2.46 gain looked worse <20Hz, see the top right plot in the attached. Elenna also checked DHARD and agreed that it looks good.
We aren't really sure why the script disagrees so much with this one dof right now. This script is based on one that LLO uses, and it seems to work for them. More thought needed.
Initial a2l gains before starting this morning:
'P2L':{'ITMX':-0.98,
'ITMY':-0.36,
'ETMX':3.08,
'ETMY':4.48},
'Y2L':{'ITMX':2.90,
'ITMY':-1.7,
'ETMX':4.85,
'ETMY':1.13 },
Final a2l gains:
'P2L':{'ITMX':-1.0,
'ITMY':-0.39,
'ETMX':2.98,
'ETMY':4.72},
'Y2L':{'ITMX':2.87,
'ITMY':-2.25,
'ETMX':4.88,
'ETMY':1.49 },
Here is a summary of the 4 spontaneous IPC errors we have seen during the O4 run so far.
alog | date | details |
79913 | 02:08:03 Thu 05sep2024 | long-range-dolphin h1susetmx sender @ |
74665 | 11:09:47 Thu 07dec2023 | CS dolphin h1lsc0 sender * |
74365 | 05:22:13 Tue 21nov2023 | CS dolphin h1lsc0 sender * |
73584 | 18:47:05 Wed 18oct2023 | long-range-dolphin h1susetmx sender @ |
Note that both the * and the @ events are identical pairs of events.
The fact that h1susetmx had todays issue back on Oct 2023 rules out the recent addition of the new LIGO-28AO32 DAC card as being a possible problem.
Today after the SRCL offset was changed from -175 to -400, I quickly ran an injection to check the performance of the feedforward. I also had uploaded a new feedforward that would fix the 100-200 Hz bump that is injecting excess noise.
The "current" feedforward, which is in FM5, still worked well even with the new -400 offset. The "new" feedforward, in FM8, fixes the excess noise and also still performs well. The "old" feedforward FM4, post vent, is shown for comparison (this is what I was improving against last week).
I have SDFed in observe and changed the guardian to use this new FF.
This is with a new SRCL1 OFFSET of -400 (for H1:LSC-SRCL1_OFFSET), as requested by Sheila from commissioning work yesterday.
Measurement NOTES:
Now handing over to Commissioners for Thurs Commissioning.
Before running this morning's calibration, Sheila asked me to change the offset for LSC's SRCL1 (so change to -400 [from -175] for H1:LSC-SRCL1_OFFSET) was made and the SDF has been ACCEPTED (attached).
Thu Sep 05 08:08:55 2024 INFO: Fill completed in 8min 51secs
Gerardo confirmed a good fill curbside.
At 02:08:03 the h1oaf and h1calcs models reported a single IPC receive error for channels being sent by the h1susetmx model.
Preliminary findings:
For all three channels this was a single IPC error in all receivers (one packet in that second's 16384 packets didn't get received in time)
There was no issue with h1susetmx's CPU usage at the time
There was no issue with h1cdsrfm's EX2CS thread (nor any thread) processing at the time
The three IPC channels which went into error are the complete set of LRD channels being sent by the h1susetmx model. (grep for RFM0 channels sent by h1sustemx model in the H1.ipc file shown)
05Sep08:17 > grep -B 1 -A 3 RFM0 H1.ipc|grep -B 4 h1susetmx$
[H1:SUS-ETMX_CAL_CS_L1_LINE]
ipcType=RFM0
ipcRate=16384
ipcHost=h1susex
ipcModel=h1susetmx
--
[H1:SUS-ETMX_CAL_CS_L2_LINE]
ipcType=RFM0
ipcRate=16384
ipcHost=h1susex
ipcModel=h1susetmx
--
[H1:SUS-ETMX_CAL_CS_L3_LINE]
ipcType=RFM0
ipcRate=16384
ipcHost=h1susex
ipcModel=h1susetmx
TITLE: 09/05 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 8mph Gusts, 5mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.18 μm/s
QUICK SUMMARY:
H1's been locked for 9.5hrs. On the CDS Overview there are red boxes for an ADC overflow and configuration change (CFC). Since it's Thurs morning will make preparations for calibration.
TITLE: 09/05 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
IFO is LOCKING at MAX_POWER
Mostly quiet shift.
Earthquakes Lockloss 3:23 UTC:
Interestingly was not due to the 6.2 Mag EQ, which we rode through but was due to a 4.5 Mag one closer-by. I don't know why we lost lock to this but I could clearly see the ISI sensor config peakmon traces go off during and for a bit after. The EQ didn't register as an EQ for quite some time and seismic only went to Earthquake mode after the lockloss whereas it was prepared in the case of the 6.2 EQ. Afterwards, we lost lock 2-3 times during IR and DRMI with some minor trouble auto-locking ALSY. So, I ran an initial alignment and DRMI caught without going through PRMI thereafter. We're powering up right now.
TCSY Observing 7-min Drop:
We dropped out of observing for 7 minutes (UTC to 00:22 UTC to 00:29 UTC) but I didn't notice until the announcement back to observing was made. I checked why this was but the only hint that may have been suspicious was that the TCS Y CO2 Laser Power was below threshold for 5 minues at that time. Whether this is the direct cause or a symptom, I do not know yet. This also came back on its own.
LOG:
TITLE: 09/05 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Lockloss earlier in the morning was pretty easy to recover from, and commissioning went well
LOG:
14:30 Observing and Locked for over an hour
14:41 Out of Observing due to SQZer losing lock
- We were having PMC PZT volts high notification before it lost lock, so makes sense
14:45 SQZer relocked, back into Observing
15:24 Lockloss, starting initial alignment
15:46 Initial alignment done, relocking
16:05 Lockloss from ENGAGE_ASC_FOR_FULL_IFO
- A few minutes into this state, PR GAIN started falling but Sheila was able to save it by turning off the DARM offset. At this point the AS_AIR spot was looking misshappen, probably due to ASC pushing it in the wrong direction. Then we had the lockloss.
16:53 NOMINAL_LOW_NOISE
17:10 To NLN_CAL_MEAS for commissioning measurements
19:06 Back to NOMINAL_LOW_NOISE
19:26 Observing
20:20 - 20:25 PEM tests with shaking the fan outside and around the corner from the Control Room entrance
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
15:19 | FAC | Karen | OptLab, VacPrep | n | Tech clean | 15:58 |
16:38 | FAC | Karen | MY | n | Tech clean | 17:32 |
16:39 | FAC | Kim | MX | n | Tech clean | 17:12 |
17:31 | FAC | Kim | Receiving | n | Loading cardboard | 18:31 |
18:11 | FAC | Karen | WoodShop | n | Tech clean | 18:41 |
20:18 | PEM | Sam | outside | n | Shaking fans | 20:24 |
20:53 | VAC | Janos | MX, MY | n | Measurements | 21:45 |
21:10 | PCAL | Franscisco | PCAL Lab | y(local) | Preparing for measurements | 22:13 |
23:42 | PCAL | Francisco | PCAL Lab | y(local) | More PCAL stuff | 23:49 |
TITLE: 09/04 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 10mph Gusts, 5mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.09 μm/s
QUICK SUMMARY:
IFO is in NLN and OBSERVING as of 19:26 UTC. Very quiet - no comments from when I came in.
With lots of help from Vicky Xu, Kevin Kuns, and Erik Von Reiss I've been working on a script that uses the noise budget infrastructure to validate a quantum noise model, using squeezing measured with and without the filter cavity and at different squeezing angles. Other people have done some similar fitting of quantum paramters, in particular Dhruva's interactive fitting code and Wen's MCMC fits. My goal was to make something we could use to quickly validate a quantum noise model for a noise budget, in the end this is a somewhat painfully manual processes to find a model, but I also find it informative. The usual process for doing this is a little circular, we start with a model of quantum noise and subtract it from a measurement without squeezing to get an estimate of the non-quantum noise, (or we use the cross correlation, and subtract a model of QRPN), and use that to subtract the non quantum noise for different squeezer settings. I was hoping to avoid doing this by using the noise budget terms, which is how the first 5 attachments to this alog were made, but the noise budget residual is too large for that approach so in the end I'm doing the usual subtraction.
SRC detuning
The squeezing angle is fit for each model by finding the squeezing angle that minimizes quantum noise at 3kHz with FDS, and then applying that as an offset to all the other squeezed or anti-squeezed traces. This is needed because changing the SRC detuning or the homodyne angle changes the squeezing angle.
The first useful thing about this script is that it clearly shows that we need a SRCL detuning to explain the data from 77710. The frequency independent data clearly show this, without an SRC deetuning there is no explanation for the elevated noise with FIS around 200-80 Hz or so (compare the red measured trace in the first attachment to the yellow model, with no SRC detuning). Adding a SRCL detuning clearly helps to fit this FIS trace, shown in the second attachment. This FIS trace would provide us a nice constraint on the arm power, if there were not SRC detuning, but as it is these two parameters both have to be adjsuted to fit FIS.
SQZ and Anti-sqz level
Plotting this data set in dB of squeezing (ratio of the traces with squeezing to without squeezing, no subtraction done), we have 4.75dB of high frequency squeezing and 15.25dB of high frequency anti-squeezing. From alog 77710, the nonlinear gain was 16.9 impling that there was 17.1dB of injected squeezing at the time. We have 7.1% known injection losses (escape efficiency, HAM7 losses, OFI). To get this level of anti-squeezing with this nonlinear gain would require high total losses, 35%, which would not be able to produce this much squeezing even without phase noise. As people have seen before, we need a lower estimate of nonlinear gain to explain our squeezing and anti-squeezing levels, which is annoying because it means we are adjusting a parameter that we would hope we could use a measurement for. After talking with Begum and the squeezers about this, I went back to the time when were measuring NLG (16:00:50 UTC on May 8th), to compare the amplified/unamplified seed measurement to amplified/ deamplified, which Begum says been making more sense for LLO (In principle they should be the same).
amplified: 0.214 deamplified: 0.00383 unamplified: 0.0127 dark: 2.11e-5 nlg = ((1+sqrt(amplified./deamplified))/2)^2 gives us an nlg of 18.04, so this is too high.
We could get out of this mess by measuring and fixing phase noise, so that we can fit generated squeezing and total losses to fit our squeezing and anti-squeezing. I've set the phase noise to 30mrad, and adjusted the injected squeezing and total squeezer losses to match anti-squeezing and squeezing.
Models for high and low arm powers
I've started with the range of arm powers from the O4a paper, 364+/-10kW, and put together a low power (354kW) , mid power (364kW), and a high power (374kW) model.
Semi-manual procedure:
It turned out that the SRC detuning doesn't need to change when the arm power is changed and the losses are redistributed between injection and output losses, and I didn't adjust FC parameters for these. So, for 354kW in the arms, I adjusted the output efficiency to 83%, to 80% for 364 kW, and 78% for 374kW. In all cases the injected squeezing was 16.7dB, 30mrad phase noise, HD angle -10.7 deg, and the SRCL detuning was 0.29 degrees.
This procedure will give us different predictions for the frequency indendent squeezing trace from 30-50 Hz, which should be able to give us a constraint on the arm power. If the arm power is overestimated, the radiation pressure noise without squeezing would be overestimated; also we would assign more of the total sqz losses to interferometer output losses, and less to injection losses. That means that there would be more anti-squeezing in the arm cavities increasing the level of raditation pressure noise with out the filter cavity. So both of these effects go in the same direction, meaning that FIS at these frequencies is one way to verify an estimate of the arm power. Clicking through these plots, it seems that the lowest powers in the range quoted in the O4a paper would be disfavored by looking at FIS. (It will also be nice to use the no squeezing measurement to estimate the non-quantum noise instead of the noise budget known noises, this might favor the middle of the arm power range more).
Anti-squeezing at low frequencies looks wrong
Noticable in all of these plots is that the anti-squeezing model is wrong at low frequencies, we don't have the decrease in noise we'd expect from frequency independent anti-squeezing when the arm cavity is rotating the squeezed quadrature. When this data is plotted without subtraction it's clear that this shouldn't be explained by the noise budget residual, that is too small. We've taken data sets like this several times over the last few years, in all cases, the FIAS doesn't go clearly below the FIS curve around 50 Hz as the model here says it should (or sometimes the plots are cut off at these frequenices): 77133 77023 71902 67498
Using a non-quantum noise estimate based on subtraction of quantum noise model
In all of these above, I was only using the non-quantum noise estimates made by the noise budget, but as I said above there is too much noise which is not understood, particularly around 200Hz. The estimate of the SRC detuning is fairly different if I instead estimate the non-quantum noise by subtracting the quantum noise model from the no-squeezing measurement, although the other parameters don't have to change. The last three attachments show low, mid and high power models with an SRC detuning of 0.14 degrees and the non-quantum noise estimated by subtraction. Looking at the frequency independent squeezing in these final three attachments, the slope isn't quite right from 90-200 Hz, which probably means that there is a mode matching effect that is not modeled here. I've set the mid power model here as a quantum parameter file for the noise budget, as QuantumParameters_May2024.yaml We can go ahead and use this to make a noise budget, while in parallel using Dhruva's interactive squeezer code to try to understand if there is set of mode mismatch parameters that can fit the data better.
There is high coherence with ASC, indicating that the A2L gains are not set correctly. Today, we tested setting them with the script and also by hand.
After the camera servos converged, TJ ran the usual A2L script with these outputs:
ETMX P
Initial: 2.99 Final: 3.08 Diff: 0.09ETMX Y
Initial: 4.9 Final: 4.85 Diff: -0.05ETMY P
Initial: 4.48 Final: 4.48 Diff: 0.0ETMY Y
Initial: 1.13 Final: 1.13 Diff: 0.0ITMX P
Initial: -1.0 Final: -0.98 Diff: 0.02ITMX Y
Initial: 2.87 Final: 2.88 Diff: 0.01ITMY P
Initial: -0.39 Final: -0.36 Diff: 0.03ITMY Y
Initial: -2.45 Final: -2.47 Diff: -0.02Naoki, Sheila, Vicky - FIS Measurements at different SRCL offsets
Setup steps:
Measurement steps:
All spans 60s
FIS original SRCL offset @ -175 1409509282 (reference, orginal FDS settings). Span 60s, brown
FIS SRCL offset @ -100 1409509687 (worse SRCL detuning), pink
FIS SRCL offset @ -250 1409510096 (better SRCL detuning, closer to 0), green
FIS SRCL offset @ -325 1409510096 (even better SRCL detuning), yellow
FIS SRCL offset @ -400 1409510673 (still better SRCL detuning), blue
FIS SRCL offset @ -475 1409511323 (very interesting, flipped around / crossed zero with SRCL detuning), black
No SQZ beam diverter closed 1409511600 - 1409511717
Posting the analysis for this FIS + SRCL offset data, where we can compare FIS + SRCL data to QN models, to try inferring the physical SRCL detuning (in degrees) for each offset value (in counts).
Comparing data + models for FIS at different SRCL detunings, with kHz sqz optimized - Attachment 1. This seems like a reasonable way to estimate SRCL detuning.
Comparing FIS models at various SRCL detunings + fit how SRCL offset scales from counts to degrees - Attachment 2
So far this code is living here.
Here also reproducing the list of times I used for the analysis, all span = 120 seconds. Also including the SRCL offset in counts of the filter bank, and the corresponding estimated SRCL detuning based on FIS quantum noise models, with khz squeezing angle minimized.
nosqz: 1409511600
FIS -100: 1409509687, pink. ~~> +0.9 deg
FIS -175: 1409509282, brown. ~~> +0.3 deg
FIS -250: 1409510096, green. ~~> +0.1 deg
FIS -325: 1409510392, orange. ~~> -0.1 deg
FIS -400: 1409510673, blue. ~~> -0.5 deg
FIS -475: 1409511323, black. ~~> -1.1 deg
Lockloss @ 09/04 15:24UTC from unknown cause
16:53UTC NOMINAL_LOW_NOISE
19:26UTC Back to Observing after commissioning
Last night at GPS=1381715243 (Wed Oct 18 18:47:05 2023 PDT) h1oaf and h1calcs long-range-dolphin receivers from h1susetmx reported a single receive error (1 errror in the 16384 packets received in that second). This is the first error of this type this year. There was no issue with h1susetmx at the time, its cpu max is 20uS. I'll clear the errors on the next TOO.
With an error rate of 1 per year, (1 in 5.2e+11) we will just continue to monitor this for now.
Happened again 02:08:03 Thu 05sep2024. FRS32032