After the PR2 spot move last night we have some CHARD Y coherence around 20 Hz, so we ran the A2L script in commissioning time today.
Want to change gain from 3.22 to 3.19, rounded to 2 decimal places. St.Div is 0.57. Change of 0.034
H1:SUS-ETMX_L2_DRIVEALIGN_P2L_SPOT_GAIN => 3.19
Want to change gain from 4.87 to 4.89, rounded to 2 decimal places. St.Div is 0.946. Change of -0.018
H1:SUS-ETMX_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 4.89
Want to change gain from 4.43 to 4.39, rounded to 2 decimal places. St.Div is 0.823. Change of 0.041
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => 4.39
Want to change gain from 1.03 to 0.98, rounded to 2 decimal places. St.Div is 0.159. Change of 0.049
H1:SUS-ETMY_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 0.98
Want to change gain from -0.99 to -1.01, rounded to 2 decimal places. St.Div is 65.221. Change of 0.015
H1:SUS-ITMX_L2_DRIVEALIGN_P2L_SPOT_GAIN => -1.01
Want to change gain from 2.82 to 2.83, rounded to 2 decimal places. St.Div is 0.512. Change of -0.006
H1:SUS-ITMX_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 2.83
Want to change gain from -0.37 to -0.35, rounded to 2 decimal places. St.Div is 0.134. Change of -0.015
H1:SUS-ITMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => -0.35
H1:SUS-ITMY_L2_DRIVEALIGN_Y2L_SPOT_GAIN => -2.47
Want to change gain from -2.47 to -2.47, rounded to 2 decimal places. St.Div is 1.043. Change of 0.003
SDF screenshot attached, these values have been updated in lscparams
ASC sdf diffs accepted before going into Observing earlier: 78036
Fri May 24 10:08:05 2024 INFO: Fill completed in 8min 2secs
Gerardo confirmed a good fill curbside.
Out of observing times: 1500-1501, 1531-1540 UTC
The TCSX laser had to relock two times in the past half hour. The first time was because it ran out of PZT range (#1 on the screenshot), not uncommon and something that happens from time to time. ~20 minutes after it relocked the chiller temperature got a bit warmer for an unknown reason (#2 & #3). This caused it to unlock and then relock again, this last time everything seems stable (#4).
Out of paranoia I when to check on the chillers and didn't notice anything odd - water levels ok, filters ok, no leaking water/coolant, no critters making nests inside that I could see.
TITLE: 05/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 9mph Gusts, 6mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.07 μm/s
QUICK SUMMARY:
H1 is currently locked and Observing for over an hour and a half.
Everything looks good for continued Observing.
TITLE: 05/24 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Most of this shift spent recovering from PR2 spot move, but locking went smoothly after. H1 has been locked and observing for 3 hours.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
22:02 | PCAL | Tony, Dripta | PCAL Lab | local | Lab measurements | 02:38 |
03:36 | ISC | Sheila, RyanS | LVEA | Local | Beatnote alignment | 04:07 |
TLDR: H1 is back to observing as of 05:47 UTC after an extended period of corrective maintenance.
[ISC] Sheila and I went out to ISCT1 to fix the COMM beatnote alignment and were able to increase it from -22 dBm to 0 dBm (all just by turning the yaw knob on the far beamsplitter which combines COMM and DIFF). Once we came back, I started the locking sequence. After a round of CHECK_MICH_FRINGES, PRMI locked instantly and ASC did its job, making the POP buildups as good as I've seen them tonight. DRMI locked quickly afterwards, and we continued locking without issue. NLN reached at 05:03 UTC.
Once locked, I noticed some SDF differences on the PRM, PR2, and PR3 models related to A2L gains. Trending them back and conferring with Sheila, these should have been accepted yesterday after Sheila's work in alog77988, so I accepted them. Trends and SDF accepting screenshots in attachments 1 and 2.
[CAL] There were also some SDF diffs on the CALCS and SUSETMX models, which were expected following alog78008; these were accepted and screenshots are in attachments 3 and 4.
[SQZ] To finish off the activities before observing this evening, Sheila and Naoki pointed out that SQZ performance was poor. I started by running SCAN_ALIGNMENT_FDS and SCAN_SQZANG with SQZ_MANAGER, but high frequency noise didn't seem to be any better. Naoki suggested setting the SQZ angle to 160 and running SCAN_SQZANG again, thinking the optimum angle was outside of the range done by the first scan. He was right, and after the second scan the angle settled at 202 and DARM looks much better. I accepted the SDF diffs for ZM4 and ZM6 alignment sliders, screenshot is attachment 5.
After we moved the PRC alignment this afternoon (alog78012), I was able to run an initial alignment without issue. When trying to lock afterwards, I was unable to lock DRMI, but I could lock PRMI, although the buildups looked poor (neither POP 18/90 above 30 counts) and PRMI ASC only made them worse. I then decided to lock PRMI, improve the buildups as much as I could by-hand with PRM alignment, then skip PRMI ASC and try DRMI locking. This also proved unsuccessful, so Sheila recommended I try to improve the buildups using the HAM1 ALS/POP beam steering picomotor with PRMI locked and ALS unlocked. To do this, I changed the 'gate_valve_flag' in lscparams.py to True, loaded both ISC_LOCK and ISC_DRMI, took ISC_LOCK to DOWN, misaligned both ETMs, aligned PRM, and requested ISC_DRMI to PRMI_LOCKED. PRMI locked quickly. I then used the picomotor to successfully improve the buildup signals and engaged PRMI ASC, which worked this time, even further improving the buildups. Satisfied with my improvements, I reverted the change I made to lscparams.py, reloaded both Guardians, re-requested INIT and DOWN in ISC_LOCK, and started lock acquisition.
Unfortunately, it seems my picomotor adjustments severely degraded the ALS COMM beatnote (was -9 dBm, now -22 dBm). After further consulting with Sheila, we agree the next logical step is to realign the beatnote path on ISCT1 as Jenne had done after the last alignment change (alog77968). She has courteously agreed to meet me on-site after a bit to assist me with this.
J. Freed, J. Kissel
Today we did damping loop injections on all 6 BOSEMs on the ITMX. Which what partially done by anamaria previously for half of them and we found simmilar coupling effects around the 14Hz range.
Changes from Anamaria:
We could not see any noticeable coupling at a gain of 600 for the BOSEMs, very likely due to the increased noise at low frequency today. As such, for this test we incresed the gain to 750. At this level saw coupling from the ITMX. We also increased the range of interest down to 8Hz (We did not change the range of the bandpass filter today, just the plot range) as we saw some noise coupling on some sensors below 10Hz.
Plots, code, and text files of flagged results can be found in /ligo/home/joshua.freed/20240523/Scripts
While the dtt's can be found in /ligo/home/joshua.freed/20240523/Data
All sensors of ITMX showed some coupling, with every sensor showing coupling in different ranges around 14Hz. With the F1-3 being narrow band around 14Hz, and the LF, RT, SD having a larger range from 10-14Hz. Also noting, F1, LF, RT had more than one instance of coupling in a small range around 92Hz, which Anamaria's F1 data also shows.
itmx_f1_20240523.png shows an example plot of the coupling with the grey dots on the bottom plot being the Estimated upper limit of the ambiant noise and the blue dots are the actual measured noise that are flagged
itmx_f1_ana_20240502.png Shows Anamaria plot for comparison
Sheila D, Ryan S, Jenne D
We moved our PRC back to its old alignment that we've had before 8 days ago. To do this we ran a green initial alignment and then went to the PR2_spot_move state to slowly step PR3 in the direction of P:-117 Y:154. We had to move the pico a bit every 4urads or so to compensate. The AS air spot and Refl spot were long gone on the cameras and when we stopped at PR3 P:-124 Y:94.7 we tried to find it by hand moving PR2 and IM4 without luck. Sheila brought all PR optics back to their 8 days ago position and we found light on the cameras again. We then went back to where we were and continued the walk to the desired PR3 postion and the light again returned on camera.
Ryan is starting an initial alignment with this new (old >8 days ago) alignment now.
TITLE: 05/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Calibration sweep and then some commissioning time today. A lock loss ended a 26 hour lock. We then move the PR2 spot back to our previous position >8 days ago. We just finished that move and now Ryan is starting an alignment.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
16:27 | PCAL | Francisco, Tony | PCAL lab | local | Lab measurements (Tony out 18:30) | 19:01 |
22:02 | PCAL | Tony, Dripta | PCAL Lab | local | Lab measurements | 00:02 |
TITLE: 05/23 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 22mph Gusts, 14mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.08 μm/s
QUICK SUMMARY: H1 is currently down for some corrective spot position moves.
Naoki, Karmeng, Andrei, Sheila
We did NLG sweep on DARM at NLG 16.9 (nominal) and 42. The IFO was locked for more than 20 hours and well thermalized. We also tried NLG of 65.9, but the squeezing level was not stable so we gave up this NLG. We will take the third NLG data tomorrow if IFO is thermalized.
Previous NLG sweep on DARM: 73747
How to measure NLG: 76542
How to change NLG: 73801
Note:
UTC | demod phase | DTT ref | NLG | SQZ at 2kHz (dB) | |
FDS | 16:29:00-16:34:00 | 160.91 | 3 | 16.9 | -4.2 |
No SQZ | 16:36:20-16:41:20 | 0 | |||
ASQZ | 16:56:20-17:01:20 | -100.37 | 6 | 16.9 | 15.4 |
mean SQZ | 17:11:00-17:16:00 | 7 | 16.9 | 12.6 | |
FDS | 18:02:10-18:07:10 | 162.13 | 4 | 42 | -4.4 |
ASQZ | 18:19:30-18:24:00 | -87.6 | 8 | 42 | 20 |
mean SQZ | 18:29:00-18:34:00 | 9 | 42 | 17 |
OPO trans (uW) | OPO temp | Seed amplified | Seed unamplified | NLG |
80 | 31.470 | 0.215 | 0.0127 | 16.9 |
100 | 31.454 | 0.534 | 0.0127 | 42 |
110 | 31.448 | 0.0725 | 0.0011 | 65.9 |
After PR2 spot move yesterday in 78012, we did NLG sweep again. This time we took three NLG at 7.9, 16.3 (nominal), 55.9.
UTC | demod phase | DTT ref | NLG | SQZ at 2kHz (dB) | |
No SQZ | 16:41:00-16:46:00 | 0 | |||
FDS | 16:54:08-16:59:08 | 161.59 | 10 | 7.9 | -4.4 |
ASQZ | 17:04:00-17:09:00 | -95.63 | 11 | 7.9 | 11.1 |
mean SQZ | 17:10:52-17:15:52 | 12 | 7.9 | 9.1 | |
FDS | 17:31:40-17:36:40 | 192.47 | 13 | 55.9 | -4.1 |
ASQZ | 17:43:54-17:48:54 | -86.42 | 14 | 55.9 | 21.2 |
mean SQZ | 17:50:53-17:55:53 | 55.9 | 18.5 | ||
FDS | 18:12:31-18:17:00 | 190.31 | 15 | 16.3 | -4.7 |
ASQZ | 18:21:54-18:26:54 | -97.79 | 16 | 16.3 | 15.3 |
mean SQZ | 18:28:12-18:33:12 | 17 | 16.3 | 12.5 |
OPO trans (uW) | OPO temp | Seed amplified | Seend unamplified | NLG |
60 | 31.484 | 0.0086 | 0.00109 | 7.9 |
80 | 31.468 | 0.0174 | 0.00107 | 16.3 |
105 | 31.446 | 0.0609 | 0.00109 | 55.9 |
Vicky, Karmeng
This NLG scan is compatible with ~30% SQZ losses, ~20 mrad phase noise.
Attachment 1, 2 - Calculated loss ~30% from mean sqz and generated sqz, then fit ASQZ/SQZ to estimate phase noise ~ 20 mrad and technical noise. If fitting SQZ+ASQZ together to estimate, then fit loss ~32-33%. This uses standard linear opo equations to estimate generated squeezing level based on NLG.
Attachment 3 - Calculated loss ~ 27% from mean sqz and generated sqz, then fit ASQZ/SQZ to estimate phase noise ~ 20 mrad and technical noise. This uses bowtie opo equations to estimate generated squeezing level based on NLG (few % lower generated sqz than the above estimate). See Eq. 13 of Dhruva's ADF paper, e.g. P2200041.
NLG calibration - Estimates OPO green pump trans threshold @ 142 uW. This seems close to previous threshold estimates ~149 uW made just after moving to this crystal spot (LHO:73562, Oct2023 crystal move).
A comparison of O4a (hd,ifo) and O4b NLG (ifo) scans, maybe most interesting is comparing homodyne vs. interferometer squeezing in O4a (~32% loss, LHO:78000). O4a/O4b IFO losses look similar, but I think it's largely an issue with this O4b measurement?
A note about this NLG scan - I think total optical losses should be < 30% based on seeing >5dB SQZ previously. For example, the -5.4 dB SQZ observed in LHO:76553 is too much squeezing, and incompatible with losses >30%. So I think this measurement has higher losses than "normal" in O4b, maybe related to the alignment / mode-matching / (something that drifts) not being optimal here. Would be interesting to get back to the -5dB spot (of course), and see how losses look then.
Code with instructions is here: https://git.ligo.org/victoriaa.xu/nlgscans
Lockloss @ 05/23 21:31 UTC
J. Kissel, T. Shaffer, J. Driggers Joe Betz and Jenne Driggers spoke of increasing the calibration line heights that drive the ETMX actuation stages in the face of the elevated noise in the detector in the 10-20 Hz frequency region (LHO:77993). TJ caught me, pointed this out to me, so I've staged this change by editing - /opt/rtcds/userapps/release/isc/h1/guardian/lscparams.py (rev 27751 lines 481 - 484) here, I increased the gains on the calibration line oscillators STAGE FROM TO FACTOR OF UIM / L1 6.6 15.0 ~2x PUM / L2 1.7 8.0 ~4x TST / L3 0.061 0.1 ~2x - /opt/rtcds/userapps/release/isc/h1/guardian/ISC_LOCK.py (rev 27729, lots of lines, where "CAL_LINE" appears in several states) here, as indicated in Louis' aLOGs where he's changed the line heights (e.g. LHO:71947), one *also* needs to change the correspond gains in the front-end calibration pipeline's demodulation of the lines. So I've added the following lines to the existing for loop that changes these gains for g in ['CLK','SIN','COS']: ezca['CAL-CS_TDEP_SUS_LINE1_COMPARISON_OSC_%sGAIN'%(g)] = (value) ezca['CAL-CS_TDEP_SUS_LINE2_COMPARISON_OSC_%sGAIN'%(g)] = (value) ezca['CAL-CS_TDEP_SUS_LINE3_COMPARISON_OSC_%sGAIN'%(g)] = (value) Will load at our earliest convenience.
Guardian code loaded, and I've also committed the changes to the userapps svn: /opt/rtcds/userapps/release/isc/h1/guardian$ svn commit -m "Adjusted calibration line height gains. See LHO:78008." lscparams.py Sending lscparams.py Transmitting file data .done Committing transaction... Committed revision 27753. /opt/rtcds/userapps/release/isc/h1/guardian$ svn commit -m "Added calibration line comparison oscillator gains as a thing to get set as well when calibration lines are turned on and off in various states." ISC_LOCK.py Sending ISC_LOCK.py Transmitting file data .done Committing transaction... Committed revision 27754. /opt/rtcds/userapps/release/isc/h1/guardian$ OPSINFO :: As of this entry, the guardian states which set these gains have not yet run, so the new gain settings will need to be accepted in SDF before we can go to observe again.
Wrapped up commissioning at 1920UTC and we are back to Observing. Locked for 23:39
I ran the A2L script again today, accepted the gain diffs for the 4 test masses.
The script is still in ...userapps/isc/common/scripts/decoup/a2l_min_generic_LHO.py . Some room for improvement is that it leaves several SDF diffs (TRAMPs on the 4 quads, and settings in the PIT7 and YAW7 ADS loops), so we should add into the script to revert those.
Attached is the printout of what the script measured, as well as a screenshot of the accepted a2l gain diffs.
The attached screenshot shows that the A2L script worked well, the ASC coherences around 30 Hz are now low (the CHARD Y coherence below 15 Hz is there if things are well tuned at 25-35 Hz, this has been the case for a long time).
Otherwise, our sensitivity is still worse below 50Hz than it was in early May. The PRCL coherence may explain some of our noise in this region, but it is the same level of coherence as in early May.
Alex Ritzie, Ansel Neunzert
Key points
The 9.5 Hz comb triplet (LHO worst offender comb), 11.11 Hz comb, and 11.9 Hz comb, are present in {H1,L1}:PSL-ISS_PD{A,B}_REL_OUT_DQ. These combs were previously known to be common between the two sites (see LLO 70030, LLO 66036, git issue for 9.5 and 11.9 for more info). A near-30 Hz comb is also seen at LHO only.
Details
Plots of H1:PSL-ISS_PDA_REL_OUT_DQ and L1:PSL-ISS_PDA_REL_OUT_DQ are attached (figures 1 and 2). Note that the color coding differs between the two plots. The 9.5 Hz combs are much stronger at LLO than at LHO. The 11.9 Hz comb is almost not visible at LLO, but the first harmonic is faintly present (figure 3).
Note that the 9.5 Hz combs may not appear to line up exactly on this plot at higher frequencies, but they are known to shift around regularly and I'm just plotting the average O4a positions here. I'm confident that it's the same artifact because the characteristic triplet structure is clearly apparent at every peak (see figures 4 and 5).
Both of these plots are from May 6. This date is not special, it's just a convenient recent date with a reasonable amount of observing time, which avoids other recent comb contamination issues at LLO.
Methods & context
Alex has been building an improved version of the STAMP-PEM / Fscan comb comparison tool first mentioned in this alog. Essentially, this tool leverages the relatively low-resolution but much larger channel set of STAMP-PEM's coherence data to try to pick out possible new witness channels for combs identified by Fscans. Alex's results for Hanford December 30-31 2023 are attached in figure 6 (more recent STAMP-PEM data was not yet available). This reproduces prior results showing the combs in IMC WFS channels, and highlights several other channels. Following up with high-resolution Fscan spectra, I found that the PSL accelerometers which appear on the heatmap show some broad peaks in the vicinity of some comb frequencies, but are not a match to the combs at high resolution (probably unsurprisingly) so I moved on to looking at the channel mentioned above, and from there to looking at the corresponding LLO data.
I have opened a git issue here https://git.ligo.org/detchar/detchar-requests/-/issues/243 with notes on next steps & follow up; additional input welcome.
Since we are considering reverting the PR2 spot move, I measured the spot positions by adjusting A2L gains for PR2, PRM, and PR3. The first attached screenshot shows the current sliders and pico position, the second screenshot shows the A2L gains in SDF.
A2L gain | ||
PRM Y2L | 0.48 | |
PRM P2L | 1.76 | |
PR2 Y2L | -0.39 | |
PR2 P2L | -3.0 | |
PR3 Y2L | 1.5 | |
PR3 P2L | -0.3 |
Here is the calculation of what these a2l coefficients imply in spot position (fixing the typo of swapping the PR2 P2L and Y2L coeffs):
A2L gain | Spot position [mm] | |
PRM Y2L | 0.48 | 1.0 |
PRM P2L | 1.76 | 3.6 |
PR2 Y2L | -3.0 | -6.0 |
PR2 P2L | -0.39 | -0.8 |
I don't have handy the conversion for the larger PR3 triple suspension's A2L coeff to spot position, and Sheila also mentioned that the error bars on that one are a bit larger, so I'm not quoting a spot position for PR3.
PRM P2L | 1.7 | |
PRM Y2L | 0.52 | |
PR2 P2L | -0.38 | |
PR2 Y2L | -7.5 | |
PR3 P2L | -1.5 | |
PR3 Y2L | 1.6 |
In the measurements above, I didn't mean that the PR3 gains had more uncertainty than the others, but that the pitch ones had more uncertainty than yaw, because when I was tuning pitch I sometimes didn't see a clear difference. PR3 yaw seemed similar to the other yaw measurements.
I've accepted this in the OBSERVE and the safe.snap. Also attached is a screenshot of the sliders at the time of this measurement.