TITLE: 03/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 11mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:
H1 Is locked an Observing for 16.5 hours.
H1:PEM-CS_DUST_PSL101                    Error: data set contains 'not-a-number' (NaN) entries

All three IFO's are locked and Observing.
Everything looks good.

TITLE: 03/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

• 13:00 - ETMX A2L stepper script started (scheduled)
• 17:00 - ETMX A2L stepper script finished
• 17:03 - ITMX A2L stepper script started; dropped observing
• 21:03 - ITMX A2L stepper script finished
• 21:05 - To NLN_CAL_MEAS for calibration sweeps
• 21:38 - Calibration sweeps finished; back to NLN and resuming observing

LOG:

No log for this shift.

Following instructions from the TakingCalibrationMeasurements wiki, this afternoon I ran both broadband PCal and Simulines measurements.

Sun Mar 24 10:11:41 2024 INFO: Fill completed in 11min 37secs

TITLE: 03/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph 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 over 8 hours. The ETMX A2L gain stepper script started 2 hours ago, but since the ETMX P2L and Y2L spot gains are not monitored in SDF, the IFO has remained observing (Do we want this? Tagging ISC).

• Wind and seismic motion are low
• All other systems nominal

TITLE: 03/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 134Mpc
INCOMING OPERATOR: None
SHIFT SUMMARY:
In short H1 was tough to lock tonight mostly due to Earthquakes, a sudden spike in wind, potentially a lighning storm, and poor alignment.

ALS X had a PLL PDH error and gave me an ARM In fault code
Crystal Frequecy out of Tolerance
But it seems to have resolved the issue with out any real intervention from me.

Had many locklosses that I could not explain, and the Lockloss select tool is no longer working.
To get H1 relocked again:
Restored all (except SQZ back to the point of Right After an the First Initial Alignment tonight that lead us to the Low Noise Length Control State. GPS Time: 1395274481
Touched up x and Y are for Green arms.
Had another Lockloss @ PRMI and then Ran another Initial Alignment and I was able to get to NLN right before the end of the night.
Accepting the H1:SQZ-OPO_PZT_1_OFFSET in SDF.
Observing reached at 6:53 UTC

LOG:
No Log

TITLE: 03/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Earthquake
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.20 μm/s
QUICK SUMMARY:

H1:PEM-CS_DUST_PSL101                    Error: data set contains 'not-a-number' (NaN) entries

Waited For ground motion to go down.

started Initial alignment and X arm looked a little strange so I took ISC_lock to GREEN_ARMS_MANUAL [13]
Which allowed me to touch up X arm a bit.
I ten too ISC_LOCK back to Initial_Alignment and this screen shot was taken where X arm seems to be "a fat noisey signal" more so than usual. I though that was a little weird.
COMM = +3
Diff= -8
 
Relocking got to Transition from ETMX then a lockloss  00:51 UTC .
Lockloss from Find IR
Lockloss from LOW_NOISE_LENGTH_CONTROL
Redoing Initial_Alignment
Another Lockloss at LOW_NOISE_LENGTH_CONTROL

None of the Locklosses at LOW_NOISE_LENGTH_CONTROL seem like they were caused by ground motion.
Incoming  Earthquake from Timor_Leste 5.7
Lockloss at Find IR
Another Lockloss at Find IR
Did I just hear thunder? Do we have a lightning sensor to check out?
Checked the H0:FMC-EX_MAINS_CHAN_ voltage channels for spikes. I didn't  see anything Like Oli's Alog.

I'm still not sure why we are losing lock at LOW_NOISE LENGTH CONTROL yet because we keep getting Locklosses at DRMI and below.
Holding for a few 5.7 Mag earthquakes to roll through.








 

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

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.