Got called at 10:57PM (PT) and IFO was actually locked in NLN with one SDF Diff, which I accepted and is screenshot is below (IMC_DOF_1_P TRAMP from 0 to 3 and IMC_DOF_2_Y TRAMP from 0 to 3).
Good timing for this since the 1Hz ringup was happening. I saw earlier today that turning on the ASC High Gain might help with this so I turned it on and it seems to be working.
SQZ also looked terrible inthe high-frequency domain. I ran the OPO temp scan and the SQZ Angle, but this did not seem to improve anything (plot attached).
Additionally, the EY Roll Ringup that plagued Ryan C's EVE shift is indeed happening again. I'm unsure what to do about this since it seems he and Rahul tried a multitude of damping techniques without avail.
ASC High Gain was turned off ~5 minutes after it seemed to be working. A minute later, we it rang up again and we lost lock.
So there's two issues (or maybe they're related I don't know):
1. 1Hz Ringup that can be survived while locked but only in High Gain settings
2. ETMY Roll mode which just rings up consistently
Out of ideas - will continue to investigate but nothing seems to be helping.
Called Rahul for help with the EY Roll Mode
The plan:
The issue with this plan is that it seems that without the high gain on, the oscillation prompts a lockloss but we'll see what happens as I watch it closely this time.
Lost lock at OMC_WHITENING after spending ~10-15 minutes at each powerup state to ensure EY Roll mode and Violins were low. They were. The 1Hz ringup started on queue as soon as LOWNOISE_ASC turned on and got worse. I think I turned on the ASC High Gain too early - confused as to what caused this lockloss. Trying again. It seems that the slow method works to avoid the EY Roll Mode ringup.
Additionally, Elenna's alog 87658 talks of her plan for how to try to avoid the 1Hz ringup and it involves DHARD_P to HBW using turning off FM8, then FM4. I will do this instead of the entire HBW ASC EQ script.
Lockloss tool sees EY glitching 1.2 before lockloss.
After some DRMI troubles, finally back to where I was before. In about 10 minutes, EY Roll Mode permitting, I will attempt to go to NLN and watch the 1Hz ringup, turning on HBW DHARD_P when I see the ringup.
It worked! (for now). We're in NLN with bad SQZ though similar range to last time we were locked (which isn't that good). The EY Roll Mode is on the rise though and if this lock is like the ones Ryan C (EVE) had, then usually they rise until lockloss in ~45 mins to an hour. I'm going to give IFO at least 10 minutes before re-engaging the DHARD_P LBW. The ringup comes back thereafter according to my last lock and Ryan's too. So, let's see what happens.
Really doesn't look great especially that as soon as we're near NLN, the EY Roll mode begins to trend upwards. Violin modes are going down though.
Well... The mode has rung up again after switching FM4 and FM8 back on... I don't know what to do here. Meanwhile EY Roll Mode is still ringing up despite locking veeery slowly per Rahul's advice.
EY Mode 15 is rung up slightly and damping it per the settings has made things worse - resetting its gain to 0 seems to calm it down.
My not-very-creative-out-of-options plan now is to wait here in these settings and attempt to go back to LBW DHARD P in another 20/30 or so... However, by then we will probably have lost lock due to Roll EY ::(
As expected when I went back to LBW, DHARD P rung up again so that doesn't work either.
While violins are high, they've been much higher before so we're not really ringing them up - they're all reporting as damping now anyway.
OMC DCPDs are going quite wild I assume due to this Roll Mode (attached).
If we lose lock here, I'm just going to IDLE IFO due to inability to stay locked and to avoid any more violin mode ringup. On the bright side, it's nearing DAY shift, involving well-rested experts.
Lockloss 11:51 UTC - IFO in IDLE.
TITLE: 10/23 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: We made it to NLN but the ETMY roll mode took us down, it appears to have rung up each time we get into OMC_WHITENING since maintenance.
I found new settings for ITMX mode13, FM1+FM2+FM10 G= -0.5.
The first 2 aquisitions we saw the Roll mode ringup but this 3rd time we did not, we slowly brought the IFO up, pausing to look at the mode in CHECK_VIOLINS, 10Ws, 25Ws, MAX_POWER, TRANSITION_FROM_ETMX, and LOWNOISE_ESD_ETMX.
LOG: No log.
I had been in NLN for 35 minutes fighting the ETMY roll mode, I also ran some SQZ stuff since it looked terrible (OPO_TEMP_SCAN, then ANG_SCAN) while in NLN. I was unsuccessful in damping the mode and it eventually grew saturated the DCPDs and killed the lock, there was also increased ground motion from a 5.6 from eastern Russia during this. In the middle of fighting the roll mode I saw the 1Hz oscillation start in DHARD_P so I turned off FM8 then FM4 on DHARD_P which fixed it.
Turns out that I had forgotten to turn the input on for the PR3 P estimator contribution from L (H1:SUS-PR3_M1_EST_P_FUSION_MODL_DRV_L_2GAP) (thanks to Edgard and Brian for having us even consider the estimators!), and that was causing the 0.6 Hz ASC ringups (87658). Even though we're pretty sure we found the cause, we've decided to temporarily turn off the PR3 and SR3 L and P estimators until we're back up and can verify that they are now working correctly.
Thanks for catching this, Oli. I made a note in FRS ticket 35410 reminding us to make an installation script which automatically sets all the epics variables so we are more likely to get all the right settings from the beginning.
TITLE: 10/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Currently relocking and at LOWNOISE_COIL_DRIVERS. Still struggling with a 1 Hz oscillation(87658), but we've solved issues with MICH phase margin and with a 0.6 Hz oscillation caused by incorrect estimator settings, so 2/3 of the issues solved?
LOG:
14:30UTC Started relocking
Initial alignment
Lockloss from OMC_WHITENING due to 1 Hz ringup
Multiple locklosses from DRMI and under due to ALSX getting noisy and ALSY having some glitchy drops in power
Locklosses from LOWNOISE_LENGTH_CONTROL, MOVE_SPOTS, etc.
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 15:45 | Matt | JOAT | n | Putting stuff away | 15:50 | |
| 15:49 | FAC | Kim | OptLab | n | Tech clean | 16:10 |
| 16:48 | FAC | Randy | XTube | n | Caulking more tube | 20:40 |
| 17:26 | Tony | CER | n | Putting laptop away | 17:31 | |
| 20:18 | VAC | Travis | MX, MY | n | Taking measurements | 23:43 |
| 20:18 | Keita | OptLab | y(local) | ISS Array | 21:44 | |
| 20:39 | FAC | Randy | Yarm | n | More Caulking of the BTE, starting at EY | 22:08 |
| 20:40 | IO | Rahul | Opt Lab | y(local) | ISS array | 21:44 |
| 20:58 | SEI/CC | Jim, Mitch | Ends | n | Wind fence, HEPI, and dust mon pump FAMISs | 00:27 |
| 21:17 | Tyler, Shinji | OptLab | y(local) | Meeting with Keita | 21:44 | |
| 21:47 | Jenne, +PAC | Roof | n | Overlooking the arms | 22:08 | |
| 22:38 | PCAL | Tony | PCAL Lab | y(local) | Setting up measurement | 22:38 |
We managed to track down the source of the 0.6 Hz oscillation that we see at move spots and full power. It seems to be the result of the new pitch and length estimators on PR3 and SR3 that were installed on Tuesday. We tested this by sitting at move spots (after the spots converged), and turning on and off the estimators for a few minutes at a time. When turning ON the estimators, the 0.6 Hz ringing is not immediately apparent- it will slowly grow. However, once the 0.6 Hz oscillation is visible in the controls, turning OFF the estimator immediately stops the ringing. Therefore, we think this is the culprit for this instability. Oli will be turning off the length and pitch estimators for PR3 and SR3 for now. The yaw estimators are still on because they have been operating stably for a long time and were not changed this Tuesday.
We have also put the factor of 2 increase of MICH2 gain into the guardian, since we kept forgetting to add it in. Several locklosses that we thought were due to various other things were actually due to the MICH loop ringing up.
Finally, we just had a lockloss after moving to camera servos because the 1 Hz oscillation began to grow. Here is everything I tried to stop the ringing (none of it worked):
I then had an idea to go to high bandwidth ASC using the seismic script, but we lost lock as soon as I thought of that.
Next plan: go to lownoise length control, skip lownoise asc, go to the final spots and camera servos, stay in HBW ASC and wait for the 1 Hz ring up and see if we can ride it out this way.
Attached scope screenshot shows the 0.6 Hz oscillation disappearing as soon as Oli flipped the length and pitch estimator switches OFF.
Here's the measurements taken for MICH that show the phase margins at different points in the locking sequence
We have been thinking that maybe the MICH UGF is too low (I had a memory that it was supposed to be 8 Hz). Then I found this alog from Evan where he designed it to be 5.5 Hz and the phase margin looks about the same 76631. Note that Oli's measurement was taken after we DOUBLED the gain, so somewhere along the way we lost 6 dB of gain.
I held us at high bandwidth ASC for 9 minutes and there was no 1 Hz oscillation. A few minutes after running lownoise ASC the 1 Hz oscillation came back. It begins first in DHARD P. I stopped the oscillation by running the ASC HI GAIN script that we set up for earthquakes. It looks like the oscillation stopped as soon as DHARD P was put into HBW state. After waiting a few minutes, I put us back into the lownoise state. I have previously been suspicious of DHARD P for being the culprit causing the 1 Hz ring up. My recommendation is that if we see this again, try turning OFF FM8 in the DHARD P filter module (labelled GVBoost). If that doesn't work, just run the HI GAIN ASC script like you would for an earthquake, on the IS sensor config screen.
EDIT: I posted this comment too soon- the 1 Hz ringing came back. I tried just turning off DHARD P FM8, but that did nothing. However, going to Hi Gain ASC worked again, so that seems to be a good way to get around this (for now).
I've been flipping back and forth between high and low bandwidth DHARD P. The 1 Hz definitely begins when we are in LBW, and it seems to actually be the lowpass/reshaping in FM4 that is the issue.
I also noticed that there is a glitch in DARM whenever FM4 is turned on or off, so I increased the filter ramp time from 15 to 20 seconds.
To take DHARD P to HBW, disengage FM8, wait for the filter to ramp, then disengage FM4.
To take DHARD P to LBW, engage FM4, wait for the filter to ramp, then engage FM8.
I tried to measure DHARD P to understand what the instability is but we had a lockloss. Looks like it's an ETM glitch?
My recommendation is to put DHARD P in HBW if the 1 Hz starts oscillating again.
TITLE: 10/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 21mph Gusts, 17mph 3min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.30 μm/s
QUICK SUMMARY:
00:43 UTC We reached OMC_WHITENING where we will sit to damp violins for a bit.
IX13 has been the problem mode, I've set its' gain to 0 in lscparams and reloaded the VIOLIN node. I think I have found a new setting for IX13, I changed the phase from -60 to-30 and used a negative gain. Its damping, slowly...
We've also noticed that the ETMY roll mode is ringing up, turning off the damping made it ringup faster.
Sheila, TJ, Oli, Matt
We reverted the ASC gain changes (87582) setting INP1 P to 1 and CSOFT P to 25 at MAX power (rather than 30). Most of our locklosses overnight were from states before Max power, so the CSOFT P gain can't have been the problem, but we are undoing it for now just for the sake of reverting recent changes.
We looked at one of the overnight locklosses, it seems that MICH is ringing up at 4.7 Hz. Since Oli is sitting at 2W DCreadout to damp violin modes, we measured the MICH OLG there, and we see it is pretty close to unstable at 5Hz, with low coherence there. We added a factor of 2 gain in LSC MICH2, to bring the UGF to 10 Hz similar to the references, and give us 35 degrees phase margin.
Next we checked the SRCL UGF, which is also locked on POP45, and it's gain looks low by a factor of 5 compared to the reference. This loop has a large phase bubble so it's still stable. POP 45 whitening gain and filters seem to be the same as a few days ago, and the POP LF power is the same as it was a few days ago at 2W. PRCL gain also looks low compared to the reference, but is stable.
We were able to get to OMC_WHITENING (almost to low noise), but while we were sitting there we had the old ring up. We tried manually increasing the CSOFT P gain to 30, but the osciallation had already grown large and we lost lock anyway. I've now put the csoft P gain back to 30 in max power in the guardian.
To add to today's mysteries, I tried raising CHARD P gain by 20% in HBW to see if that would stabilize us, but that caused a lockloss, indicating that maybe CHARD P HBW is marginal.
We also had a lockloss while I was measuring the CHARD P HBW OLG, but I was running an injection that I had run earlier today, so that also doesn't make sense to me as being the cause.
We just tried powering up without moving the spots, but had a lockloss as soon as we got to 60 W.
Following the reversion of gains in lscparams.py and the reload of ISC_LOCK, I also reloaded the nodes which import this file but do not use the modified lines in order to green-up GRD-CFC. Nodes loaded are:
ALIGN_IFO,ALS_COMM,ALS_DIFF,ALS_XARM,ALS_YARM,CAMERA_SERVO,H1_MANAGER,IMC_LOCK,INIT_ALIGN,ISC_DRMI,LASER_PWR,LOCKLOSS_SHUTTER_CHECK,OMC_LOCK,SEI_CONF,SEI_ENV,SQZ_FC,SQZ_MANAGER,SUS_CHARGE,TCS_ITMX_CO2_PWR,TCS_ITMY_CO2_PWR,TEST,THERMALIZATION,TMS_SERVO,VIOLIN_DAMPING
The ringup and lockloss in OMC_WHITENING was indeed the usual 1 Hz ringup
We've had a lot of 0.6Hz wobbling in the move spots state, so Elenna made the move spots a2l gains different from final (undoing a change from this spring), and made the move spots ones the same a2l gains as they were before the camera bump (87473)
Attached is a comparison of the build ups in the move spots states before and after this change, things look about the same, so this hasn't fixed the wobbles.
This isn't our main locking problem today, it doesn't seem to be causing our locklosses and gets better as we power up.
Actually, we just realized we've been forgetting to change the MICH LSC gain before powering up, and looking back the last several locklosses have been due to MICH ringing up. I added a line in DRMI_TO_POP to increase the MICH2 gain to 2. I'm not sure if this is the best permanent solution, but it means we won't forget for now.
Something happened with BRSY this morning during maintenance that caused it to ring up more than normal and now the damping is not behaving quite as expected. For now, I have paused the ETMY sensor correction guardian with the BRSY out of loop and turned off the output of the BRS so it won't be used for eq mode, should that transition happen.
So far today, I did a bunch of "recapturing frames" in the BRS C# code, which has usually fixed this issue in the past. We also restarted the beckhoff computer, then the plc, C# and epics ioc. This did not recover the BRS either. Marc, Fil and I went to EY and looked at the damping drive in the enclosure and I think it was behaving okay. When the drive came on, the output would reach ~1.8V, then go to 0V when it turned off.
I've contacted UW and we will take a look at this again tomorrow.
Looked at this with Michael and Shoshana and the BRS is damped down now. Still not sure what is wrong but we have a theory that one side of the capacitive damper is not actuating. This seems to work okay when the velocities are either low or very high, but if they are moderate the high gain damping doesn't work well enough to get the BRS below a certain threshold, and instead keeps the BRS moderately rung up. We adjusted the damping on/off thresholds so the high gain damping will turn off at a higher velocities.
I will try to do some tests with it next week to see if we can tell if one side of the damper is working better than the other. For now, we should be able to bring the BRS back in loop.
[Joan-Rene Merou, Alicia Calafat, Anamaria Effler, Sheila Dwyer, Robert Schofield, Jenne Driggers] We have looked at the near-30 Hz and near-100 Hz combs (Detchar issue 340) in all of LHO Fscan channels (Full 148 channels list can be found in O4_H1_Fscan_ch_info.yml) to find witnesses and also channels where the amplitude and coherence change at the same dates as DARM. The list of combs is the following one:
| spacing (Hz) | offset (Hz) |
|---|---|
| 29.9695138888 | 0 |
| 99.99845486125 | 70.02888889 |
| 99.99845679 | 0 |
| 99.99846 | 29.9694 |
| 99.9984722225 | 89.90847222 |
| 99.99865 | 0 |
| 99.99845 | 10.08992 |
| 29.96952 | 520.17208 |
| 29.9695211 | 589.9007589 |
| 29.96951374 | 760.22840625 |
We list here the channels that do show most of these Combs. These same channels do show changes in coherence between July 1st and July 7th 2024, but do not show changes in the amplitude of the combs.
- H1_IMC-F_OUT_DQ
- H1_LSC-MCL_IN1_DQ
- H1_LSC-MICH_IN1_DQ
- H1_LSC-SRCL_IN1_DQ
- H1_PEM-CS_MAG_EBAY_LSCRACK_X_DQ
- H1_PEM-CS_MAG_EBAY_LSCRACK_Y_DQ
- H1_PEM-CS_MAG_EBAY_LSCRACK_Z_DQ
- H1_PEM-CS_MAG_LVEA_INPUTOPTICS_X_DQ
- H1_PEM-CS_MAG_LVEA_INPUTOPTICS_Y_DQ
- H1_PEM-CS_MAG_LVEA_INPUTOPTICS_Z_DQ
In most channels, the comb amplitude tends to get quite low after ~1500 Hz. The following sets of channels show differences between X, Y and Z:
- H1_PEM-CS_MAG_EBAY_SUSRACK_X_DQ (Higher amplitudes and towards higher frequencies)
- H1_PEM-CS_MAG_EBAY_SUSRACK_Y_DQ (Lower comb amplitudes)
- H1_PEM-CS_MAG_EBAY_SUSRACK_Y_DQ (Lower comb amplitudes)
Regarding CS_MAG_LVEA_OUTPUTOPTICS, these combs can be seen best in X, weaker in Y and almost non-existent in Z. (In CS_MAG_LVEA_INPUTOPTICS they look roughly the same height)
- H1_PEM-CS_MAG_LVEA_OUTPUTOPTICS_X_DQ (Strongest)
- H1_PEM-CS_MAG_LVEA_OUTPUTOPTICS_Y_DQ (Weaker lines)
- H1_PEM-CS_MAG_LVEA_OUTPUTOPTICS_Z_DQ (Almost no lines)
Same behavior at:
- H1_PEM-CS_MAG_LVEA_VERTEX_X_DQ (Strongest lines)
- H1_PEM-CS_MAG_LVEA_VERTEX_Y_DQ (Weaker lines)
- H1_PEM-CS_MAG_LVEA_VERTEX_Z_DQ (Almost no lines)
We can see that these combs mostly appear in the corner station. The combs do not appear in neither EX nor EY channels. However, comb 99.99865 Hz offset 0.000 appears in many EX, EY channels and does become more coherent after July 7th. However, it is very close to 100 Hz so it may be influenced by other round-number combs (?)
Looking at the 52 additional channels listed in LHO ADC channels list, we have found the following information: The combs appear in the following channels with high peaks and high coherence: - H1:PEM-CS_ADC_5_18_2K_OUT_DQ - H1:PEM-CS_ADC_5_21_2K_OUT_DQ - H1:PEM-CS_ADC_5_26_2K_OUT_DQ ! All combs appear here and with high peaks Some combs appear in the following channels with low peaks and low coherence: - H1:PEM-CS_ADC_5_22_2K_OUT_DQ - H1:PEM-CS_ADC_5_23_2K_OUT_DQ - H1:PEM-CS_ADC_5_24_2K_OUT_DQ The following channels do not show the peaks but show an increase in coherence from July 1st to July 7th 2024: - H1:PEM-CS_ADC_5_25_2K_OUT_DQ - H1:PEM-CS_ADC_5_27_2K_OUT_DQ - H1:PEM-CS_ADC_5_30_2K_OUT_DQ Only the 99.99 Hz offset 0 combs appear in the following channels: - H1:PEM-CS_ADC_4_27_2K_OUT_DQ - H1:PEM-CS_ADC_4_28_2K_OUT_DQ - H1:PEM-CS_ADC_5_19_2K_OUT_DQ - H1:PEM-CS_ADC_5_20_2K_OUT_DQ - H1:PEM-CS_ADC_5_31_2K_OUT_DQ In the arms, the following channels show coherence with only the 99.99 Hz offset 0 combs: - H1:PEM-EX_ADC_0_09_OUT_DQ - H1:PEM-EX_ADC_0_13_OUT_DQ - H1:PEM-EY_ADC_0_11_OUT_DQ - H1:PEM-EY_ADC_0_12_OUT_DQ - H1:PEM-EY_ADC_0_13_OUT_DQ - H1:PEM-EY_ADC_0_14_OUT_DQ The following channels show the unexpected behavior of showing the 99.99 Hz peak in July 1st with coherence, but it disappears on July 7th: - H1:PEM-EX_ADC_0_12_OUT_DQ In summary, after investigating the Fscan channel list and the additional channels. The ones that seem more promising as showing most of the lines with high coherence and high amplitude peaks are: - H1:PEM-CS_ADC_5_18_2K_OUT_DQ - H1:PEM-CS_ADC_5_21_2K_OUT_DQ - H1:PEM-CS_ADC_5_26_2K_OUT_DQ - H1:IMC-F_OUT_DQ - H1:LSC-MCL_IN1_DQ - H1:LSC-MICH_IN1_DQ - H1:PEM-CS_MAG_EBAY_LSCRACK_X_DQ - H1:PEM-CS_MAG_EBAY_LSCRACK_Y_DQ - H1:PEM-CS_MAG_EBAY_LSCRACK_Z_DQ - H1:PEM-CS_MAG_LVEA_INPUTOPTICS_X_DQ - H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Y_DQ - H1:PEM-CS_MAG_LVEA_INPUTOPTICS_Z_DQ - H1:PEM-CS_MAG_EBAY_SUSRACK_X_DQ - H1:PEM-CS_MAG_LVEA_OUTPUTOPTICS_X_DQ Of these, channel H1:PEM-CS_ADC_5_26_2K_OUT_DQ appears to be the one with the highest amplitudes. The following figure illustrates its ASD and Coherence with DARM on the date of July 7, 2024, showing the peaks for the harmonics of the combs in this study. As can be seen in the ASD, the highest peaks are those in the list of the near-30 and near-100 Hz plots. The only peaks higher than these are the power mains at powers of 60 Hz. This channel shows all the combs listed. Most of these combs also show very high coherence with DARM.![]()
After determining in which channels the peaks appear present, we have studied the coincidence of changes in the comb heights versus the bias in the H1:SUS-ITMY_L3_ESDAMON_DC_OUT16. The following figure shows the coincidences between the changes in the relative amplitude of the first harmonic of each comb (sort of SNR) in DARM and the mean counts in H1:SUS-ITMY_L3_ESDAMON_DC_OUT16 across time. It can be seen that previously to May 2nd, the channel count was set to 60. Once it changed to around -223 after that date, the SNR of the peaks overall increased in a sudden way. Afterwards in June 13th when the count was reduced to 0, most peaks got a much lower SNR at the same time.