Naoki, Corey, Vicky

Corey is taking it to OBSERVE without squeezing tonight.

We traced down an issue to FC2 0.3-0.5 Hz oscillations, which maybe is worse right now due to wind. We think this excess FC2 motion is preventing FC from locking. 

FC2 0.3-0.5 Hz oscillations screenshot - see the FC Green VCO control signal trying to lock and failing - at the same time, we can see the FC2_M1_L oscillations around 0.4 Hz, even with no control signals sent to FC2 SUS. So, seems like FCGS VCO is trying to track the FC2 L oscillations, but the real FC2 motion is too much for the FCGS VCO to hold lock, and this prevents further locking. Corey says perhaps this FC2 motion is extra bad right now due to the wind. I don't remember this issue in O4a. Without FC2 L motion calming down a bit, I don't think we can hold a stable FC lock. 

So, we decided to go to Observe without SQZ tonight, at least until the wind calms down. Maybe could try SQZ later if wind calms down.

Edit: It seems FC has been struggling to lock with winds > 30-40 MPH these last couple days, see screenshot with FC locking and wind speeds.

TITLE: 04/15 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 161Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

With another 4hr wind storm, Squeezing wasn't possible due to a noisy HAM8 & an FC2 mirror oscillating at 0.35Hz.  This wind storm also caused a lockloss.  Initial Alignment was run (skipping SRC).  Winds calmed, and made it to Observing w/ Squeezing due to quieter conditions.  Overall about 5hrs of downtime due to winds preventing Squeezing and causing a lockloss. 
LOG:

• 2335 SQZ_FC takes Out of OBSERVING
  • 2339 Back to Observing after, SQZ_FC relocks....but....
  • 2340 SQZ_FC unlocks again.  Staying down as Naoki investigates FC's ASC
  • In thoughts of prepping for operating with No Squeezing, I did svn commits to all SQZ files which were M-odified.  But we ended up not making changes since the wind storm died.
• 2348 Received Dust Monitor PSL Major alarm (~120counts @300nm)
• 0022-0144 PCal Lab work (francisco)
• 0230 Lockloss due to Wind gust
• 0344 Initial Alignment (skipping SRC)
• 0454 OBSERVING w/ Squeezing (since winds dropped around 0430)

Similar to yesterday, we had a 4hr wind storm.  This caused issues with the Squeezer during the last lock and then eventually had gusts that rumbled the detector for a lockloss!  Reacquisition was tough, so optedfor a "partial" Initial Alignment (skipping SRC since SRY doesn't acquire).  After an IA, H1 locked on its first attempt. 

Aaaaaand, we also have Squeezing....BECAUSE...30min ago the wind storm calmed down!  (and I was all ready to make changes to SQZ nominal states for guardian nodes!)

I believe SQZ_FC now has the ASC "on" from Naoki's earlier work, so I ACCEPTED the SDF diffs for this (attached).

H1 just had a lockloss (after 10.5hr lock) due to a big wind gust (coincident with an audible "creak" in the Control Room).  Prior to this, coincident with the beginning of this current wind storm about 3.5hrs ago, the Squeezer unlocked taking us out of Observe (similar to last night when wind storm occurred).  Naoki & Vicky spent a bit of time trying to get the squeezer back, but I overheard them talking about lots of motion on SQZ optics).  

Was getting ready to transition H1 to a No Squeezing state for the night, but the Squeezer locked back up (see Naoki/Rahul alog). But it only lasted 30min until winds increased.

Here we are after the H1 lockloss.  By default, will see if Squeezing is possible, but if we run into the same issues & it's windy, will transition H1 for No-Squeezing operations for the night.

Fernando, Dave:

We have released a new SUS Oplev Overview MEDM in which the BSC oplevs have CONTROL buttons to open Fernando's control screens.

I took the opportunity to macrotize the overview, with the oveview opening two MICRO MEDMs: H1SUS_OPLEV_MICRO.adl is opened directly for the HLTSs, and H1SUS_OPLEV_WCTRL_MICRO.adl is opened for the BSCs. The latter in turn opens H1SUS_OPLEV_MICRO.adl and adds the CONTROL button. The control adl file resides in the SYS/H1/MEDM directory and is called H1SYS_OPLEV_CONTROL.adl.

The new Oplev Overview was created in the SUS/H1/MEDM directory, the original remains in the SUS/COMMON/MEDM directory and has not been modified.

To see the new Oplev MEDM you will need to start a new SITEMAP.

Attachment shows the Overview MEDM, with ETMY's Control MEDM superimposed.

TITLE: 04/15 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT
    Wind: 10mph Gusts, 5mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.15 μm/s
QUICK SUMMARY:

Nicely Observing H1 handed off by RyanC.  He mentioned, same issue with SRC for alignment and needing to skip it (that's atleast 3x in a row).  He also mentioned a drop out of Observing due to SQZ_FC as observed last night (and tweaks Naoki made for this).  Currently, waiting for a M5.9 S.Korea earthquake to roll through with its R-wave in 10min.

TITLE: 04/15 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: We stayed locked the whole shift after locking.

The wind started to pickup in the early afternoon, gust over 30mph

Lock#1

Found the IFO in IA, stuck at SRY. I adjusted SRM to maximise the spot on AS AIR then got out of IA and was able to lock. It took a few tries, ALS was getting knocked out by the wind possibly.

• 16:10 - 19:27 UTC Observing
  • We dropped observing briefly when the FC lost lock, it relocked itself
• 19:29 - 21:36 UTC Observing
  • Naoki adjusted the SQZ angle to maximize squeezing, alog77180
  • The SQZer lost lock again, returned to OBS after it relocked itself
• 21:38 - 23:00 UTC Observing

LOG:

Jeff K, Sheila D

We are interested in which signals we can use to try to damp triple bounce and roll modes, since these are probably responsible for some of the peaks in our forest of peaks around 25-35Hz (77109 and 76505).  Jeff is preparing to implement a damping path on the HSTSs so that we can try to damp these. 

We looked at signals (in addition to DARM) that we may want as options for damping. 

• 27.42 Hz - REFL A 9I PIT
• 27.5 Hz -nothing other than DARM
• 27.6 Hz - REFL A 45I yaw (plus several LSC signals, PRCL, SRCL, REFL45 I, POP9Q)
• 27.72 Hz nothing but DARM
• 28.2 Hz PRCL, LSC REFL45 I, ASC REFL A 9I pit, ASC REFL A 45 I yaw

Dtt template is at /ligo/home/sheila.dwyer/SUS/HSTS_damping_signals_checks.xml

FranciscoL, RickS

On April 4, 2024 we used DTT to measure the amplitudes of the Pcal lines used in the Pcal X/Y calibration comparison in both the Pcal end station Rx sensor outputs and the DARM_ERR signal.  The attached plots shows the peaks in the spectra measured with 0.001 Hz requested BW, 50% overlap, 10 averages during a long lock stretch.  The second image is a page from Francisco's lab book.

The SNRs for the lines from the Pcal Rx sensors is about 5e-5 and

the SNRs of the lines in the DARM_ERR signal are about 1350.

Since the sqz angle seemed not optimized and range was below 160 Mpc in this lock, I tuned the sqz angle during observing after 4 hours into lock. The attachment shows that sqz and range improved with sqz angle at 200. The previous sqz angle was 192 and it was set just after the lock in 77144.

We've been locked for 3 hours, in observing since 16:10 UTC. SQZing has been getting better as we thermalize.

TITLE: 04/15 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 8mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:

• Currently in IA following a LL at 13:46UTC
• ITMY camera is blue?
• A little windy out, EX is seeing gusts up to 20mph, and EY up to 30mph

Vicky, Naoki

In the last lock, the FC IR kept unlocking. We first thought the timer issue similar to 76280 so we removed the timer, but it did not help. We checked the FC IR OLG and it was fine. Then we found that the FC ASC input signal moved a lot. We turned off FC ASC and the stability was improved. We decided to go to observe without FC ASC tonight. 

Eric, Naoki, Vicky, Jennie W, Sheila

We did SQZ OMC mode scan with cold OM2. The PSAMS is 175/100 (strain voltage 8.9/-0.69). The attached figure shows the result (ref 34). The SQZ OMC mode matching is 0.64/(0.64+2*0.03)~91.4%.

We followed the instruction in 74892. Here are some notes.

• We increased the seed power to 76mW and requested the OPO guardian to LOCKED_SEED_DITHER and FC guardian to MISALIGNED. The OPO_IR_PD_DC_POWERMON reached only 0.3mW while it was 0.89mW in 74892. We noticed that the seed was locked on the higher order mode. Vicky fixed the OPO guardian and the seed was locked on TEM00. The OPO_IR_PD_DC_POWERMON reached 1.26mW.
• We opened SQZ beam diverter and requested SUS_SR2 guardian to MISALIGNED (SUS_SRM guardian is ALIGNED). After we engaged DC3/4 centering loops, ASC-AS_{A/B}_DC_NSUM_OUT16 are ~75 and ASC-AS_C_DC_NSUM_OUT16 is 0.0009.
• We manually locked OMC. We turned on input and output switch, increased the gain to 1, turned on boost and integrator.
• For rough OMC alignment, we turned on OMC ASC by increasing the OMC ASC master gain "one click up" to 0.025. After that, we decreased the OMC ASC gain to 0 and manually aligned the OM3/OMC to maximize the OMC-DCPC_SUM_OUTPUT. After the manual alignment, OMC-DCPC_SUM_OUTPUT is 0.63.
• For OMC scan, we set the OMC-PZT2_OFFSET to -50 and ran the scan template in $(userapps)/sqz/h1/Templates/dtt/OMC_SCANS/April9_2024_PSAMS_OMC_scan_coldOM2.xml

PSAMS 175/100, cold OM2

• LOCKED: 1396722738 (2024-04-09 18:32:00 UTC) + 60 seconds 
• UNLOCKED: 1396722978 (2024-04-09 18:36:00 UTC) + 60 seconds
• Mode-scan (ref 34): 1396723292 (2024-04-09 18:41:14 UTC) + 200 seconds

DARK

• DARK: 1396723968 (2024-04-09 18:52:30 UTC) + 60 seconds