Lockloss @ 01:38 UTC - link to online lockloss tool

No obvious cause; LSC-DARM saw the first motion.

[Sheila, Jenne, Betsy, TJ]

Today we had a saga of trying to move even closer to center on PR2, however we were struggling to lock DRMI when relocking, so we've reverted to the alignment situation we were in for our long lock last night.  Since that work took longer than anticipated, we still have not yet remeasured our position on PR2 and PRM, so we plan to do that next time we're commissioning.

• We extrapolated from alog 77870 that we needed to move the PR3 yaw slider to a value of -234 urad, which is a further 159 urad more than we had moved so far.  This comes from our measurement noted in that alog that having moved the PR3 slider by 64 urad moved the spot on PR2 by 2.5 mm, and we wanted to move a total of 15mm from our original position. 
• Since we were unlocked anyway from maintenance day, we got the green arms locked (so that we could see the ALS COMM and DIFF beatnotes), and then manual-ed ISC_LOCK to PR2_spot_move.  
  • Aside: later in the day it was noticed by some GDS folks that using this state with index 900 (which is greater than 409) meant that the range was being calculated, but was returning a nonsensical value, because the IFO wasn't actually locked.  TJ changed the index of this state to be -11 so that the range won't be calculated when we're in that state.
• When almost all the way on the PR3 slider to our goal position, verbal alarms warned us that we were saturating IM4.  This is because the PR2_spot_move state watches how much you move the PR3 slider, and applies a scaled change to PR2, PRM, and IM4 sliders. 
  • My plan for mitigating this was to move IM3 to relieve IM4, but since we had fallen off of ASC_POP_A basically as soon as we started moving PR3, we had to walk all the way back in PR3 slider to where we started, in order to see beam on ASC_POP_A.  However, moving just IM3 gives a pretty significant angle change, so in the end I moved a combination of IMs 1-3 to keep in roughly the same place on IM4_trans and POP_A, while relieving the IM4 yaw slider. 
• Went back to moving PR3
• I think around here is when I realized that we had no light on the AS_AIR camera, and also that we had again fallen off of POP_A. 
• Re-reverted about halfway to last nights alignment situation, to get onto POP_A.
• Went 'forward' with PR3 a little bit, moving IMs 1-3 to keep on POP_A and IM4_trans.  Didn't go very far though, since it was getting late in the day.
• When trying to relock, saw that the ALS COMM beatnote was too low, and could not be improved by either moving PR3 or by pico-ing.
  • Went to ISCT1 and touched up the COMM beatnote alignment, and brought it up from -20dBm to about 0dBm.
• We went through an initial alignment and were trying to relock, but it was very nearly impossible to get DRMI to catch lock.  I could get it to catch and hold for 1-2 seconds or so, but only a very few times. 
• In the end, we went back to green arms locked, and I manual-ed again to the PR2_spot_move state, and I moved the PR3 yaw slider back to about where it had been last night.
  • Re-did the IR parts of initial alignment, and saw that the comm beatnote was still good, so no need to go back to ISCT1. 
  • This time we were able to get locked on basically the first attempt.
• I'm not so sure that the attached screenshot is very helpful, but at least it gives a timescale so we can go back and look at some things in more detail later if need be. Also, the y-cursors, if set, are at the value at the end of the long lock that ended just before maintenance today, so you can see that alignment-wise we're pretty similar to where we were last night.

H1 is now back to observing as of 00:09 UTC following input alignment changes and other maintenance today.

After we reached low noise, I took 10 minutes of no-SQZ time from 23:55 to 00:05 UTC.

MinhyoK, FranciscoL, [Remote: DriptaB]

After one week of moving the inner beam 5 mm to the right of the Rx (see alog 77840), we moved the beam to the center. This will help to evaluate the reproducibility of this procedure and the risks from moving the beam at the ETM.

Attachment 'BothBeamsBefore' shows the beams before making any changes. (image taken before step (1))

The pdf 'EndStationLog.pdf' lists the voltage values after each significant step of procedure T2400163. The steps are represent writing down a voltage value after a particular change of the system:

• 'Pre' - Nothing has changed, reading voltmeter after plugging it to "Rx PD Mon".
• (1) Alignment of the target.
• (2) Only inner beam at Rx detector. (see image 'InnerBeamOffCenter')
• (3) Finalized beam movement. (see image'InnerBeamCentered')
• (4) Both beams at Rx detector, target still on (see image 'BothBeamsAfter')
• (8) Target off.
• 'Final' - Measuring after placing enclosures.

The initial measurement (done on step 'Pre') agree with the last voltage measurement from the previous movement, done on May 14 (see alog 77840), by a factor of 3 HOPs.

The changes we saw from making the movement of last week will be reported as a comment to alog 77840. In summary, our values disagree by a relative difference (measured/expected -1) of 15%.

With the movement made today, we expect that the X/Y comparison will return to a value of 1 in the upcoming week.

TITLE: 05/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Maintenance activities were light, but the was some work to try and get the PR2 spot moved closer to the center that had some alignment consequences. We have been trying to recover the IFO since the moves but unable so far. Right now Jenne is working to revert us back to our configuration we were in last night and then we can try with that.
LOG:

TITLE: 05/21 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 20mph Gusts, 16mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY: After some alignment changes today (and reversions) during maintenance day today, H1 has just finished initial alignment and starting lock acquisition.

• Rainy and slightly windy on-site
• All other systems nominal

During maintenance and during relocking today we tested out a few new features in both guardian land and for Verbal. Here's a summary and status of each:

Guardian

• PR2_SPOT_MOVE index changed from 900 to -11
  • This state was changed recently to be used out of full lock, but this messed up some things downstream, such as our cleaned range. I changed the index to be undefined and then Guardian assigned it a negative number. It would not let me manually assign a negative number.
• Ryan C tested out his SDF diff dump  - REVERTED
  • The idea of this is that it would dump all of the sdf differences into a log file before we revert them so that we have a record of all of the changes if we are struggling to figure out what all has changed. Ryan tested this today but will need to rework it a bit before we try it again.
• Fine tune IR to use max values rather than average - REVERTED
  • In higher ground motion times, DIFF in particular, this state can get stuck fine tuning. This is because the code takes the average of the LSC-TR_{X,Y}_NORM_INMON channel which is moving with the ground. Sheila suggested that we take the max instead, but testing this out today didn't quite do what I expected and made it worse at times for COMM. I plan to write a hybrid of the two and try that next.

Verbal

• ISI saturations added
  • ISI saturations are now added since it was brought up that we didn't always know when we were smashing an ISI during measurements.
  • Message example: "ISI HAM3"
• ISI CPS glitch notifications added
  • In repsonse to the number of times that the ISI CPSs start to glitch (HAM3 examples: alog75134, alog77906, alog77935), this should tell us if the 130-200Hz CPS blrms channel in one of the corners gets above 100.
  • Message example: "HAM3 CPS glitch"
• Updated calibration measurement times for the new norm that started this week.

Maintenance finsihed up around 1145PT, but some input mirror movements done by commissioners are still trying to get the beam back. We will resume locking as soon as we can.

CDS Wifi access points at both mid stations are down for maintenance waiting on parts.  If you need to use a CDS laptop at either mid station, ask Jonathan, Erik or Dave for help

Tue May 21 10:09:01 2024 INFO: Fill completed in 8min 57secs

Travis confirmed a good fill curbside.

The IFO lost lock just before maintenance started while the SUS_CHARGE guardian was in the state SWAP_BACK_ETMX. The lock loss happened at 14:58:35 UTC, between the last two lines below from the Guardian log.

2024-05-21_14:58:22.768728Z SUS_CHARGE [SWAP_BACK_ETMX.enter]
2024-05-21_14:58:22.768728Z SUS_CHARGE [SWAP_BACK_ETMX.main] ezca: H1:SUS-ITMX_L3_DRIVEALIGN_L2L_GAIN => 0
2024-05-21_14:58:22.769665Z SUS_CHARGE [SWAP_BACK_ETMX.main] ezca: H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN => 184.65
2024-05-21_14:58:42.790151Z SUS_CHARGE [SWAP_BACK_ETMX.main] ezca: H1:SUS-ITMX_L3_ISCINF_L_SW1S => 4

ETMX seems to move too much after the the L2L gain is applied.

TITLE: 05/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 22mph Gusts, 18mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY: Locked for 7.5 hours, range hasn't been looking too good. A glance at the SQZ FOM when I walked in had the live trace above the reference in higher frequencies. Magnetic injections just started, maintenance day will start soon.

Workstations updated and rebooted.  This was an OS package update.  Conda packages were not updated.

TITLE: 05/21 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 141Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:
Due to 2 backto back locklosses that both happened at LOWNOISE_LENGTH_CONTROL, after 2 sec in that state, I decided to stop in the state directly before and walk through Line by Line to see if there was a particular line in the code that was causing a lockloss. Each line was ran and no lockloss happened. We made it back to OBSERVING at 7:09 UTC.
 
The wind  was elevated, at the time of both locklosses so perhaps it was the wind or the incoming 5.7M earthquake , Plots attached. Perhaps a coinicidence?  IDK.

ISC_LOCK.py is still the previous version the latest version is this one:  ISC_LOCK.py_20may2024
I do beleive I made a change in the Current copy of ISC_LOCK.py but that change should be discarded in favor of ISC_LOCK.py_20may2024
LOG:
                                                                                                                                                                                                                                     

TITLE: 05/21 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 13mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

Took H1 Out of Observing to do a SQZr Scan.

Incoming 5.4M Earthquake.  - Survived it.

Locklosss from Observing 02:31 UTC
Screenshots attached.

H1 made it all the way up to LOW_NOISE_LENGTH_CONTROL and was knocked out of lock by what I pessumed was wind. But looking at the scopes I dont see any extreme gusts.

On the Second locking attempt H1 also made it to LOW_NOISE_LENGTH_CONTROL, But both times i made it to that state it lasted 2 seconds and 124ms, then lost lock. which looks suspicious.

I started to try to open ISC_LOCK to stop it from getting to that state, and was greated with the following.

Traceback (most recent call last):
  File "/var/opt/conda/base/envs/cds/bin/guardmedm", line 11, in
    sys.exit(main())
  File "/var/opt/conda/base/envs/cds/lib/python3.10/site-packages/guardian/medm/__main__.py", line 177, in main
    system.load()
  File "/var/opt/conda/base/envs/cds/lib/python3.10/site-packages/guardian/system.py", line 400, in load
    module = self._load_module()
  File "/var/opt/conda/base/envs/cds/lib/python3.10/site-packages/guardian/system.py", line 287, in _load_module
    self._module = self._import(self._modname)
  File "/var/opt/conda/base/envs/cds/lib/python3.10/site-packages/guardian/system.py", line 159, in _import
    module = _builtin__import__(name, *args, **kwargs)
  File "", line 1129, in __import__
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 1006, in _find_and_load_unlocked
  File "", line 688, in _load_unlocked
  File "", line 883, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/opt/rtcds/userapps/release/isc/h1/guardian/ISC_LOCK.py", line 8, in
    import ISC_GEN_STATES
  File "/var/opt/conda/base/envs/cds/lib/python3.10/site-packages/guardian/system.py", line 159, in _import
    module = _builtin__import__(name, *args, **kwargs)
  File "", line 1129, in __import__
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 1006, in _find_and_load_unlocked
  File "", line 688, in _load_unlocked
  File "", line 883, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/opt/rtcds/userapps/release/isc/h1/guardian/ISC_GEN_STATES.py", line 5, in
    import ISC_library
  File "/var/opt/conda/base/envs/cds/lib/python3.10/site-packages/guardian/system.py", line 159, in _import
    module = _builtin__import__(name, *args, **kwargs)
  File "", line 1129, in __import__
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 1006, in _find_and_load_unlocked
  File "", line 688, in _load_unlocked
  File "", line 883, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/opt/rtcds/userapps/release/isc/h1/guardian/ISC_library.py", line 1189, in
    class DUMP_SDF_DIFFS():
  File "/opt/rtcds/userapps/release/isc/h1/guardian/ISC_library.py", line 1199, in DUMP_SDF_DIFFS
    dcuid = str(models.fec)
AttributeError: 'generator' object has no attribute 'fec'

TITLE: 05/20 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:
The H1 has now been locked for 2 + hours and are currently Observing.
Everything currently looks great.
 


 

Now that the wind has (mostly) calmed down, and we're pretty confident that the increased low frequency noise late last week was due to (not yet understood, intermittent) squeezer-related noise, Sheila and I moved PR3 to get closer to center on PR2.  Mostly we were moving in yaw, but then we occassionally moved PR3 pitch to counter-act the pitch shift that was happening due to cross-coupling. We were making these PR3 pit moves primarily according to the PR3 top mass OSEMs.

While we were moving in yaw using the ISC_LOCK guardian state PR2_spot_move, Sheila noted that the scaling of the slider moves for PR2, PRM, IM4 in response to a PR3 move weren't quite right, since the ASC had to respond a bit.  So, she re-calculated and tuned the scaling factors in that guardian state, and now the ASC responds much less (indicating that all the sliders are moving close to the correct values in response to a PR3 move). 

Overall, we moved PR3 yaw slider from +152.4 to -74.9. We did about the first half of the move in full lock, gaining about 1% increase in POP_A_LF and also about 1% increase in arm cavity buildups.  We had gone maybe 1/4 of our total for today, and we stopped gaining in overall buildups, which makes sense if we got to a point where we're no longer really clipping (and so moving farther isn't un-clipping us more).   I think I started going too fast (and didn't pause to use the pico motor), and we lost lock, so then we did the second half with just the green arms locked, and pico-ing to keep the COMM beatnote high. 

We redid initial alignment, and are on our way back to lock.  We'll post more details on this morning's work, but this is just a quick alog so I don't forget, while I go off to another meeting.

Before we did any work today, we had two quiet times.

• After A2L was run, but before any alignment changes: from 16:53:30 UTC to 17:07:00 UTC.
• After A2L was run, before any alignment changes, but with No SQZ: from 17:08:00 UTC to 17:13:00 UTC.