Corey, (Jenne, Keita

For last few days, to lock the OMC, one needed to manual adjust SRM pointing to minimize POP90 before Locking the OMC---this was done from the ENGAGE SOFT LOOPS state (steps noted by Sheila and in  alog 78331).

To make this step easier in the future, went through the same process, but at the end, we wanted the ASC to take care of this in the future.  So,

• SRM was manually adjusted to minimize POP90 (from 9 down to 7)
  • So SRC1 p & y inputs turned OFF
  • SRM was moved to minimize pop90
• Then for SRC1 Pit, looked at the INMON and entered a smooth offset to make the INMON zero (so, the INMON was at around 0.1 and an offset of -0.1 was entered).  The same was done for SRC1Yaw.  Attached Here are the values: 
  • H1:ASC-SRC1_P_SMOOTH_OFFSET = -0.100
  • H1:ASC-SRC1_Y_SMOOTH_OFFSET = 0.830
  • Attached screenshot shows these new values from the ASC WFS SERVO CENTRAL medm
• Then the inputs for SRC1 Pit & Yaw were turned back ON (they were turned off to allow the manual SRM tweak).

And we are currently attempting the MAX POWER step on ISC LOCK.....but there is also some ground motion going on by the film crew's trucks and Richard is also going to be using the Genie Lift to help them put some equipment on the roof.

Mike & Jenne gave the OK for operations above 10W.

Made it to 25W (after a manual tweak of SRM at ENGAGE SOFT LOOPS to be able to lock the OMC), but had a lockloss at MOVE SPOTS.

Film crew is here and mainly doing set-up in the Multi-Purpose Room of OSB (Richard & Mike are with them).

Keita has been helping me online, Sheila has posted comments in chat, and Jenne said she'd be available remotely now-ish.

Manual SRM Moves at ENGAGE SOFT LOOPS

Attached is the tiny moves made on SRM to lower POP90.

To do this, after ENGAGE SOFT LOOPS was completed, Sheila said to turn off the Inputs to SRC1 pit & yaw and then make SRM adjustments.  I had then kept the SRC1 input OFF and moved on (to that lockloss at MOVE SPOTS.  (Jenne is saying we might want to turn those SRC1 offsets back ON with an offset).

Corey, Keita (w/ Jenne on cell)

Last night, Jenne had Tony make a few changesto allow us to run 10W lockloss tests WITHOUT the OMC/DC Readout.  Here are the changes made to Guardian files, which were SAVEd & LOADed for ISC_LOCK.

Reversion for ISC_LOCK.py:

• line3044 (under PREP DC READOUT TRANSITION state):  nodes['OMC_LOCK'] = 'READY_W_NO_WHITENING' #was DOWN for 10W/pressure spike issues Jun2024, returning to "READY..." cg

Reversion For lscprams.py:

• line589:  power_up_on_RF = False   #was True for 10W/pressure spike issues Jun2024 cg

This will allow us to lock the OMC (unless I missed other changes from last night).

Sun Jun 09 10:10:28 2024 INFO: Fill completed in 10min 24secs

Running an alignment this morning and noticed that ALS X-ARM was stuck.

• Symptoms: 
  • Green Arms ndscope was 0 for X-arm WFS signals (this was a new one to me)
  • ALS Overview had a RED box for AutoCenter for the EX WFS Indicator.
  • Went to ALS-X Conotrols Overview and focused on WFS-related stuff.  Noticed that all the WFS DOF filter banks had no inputs/outputs
  • Eventually noticed a RED box on the ALS-x Overview which was the Auto Center again, so I opened the adjacent TRIG box.  
• On Triggering box, clicked FORCE (from AUTO) for Auto Centering, and this immediately brought signals to all ALS-x WFS!  Returned ALS-x back to AUTO and moved on with alignment.

TITLE: 06/09 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: n/a
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 3mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:

H1 was in the SDF Revert state (took to READY) overnight.  Continue to be in the holding pattern of not going with more than 10W in power until approved. 

IMAX crew continuing with set-up work.

There was a 6.2 earthquake down along the Pacific/Antartic Ridge about 5hrs ago.

TITLE: 06/09 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Commissioning
SHIFT SUMMARY:

Ten 10Watt locks tonight with no obvious spikes in pressure .
2024-06-08_22:58:05  ISC_LOCK  POWER_10W -> LOCKLOSS
2024-06-08_23:53:25  ISC_LOCK  POWER_10W -> LOCKLOSS
2024-06-09_00:40:40  ISC_LOCK  POWER_10W -> LOCKLOSS
2024-06-09_01:22:46  ISC_LOCK  POWER_10W -> LOCKLOSS
2024-06-09_02:42:00  ISC_LOCK  POWER_10W -> LOCKLOSS

The above locklosses at 10Watts can be seen at alog 78320
Had to do an initial alignment inbetween the the first and last 5, that struggled to get past SRC, but I lowered the threshholds again.

2024-06-09_05:23:19  ISC_LOCK  POWER_10W -> LOCKLOSS
2024-06-09_05:58:34  ISC_LOCK  POWER_10W -> LOCKLOSS
2024-06-09_06:26:14  ISC_LOCK  POWER_10W -> LOCKLOSS
2024-06-09_06:53:46  ISC_LOCK  POWER_10W -> LOCKLOSS
2024-06-09_07:21:12  ISC_LOCK  POWER_10W -> LOCKLOSS
On the last one I forgot to return H1:IMC-REFL_SERVO_IN1POL back to positive, and spent some time wondering why the IMC wasn't locking any longer lol. 


LOG:

TITLE: 06/08 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 7mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.15 μm/s
QUICK SUMMARY:

H1 was able to get locked up to POWER_10W twice so far.

First 10W Lock Pressure ndscope

Second 10W Lock Pressure ndscope
Notes: this lock had many EX saturations.

 

TITLE: 06/08 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

Operations NOTE:  H1 -NOT- to be taken higher than 10Watts until commissioners give the OK (which will most likely be tomorrow).  Jenne/Sheila/Keita on Teamspeak discussed plans for the rest of the weekend and the goal for tonight/tomorrow is to get (5) H1 locklosses from 10W (The hope is to NOT have any more pressure spikes coinciding with H1 locklosses.) 

Next Steps?  Once (5) 10W locklosses have been achieved, will reassess what to do next.

Whew!  What a day!  H1 continued to have issues locking DRMI today as it did yesterday.  Keita & Sheila were helping remotely from 9am(local) to about 4pm (with Jenne joining at the end of the shift).  PLUS, there were Saturday tours today, AND THEN a film crew showed up!

I wrote a running diary covering what activities we did for H1 (with the hopes of posting entries throughout the day, but it was too hectic of a day!).  

The main point is that H1's DRMI-locking issues seem to be addressed (I was able to get the #1 10W lock before the end of my shift, and Tony just broke lock for the #2 10W lock.  Only 3 more needed!)

Started today's shift by starting with a fresh alignment (reverted to the time when TJ & Sheila handed H1 over to me for an alignment at lunch time Friday afternoon).  After that, I basically started "my diary," but since Sheila/Keita will have a better summary of what happened to get H1 back (I will post my locking notes for today as a text file---because they were basically chicken scratch with all the activity going on!)

Attached are screenshots of the SUS sliders (yesterday and what they were first thing this morning), Locking Notes, and the text file for the SUS slider revert.
LOG:  (not much here, because the day was focused on H1 getting through DRMI!)

• 1440-1518 "Buddy" for Richard as he does work at LExC
• 2203-2233 Film crew driving over the bridge & entering the filter cavity (landry)
  • 2233 Film crew on the roof (landry)
• 2245 Covering up viewports to go to laser SAFE (robert)

I replaced the temporary viewport covers with the permanent ones and I cleared the LVEA for observation mode.

Sheila, Keita, Corey

The ISC lock guardian wil lock the bright MICH if PRMI is taking a while to lock.  Sometimes we do not want this, as today when we just manually aligned the BS in PRMI and don't want it adjusted.

I've added a flag to lscparams to stop this, called auto_MICH_fringes.   I added a similar flag called auto_DRMI, which is also now set to False.

We will want to set these back to True when we are ready to go back to fully automated locking, for now operators can request PRMI or MICH fringes if they like.

Sat Jun 08 10:11:08 2024 INFO: Fill completed in 11min 5secs

TITLE: 06/08 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: n/a
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 10mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:

H1 was in IDLE for the night after (also Tony had to deal with some alignment grief with H1).  Will look at the alignment this morning and then chat with Sheila & Keita.

Saturday Tours Day & a film crew is also scheduled to be on-site this forecasted hotter afternoon.

TITLE: 06/08 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: OWL Shift Canceled.
SHIFT SUMMARY:

The Plan for tonight: Tony will power up on RF to avoid the difficulties we have with turning on a DARM offset. Stop at 10W, which is the smallest power at which we saw a pressure spike yesterday, and intentionally unlock (request down or flip sign on IMC servo). Check for a pressure spike. If there is no spike, repeat this until the end of Tony's shift when he will leave the IFO in DOWN. No owl operator. In the morning, @Keita Kawabe @Corey Gray and I will chat on zoom at 9 am, to discuss next steps, and what is needed for debugging the locking issues. @Jenne Driggers I think that today's locking situation is very similar to what you alogged on Wed, we were able to turn on the DARM offset once when I opened the SRC1 loops and aligned SRM by hand to reduce POP90.

What Actually happned:
Got stuck at locking DRMI for the entire night trying different alignments and troubleshooting tips.

I moved the BS and PRM around so much that I could no longer convince ISC_lock to go to AQUIRE_DRMI_1F any longer again.
So I went back to do an Initial Alignment. interestingly enough I ended up in the same spot as last time where I was stuck in AQUIRE_SRY, I touched up PRM by hand again as best I could while watching AS_AIR and ASC_AS_A_DC Sum again. once I got that as maxed As i could get it, I lowered the threshholds again.

H1:LSC-SRCL_TRIG_THRESH_ON from 0.006 -> 0.003
H1:LSC-SRCL_TRIG_THRESH_OFF and 0.004 -> 0.002

Allowed Initial_alignment to complete again.
And once ISC_LOCK got back to locking DRMI I was greeted with another instance of the beam splitter or PRM being off in YAW by a lot.
I then held ISC_LOCK in AQUIRE_DRMI_1F & set the slider values for PRM and BS to the value that they were at during the last lock with DRMI. This did not work either.

I tired this a few more times using different places along the locking process.

Rolling ALL sliders back to GPS Time 1401839323 (the IDLE time before the last time we had a locked DRMI.)
I was hesitant to revert ALL sliders back because I was under the impression that there was some significat work done on that particular alignment.

All sliders restored to GPS time: 1401762164 (Tail end of Initial alignment before a good lock)

The Alignment is off somewhere, And I'm not sure where.

I stayed a little late to try one more thing:
I restored back to a know good alignment, then ran another initial alignment on top of that! but I did't move SRM in the SRC ALIGN IFO stage. instead I just quit the Alignment.

This resulted in an alignment that got DRMI locked but SRM saturations were constant and I got stuck in DRMI_LOCKED_CHECK_ASC because the SRC channeles were not converging.

I tried this again and tripped the SRM SUS  WatchDog. I have now taken ISC_LOCK to Down for the night.

LOG:

TITLE: 06/08 Eve Shift: 2300-0800 UTC (1600-0100 PST), all times posted in UTC
STATE of H1: Commissioning
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 6mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY:

While trying to LOCK DRMI

I touched up BS and SRM but I still couldn't get DRMI locked. (likely pecause there was activitiy on the HAMS)

I then started an initial alignment.
I got into SRC align and could not find SR2. I pushed around SR2 to try and find it by hand, but I realized that there was still activity on and near the HAMS duirng the first stages of IA, and I had also potentially caused problems with the IA by requesting the laser stay at 2 watts in the middle of a movement. So I re-requested initial alignment and allowed SRC to do it's thing without intervention.

SR2 sliders are currently -8.6 for P and 2058.8 for Yaw

Reverting SR2 Sliders ONLY to 1401741295 (Last initial Alignment before a lock)
Which were -631.6 in P 282.6 in Yaw

Ended up moving SR2 sliders back, and moving SRM sliders to get better fringes while align IFO was in SRC align.
Jenne Driggers helped me out by pointing me in the right direction with SRM and showing me which thresholds to lower
H1:LSC-SRCL_TRIG_THRESH_ON from 0.006 -> 0.003
H1:LSC-SRCL_TRIG_THRESH_OFF and 0.004 -> 0.002

Once I started to lock and got back up to DRMI the Beam splitter was very off in pitch, which is wild since I just did an initial alignment. While touchingup the beamsplitter alignment, there was a lockloss from DRMI, maybe from my BS movement.

X arm had the PDH issue again which eventually resolved itself.

Currently trying to lock DRMI again.

Since Tuesday some of our sucsesfull locks have required manual intervention with the alignment of SRC to be able to turn on the DARM offset. 

We would like to have Tony lock the IFO to 10W tonight and intentionally unlock it to see that we do not have any pressure spikes when this happens in this alignment. 

I've edited the guardian, setting the flag in lscparams so that we power up on RF, and adding a check of this flag in DARM_OFFSET so that we don't engage the DARM offset if the flag is True. 

Keita, Sheila,Robert, TJ, Jennie, Corey, Tony

Dave and Gerardo alerted us that there have been vacuum spikes after locklosses in HAM6 yesterday.  We are looking at what circulating powers were and what the lockloss transient was at the time of locklosses that caused and didn't cause a vacuum spike in HAM6.  Here is a comparison table:

In the bad alignment, the beam was clipped on it's way to AS_C, so that diode wasn't catching all the power it would have in the good alignment.  AS_A and AS_B saturate at the time of locklosses. 

The spike in vacuum pressure was higher with each successive lockloss, although the power on AS_C was largest in the second one.