Reports until 19:46, Monday 02 June 2025
H1 ISC
elenna.capote@LIGO.ORG - posted 19:46, Monday 02 June 2025 - last comment - 20:48, Monday 02 June 2025(84731)
Overall Summary of Afternoon/Early Evening locking progress

Writing this alog on behalf of most of the control room...

After we redid the input matrix for CHARD and INP1 10W, we checked the PRC2 and INP1 bandwidth. We were also concerned about the overall gain of CHARD P and Y since they seemed to be way too low

We decided to power up anyway, and saw that the pitch ADS was able to run fine, now that the CHARD pitch gain was nominal. However, yaw ADS still had problems during move spots.

Everything looked good, so I took us up in power from 25W to 60W, stopping frequently to check for instabilities. We made it, but again the ADS was unstable, so Georgia used the Camera servo guardian to move off the ADS to camera servos, and everything was fine.

I stepped through lownoise ASC by hand, skipping the lownoise steps of CHARD P and Y since those gains were not nominal.

Lots of the of the usual wobbly stuff in the ASC and buildups at high power, but the overall alignment and control looks good: PRG is still around 50 at full power.

We then ran through lownoise coil drivers and the ETMX ESD transition. We had one guardian error at the end of TRANSITION FROM ETMX due to divide by zero error since the convergence checker looks for something that is like [ADS error signal / ADS CLKGAIN] and the ADS CLKGAINs were zero. Georgia and I fooled the guardian by setting the CLKGAINs to 1 momentarily, and then undoing them once the state completed.

We ran all the way through LOWNOISE LENGTH CONTROL, although the LSC feedforward is no longer well-tuned, so I turned it off momentarily so we could check OLGs.

The LSC feedforward is currently so bad that we should go from-scratch when we retune it instead of the iterative method.

We had a fast unknown lockloss while sitting in this state- no one was doing anything and we don't see an obvious cause.

We think we have properly SDFed and guardianized all changes from today.

My only worry: we were not able to raise the CHARD Y gain until we reached maximum power, but obviously we are having ADS stability issues since this gain is too low. Currently I have set the guardian to have what I think is the "correct" CHARD Y gain (300 once all loops are closed), but if it's too high, drop it back to 3.

Recommended to do list:

Comments related to this report
elenna.capote@LIGO.ORG - 20:18, Monday 02 June 2025 (84732)

Oli and I are trying out relocking, and both sitting at 2W and sitting at 25 W (before move spots), I cannot raise the CHARD Y gain beyond 3 without causing some slow growing ~0.8 Hz oscillation in CHARD Y. We will try full power up again with low CHARD Y gain. Turns out the CHARD Y gain was not actually set to 300 at 2W (I only updated lscparams, not ISC_LOCK).

After MOVE SPOTS and reducing modulation depths (but before the rest of the power up), I tried again to raise the CHARD Y gain- same problems.

But once MAX POWER gets us to 60W, I can raise the gain no problem!

I edited MAX POWER to change the CHARD Y gain right at the end of the state (I think).

elenna.capote@LIGO.ORG - 20:30, Monday 02 June 2025 (84734)

In terms of setting the time on the ASC convergence in MOVE SPOTS, YAW3 (ITMX spot feedback to PRM) is the culprit that is taking forever.

Oli just took a look back- we usually spend about 5 minutes in move spots, and tonight it is taking more than 10 minutes.

elenna.capote@LIGO.ORG - 20:44, Monday 02 June 2025 (84735)

We were able to run through LOWNOISE ASC guardian state fine, so the edits described above work!

elenna.capote@LIGO.ORG - 20:48, Monday 02 June 2025 (84736)

We lost lock from a 1 Hz DHARD P ring up that began during the "TRANSITION FROM ETMX" state.

When we went through this state previously and successfully, we were running camera servos instead of ADS. I wonder if that's related to this lockloss.