This morning while Corey and the commissioning team were trying to lock and power up the interferometer, the violin modes were pretty rung up. For most of the modes, I was able to damp them down using nominal settings except three of them which are listed below along with the settings which seems to be working for now.
FAMIS 31088
No major events of note. The slow changes in PMC TRANS and REFL power seem to follow AMP2 output power.
TJ, Camilla, Checking as Sheila was concerned about this as Georgia/Craig need to move the ITMX SPOT GAIN "CENTER
" 84702.
Attached are the HWS Live plots comparing when we get to 10W and 120s later for ITMX and ITMY now. And also for ITMX and ITMY at our last 10W power up before the vent (note that then we don't pause at 10W and continue increasing power during the 120s).
Can see no obvious new point absorbers, ITMY looks perfect and ITMX has the same point absorbers as before, it;s possible there's a new point absorber on the right of the optics (orange arrow in attached) but it doesn't look scary. We will continue to check this but it's possible that our alignment has just changed (has since 66198) so that we can now see this point.
Sheila and Elenna turned the CO2s on as we were powering up from 10W to 25W. Attached is the 2 minutes after CO2s were turned on while we were sat at 15W for 4 minutes.
Can see the CO2 patterns of ITMX and ITMY. IY CO2 looks good but IX CO2 it looks off in YAW, we should check how this compares to the IFO spot at full power. It would be worth doing some dither tests to see if this needs adjusting.
HAM1 annulus system appears to have issues pumping down, currently its annulus ion pump is railed 10 mA, and the pump cart pumping on this system is sitting at 6.04x10-05 Torr, see attached photo.
Process thus far:
I plan to visit HAM1 to check the rest of the bolts on -Y door and +Y door.
HAM1 internal pressure is doing good, see attached photo of the pressure at the SS-500 pump cart pumping on HAM1. Second attachment is a 5.5 day plot of the pressure internal to HAM1, the large step noted on the plot is due to the introduction of HAM1 ion pump.
(Jordan V., Gerardo M.)
Today we went and performed the following on the annulus system for HAM1:
Now we wait to see the results of today's changes overnight.
Mon Jun 02 10:12:16 2025 INFO: Fill completed in 12min 13secs
Gerardo confirmed a good fill curbside.
M. Todd, C. Cahillane
Yesterday we were interested in some noise we were seeing around 6Hz in various ASC signals (mostly CHARD pitch). This motivated us to look at the RMs, so I took a PSD of each DOF for both RMs. We are not sure why there are such differences in all the dofs, and if there are unintended side-effects to this.
I'm specifically wondering why RM2 has larger peaks around 6.25 Hz in all dofs...
This feature is the primary vertical resonance of the HTTS. The ISI HAM1's control system has still not yet been commissioned, so the decision to *unmute* the HTTS "because the ISI isolation performance should be much better than the Stack" will plague us until that's true. See "muting the HTTS blade springs" ECR E2200181, which confirms the 6.25 Hz resonance. See Integration Issue 33777 for historical notes, specifically Comment 2's record of IIET call discussion and agreement to *unmute*. I suspect the low-frequency performance will also improve once the ISI's controls are commissioned. Let's give Jim some time to figure out how to dance around the ~70 Hz feature that he's dealing with, see LHO:84638 (and last week's lock-acquisition problems do to ignoring it LHO:84640).
Camilla, TJ
Sheila asked us to look for post vent point absorbers, but when we went to check, we found that the code hadn't been running since May 23rd.
Looking further into it, we could log into the machines and open the tmux sessions, but the code was frozen from May 23 821UTC and could not be Control C'd. I then tried a pkill on that python process, this also did not work. Trying to reboot the machines remotely aslo didn't work. I power cycled the machines from the MSR, then we were finally able to start the code up. ITMX needed the camera initialized for some reason.
We are thinking about ways to catch this in the future, maybe having DIAG_MAIN monitoring if values are updating properyly.
TITLE: 06/02 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 15mph Gusts, 8mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.22 μm/s
QUICK SUMMARY:
H1 was down for the night, so will most likely run an alignment and then go for Power 10W and then assess.
TITLE: 06/02 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
IFO is in DOWN and in PLANNED ENGINEERING
Productive day in which we made it past 25W before a violin-mode gain related lockloss.
The lockloss kicked our alignment so I did a manual initial alignment, which worked to lock DRMI. We can now semi-reliably get to powerup automatically. The goal now is to continue powering up while monitoring IFO status.
For details, check out alog 84706, alog 84702
LOG:
Just a brief note on the CHARD P error signal. When fitting an excitation for injection, I noticed a large peak at 6 Hz that I hadn't seen previously. I'm guessing it's from RM damping but I'm not 100% sure. I went back to a NOMINAL_LOW_NOISE time from last March 12, 2025, to compare what we had before. There seems to be a number of differences. There's some large broad peak around 16 Hz in March 12 that's no longer there now. I checked a couple of times in that March 12 lock at this broad 16 Hz lump is always there. The 6 Hz peak is much larger now, but there appears to be a small peak there even in March. Not sure the causes of such differences, but someone who knows more about the HAM1 changes could have better insight, especially related to the ISI upgrade and status of the RMs. The comparison is not fair either, since we are only at high noise, 20 W of input power now for June 01, whereas in March we had NLN and full power.
Closes FAMIS 26455. Last checked in alog 84145
Trends are within red error lines. Seems that there were 3 spikes week of 05-11 to 05-18 which can probably be attributed to vent work, but I am unsure.
Closes FAMIS 26386 and FAMIS 26384 and FAMIS . Last checked in alog 84405,
Everything is under threshold. Took 2 weeks since was undone for the week prior.
Corey, Ibrahim, Georgia, Craig, Matt, Caroline, Julia
Corey locked the interferometer after the earthquake.
We were pretty much able to go directly to CHECK_VIOLINS_BEFORE_POWERUP without touching anything.
Corey did tidy up the 2f signals by adjusting PRM and SRM alignment after DRMI locked, but the other guardian states "just worked" after our changes from last week.
We went up to POWER_10W, no problems there.
Then we started stepping through POWER_25W.
We ended up losing lock after upping the ADS gain from 1 to 2.
It was a very slow lockloss, which seems consistent with this story about it being ADS-driven.
We also had just turned on the SOFT Y loops to high gain (20 for CSOFT Y, 30 for DSOFT Y).
Georgia looked at the ADS control signals and it appears to be the PIT loops which killed the lock.
The above lock was with the ITMX SPOT GAIN at it's new "CENTER
" value of -1.25, rather than 0.85.
We figured that since we MOVE_SPOTS soon after anyways, we can focus our efforts on trying to get up to high power with ASC relatively stable.
EDIT: We lost lock after going up to POWER_25W from what was probably that same very slow 0.02 Hz oscillation. See picture 2.
Leaving the ADS pitch loops on at only a gain of 1 was not good enough.
Georgia added back in +10 dB to both PIT3 and YAW3 for the ADS which was commented out a few days ago while we were sitting at 2W CHECK_VIOLINS_BEFORE_POWERUP.
This caused a lockloss when going up to POWER_10W.
This indicates it's just ADS PIT3 which is the major problem here.
EDIT2: We are sitting here at 20 W of input power, measuring CHARD P for an hour.
We turned off ADS PIT3 while going up in power, with the plan of trying to ease it on at lower gain.
While we were sitting here measuring, the 0.02 Hz oscillation came back.
Georgia stopped it by lowering the PIT4 and PIT5 gains from 1 to 0.1.
EDIT3: We tried to MOVE_SPOTS, but lost lock after about 8 minutes due to a violin mode damping typo.
Georgia lowered the ADS gains to 0.1 for all, including PIT3 starting at the weird spot position on IX.
The buildups were getting very choppy, but we were surviving. Unclear how far we could have made it.
Julia was damping violin modes and accidentally typed in -20000 into a filter module gain, which seems to have immediately saturated the IX PUM stage and killed the lock.
This is Julia's first lockloss so we will be nice to her this time.
Changed the DARM_OFFSET ISC_LOCK state number to be in order, after ENGAGE_ASC_FOR_FULL_IFO
This change was reverted - alog84741
TITLE: 06/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:
After alignment and taking H1 up in ISC LOCK, Syracuse crew arrived and covered various items:
Guardian Note: ALS_YARM needs a mindful eye, because it was frequently go into a (yellow) STALLED state. To "unstall" it I just reselect the state it is in. Can't recall if this has been happening with other nodes.
LOG:
TITLE: 06/01 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 11mph Gusts, 4mph 3min avg
Primary useism: 0.12 μm/s
Secondary useism: 0.13 μm/s
QUICK SUMMARY:
IFO is LOCKING in PLANNED ENGINEERING
While we just got hit by an earthquake, locking has been fairly straightforward.
The plan is to power up slowly after 10W since we are able to automatically get through ENGAGE_ASC_FOR_FULL_IFO.
Georgia, Kevin, Corey, Craig, Matt, Caroline, Julia First thing done was to turn off the ADS PIT3 Pitch loop, as we still have a massive offset on IX SPOT GAIN. Plan is to remove this before going up by walking the alignment. We'll check the phasing of the REFL WFS as well. INP1 P is on REFL 9 I, while CHARD P is on REFL 45 I. OMC is not actually sweeping, and so is not locking. Georgia has found that the PZT2 monitor is not reaching the high voltage levels that it usually has during OMC_LOCKing. We went to the mezzanine and found the HAM6 PZT driver power supply was stuck in constant current mode (first pic). Georgia flipped it off and on and it fixed itself (second pic). Now the OMC is locked again. Someone serious should look at this. Started to phase POP X WFS using a frequency line at 8.125 Hz. We engaged all the Notch8 filters. All POP X segment phasings are around -23 degrees or so. We were unable to put all the signal in I using the frequency line. Then we switched to using PRC2_P_SM_EXC for the injection line. This was a lot more fruitful. Matt and I rephased segments 3 and 4 to reduce the PRC2 P signal in Q. The phases are pretty different between segments, but overall they are close to what they were before... These changes were saved in SDF. We reset the IX SPOT GAIN to 0.85, which put the ADS PIT3 error signal back to around 10. Our problem is if we zero this PIT3 error signal with the current alignment, we lose buildups and eventually kill the lock. Our goal is to walk the alignment to zero this signal without losing lock. Georgia opened INP1 P, which control IM4. Julia and Georgia are walking IM4 and PRM together now, with PRC2 and CHARD P closed to try to point us back on the center of the ITMs for powering up. We lost lock while walking IM4 P in the negative direction, and recovering with PRM. We were about to switch directions we were walking in when we died.
M. Todd, C. Cahillane, S. Dwyer
I ran another estimate of the PRG, following Craig's method in alog 58327, and estimate it to be around 54.2 W/W.
I compared the TRX power to Input Power ratio during the FIND_IR state versus the PREP_ASC_FOR_FULL_IFO state, with the PRM transmission as a normalization factor.
TRX_POWER_FULL_IFO / INPUT_POWER_FULL_IFO
PRG = -------------------------------------------------------------------------------------
TRX_POWER_FIND_IR / (Tp * INPUT_POWER_FIND_IR)
I've attached the quick script I've used for the interesed reader.
I reran this measurement during DARM_TO_DC_READOUT (GRD-ISC = 501, input power = 2W), comparing the input and TR-X powers during the previous FIND_IR state (GRD-ISC = 16, input power = 2W). And I got a post vent PRG of 55.6 W/W. (post-vent)
I reran this estimate for the same states, before the vent (FIND_IR = 1427488687, DARM_TO_DC_READOUT =1427490018) and got a PRG of 55.7 W/W. (pre-vent)
It's interesting that we estimate almost the exact same PRG pre and post vent, though we may be able to improve this post vent value (probably not drastically) with some ASC improvements. We wanted to get this estimate to just check that everything is in general order in HAM1 after the vent.
I think our PRG channel calibration needs updating. Matt's measurement agrees with mine: that the PRG is about 54 when we are at 2 W of power. However, at 2 W it is currently reading 60, which is wrong, possibly due to slightly less power on IM4 trans. I will add a correction factor in FM4 of our "LSC_PR_GAIN" bank, 55.6/59.8 = 0.93.
I checked what the PRG was according to the calibration channel H1:LSC-PR_GAIN_OUT16 during the same time that I used for my measurement of the post-vent PRG (1432694134) and it is off by roughly a factor of 8%.
The calibration channel reports a PRG of roughly 59.9; I've measured it to be 55.5. We may benefit from some re-calibration.
Made those changes for 2W damping, and will hopefully be able to confirm whether they also work for 60W. For ITMX 03 and ITMY 05, I added new 2W settings for IX3 and IY5. These changes were saved in lsc_params and the violin damping guardian has been reloaded.