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.
 


 

TITLE: 05/20 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Lost lock during commissioning, relocking was straightforward and unassisted after finishing the manual IA after the PR3 moves. We've been locked for 2:15 as of 23:30 UTC

16:00 UTC  We started commissioning

• optimizing SQZing with SQZ_MANAGER, scanning the alignment and angle
• FC2 spot centering alog77942
• A2L alog77945
• PR2 spot move via PR3 alog77949

18:45UTC lockloss from commissioning activities

18:46 UTC Manual IA

19:22 UTC Another PR2_SPOT_MOVE

19:41 UTC 2nd Manual IA

While relocking we paused in PRMI to run OLG measurements of MICH and PRCL

21:19 UTC back in Observing after accepting/reverting some SQZ diffs

From the DARM_coherence_checks.xml template it looks like MICHFF needs to be re-tuned

21:36 UTC Superevent S240520cv

LOG:

We paused in PRMI_ASC to run the OLGs for MICH and PRCL, they both seem fine.

I ran the new A2L script (from alog 77704), after incorporating suggestions from Vlad and Sheila.  In particular, now the script enables the 30 Hz bandstops in the quads, so that we are preventing the oscillation from going around the loops.

It seems to have run okay.  As a future enhancement, I might move the dither oscillation (and the associated bandpasses / bandstops) to a sligthly different frequency, since there may be some persistent line in DARM very close to the A2L freq we are using right now of 30.0 Hz.

Here is what the script printed out:

• ITMX P: Want to change gain from -1.0 to -1.01, rounded to 2 decimal places. St.Div is 26.282. Change of 0.011197837420762191
• ITMX Y: Want to change gain from 2.8 to 2.82, rounded to 2 decimal places. St.Div is 0.45. Change of -0.019285751881707114
• ITMY P: Want to change gain from -0.3956 to -0.35, rounded to 2 decimal places. St.Div is 0.115. Change of -0.04102769287242841
• ITMY Y: Want to change gain from -2.458 to -2.46, rounded to 2 decimal places. St.Div is 0.936. Change of -0.0013939077390441312
• ETMX P:  (This printout scrolled too far back in terminal history, so can't copy it to alog)
• ETMX Y: (This printout scrolled too far back in terminal history, so can't copy it to alog)
• ETMY P: Want to change gain from 4.4 to 4.43, rounded to 2 decimal places. St.Div is 0.744. Change of -0.030175185139269978
• ETMY Y: Want to change gain from 0.95 to 1.02, rounded to 2 decimal places. St.Div is 0.133. Change of -0.06945831046387796

Overall this seemed good, and Sheila noted that the coherence with the HARD ASC loops went down.  I'll check again after we re-lock.  This took about 30 mins (plus about 10 mins before that, for some last min debugging of variable name spelling errors).  I need to check on the fits and the stdevs, to make sure they make sense, since the stdev now seems much higher than Vlad's notes say it should be.

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.

FAMIS Link:  25992

Only CPS which looks higher at high frequencies (see attached) would be:

1. ITMx St1 V1 (with & ITMx St1 V2 being just a little higher than ADE 1mm noise).
2. ITMy St1 V2