TITLE: 03/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: EARTHQUAKE
    Wind: 7mph Gusts, 4mph 5min avg
    Primary useism: 0.56 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY:
H1 Down due to a series of earthquakes up to magnitude 6.9.
We have been holding in down for a while and earthquake mode may be deactivated shortly and I will begin to relock.

 

TITLE: 03/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Spent most of the day in commissioning for the ETMY A2L stepping script, but lost lock mid-afternoon from an earthquake; H1 has been holding in DOWN since.

• 16:45 - Dropped observing from SQZ FC unlocking
  • After a couple failed lock attempts by SQZ_FC, everything was brought back to nominal by SQZ Guardians
• 16:51 - Resumed observing
• 17:10 - Dropped observing again from SQZ FC unlocking
  • SQZ_FC brought everything back first try
• 17:12 - Resumed observing
• 17:34 - Dropped observing to start ETMY A2L gain stepping test
• 20:39 - Lockloss from M7.0 EQ - alog76655

LOG:

No log for this shift.

Lockloss @ 20:39 UTC from M7.0 quake out of Papua New Guinea, lock stretch was 6:17. Earthquake mode activated 4 minutes prior.

I was running the A2L stepper script for ETMY when the EQ hit; output of the progress made below:

Start time:

PDT: 2024-03-23 10:34:21.512854 PDT
UTC: 2024-03-23 17:34:21.512854 UTC
GPS: 1395250479.512854

ryan.short@cdsws29[/ligo/gitcommon/labutils/beam_spot_raster]: python a2l_gain_stepper.py ETMY --start "now"
Waiting for start time...
starting p2l: 4.6
starting y2l: 3.2
Adjusting P2L gains @ 1395250501.0 to to 4.3999999999999995
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => 4.3999999999999995
Now waiting for 900 seconds
Adjusting P2L gains @ 1395251402.0 to to 4.199999999999999
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => 4.199999999999999
Now waiting for 900 seconds
Adjusting P2L gains @ 1395252302.0 to to 4.3999999999999995
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => 4.3999999999999995
Now waiting for 900 seconds
Adjusting P2L gains @ 1395253202.0 to to 4.6
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => 4.6
Now waiting for 900 seconds
Adjusting P2L gains @ 1395254102.0 to to 4.8
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => 4.8
Now waiting for 900 seconds
Adjusting P2L gains @ 1395255002.0 to to 5.0
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => 5.0
Now waiting for 900 seconds
Adjusting P2L gains @ 1395255902.0 to to 4.8
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => 4.8
Now waiting for 900 seconds
Adjusting P2L gains @ 1395256802.0 to to 4.6
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_SPOT_GAIN => 4.6
Now waiting for 900 seconds
Adjusting Y2L gains @ 1395257702.0 to to 3.0
H1:SUS-ETMY_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 3.0
Now waiting for 900 seconds
Adjusting Y2L gains @ 1395258602.0 to to 2.8000000000000003
H1:SUS-ETMY_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 2.8000000000000003
Now waiting for 900 seconds
Adjusting Y2L gains @ 1395259502.0 to to 3.0
H1:SUS-ETMY_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 3.0
Now waiting for 900 seconds
Adjusting Y2L gains @ 1395260402.0 to to 3.2
H1:SUS-ETMY_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 3.2
Now waiting for 900 seconds
Adjusting Y2L gains @ 1395261302.0 to to 3.4000000000000004
H1:SUS-ETMY_L2_DRIVEALIGN_Y2L_SPOT_GAIN => 3.4000000000000004

Sat Mar 23 10:09:44 2024 INFO: Fill completed in 9min 40secs

Outside temps have dropped again (47F this morning) so the -120C trip was barely sufficient (TCmins -137,-130 today). I've increase the trips to -100C for the next week as we go into a cold spell.

TITLE: 03/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 144Mpc
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 5mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY: H1 has been locked and observing for 40 minutes. The ETMY A2L stepper script started at 13:00 (6am PDT), but H1 lost lock around 30 minutes later, so I'll find time to run it again today.

• 3 locklosses overnight; each reacquisition seems to have gone smoothly
• Wind and microseism are low
• All other systems nominal

Related to alog 76642 the following parameters of the OPO were updated:

TITLE: 03/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 140Mpc
INCOMING OPERATOR: None
SHIFT SUMMARY:
We have been in Nominal Low Noise for 3 hours.
6:39 UTC dropped out of Observing SQZ manager Dropped from FREQ_DEP_SQZ (100) to FDS_READY_IFO (50)
I then set SQZ manager to NO_SQUEEZING (7)
AND while trying to find write my steps down that I just took, I accidentally Unlocked the SQZr by unintentionally clicking a random SQZ state and had to repeat my steps.
Returned back to OBSERVING at 6:48 UTC.

GRB-Short E470299 candidate @ 6:55 UTC.

I have set Sheila as the Remote Contact and edited the contact type to TXT as requested by the Prior Operator.
SQZr unlocked again right as i was leaving. Stayed to relock it.


LOG:
No Log

TITLE: 03/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 133Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 15mph Gusts, 13mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:
Verbals still funny every hour on the hour.  Great comedic timing.

Lockloss : 2:36 UTC (GPStime: 1395196594)
The Lockloss select tool does not bring up the latest lockloss.
The newest lockloss the lockloss select tool has availible is 2024-03-21_21:15 (GPStime 1395090968)

Relocking:
Initial Alignment: I touched up ETMY in Yaw for Green arms
NOMINAL_LOW_NOISE reach at 4:09 UTC
Observing reached at 4:14 UTC

 

TITLE: 03/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 15mph Gusts, 12mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.18 μm/s
QUICK SUMMARY:
H1 Is currently locked and OBSERVING for over 16 hours now.

Verbals is telling me jokes at the start of every hour now, which is fun. I'm not sure if this is going to continue all night or if someone is waiting for this to hit the Alogs, but I love it.

Current time:   (Mar 23 0000 UTC)
The time is... joke time: My pet mouse 'Elvis' died last night. He was caught in a trap..   (Mar 23 0000 UTC)

Current time:   (Mar 23 0100 UTC)
The time is... joke time: I really want to buy one of those supermarket checkout dividers, but the cashier keeps putting it back.   (Mar 23 0100 UTC)

But over all everything is going fine, well except for poor Elvis.

As shown in the attachment, the output of CLF second AOM is 61dBm while the nominal is 31dBm. The output increased 10 days ago when new CLF VCO is installed in 76297.

Naoki, Sheila, Nutsinee, Daniel

Today we found that the CLF_LAUNCH_DC_POWERMON was 270uW and the CLF_REFL_LF_OUTPUT was 30uW, which means the CLF fiber coupling is only 10%. First we thought the fiber coupling got worse so we went to SQZT0 and tried to align the CLF fiber. However, we could not improve the alignment and found that the CLF power before the fiber is 75uW, which should be 270uW according to the CLF_LAUNCH_DC_POWERMON. So the fiber coupling is 40%, which is OK, but the calibration of CLF launch PD has changed. We calibrated the CLF_LAUNCH_DC_POWERMON to 75uW as shown in the first attachment.

The second attachment shows that the CLF launch power was 650uW and the CLF REFL power was 245uW 8 days ago. We reduced the CLF power 8 days ago in 76405 and after that, the CLF launch power was 270uW and the CLF REFL power was 10uW. 

Daniel pointed out it is due to the polarization contamination. The CLF launch light might have some p-pol from the imperfect PBS for CLF rejected and it is a fixed proportion of the light incident to the PBS. Since the reflectivity of BS before the CLF launch PD is different for p/s-pol, when we reduced the CLF power, the p/s-pol ratio increased and effectively changed the calibration of the CLF launch PD.

Daniel, Nutsinee

OPO didn't lock last night because it couldn't find a dual resonance. The OPO scan starts from 60V to 110V but it should have been 20 to 70V. The lock point prior to down time the dual resonance was found at 64V. We started scanning too close to the lower threshold. After several failures the OPO guardian went to idle and stopped trying for the rest of the night. 

An instruction to ops:

Next time the IFO loses lock, please go to sitemap > SQZ OVERVIEW > SQZT7 > OPO PZT and drag the PZT offset slider bar to 0. See screenshot attached.

TITLE: 03/22 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 9mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY:

IFO was in NOMINAL_LOW_NOISE when I arrived and shortly after H1 was in OBSERVING.
The Lockclock should not be trusted for the duration of this lock because it was restarted 6 hours ago.
The Current Lock has been in NLN and above for over 14 Hours and 30 minutes.
Everything else looks good and is currently running smoothly.
 

TITLE: 03/22 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: Tony
SHIFT SUMMARY: H1 remained locked all shift, current stretch is at 14 hours (lock clock in control room is inaccurate for this lock), which made for lots of commissioning opportunities.

• 21:21 - NLN_CAL_MEAS for LSC measurements
• 22:43 - Back to NLN
• 23:05 - Started Observing (no commissioning activities desired at the moment)

LOG:

Last night due to some SQZ MANAGER issues, we had a long period without squeezing on. For future reference here is a list of NO SQZ quiet times with no glitches:

First 10 mins of a lock at NLN: GPS 1395133005

then 1395134044 - 1395139295 GPS for thermalisation period of 1 hr 28 mins with no glitches.

Then period 1395139667 to 1395146035 is 1 hr 44 mins about 2 hours into lock.

Then best thermalised period is GPS 1395151019  for 53 mins. (third image).

SQZ time starts at 1395165711 GPS for 53 mins on 22nd March. This was while we were doing our REFLB off test but it should be fine range-wise. (second image)

Calibrated measurement of DARM is shown in first image.

Code located in /ligo/gitcommon/labutils/beam_spot_raster/a2l_gain_stepper.py

Current spot positions (e.g. H1:SUS-ITMX_L2_DRIVEALIGN_P2L_SPOT_GAIN):

It will step the nominal values up and down 0.4 in 0.2 steps / 15 minutes. e.g. starting a2l + [-0.2, -0.4, -0.2, 0, 0.2, 0.4, 0.2, 0]

I've set up a script to run this on ETMY at 6am to 10am tomorrow (23rd) in a tmux session on cdsws26, will only run if the IFO is at NLN (>=600)  at 6am.

Ryan S will try to find times (4 hours each) to run this on the other optics ITMX and ETMX over the weekend, command below. We don't have beam spot control on ITMY so can skip that.

>> python /ligo/gitcommon/labutils/beam_spot_raster/a2l_gain_stepper.py ETMY --start 'now'

EvanH, FranciscoL

Because we've been loosing lock for unknown reasons, we measured OLG transfer function of MICH, SRLC, and PRLC. The UGF for each one is (see attached figures for reference) roughly

MICH: 10 Hz

SRCL: 12 Hz

PRCL: 35 Hz

We may want to lower the MICH UGF to avoid cross coupling with the SRCL loop.