Sat Apr 22 13:27:36 2023 INFO: Fill completed in 12min 34secs
Sun Apr 23 13:28:08 2023 INFO: Fill completed in 13min 7secs
TITLE: 04/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 10mph Gusts, 7mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.16 μm/s
QUICK SUMMARY: The IFO was locked for 5 hours and in NLN when I arrived. The 300NM Dust CS Optics Lab Dust Monitor was giving an audbile minor (yellow) alarm - I turned it off. Randy and Mitchell were working at EY wind fence before I had arrived.
I've asked the IFO to relock itself. First person in in the morning should feel free to ensure it's locked, or do whatever.
I was thinking of locking after the earthquake, and found that SEI_CONF was in error. It looks like it was in Earthquake_no_brsy, and it had an error about a request of ISI_HAM2 trying to go to a state COMP250, but that state didn't exist. Suspicious that things might be okay if it tried to go to a different state (now that the EQ is over), I just hit Load, and it fixed itself and went to Windy.
Something to look into in the morning.
Retuned the MICH and SRCL feedforward with a measurement 5 hours into a NLN lock. New filters are in guardian.
The attached plot compares the CHARD and PRCL signals at the beginning of the lock and at intervals during 3 hours:
Coherences of CHARD_Y in the noisy condition (3 hours in lock) vs less noisy (beginning of lock)
The increased noise in the 5-20 Hz region is due to... HAM1
Trained new FF filters from HAM1 to CHARD_Y, PRC2_Y, INP1_Y and DC1_Y.
Some improvement in all signals, except DC1, so I turned off the DC1_Y FF.
PR3 damping and IM1 damping dominates the low frequency motion in CHARD_Y
HAM1 to ASC feed-forward off to gather training data:
from 2023-04-23 08:43:42 PDT 1366299840
to lock loss at 2023-04-23 08:59:54 PDT 1366300812
New filters uploaded to all filter banks with names FF{X,Z,RX,RY}0423 and engaged. It doesn't look like SDF revert changes them back
The violin modes have been high this lock as Gabriele noted earlier in the chat. I saw on the screenshots that when guardian turned on the OMC DCPD whitening, things were saturating.
I removed the DCPD whitening by selecting REMOVE_WHITENING in the OMC guardian. Since I'm not sure what's up with the violin damping, and I (assume) no one is working on the IFO for the rest of the day, I selected DOWN in ISC_LOCK, so that if the violin modes do get bad enough that we lose lock, the IFO will stay in DOWN until someone manually tries relocking.
Folks should feel free to relock, I just didn't want it to be trying and failing while no one was watching to try to help the lock.
Edit to add: it looks like, with the whitening off, the damping is still going well. It's just that the whitening may have turned on a teeny bit too soon, so we started saturating, and things went poorly from there. Hopefully we'll just stay locked all night :)
Eleonora, Xinghui
Today we shaked the OFI suspension in the longitudinal direction by leaving the OSEM2EULER matrix to [ 1 0 0, 0 1 0, 0 0 1 ] and setting the EULER2OSEM matrix to [ 0 0 0, 0 0 0, 1 0 0 ]. We tried to send a signal also on RT to balance for YAW, but it turned out that it was not better. The residual coupling is 6% between SD (side = longitudinal) and LF (transverse left) and 3% between SD (side = longitudinal) and RT (transverse right). This is good enough for our measurement.
We took clean data between 00h50 UTC 23 April 2023 for 10 mins without squeezing.
We injected a sine noise in the OFI longitudinal suspension at 0.65 Hz and gain = 10000 which corresponds to a motion in LF = 0.72 um, RT = 0.33 um, SD = 11.3 um at 1h10m00 UTC for 10 mins.
In Fig. 1, the scattered light noise shelf is shown in blue (we can see both the first and second orders) and the reference in magenta.
We tried to inject more noise, with a gain of 12000, but the interferometer unlocked.
As reported before, we see very often bumps in DARM spaced at 4.05 Hz.
I wrote a script to look at all 6000+ DQ'ed channels and look for peaks at 2 Hz and at 4 Hz. A peak is defined in this case as a spectral feature where the ratio of the ASD at 4 +- 0.3 Hz over the ASD at 4 Hz is at least 1/5.
The interesting result is that many PEM signals have a large peak at 4.05 Hz: mostly magnetometers and radio antennas, but also other PEM channels
This is the list of ALL Dq'ed channels that have a peak at 4.0x Hz:
H1:PEM-CS_ACC_ISCT1_REFL_Y_DQ 4.060 Hz
H1:PEM-CS_ADC_5_29_2K_OUT_DQ 4.060 Hz
H1:PEM-CS_MAG_EBAY_LSCRACK_Z_DQ 4.060 Hz
H1:PEM-CS_MAG_EBAY_SUSRACK_Y_DQ 4.060 Hz
H1:PEM-CS_MAG_LVEA_VERTEX_Z_DQ 4.045 Hz
H1:PEM-CS_RADIO_EBAY_NARROWBAND_1_DQ 4.060 Hz
H1:PEM-CS_RADIO_EBAY_NARROWBAND_2_DQ 4.060 Hz
H1:PEM-CS_RADIO_LVEA_NARROWBAND_1_DQ 4.060 Hz
H1:PEM-CS_RADIO_LVEA_NARROWBAND_2_DQ 4.060 Hz
H1:PEM-CS_TILT_LVEA_VERTEX_T_DQ 4.060 Hz
H1:PEM-EX_ADC_0_09_OUT_DQ 4.040 Hz
H1:PEM-EX_LOWFMIC_VEA_FLOOR_DQ 4.040 Hz
H1:PEM-EX_MAG_EBAY_SUSRACK_Y_DQ 4.040 Hz
H1:PEM-EX_TEMPERATURE_BSC9_ETMX_DQ 4.040 Hz
H1:PEM-EY_ADC_0_14_OUT_DQ 4.045 Hz
H1:PEM-EY_MAG_EBAY_SEIRACK_X_DQ 4.045 Hz
H1:PEM-EY_MAG_EBAY_SEIRACK_Y_DQ 4.045 Hz
H1:PEM-EY_MAG_EBAY_SEIRACK_Z_DQ 4.045 Hz
H1:PEM-EY_MAG_EBAY_SUSRACK_X_DQ 4.045 Hz
H1:PEM-EY_MAG_EBAY_SUSRACK_Y_DQ 4.045 Hz
Some of them have a narrow peak at 4.040 Hz, most have a narrow peak at 4.045 Hz, and a few have a broader peak at 4.06 Hz.
I could not find any change in the peak amplitudes in those channels when we see the bumps in DARM. This might suggest that 1) the peaks are a coincidence 2) there is some non-linear effect implied, for example if the radio antennas are measuring noise around some VCO frequency, and the VCO drift around and downconvert the noise from time to time.
Adrian, Robert
I looked at one of the "STRONG" times noted in your previous aLog. I see the harmonics of the 4 Hz bumps in a spectrogram of the strain at about +2 minutes in the attached image, but I do not see corresponding bumps in speectrograms of these channels - these can be found in the zip file attached. Many of these channels are marked as disconnected on the latest LIGOCAM run - see the attached screenshot. The 4 Hz peaks in the PEM channels are probably coincidental unless they are wiitnessing a DAQ issue that also affects controls channels.
Today squeezing did not inject at the "inject squeezing" ISC_LOCK guardian state. First, I saw that the sqz CLF guardian said the pump ISS was down due to multiple failed locking attempts. I noticed that the "SQZ-OPO_REFL_REJECTED" PD was in error, saying "voltage readback saturated". I reduced the gain settings to 20 (dB I assume), and the error message went away. Then, I took the CLF guardian to down and re-requested locked, which removed the guardian error message. That worked, but we still did not make it to "sqz ready ifo". The "SQZ-FC" guardian was failing to find IR over and over. I am not sure if that is because of the updates to the FC mirror offloading (alog 68914). I took the SQZ guardian to "no squeezing" for now.
Most likely too much CLF power. There should be no more than 0.03 mW injected into CLF launch fiber. Turned it down. Worked fine before we left.
Kevin, Vicky
I've been working with Kevin on the full quantum noise budget for H1 using gwinc. Running this for Elenna's noise budget times from Wednesday at 76W (LHO:68869), this quantum noise budget is what I have so far, it still needs work. One takeaway so far is that - there is possibly some low-frequency quantum noise contribution to DARM above 40 Hz, but we need to be careful calculating the squeezing parameters to be sure. This is a work in progress. But, it would be interesting to understand if some of the low-frequency excess is really attributable to quantum noise, and if so what to do about it; I think reducing generated sqz levels will generally help us here. Another major reason to budget the quantum noise, is to understand in what ways we need to optimize, and how much squeezing we can still realistically optimize for.
One comment: this low frequency 40-100 Hz band is where quantum shot noise and radiation pressure noise are similar magnitude effects (frequency at which the "standard quantum limit" piles up). This is basically where FC was designed to operate at, and (I think) where a bunch of strange squeezer effects (like coherent misrotations), could thus really factor in. So, it'd be nice to accurately understand the full quantum noise calculation in this low frequency range, where DARM at higher power now sees excess mystery noise, to understand if it's related to squeezing. Below is how I (and I think generally, squeezers) am approaching the quantum noise budget.
1) Understand interferometer quantum noise without squeezing. Here's an example of gwinc's full quantum calcuation on no-squeeze data at 76W. Sheila has done this previously for 60W (LHO:67610) to understand IFO output losses. I'm following through her analysis now at 76W. One major takeaway at 60W, was that the interferometer losses may be high, for example ~10-25%. I second Sheila's recommendations, that we should better constrain our homodyne angle (aka measure the contrast defect) and SRCL detuning throughout thermalization, and optimize the optical gain in the IFO, to reduce/ understand IFO output losses better. And, we should try operating at higher DCPD currents like 30 mA to improve the readout angle for squeezing. At higher power, maybe we can also measure these two during thermalization. I believe the losses are still high when thermalized at 76W, most likely 15%, maybe up to even 30%. But, IFO output losses also seemed high (10-25%) before TCS tuning at 60W, so this could improve still. Our best squeezing at 60W, 4.5 dB, was observed after TCS optimizations to increase IFO optical gain and reduce high-freq laser noise. I think reducing IFO output losses and technical noise is our best path forward to observe / reveal more total DARM noise reduction from squeezing.
Budgeting IFO output losses -- from the squeezing loss wiki,
With our squeezing observations of up to 4.5 dB (LHO:68251), we can constrain IFO readout losses as -- more than the known 8%, and likely less than < 25% for compatibility w/4dB sqz losses.
Looking at a no-sqz quiet time noise budget (GPS = 1366017765, span = 2400s), we can consider an arm power of 400kW, and readout losses of 20%. Higher arm powers (ASC_{X,Y}_CIRC_OUT reads ~430kW) will require more IFO readout losses to give our observed shot-noise-limited-displacement sensitivity -- that is, higher readout losses can explain the discrepancy between the circulating arm power and calibrated m/rtHz sensitivity of DARM, in the range where DARM quantum-noise-limited. Note: it seems LLO can operate with about 75% the circulating arm power, and yet reach almost similar shot-noise-limited displacement sensitivity, without squeezing. This suggests their IFO output losses are lower; if that is true, it would allow for higher observed squeezing levels, given similar squeezing-specific losses.
As external measurements of relevant IFO parameters, I'm considering the following for the noise budget:
2) Now calculate the quantum noise with frequency-dependent squeezing. With this model of the IFO's ambient quantum noise without squeezing, we can now estimate the quantum noise with freq-dep squeezing, and begin to add it fully into the H1 noise budget. Full quantum noise calculation is more involved than the semiclassical quantum noise calculation typically calculated in the gwinc noise budget.
To summarize, for IFO parameters, I'm using 400kW, homodyne angle at -17 deg, SRCL @ -0.2 deg, and considering IFO readout losses of 20% (mid-range ish). For SQZ, I'm considering 16.5 dB generated sqz, FC detuning -35 Hz, and 15% excess sqz injection losses (for ~20% total). To start, injection losses are just broadband loss, ignoring all the complexity from coherent mode-matching interference, which can cause loss (~few %) and squeezing misrotations (~few degrees).
Some thoughts on SQZ optimizations going into ER15.
Squeezer mode-matching and alignment: I don't think this is the biggest limiting effect on observed squeezing yet. I think we need to better understand the IFO output losses, given the serious circulating arm power vs. darm m/rtHz discrepancy. But, I do think with mode-matching and alignment, we can win a bit of squeezing if we check with classical noise (esp laser noise) subtraction. Overall, I think we've had conflicting observations on this front.
If the IFO TCS tuning can further optimize optical gain (aka reduce IFO output losses) and reduce laser noise, continuing on from LHO:68875, that would of course be great all around. Once IFO alignment changes / settles, we can re-zero our AS42 offsets, and begin optimizing the SQZ-ASC alignment offsets, and maybe double-check / walk OMC alignment offsets again as Koji did in LHO:67994, again looking to optimize IFO optical gain. In practice, we should probably operate with less generated squeezing than we use now. Additionally, if we can understand /mitigate the issue with higher CLF powers, running with more CLF power should help us in all ways, for example it'd give us more robust ASC alignment signals. Perhaps we can also explore the higher DCPD current (~30mA) as well, and see if the a better readout angle helps for squeezing.
Summary: going into ER, the SQZ automation with ISC_LOCK seems reasonably robust, and we will continue to work through edge cases. At this circulating arm power, we've so far observed up to 4dB FDS LHO:68701, which has been able to give us 20-25 Mpc in range. In ER, with a more settled IFO thermal state and alignment, and with more quiet time for SQZ optimization, we should be able to take on more serious squeezer optimizations, especially focusing on SQZ + IFO optimizations for increasing range. I hope that working through the full quantum gwinc noise budget can help us understand how to make these DARM range optimizations, and that doing these IFO and SQZ optimizations can bring it back up to at least the 4.5 dB noise reduction w/FDS we saw once at lower power, LHO:68251.
Adding a summary slide with my preliminary conclusions from quantum noise budgeting. It seems that, before and after IFO power up, there is now some excess measured noise in DARM below ~50 Hz; see e.g. LHO:68745 and LHO:68889. Based on gwinc quantum noise calculations, I think it is unlikely that this low-frequency < 60 Hz excess noise is strictly quantum noise.
However, in the recent noise budget at 76W LHO:68869, it's interesting that gwinc's more accurate/detailed calculation of quantum noise, using reasonable IFO+SQZ parameters, could plausibly explain some of the mid-range mystery noise, between ~40-400 Hz. Improving our calculations of the quantum noise with FDS are a work-in-progress.
At 04:56 it appears we lost communication to the CER Beckhoff system. Timing MEDMs are attached.
Gabriele, DanielS, Jenne
Indeed it looks like the power supply has failed. Alog 68911 indicated it was very much not healthy, and Richard pointed out in a comment that plans were already in place to replace it early next week, but it seems that it didn't last that long.
Fil and Fernando are discussing whether it'll be possible to replace it this weekend.
Corner station ethercat device3 Slavecountactual went from 310 to 1 at 04:55:54 PDT
Supply replaced per WP11147
Power looks good, old supply fan bushing was completely shot. Turning off the lights and heading home.
Device3 Slavecountactual increased from 1 to 301, but still 9 shy of 310 needed. We are contacting Daniel and Patrick to see what is needed to complete the recovery.
Logging into 10.105.0.26 I first saw that the Anybus X-gateway terminals were not in OP, so I toggled the requested state of the EtherCAT device. This brought these back but then I noticed that the Corner Chassis 4 L10 EL9410 was in error (see first two screenshots), so I tried toggling some more. Now that terminal is back, but a few of the terminals after it are still in error (see last screenshot, yellow above terminals instead of green).
Toggling isn't bringing these back. Next step would be to power cycle corner chassis 4. If that fails, pull the chassis.
Power cycled Corner 4 at 1:25 pm
Power cycling appears to have brought things back online.
Supply replaced was S1201930, this supply had a failed fan. We will replace the fan and put this supply into the spares inventory. I have it recorded that thie old supply was sourcing 4A at 24V.
Supply installed was S1201903. This supply is on mezanine rack C2, U25-U27 LHS powering ISC C2 Slow Controls with 24V. This supply seems to be delivering 8A, unclear why this is.
We now had several locks with the PRCL UGF on. In each lock there were different TCS settings and different thermalization going on. Nevertheless the behavior is quite consistent.
The PRCL gain needs to be increased by a factor 3.8 in about 400 seconds.
A fit of one of the trends shows a good match with an exponential thermalization with a time constant of 100 minutes.
We could switch off the PRCL UGF servo (and the 52.1 Hz line) and hard code a gain change as above.