aLIGO LHO Logbook

H1 General - Sat Eve Ops Shift End

anthony.sanchez@ligo.org — Sun, 28 Apr 2024 00:01:35 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77469

TITLE: 04/28 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 2mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.11 μm/s
SHIFT SUMMARY:
Very quiet night.
The Wind is dieing down finally.
H1 Has been locked for 12 Hours and 12 minutes, and Observing.

H1 SEI - BRS Drift Trends--Monthly

anthony.sanchez@ligo.org — Sat, 27 Apr 2024 23:46:41 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77468

BRS Drift Trends--Monthly Famis 26442

Trends go all the way back to Febuary which is when we let air into the vacuum chamber, so the ETMY Damp CTRL signal does make sense for that time frame in Febuary and early March.
BRSX has a few interesting spikes, April 2nd or 3rd Jim was adjusting the mass adjuster pico meter.
March 6th & 7th ish there was some BRSX work & computer restart due to BRS not damping .

But Both BRS X & Y are within range!

Images attached to this report

H1 CAL - PCAL EX End Station Measurements & Lab Measurements April 23rd

anthony.sanchez@ligo.org — Sat, 27 Apr 2024 22:29:02 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77467

A PCAL EndX Station Measurement was done on April, the PCAL team(
Dripta B. & Tony S.) went to EndX with Working Standard Hanford aka WSH(PS4) and took an End station measurements.
The EndX Station Measurement was carried out according to the procedure outlined in Document LIGO-T1500062-v15, Pcal End Station Power Sensor Responsivity Ratio Measurements: Procedures and Log.

Measurement Log
First thing they should have done was take a picture of the beam spot before anything is touched!

Martel:
Martel Voltage source applies voltage into the PCAL Chassis's Input 1 channel. We record the GPStimes that a -4.000V, -2.000V anhttps://alog.ligo-wa.caltech.edu/aLOG/uploads/77467_20240427213103_SPot.jpgd a 0.000V voltage was applied to the Channel. This can be seen in Martel_Voltage_Test.png . We also did a measurement of the Martel's voltages in the PCAL lab to calculate the ADC conversion factor, which is included on the above document.

Plots while the Working Standard(PS4) is in the Transmitter Module during Inner beam being blocked, then the outer beam being block, followed by the background measurment: WS_at_TX.png.

The Inner, outer, and background measurement while WS in the Receiver Module: WS_at_RX.png.

The Inner, outer, and background measurement while RX Sphere is in the RX enclosure, which is our nominal set up without the WS in the beam path at all.: TX_RX.png.

The last picture is of the Beam spots after we had finished the measurement.

All of this data is then used to generate LHO_EndX_PD_ReportV2.pdf**** which is attached, and a work in progress in the form of a living document.

All of this data and Analysis has been commited to the SVN :
https://svn.ligo.caltech.edu/svn/aligocalibration/trunk/Projects/PhotonCalibrator/measurements/LHO_EndX/

PCAL Lab Responsivity Ratio Measurement:
A WSH/GSHL (PS4/PS5)FrontBack Responsivity Ratio Measurement was ran, analyzed, and pushed to the SVN.
The analysis of this measurement produces 4 PDF files which we use to vet the data for problems.
raw_voltages.pdf
avg_voltages.pdf
raw_ratios.pdf
avg_ratios.pdf

Obligitory BackFront PS4/PS5 Responsivity Ratio:
PCAL Lab Responsivity Ratio Measurement:
A WSH/GSHL (PS4/PS5)BF Responsivity Ratio measurement was ran, analyzed, and pushed to the SVN.
The analysis of this measurement produces 4 PDF files which we use to vet the data for problems.
AlphaTrends
raw_voltages2.pdf
avg_voltages2.pdf
raw_ratios2.pdf
avg_ratios2.pdf

This adventure has been brought to you by Dripta B. & Francisco L.

Images attached to this report

Non-image files attached to this report

T1500062.pdf

LHO_EndX_PD_ReportV2.pdf

PS4PS5_alphatrends.pdf

H1 General - Sat Eve Ops Shift Start

anthony.sanchez@ligo.org — Sat, 27 Apr 2024 16:12:00 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77466

TITLE: 04/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 23mph Gusts, 14mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:
Wind speeds are elevated, but H1 has been Locked and Observing for over 4 hours.
Robert has an accelerometer line going through the Hallway, out the door and across the road. Please dont drive down Y arm until after the cable has been removed sometime tomorrow.

OpsInfo, PEM

LHO General - Ops Day Shift Summary

ryan.short@ligo.org — Sat, 27 Apr 2024 16:00:50 -0700

Author: ryan.short@ligo.org

Report ID: 77465

TITLE: 04/27 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: One lockloss and an earthquake this shift, but otherwise a quiet one. Since neither H1 nor L1 were locked for the scheduled 18:30 UTC coordinated calibration sweeps, we have postponed them until tomorrow at the same time.

16:50 - Incoming EQ from Christmas Island
17:18 - Lockloss (alog77463)
17:33 - EQ mode activated while relocking
18:47 - Reached NLN
18:49 - Started observing

H1 has now been locked for 4 hours.

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
17:19	PEM	Robert	EX	-	Picking up cables	17:37

H1 General - Comment to Lockloss @ 17:18 UTC

ryan.short@ligo.org — Sat, 27 Apr 2024 11:59:15 -0700

Author: ryan.short@ligo.org

Report ID: 77464

H1 back to observing as of 18:29 UTC.

H1 General - Lockloss @ 17:18 UTC

ryan.short@ligo.org — Sat, 27 Apr 2024 10:36:35 -0700

Author: ryan.short@ligo.org

Report ID: 77463

Lockloss @ 17:18 UTC - link to online lockloss tool

There was a M6.1 quake from Indonesia incoming at the time, although I don't immediately see evidence that ground motion caused this lockloss.

Lockloss

Images attached to this report

LHO VE - Fri and Sat CP1 Fill

david.barker@ligo.org — Sat, 27 Apr 2024 10:26:38 -0700

Author: david.barker@ligo.org

Report ID: 77462

Sat Apr 27 10:10:32 2024 INFO: Fill completed in 10min 28secs

Fri Apr 26 10:10:46 2024 INFO: Fill completed in 10min 42secs

Jordan confirmed a good Friday fill curbside.

Images attached to this report

LHO General - Ops Day Shift Start

ryan.short@ligo.org — Sat, 27 Apr 2024 08:06:16 -0700

Author: ryan.short@ligo.org

Report ID: 77461

TITLE: 04/27 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY: Looks like H1 lost lock around 6 hours ago from a M6.5 EQ from Japan and Oli was able to help it back up. H1 has been locked and observing for 3 hours.

Microseism is trending down and wind is low
All other systems nominal

H1 ISC - Step in Clean range around 5:20 this morning

sheila.dwyer@ligo.org — Sat, 27 Apr 2024 07:34:20 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77460

There was a drop in clean range around 5:20 this monrning, which doesn't seem to be a reapeat of the output arm shift we had earlier this week.

Attached is a trend of the DARM blrms (based on DARM error, no calibration corrections or cleaning) and comparison of the cleaned and corrected range against the CAL-DELTAL range, only the cleaned channel sees the drop. This made me concerned that we had a drop in optical gain, but the trend of the time dependent calibration correction factors doesn't show anything happening at this time.

I don't know what would cause a sudden change in the clean range, since I don't think that the jitter subtraction would cause a sudden change like this.

Images attached to this report

H1 General - 04/27 OWL Intervention

oli.patane@ligo.org — Sat, 27 Apr 2024 04:47:42 -0700

Author: oli.patane@ligo.org

Report ID: 77459

H1 Manager called because it couldn't get ALSY to lock in initial alignment. The flashes were barely below being able to catch. I paused INIT_ALIGN and touched ALSY in yaw and we were able to lock green and are on our way back up.

H1 General - Friday night Eve Shift End

anthony.sanchez@ligo.org — Sat, 27 Apr 2024 00:02:03 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77458

TITLE: 04/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
H1 is locked and Observing for 4 Hour now.
Relatively quiet night.

LOG:
No log

LHO FMCS - Vibration Sensors HVAC Fans Health

anthony.sanchez@ligo.org — Fri, 26 Apr 2024 22:57:22 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77457

FAMIS 26297

H0:VAC-MX_FAN1_370_2_ACC_INCHSEC has a very Strange looking reoccuring ingrease in its noise.
It looks like this fan wasn't being used until about 100 days ago. 100 days ago it seemed to be fairly noisy as well, but this is strange looking and very different.
it seems like the fan is noisy for 12-16 ish hour and quiet for 8-16 hours. Maybe this particular fan isnt on for 8 hours,
It's likely it turns on at 1Pm and turns Off at 9-10 pm.

I think this is a new noticable development since the last time I checked on the Vibrometers.

Images attached to this report

H1 General - Lockloss & Fri Mid Eve shift update

anthony.sanchez@ligo.org — Fri, 26 Apr 2024 20:39:34 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77456

TITLE: 04/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:

00:52 UTC Intentional Drop from Observing to adjust squeeze angle.

Requested SQZ_MANGER to go to SCAN_SQZANG saw the phase slider move around a bit and it created https://lhocds.ligo-wa.caltech.edu/exports/SQZ/GRD/SQZANG_SCAN/SQZANG_SCAN_240426175458.png

00:56 UTC Back to Observing

2:04 UTC Lockloss https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1398218686

Unknown cause but ETMY L2 Master out starts to change behaivor about a second before the lockloss.

---Relocking--
Increase flashes ran for YARM
Happened automatically without any input from me.
Nominal_Low_Noise reached at 3:01 UTC
Observing reached at 3:04 UTC

Lockloss

Images attached to this report

X1 SUS - Searching for the perfect position for the secondary prism on the BBSS

oli.patane@ligo.org — Fri, 26 Apr 2024 20:05:16 -0700

Author: oli.patane@ligo.org

Report ID: 77455

Ibrahim A, Oli P, Mark B, Betsy W

Context:

M3 on the beam splitter has secondary prisms that are placed along the barrel below the primary prisms. These secondary prisms are placed at a location below the primary prism, and if placed in the correct spot, act as a clamp, damping the oscillations moving down the wire loop into the optic. We've been working on finding the optimal secondary prism position for the BBSS.

Experiment:

The experiment for determining this position was developed for the BSFM in 2011(T1100086), and we used a similar setup for our three (successful) runs for the BBSS. This is basically how the experiment is set up to work:

A biased solenoid is placed a few millimeters away from one of the M2-M3 loop wires. The solenoid is driven at the wire’s predetermined resonance frequency using a waveform generator.
The wire goes from M2 down through M3’s fixed primary prism and (the reason for this experiment) moveable secondary prism.
Phonograph needle is rested on wire below the secondary prism and the other end is connected to a spectrum analyzer. Five FFT averages are taken to give us an attenuated peak at the resonant frequency. This is a reading. We took 4/5 measurements for each location, where each measurement consisted of five 8-second averages.
We move the prism down by a millimeter or two and take more readings.
From the results, we determine the lowest amplitude peak/highest attenuation and note the prism position.
This becomes the new BBSS secondary (glued on) prism position.

Results + Commentary:

Note: Mark has an upcoming alog about the run of data and issues that we took when he was here, but in LESS IMPORTANT Auxiliary Investigations we will be focusing on the data from the second and third runs, but here in the results will still be showing the data we got with him.

The plot attached shows the attenuation measured versus the position (positive distance relative to the mass’ centerline) of the secondary prism. Each color is a separate run, and the more negative the attenuation, the quieter the reading was, so we are looking for a location with the lowest values where the secondary prism would do the most damping.

We found that there is a region between ~29.00mm and ~31.5mm below the horizontal center of the mass where the amplitude is minimized. There are approximately three anomalous data points in between, with one confirmed being due to cross-coupling of above wire. As of now, we’re still working on understanding this data and have spoken to Mark B and Jeff K about how we can go about accurately interpreting the raw data (including essential questions about the calibration and setup. See below.)

LESS IMPORTANT Auxiliary Investigations - Details, Details, Details

Read for Clues/Hints (things we noticed, changed etc.):

Mass Locking: When Mark Barton was at LHO, we “almost locked” the Test Mass in order to help damp any motion that we caused when we adjusted the experiment for a new reading. This locking was not meant to take the load off the wires but we realized that given differing amounts of “just touching”, our attenuation amplitudes changed by over 20dB systematically. Importantly, the attenuation difference did not change the resonant frequency, which is what really matters. Given this, we proceeded with an “almost locked” Dummy Test Mass.
Cross Coupling: The expected behavior for this experiment is that there is a minimum/dip in the resonant frequency amplitude where we can optimally glue the secondary prism. At certain positions along this trend however, we noticed a marked and visible vibration in the wire. Upon further investigation, we found that the wire segment directly above it (Top Mass - PUM) was also visibly vibrating. Upon meeting with Mark and checking records, we found that this was more than likely an nth harmonic of that upper wire causing cross-coupling. Thus, these “anomalous” positions should be avoided.
Needle Changes: One of the three data sets we have was taken with a different needle because the one used for the first run had broken, and we had another needle become permanently cocked out of place and give us erroneous readings before we swapped the needle again and were able to get a good second and third run. We took “no contact” or noise floor measurements for each new needle. The noise floor measurements for each run were taken and we are working on calibrating the two needle sensitivities to better represent our data.
Needle Touching: We tried to see if there was an effect in noise with the needle touching head on vs. on the side of the wire. We found that while the location of the needle on the wire didn’t really matter, the amount of tension between the needle and the wire does add some damping to the wire. As such, we attempted to ensure that the needle was resting on the wire rather than applying any force to it. We also tried to replicate the location/contact area of the needle for consistency.
Cable Changes: We noticed that moving BNC cables too close together or having them sway in the cleanroom air contributes to noise. To tackle this, we used small weights to secure them to the ground and separated them as much as possible.
Solenoid Distance Changes: For unknown reasons, and despite our wave function generator having the same output throughout, the wire would vibrate visibly at certain times than others for the same frequency. After playing with certain distances, we landed on the original 2.5mm for the sake of consistency. An effect we did notice is that if the solenoid was actuating too strongly, it would move the wire laterally back and forth with some oscillatory behavior. This would move the entire mass. At our 2.5mm, we tried to ensure that the wire was still visibly vibrating but not so much as to cause translation movement in the masses or the wire.
Resonant Frequency Experimentation (Largest Persistent Confusion):
- Mark gave us this suggestion to see the effect of frequency changes on the wire for different prism positions. We realized that when we sweep the frequency over +-2Hz, there was definitely more oscillation in some points than others. This was the case for each position we tried. I.e. The resonant frequency of the wire changed slightly as the prism moved down (and even just with a prism in vs. without), and as such, the actuation frequency from the solenoid was not (and could not have been) exactly at the resonance of the wire.
- What is confusing to us here is that if the entire point of the experiment is to shake the wire by some constant amount to measure the attenuation below the prism, how can we be sure that this attenuation is maximized if the amount that the wire is shaken changes and in fact, depends on the prism position? (by virtue of the res. Freq. moving slightly by each move).
  - E.g. At position 16, the wire was vigorously shaking (due to coupling) so obviously our reading was just … louder.
  - E.g. At position 18, the wire was so far away from the attenuation frequency that it was not moving at all so obviously our reading was just … quieter. We spanned the frequency at the same actuation strength and found that the resonant frequency had moved all the way from 303 to 307 Hz - so obviously the wire isn’t resonating/shaking things as much.
- We tried taking readings where we just match the visible vibration at each prism point but quickly realized that this would just yield us the same results each time because it tells us nothing about the attenuation of the actual resonant frequency we want to damp just how good this prism system was at damping any vibration.
- With 2 needles, this effect would be negated because we could just take signal A and signal B and compare the attenuation before and after the prism. We have the tools for this if it is worth doing.

SUS

Images attached to this report

H1 General - Friday Eve Shift Start

anthony.sanchez@ligo.org — Fri, 26 Apr 2024 16:12:32 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77454

TITLE: 04/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT
    Wind: 9mph Gusts, 6mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY:
H1 is locked for 2 hour 52 minutes.
When H1 has been locked for 4-5 hours I will follow the instructions out lined by Sheila's Alog 77447 to adjust the SQZ angle after the IFO has been thermalized.
The will take us out of Observing for a short time.

SQZ

LHO General - Ops Day Shift Summary

ryan.short@ligo.org — Fri, 26 Apr 2024 16:07:01 -0700

Author: ryan.short@ligo.org

Report ID: 77450

TITLE: 04/26 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: Commissioning for most of the morning which ended in a lockloss. Relocked easily and have been observing for the afternoon.

15:20 - S240426dl
16:01 - Dropped observing for commissioning
18:55 - Lockloss - alog77442
20:12 - Reached NLN
- During this acquisition, Jenne re-enabled the PRMI ASC loops in the ISC_DRMI Guardian after we realized they were not turning on during PRMI_ASC
20:34 - Started observing after Sheila retuned SQZ angle (alog77447, will need to do this again this evening after H1 is thermalized)
22:32 - Saturation callouts for ITMX, ITMY, and BS simultaneously; PRG, CSOFT_Y, DHARD_P all saw motion at this time

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
15:48	SQZ	Terry, Kar Meng	Opt Lab	Local	SHG work	16:52
16:04	PEM	Robert	LVEA, EX	-	Pack up equipment	17:52
17:46	VAC	Janos	EX	-	CP dewar jacket pumping	18:39
17:52	SQZ	Terry, Kar Meng	Opt Lab	Local	SHG work	20:17
18:49	PEM	Robert	EX	-	Shutting down PEM setup	19:38
20:21	PEM	Robert	CER	-	Retreive cable	20:32
21:36	SQZ	Terry, Kar Meng	Opt Lab	Local	SHG work	23:36

H1 ISC - Comment to Ran Bruco on DARM stretch while we were at 152MPc last night

sheila.dwyer@ligo.org — Fri, 26 Apr 2024 15:01:49 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77453

There's coherence with CHARD Y and SRCL,
HAM4 L4C
CHARD P has a lot of coherence at 20 Hz, running A2L again may help clean this up.
A lot of HAM2 sensors around 40 Hz

H1 ISC - OMC fringe wrapping measurement to check OFI health

sheila.dwyer@ligo.org — Fri, 26 Apr 2024 14:48:13 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77452

After the changes in our output arm this week (77427) we took some time to check the level of backscatter from the AS port, as a way to check the health of the OFI.

I tried to reproduce Camilla and Eleonora's excitation from 71354, using a 0.65 Hz excitation on OMC L, and adjusted the amplitude until I saw about 12um peak to peak motion of the OMC (peak to peak amplitude measured by OMC M1 DAMP IN1, in um, are listed in the legend.)

Comparing this plot to 71354, the amplitude of reflected light does seem higher now by about a factor of 2. We didn't repeat this measurement after the OMC was swapped, before the apparent changes in the OFI.

Images attached to this report

H1 ISC - Comment to Ran Bruco on DARM stretch while we were at 152MPc last night

sheila.dwyer@ligo.org — Fri, 26 Apr 2024 14:31:48 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77451

Elenna's bruco instructions are at /ligo/home/elenna.capote/bruco_instructions.txt

(I've attached a copy here as well)

Non-image files attached to this report

bruco_instructions.txt

H1 ISC - Ran Bruco on DARM stretch while we were at 152MPc last night

jennifer.wright@ligo.org — Fri, 26 Apr 2024 13:45:38 -0700

Author: jennifer.wright@ligo.org

Report ID: 77449

Thanks to Elenna for the instructions!

The BRUCO can be found here and ran on 400s seconds starting at 1398159599.

Analysis in progress.

ISC

H1 General - Comment to Lockloss @ 18:55 UTC

ryan.short@ligo.org — Fri, 26 Apr 2024 13:40:26 -0700

Author: ryan.short@ligo.org

Report ID: 77448

H1 back to observing as of 20:34 UTC.

H1 ISC - operator request for sqz angle adjustment once IFO has thermalized

sheila.dwyer@ligo.org — Fri, 26 Apr 2024 13:36:58 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77447

I've just retuned the SQZ angle with a freshly locked IFO, which will not be well tuned once the IFO is thermalized. Once we have been locked for ~4-5 hours, it would be good for the operator to re run this so that the squeezing angle is set for a thermalized IFO.

Please, go out of observing, from sqz manager select SCAN_SQZANG. This will create a folder (named by the time you run it) https://lhocds.ligo-wa.caltech.edu/exports/SQZ/GRD/SQZANG_SCAN/

The plot should look something like this, with a minumum of squeezing at some CLF phase, which should now be where H1:SQZ-CLF_REFL_RF6_PHASE_PHASEDEG is set to.

H1 ISC - Comment to Can un-clip at AS port with massive SR3 and SR2 moves

sheila.dwyer@ligo.org — Fri, 26 Apr 2024 12:51:38 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77446

slider changes:

SR2 P + 60 urad SR2 Y +1786 urad
SRM P didn't move much compared to it's usual drift SRM Y - 148 urad
SR3 P no change SR3 yaw +269 urad

H1 ISC - Beam positions on SRM, SR2 after The Move

jenne.driggers@ligo.org — Fri, 26 Apr 2024 12:50:40 -0700

Author: jenne.driggers@ligo.org

Report ID: 77443

There had been a suggestion (passed to me by Sheila) that we should measure the beam positions on SRM and SR2 after the big move that we made this week (which is summarized in alog 77427).

We don't have a premade script to do this like we have for the test masses, so I just did it by hand. One at a time, I put in a line using the ADS screen to SR2 or SRM pit or yaw, then changed the corresponding A2L element to minimize the line height in CAL-DELTAL_EXTERNAL. I was also watching SRCL_IN1 and SRCL_OUT, but the lines disappeared in the SRCL signals before they disappeared in the DARM signal, so I just used DARM.

All A2L values for SR2 and SRM had been 0.0, so I'm not going to bother putting in a 'before' column in the table below since they were all the same value of zreo.

After finding those values, I ran /opt/rtcds/userapps/release/isc/common/scripts/decoup/BeamPosition/CalcSpotPos.py to get from A2L coefficient to beam spot. This script had been made for IMC optics, but since SRM and SR2 are the same style, the calculation should be the same. Reminder of where this calc comes from (it's referenced in the script): alog 31402.

We don't have any 'before' measurements to compare to, but at least we now have some amount of information of where we are on these optics after the big move.

I'm pretty sure that these new A2L values can only be good, so I've accepted them in both safe and observe snaps for SR2 and SRM (see first and second attachments, only 2 rows per SDF table are accepted). These A2L gains for non-test mass suspensions are not under guardian control, so this should be good enough to keep them in place.

In the table below, the Cal-Deltal line reduction factor ends up really just being the ratio of the peak height in DARM before I started doing anything to that dof, and the noise level. To do a better job of measuring this, I would have had to increase my excitation amplitude, but that didn't seem important enough to do given the limited commissioning time we had.

	ampl [counts] of line at 30.5 Hz	A2L gain step size when minimizing	CAL-DELTAL line reduction factor	Final A2L gain	Inferred spot position [mm]
SR2 P2L	0.1	0.1	50x	+5.5	11.1
SR2 Y2L	0.1	0.3	45x	-4.5	-9.1
SRM P2L	0.7	0.1	100x	-3.4	-6.8
SRM Y2L	0.7	0.1	50x	+3.6	7.2

I don't have time right now to think through the whole left-vs-right sign convention (it's discussed in alog 31402), but it does look like we're rather 'diagonal' in the SRC now, since the signs of the spot positions are opposite for SR2 vs SRM (eg one positive P2L and one negative P2L means the beam is on opposite sides of center).

Images attached to this report

H1 ISC - attempt to retune SQZ

sheila.dwyer@ligo.org — Fri, 26 Apr 2024 12:42:15 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77445

First I ran SCAN_SQZANG from SQZ_MANAGER, result is here

Then switched to anti squeezing by flipping sign on CLF servo and adjusting sqz angle to 98 (roughly watching the DTT template), and ran SCAN_ALIGNMENT_FDS. Results are here: https://lhocds.ligo-wa.caltech.edu/exports/SQZ/GRD/ZM_SCAN/240426111805/

In that scan it looked like some of the degrees of freedom didn't end at the place that was really maximizing anti-squeezing, perhaps because the best alignment was at the edge of the scan range. I manually moved AM4 + ZM6 to try to increase the anti-squeezing based on these plots (and watching in dtt). I also noticed during this that a lot of time in SCAN_SQZ_ALIGNMENT is taken up with scanning the squeezing angle, which is necessary if we are using squeezing to align, but seems like it will be less necessary for anti-squeezing. I looked at the sqz angle the script was choosing, and indeed it wasn't changing much at each alignment step. I've added logic to the state that it does this sqz angle scans if the fom is sqz, but skips it for asqz. This cuts the time that the script takes in half, so it now takes 5 minutes.

Re-running the script (without scanning sqz angle) produced this set of plots: 240426115056/ which show that we seem to have maximized anti-squeezing for differential alignment, but the plots for common seem like noise. We may need to make a larger scan for common.

We lost lock right as this scan finished, but don't think that the scan was the cause of the lockloss. We will need to retune the sqz angle when we relock, and may also need to retune it after the IFO has thermalized.

H1 ISC - Comment to Aligning then lock attempt coming up

jenne.driggers@ligo.org — Fri, 26 Apr 2024 12:31:30 -0700

Author: jenne.driggers@ligo.org

Report ID: 77444

We had an almost 30 hour lock, but probably we want PRMI ASC to work again now that we're relocking. RyanS and I have just set lines 737 and 738 back to True to enable PRMI ASC.

H1 General - Lockloss @ 18:55 UTC

ryan.short@ligo.org — Fri, 26 Apr 2024 12:13:00 -0700

Author: ryan.short@ligo.org

Report ID: 77442

Lockloss @ 18:55 UTC - link to online lockloss tool

This was at the tail-end of commissioning time, but commissioning activities happening at the time don't seem to be the cause. At this point, no obvious cause.

Lockloss

Images attached to this report

H1 ISC - AS single bounce powers April 16th vs 24th

thomas.shaffer@ligo.org — Fri, 26 Apr 2024 10:42:22 -0700

Author: thomas.shaffer@ligo.org

Report ID: 77441

In alog77427, Sheila notes that our optical gain and power at the AS port PDs dropped 4% Monday night. On Wednesday after we moved SR3, SR2 to recover the throughput into HAM6, in a full lock our AS port PDs are now 12% lower than out last good lock Monday night before the optical gain drop. This number might be confusing with an alignment change, getting more or less 45Mhz down into HAM6. Another good comparison is from a no SQZ single bounce that Jennie Wright did in alog77204 a few weeks ago, compared to just after Jenne moved SR3, SR2 (alog77395).

PSL single bounce comparision

PD	2024-04-16 16:23 UTC	2024-04-24 20:50 UTC	% diff
AS_A sum	1867	1850	0.91%
AS_B sum	1900	1878	1.16%
AS_C sum	0.0228	0.0225	1.32%

H1 ISC - OMC alignment scan started

sheila.dwyer@ligo.org — Fri, 26 Apr 2024 09:39:47 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77440

started scan of OMC alignment started with no squeezing: April 26th 2024 16:36:47 ended at 17:30 UTC

H1 General - H1 Out of Observing for Commissioning

ryan.short@ligo.org — Fri, 26 Apr 2024 09:06:56 -0700

Author: ryan.short@ligo.org

Report ID: 77439

H1 dropped observing at 16:01 UTC for a planned three hours of commissioning. Activities will at least include OMC alignment scans and more PEM tests.

H1 PSL - PSL Status Report - Weekly

ryan.short@ligo.org — Fri, 26 Apr 2024 08:53:30 -0700

Author: ryan.short@ligo.org

Report ID: 77438

FAMIS 26241

Laser Status:
    NPRO output power is 1.82W (nominal ~2W)
    AMP1 output power is 67.0W (nominal ~70W)
    AMP2 output power is 138.8W (nominal 135-140W)
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 23 days, 21 hr 48 minutes
    Reflected power = 17.88W
    Transmitted power = 108.6W
    PowerSum = 126.5W

FSS:
It has been locked for 1 days 3 hr and 40 min
TPD[V] = 0.8223V

ISS:
The diffracted power is around 2.2%
Last saturation event was 1 days 3 hours and 51 minutes ago

Possible Issues: None reported

H1 SQZ - Comment to ZM4, ZM5 PSAMs changed on their own at ~3am last night.

jeffrey.kissel@ligo.org — Fri, 26 Apr 2024 08:23:54 -0700

Author: jeffrey.kissel@ligo.org

Report ID: 77437

This starts FRS Ticket 31062.

LHO General - Ops Day Shift Start

ryan.short@ligo.org — Fri, 26 Apr 2024 08:04:34 -0700

Author: ryan.short@ligo.org

Report ID: 77436

TITLE: 04/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 11mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.20 μm/s
QUICK SUMMARY: H1 has been locked for 26 hours and observing through the night. Planning for commissioning time from 09:00 to 12:00 PDT this morning.

Microseism has been trending upwards
All other systems nominal

H1 General - Thurs Eve Shift End

anthony.sanchez@ligo.org — Fri, 26 Apr 2024 00:06:21 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77435

TITLE: 04/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
Quite night up until we had SuperEvent S240426s Candidate at 3:15 UTC
4:57 UTC Dropped out of Observing due to the Squeezer getting unlocked. Ground motion was low but the wind is slightly elevated.

LOG:
No log

H1 SEI - Hepi Pump Trends - Monthly

anthony.sanchez@ligo.org — Thu, 25 Apr 2024 23:48:01 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77434

FAMIS 26465

Hepi pump Trends for the past month

Images attached to this report

H1 General - Thurs Mid Eve Shift update

anthony.sanchez@ligo.org — Thu, 25 Apr 2024 22:05:19 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77433

TITLE: 04/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 23mph Gusts, 20mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.15 μm/s
QUICK SUMMARY:

Quite night up until we had SuperEvent S240426s Candidate at 3:15 UTC
4:57 UTC Dropped out of Observing due to the Squeezer getting unlocked. Ground motion was low but the wind has been slightly elevated.
5:00 UTC Back into Observing after the SQZ subsystem relocked it's self.

SQZ

H1 SUS - Trended IM1-4 (HAUX) inmons to look for any drifts - looks fine

rahul.kumar@ligo.org — Thu, 25 Apr 2024 21:49:06 -0700

Author: rahul.kumar@ligo.org

Report ID: 77432

Betsy, TJ, Rahul

This afternoon I trended the inmons of IM1-4 to look for any signs of suspension drifting after they (IM1-2) were moved (and then reverted to nominal) this Tuesday (LHO alog 77347). Attached below is the ndscope plot for the last 2 weeks and they look fine to me (IM1 LR and UL bosems showed movement but that was 12 days ago - possibly slider changes - see J Kissel's alog 77211).

I also took their osem spectra and they look fine.

SUS

Images attached to this report

H1 ISC - Comment to LSC FF Meassuremnts taken with ITMY L2 L2L DRIVEALIGN LP filter off.

camilla.compton@ligo.org — Thu, 25 Apr 2024 17:28:34 -0700

Author: camilla.compton@ligo.org

Report ID: 77431

Struggling to fit these.

I have a MICHFF (pasted below) that's a factor of 10 worse than usual (plot attached). We may need to try to put this in and measure iterativly next week.

zpk([-6.816742648521258+i*81.77990170298034;-6.816742648521258-i*81.77990170298034;-77.88634028587184+i*89.33349468557826;-77.88634028587184-i*89.33349468557826;-718.113182677264+i*694.9426298748548;-718.113182677264-i*694.9426298748548;900.2096672125509+i*1208.040185682559;900.2096672125509-i*1208.040185682559;44.6571105273674;-170.8240187509259;-448.0004789051675;-596.150964242976],[-7.116688087177324+i*81.29900739837851;-7.116688087177324-i*81.29900739837851;-310.9419719288208+i*548.6326527169308;-310.9419719288208-i*548.6326527169308;-27.13254150394529;-30.48270823801881;-135.6924431195733;-151.8787517615438;-191.3877206479833;-2313.589507955138;-2602.376933025248;-2783.911401801387],-3.94153891134724)

Somethings wrong with the SRCL data I exported (even after re-exporting), plot attached. Data prepared using NotItter_LSC_FF_PrepareData.ipynb

Images attached to this report

H1 ISC - Summary of alogs related to changes in our output arm this week

sheila.dwyer@ligo.org — Thu, 25 Apr 2024 16:27:04 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77427

In the observing stretch that started Monday around 8 pm, there was a drop in optical gain (by 4%), and power at AS port PDs (4% drop in AS_A sum, AS_B sum, AS_C sum, and OMC REFL). There not at that time any change in circulating power in the arms, PRG, coupled cavity pole, or alignment of suspensions (shown are SR2, SRM, OM1+2, but we have also looked at many other suspension, ISI and HEPI related channels for this time 77382 ). This time is shown by the first vertical cursor in the attachment.

We were unable to relock the interferometer after that Monday evening lock (a new lockloss type appeared early Tuesday morning, 77359), and after the maintence window we were uable to lock with difficulties powering up (77363) and an AS camera imagine that had lobes whenever the beam was well centered on AS_C. We locked that evening by adding large offsets to AS_C's set point, (77368). This is the cause of the large alignment shifts seen in the screenshot on Tuesday evening to Wed morning, which allowed us to lock the IFO but created a large scatter shelf and resulted in a lower coupled cavity pole, and lower optical gain, and we did not have much squeezing that night.

We do not think that Tuesday maintence activities are the cause of our problems, although some of the Tuesday work has been reverted (77350 77369).

Yesterday we spent much of the day with SRY locked, single bounce or using the squeezer beam reflected off SRM to investigate our AS port alignment. 77392, We are able to recover the same throughput of a single bounce beam to HAM6 by moving the alignment of SR2 + SR3 by a huge amount 77388, which also produced a round looking beam on the AS camera. We haven't since tried to explore this aperture, to see if we could have also recovered this thoughput with a pitch move, for example. We also saw that the squeezer beam does not arrive in HAM6 with a good transmission when injected with the alignment used previously, but that we could recover good transmission to HAM6 by moving ZM5 by 150-200 urad, in pitch or yaw. With this shift in SRC axis, and squeezer alignment we were able to relock and not have the large scattering issues we had Tuesday night.

Today's time was spent recovering from a seemingly unrelated problem in the SQZ racks, and some commissoning aimed at recovering our previous (165Mpc) sensitivity with this new alignment. This will continue during tomorow's commissoning time.

additional related information:

(no SQZ, HWS, OFI voltmons) 77374
Move of SQZ beam in lock to get squeezing: 77400
OFI transfer functions: 77391
other suspension health checks: 77383
dark offset script: 77362
SRM and SR2 beam positions after the shift: 77443
Further look at powers on HAM6 PDs: 77441
AS port fringe wrapping worse than Summer 2023: 77452

Images attached to this report

H1 General - Thurs Eve Shift Start

anthony.sanchez@ligo.org — Thu, 25 Apr 2024 16:15:35 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77430

TITLE: 04/25 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: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 23mph Gusts, 15mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:
H1 has been locked for 10 hours, and now Observing.
Were are expecting to stay locked through out the night.

LHO General - Ops Day Shift End

thomas.shaffer@ligo.org — Thu, 25 Apr 2024 16:09:53 -0700

Author: thomas.shaffer@ligo.org

Report ID: 77409

TITLE: 04/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Commissioning most of the day to understand our squeezer and IFO issues from the last few days. We are basically back into the same place we were last night. Tomorrow there will be some more commissioning time to help tune us to this new IFO alignment.
LOG:

1600 Out of observing for planned commissioning
2105 Observing
2203-2209 Out of Observing from SQZ SDF diffs

H1 AOS - SQZ fiber demod RF max increased

sheila.dwyer@ligo.org — Thu, 25 Apr 2024 15:16:49 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77426

After replacement of the SQZ FSS beatnote chassis this morning, there is a little more RF power on the demod. There is an error message in the beckhoff logic for the TTFSS that was intended to identify times when the noise eater is oscillating. If the demod RF goes above RFMax the screen shows an error message that flashes extremely quickly (red circle on screenshot attached), the state machine will go back to Acquire, and the FSS servo board common gain will toggle between 17 and 20 dB, which is what causes the SDF to knock us out of observe.

We've increased RFmax for the demod so this shouldn't happen.

Images attached to this report

H1 SQZ - Comment to SQZT0 - Laser Locking Fiber Beat Note Chassis Replaced

camilla.compton@ligo.org — Thu, 25 Apr 2024 14:55:49 -0700

Author: camilla.compton@ligo.org

Report ID: 77425

We created FRS 31061, this maybe also related to H1-SQZ-R1 issues in 77424.

H1 SQZ - Comment to ZM4, ZM5 PSAMs changed on their own at ~3am last night.

camilla.compton@ligo.org — Thu, 25 Apr 2024 14:46:06 -0700

Author: camilla.compton@ligo.org

Report ID: 77424

After suggestion from Richard, it seems like lots of things in H1-SQZ-R1 saw a glitch at 9:58UTC (2:58amPT), plot attached. This may have been caused by or related to the SQZT0 - Laser Locking Fiber Beat Note Chassis power regulator board failure: 77418, 77403.

As the PSAMS have hysterisis, when ZM5 turned back from 0V to it's noimnal, the strain volatge readback chanegd from -0.6V to -1.5. We reverted it back to -0.6V.

ZM2 PSAMS changed less than 1%.

Images attached to this report

H1 General - The 04/20/24 Richland earthquake as seen by the HRTS

ryan.crouch@ligo.org — Thu, 25 Apr 2024 14:31:54 -0700

Author: ryan.crouch@ligo.org

Report ID: 77422

Rahul and I trended back the current HRTS build that we're testing this weeks' BOSEM channels (in the triples lab in the staging building) to see if it saw the in-town 2.8 earthquake from saturday. Sure enough it did as this suspension is very sensitive.

SUS

Images attached to this report

H1 General - Observing 2105 UTC

thomas.shaffer@ligo.org — Thu, 25 Apr 2024 14:26:42 -0700

Author: thomas.shaffer@ligo.org

Report ID: 77423

We took a little bit extra bit of time to tune our squeezing and take a few more measurements to understand our recent IFO woes, but we are now back to an observing state at 145Mpc.

H1 ISC - Cleaning is doing okay right now

jenne.driggers@ligo.org — Thu, 25 Apr 2024 14:22:51 -0700

Author: jenne.driggers@ligo.org

Report ID: 77421

Now that we've got some updated alignment and other configuration changes to the IFO this week, I wanted to check in on the jitter cleaning. It looks like it's still working fine.

So, the fact that our GDS-CALIB_STRAIN_CLEAN range is about the same as our CAL-DELTAL_EXT range (instead of the CLEAN looking higher than CAL-DELTAL range) is likely more due to the time dependent calibration factors, and not due to problems with cleaning. Tuesday night, the jitter 'cleaning' was adding noise, when we were clipping a beam somewhere. However now that we're no longer clipping, the input jitter coupling is back to about how it was.

The first attachment shows the working cleaning in spectral form, and the second attachment shows it in the range channel time series with colors roughly matching.

Images attached to this report

H1 ISC - LSC FF Meassuremnts taken with ITMY L2 L2L DRIVEALIGN LP filter off.

camilla.compton@ligo.org — Thu, 25 Apr 2024 14:19:14 -0700

Author: camilla.compton@ligo.org

Report ID: 77420

In 77236, Gabriele found the ETMY L2 DRIVEALIGN L2L filter bank has a "L2L3LP" engaged that might be making it harder for us to fit the LSC FF. Today we re-measured the LSC FF, not interatively, with both FF's off and the "L2L3LP" filter off.

Nothing changed but we hope to refit the feedforward and implement them later. When installed, we would need to turn "L2L3LP" filter off after the ISC_LOCK states have been transitioned back to ETMX (77240).

ISC_LOCK to NLN_CAL_MEAS
Turned off both MICH and SRCL FF.
Measured MICH_excitation.xml and SRCL_excitation.xml (used half the nominal exc amplitudes as the FF's were off, saved with full exc amp)
Turned off ETMY L2_L2L_DRIVEALIGN L2L3LP filter, see 77236
Set up for FF injections, see readme. (turn off F filter and input, but turn on filter to allow excitation though)
Measure NoLP_MICHFF_excitation_ETMYpum.xml and NoLP_SRCLFF_excitation_ETMYpum.xml (have adjusted exc shape for L2L3LP being off, used half nominal amplitude)
Undo set-up for FF injections, see readme. Keep FF's off as L2L3LP filter's still off.
Turn on L2 L2L3LP filter
Turn on both MICH and SRCL FF.
ISC_LOCK to NLN

All code saved to /opt/rtcds/userapps/release/lsc/h1/scripts/feedforward/

H1 ISC - Phasing POP45

sheila.dwyer@ligo.org — Thu, 25 Apr 2024 13:41:56 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77416

We'd like to retune LSC feedforward after yesterday's big alignment shift, but before doing that we want to phase POP45 and retune the LSC input matrix element that cancels PRCL in the SRCL signal.

Injecting a PRCL signal and trying to minimize the signal in POP 45 Q suggests that we need to change our phase from 8 degrees to 12 (similar to last week's conclusion that we needed to move to 11 deg). The decoupling of PRCL from Q is not as effective as it was last Friday The second attachment shows that I checked the OLGs of MICH and SRCL before and after, and as expected they don't change much.\

After this phasing, the transfer function from POP45I/ POP 9I measured with a PRCL excitation is -0.03192. This means that POP 9I to SRCL input matrix element should be 0.1185 = (-3.712*-0.003192) The third screenshot shows the PRCL to SRCL transfer function before this change in blue, and after in red, so this reduced the PRCL signal in the SRCL error signal by more than a factor of 10.

After this I looked at some coherences during no SQZ time, we do still have LSC coherence at a similar level as last night, but not worse than in Jennie W's plot from last night. Camilla is now running measurements that can be used to fit LSC feedforward. We will leave these settings in place for tonight since it's not making things worse, and hopefully try new feedforward filters in the morning. I've added the new POP9I to SRCl elemement in lscparams, and accepted the phase change in OBSERVE.snap and safe.snap

Images attached to this report

H1 SQZ - ZM4, ZM5 PSAMs changed on their own at ~3am last night.

camilla.compton@ligo.org — Thu, 25 Apr 2024 13:03:37 -0700

Author: camilla.compton@ligo.org

Report ID: 77417

Naoki and I left PSAMs at 8.8/-0.67 in 77268, and yesterday afternoon 77389 we changed them in a test that we reverted. But last night a 3am, the offsets didn't change but the PSAMs strain readbacks changed. The PSAMs actually changed as this can be seen in the alignment readback sensors. Plot attached

Did some strange electronics issue happen with SQZ last night that also impacted the TTFSS: 77418

Images attached to this report

H1 SQZ - Comment to OPS OWL report

camilla.compton@ligo.org — Thu, 25 Apr 2024 13:00:17 -0700

Author: camilla.compton@ligo.org

Report ID: 77419

On SQZT0 Sheila and I found that even with the PSL fiber unplugged and SQZ beam blocked, H1:SQZ-FIBR_PD_DC_POWER reported power.

Fil replaced the D2300329 Fiber Beat Note Box with our spare. This solved our TTFSS issues. It appears something in the power supply for the box had failed. Details in 77418.

H1 SQZ - SQZT0 - Laser Locking Fiber Beat Note Chassis Replaced

filiberto.clara@ligo.org — Thu, 25 Apr 2024 12:59:13 -0700

Author: filiberto.clara@ligo.org

Report ID: 77418

WP 11832

While troubleshooting TTFSS (alog 77403), Sheila and Camilla found issues with the D2300329 Laser Locking Fiber Beat Note Chassis. Unit was replaced with spare. SQZ team reports outputs back to nominal.

Removed unit had power regulator board D100217 failed. Output capacitor C7 was shorting +15V rail to ground. Power regulator board replaced.

Installed Chassis S2300259
Removed Chassis S2300258

CDS

H1 ISC - A2L gains retuned

jennifer.wright@ligo.org — Thu, 25 Apr 2024 12:19:32 -0700

Author: jennifer.wright@ligo.org

Report ID: 77415

Jennie W, Sheila

Now we have our camera servo offsets that we found on the 17th tuned in we ran the A2L script again. The code is

userapps/isc/h1/scripts/run_all_a2l.sh

I saved these values in lscparams.py in userapps/isc/h1/guardian/ and accepted the sdfs in OBSERVE.snap.

Images attached to this report

H1 ISC - Comment to CAM PIT2 and YAW3 offsets not in guardian

jennifer.wright@ligo.org — Thu, 25 Apr 2024 12:11:57 -0700

Author: jennifer.wright@ligo.org

Report ID: 77414

We looked at this again today and realised the camera offsets had been set back to their former values from before our changes to PIT2 and YAW3 on April 17th when the cameras servo guardian went through state 405 (TURN ON CAMERA FIXED OFFSETS). Then we realised we may have forgotten to reload the camer servo guradian when we made these changes so we took reloaded it then took it to DITHER ON state, then to CAMERA SERVO ON and now we have CAM PIT2 OFFSET = -173 and CAM YAW3 OFFSET = -349.5 as is set in lsc_params.

FIXED ISSUE

H1 ISC - Checked coherences with LSC and ASC loops

jennifer.wright@ligo.org — Thu, 25 Apr 2024 10:42:41 -0700

Author: jennifer.wright@ligo.org

Report ID: 77413

Sheila, Jennie W

While Sheila runs a Bruco I checked the coherence from LSC - SRCL, PRCL, MICH, and ASC-MICH, DHARD and CHARD to DARM.

The first image is from our lock last night, the second is the same set of measurements from Monday night when we had a range of 156 MPc (left cursor).

Comparing the two it looks like PRCL coherence is slightly worse since Monday, CHARD looks about the same, DHARD is slightly worse in pitch but better in yaw, ASC-MICH is about the same, PRCL is a bit worse, SRCL is about the same and LSC-MICH is a bit worse.

ISC

Images attached to this report

H1 SQZ - Comment to OPS OWL report

camilla.compton@ligo.org — Thu, 25 Apr 2024 10:31:43 -0700

Author: camilla.compton@ligo.org

Report ID: 77411

Vicky, Sheila, Camilla. Went SQZ_MANAGER to DOWN which cleared any wrong sdfs that had been reverted. The H1:SQZ-FIBR_SERVO_DEMOD_RFMON should not be this low (-40dB), even in old TTFSS issues (75337). We tried touching everything on the TFFSS screen to no avail. We tried changing polarization into "to beatnote" fiber. Turning down this power dropped the H1:SQZ-FIBR_PD_DC_POWER form 0.4 to 0.3. Rather than halving it. Going out to check powers on SQZT0.

LHO VE - Thu CP1 Fill

david.barker@ligo.org — Thu, 25 Apr 2024 10:30:39 -0700

Author: david.barker@ligo.org

Report ID: 77412

Thu Apr 25 10:10:20 2024 INFO: Fill completed in 10min 16secs

Jordan confirmed a good fill curbside.

Images attached to this report

H1 General - out of Observing at 1600UTC for planned commissioning

thomas.shaffer@ligo.org — Thu, 25 Apr 2024 09:01:34 -0700

Author: thomas.shaffer@ligo.org

Report ID: 77410

We've gone out of Observing at 1600UTC to start the 3 hour planned commissioning time in coordination with LLO and Virgo.

H1 General - Comment to Wed Eve Shift End

thomas.shaffer@ligo.org — Thu, 25 Apr 2024 08:17:54 -0700

Author: thomas.shaffer@ligo.org

Report ID: 77408

The link in Tony's log is the old link. Please use the link found on the operator wiki.

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Thu, 25 Apr 2024 08:04:00 -0700

Author: thomas.shaffer@ligo.org

Report ID: 77407

TITLE: 04/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 132Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: Locked and Observing for 2 hours. Looks like Ryan C had some SQZ issues overnight. I imagine that we will be doing more investigations into the alignment shift today.

H1 SQZ - Comment to OPS OWL report

sheila.dwyer@ligo.org — Thu, 25 Apr 2024 06:49:23 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77406

The usual trick of manually moving the crystal frequency to find the beatnote (suggested by the error message Ryan reports above) doesn't work in this case. The attached screenshot shows that at about 3 am the power on the FSS PD nearly doubled, but the fiber power, polarization, and power out of the squeezer laser didn't change. We lost the beatnote at that time (BEATnote strength drops to -40dBm. Moving the laser frequency around doesn't change this.

Note that I thought I could move the laser frequency while we were in observing without squeezing, because the crystal frequency is not monitored in SDF. However changing this changes other things which are monitored, and did temporarily knock us out observing. Some automation brought us back to observing quickly enought that I didn't notice the first time and so did this twice.

Images attached to this report

H1 SQZ - Comment to OPS OWL report

ryan.crouch@ligo.org — Thu, 25 Apr 2024 04:11:50 -0700

Author: ryan.crouch@ligo.org

Report ID: 77405

Back into observing with NO_SQUEEZING at 11:09 UTC, I followed the WIKI. I forgot that I also had to edit the IFO node to add to the exclude list to get us back into observing ( we should add this to said WIKI page). I reverted the attached SDF diffs

Images attached to this report

H1 SQZ - Comment to OPS OWL report

ryan.crouch@ligo.org — Thu, 25 Apr 2024 03:36:19 -0700

Author: ryan.crouch@ligo.org

Report ID: 77404

I got ahold of Jenne, who suggested following alog 70050 which I did not notice that DIAG_MAIN was also complaining about. Doing this which is reseting the ISS did not help this TTFSS issue. Also at Jennes suggestion I'm going to try and get us into observing without SQZing

H1 SQZ - OPS OWL report

ryan.crouch@ligo.org — Thu, 25 Apr 2024 03:11:55 -0700

Author: ryan.crouch@ligo.org

Report ID: 77403

H1 called for assistance as the SQZer lost lock and has been struggling to relock, its been stuck waiting for the TTFSS to lock, it says "Check crystal frequency, can try 45MHz" which is a notification I haven't seen before and I can't find any reference in the WIKI. I'm calling out for SQZ help

SQZ

H1 General - Wed Eve Shift End

anthony.sanchez@ligo.org — Thu, 25 Apr 2024 00:07:53 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77402

TITLE: 04/25 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: Ryan C
SHIFT SUMMARY:
LOG:

Rode out a 5.5 Mag Earthquake from New Zealand.
Violins look great!
H1 Is still locked and Observing.

I put in the Lock Aqusition survey in here https://docs.google.com/forms/d/e/1FAIpQLSf_RhE5fjtL9cNhyY6dXtBunM4tonBBwgikZwr1Hg0CBkGn2A/viewform because I could not find the link to the new Lock Aqusition Survey.

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
16:53	SQZ	Terry, Kar Meng	OptLab	local	SHG lab work	19:31
19:31	PEM	Robert	CER	n	In and out to hunt for noise sources	23:16
20:31	SQZ	Terry, Kar Meng	Opt Lab	local	SHG lab work 2	23:36
23:56	PEM	Robert	LVEA	N	Turning off the Lights in the LVEA	00:56
01:05	PEM	Robert	CER	N	Checking PEM system	01:30
01:07	SUN	Pat	Mid Y	No	Walking to mid Y	01:56
07:06	PCAL	Tony	PCAL Lab	Yes	Putting USB drive back.	07:16

H1 General - Wed Eve Mid Shift Update back to OBSERVING @148Mpc!

anthony.sanchez@ligo.org — Wed, 24 Apr 2024 20:42:58 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77401

TITLE: 04/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 10mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

After manual Initial_Alignment
We tried to get locked but there were issuses getting DRMI 1F and then PRMI.
I then touched the Beam Splitter and SRM a little bit to try and get PRMI locked with no luck.
I then took IFO to Check mitch fringes. Where it struggled some more to get past PRMI.
I then Took the IFO to Initial Alignment.
After Initial_Alignment H1 was able to get past DRMI locking and got to Nominal_Low_Noise.
Nominal_Low_Noise @ 1:31 UTC
SQZrs were touching up SQZ alignment and to get the SQZ system locked. https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=77400
OBserving at 2:32 UTC

H1 SQZ - Re-aligning SQZ to current AS alignment ~4.5dB, required big ZM moves

victoriaa.xu@ligo.org — Wed, 24 Apr 2024 19:53:12 -0700

Author: victoriaa.xu@ligo.org

Report ID: 77400

Tony, Nutsinee, Vicky

We re-aligned SQZ to the current IFO AS port alignment, got from basically no sqz at all, to ~4.5dB at the end.

Screenshot. First I aligned ZM4 P/Y by ~hundreds counts to see a sqz signal again in transmission of OMC, then manually walked a bit with ZM6. Then I engaged AS42 ASC (zm5/6), which helped a bit to bring the alignment closer, but leaving ASC on for too long caused alignment to run away (so I cleared history on it and started over). I ran AS42 briefly a couple times until improvement to RF3 signal stopped, then offloaded, then some manual walks, then again. Could not use SCAN_ALIGNMENT (zm4/6) - it's range is way too big right now that LO loses lock, so we need to back off the scan range. Manually adjusted SQZ angle to maximize yellow 350 Hz / blue 1.7 kHz blrms.

Overall biggest slider moves were in YAW: ZM4_Y +600, ZM6_Y +270, secondarily ZM4_P +70.

OMC_RF3_RFMON went from around -22 (noise floor around -25), to -10 at squeezing (ofc more with antisqz). SQZ went from basically totally misaligned to almost -4.5dB, with this series of manual walks and ASC attempts. On net, probably still broadly reducing noise with sqz vs. adding noise, so we decided to call it and accept SDFs on the ZMs, so Tony could go to observe.

Edit to add: Alignment and sqz angle are probably not that optimized still. Something interesting - when I first aligned and got something, squeezing needed an RF6 demod phase below 100 deg. When aligning more and with ASC help, the sqz angle moved back up to ~177 deg (where it is left now). Before, we had been operating at around 190-200 deg. Can add those trends here tomorrow. I'm a bit surprised how big much the sqz angle changed with alignment. Unsure if it's maybe a clue in tracking down why the sqz angle is drifting so much recently (for example if alignments, either sqz or ifo, are drifting and those drifts can be compensated in part by changing the sqz angle).

Images attached to this report

H1 General - Comment to SDF Diffs for ASC TCS & CS_AUX accepted

anthony.sanchez@ligo.org — Wed, 24 Apr 2024 19:35:41 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77399

PCAL EX OSC sum SDF Change. I Thought this switch has to be on.

Images attached to this report

H1 General - SDF Diffs for ASC TCS & CS_AUX accepted

anthony.sanchez@ligo.org — Wed, 24 Apr 2024 18:50:13 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77398

I have accepted the following SDF Diffs to get into observing.
I am waiting for the SQZs to make some quick changes to get the SQZ alignment optimal for Observing.

TCS

Images attached to this report

H1 ISC - Comment to Aligning then lock attempt coming up

jenne.driggers@ligo.org — Wed, 24 Apr 2024 17:00:34 -0700

Author: jenne.driggers@ligo.org

Report ID: 77397

We've gotten as far as PRMI locked (with arms held off resonance with ALS, as usual), and at some point as soon as PRMI ASC comes on MICH Yaw gets a 2.2 Hz wiggle.

EDIT to add that a thing to try could be to turn off the ASC during PRMI (set lines 737 and 738 of ISC_DRMI.py to False). If we have similar problems in DRMI ASC, also set lines 1026-1031 to False. Save, then reload ISC_DRMI guardian.

EDIT EDIT: I just set line 737 to False. It may be beneficial to tune up the alignment by hand.

EDIT EDIT EDIT: We're still getting wobbles, even though the guardian had turned off the MICH ASC, and I had by-hand turned off the PRC1 ASC.

EDIT EDIT EDIT EDIT : I also set PRC1 to False on line 738 and loaded. I have to go now though, so good luck Tony!

H1 SUS - OFI Transfer functions

ryan.crouch@ligo.org — Wed, 24 Apr 2024 16:30:03 -0700

Author: ryan.crouch@ligo.org

Report ID: 77391

I took some transfer functions of OFI this afternoon, the references from the template were fairly old (2021), I trended the OSEM basis, and output filters gain as well at the suggestion of Jeff for the reference and things have changed. The basis matrix has different values and the gains signs have been flipped, so that may be why the magnitudes are different. The TFs don't show anything obviously wrong.

The templates are located at: /ligo/svncommon/SusSVN/sus/trunk/OFIS/H1/OFI/SAGM1/Data/

Images attached to this report

LHO General - Ops Day Shift End

thomas.shaffer@ligo.org — Wed, 24 Apr 2024 16:28:24 -0700

Author: thomas.shaffer@ligo.org

Report ID: 77396

TITLE: 04/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Since my mid shift report (alog77381), we have been able to move SR3 and SR2 to get to a good alignment (Jenne's alog77388), and check that the squeezer also has alignment issues (alog77389), leading us to think that the OFI or surrounding baffles might be the cause of the issues (alog77392). Tony is now finishing up with an alignment with the large SR3 SR2 moves to see if we can lock like that for the night, then we will continue to understand what has changed with the OFI tomorrow.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
16:47	FAC	Kim	MX	n	Tech clean	17:52
16:53	SQZ	Terry, Kar Meng	OptLab	local	SHG lab work	19:31
16:58	FAC	Bubba	MX	n	Measurements	18:58
19:31	PEM	Robert	CER	n	In and out to hunt for noise sources	23:16
20:31	SQZ	Terry, Kar Meng	Opt Lab	local	SHG lab work 2	00:31

H1 ISC - Aligning then lock attempt coming up

jenne.driggers@ligo.org — Wed, 24 Apr 2024 16:22:41 -0700

Author: jenne.driggers@ligo.org

Report ID: 77395

We've asked Tony to try locking the IFO with SR3 and SR2 in these very different positions. With these optic positions, we don't want the AS_C offsets in place that we used to get locked yesterday. So, I have now accepted in safe.snap for the ASC model that the AS_C offsets are off (but I've left the numerical values).

If we're unable to lock, then the plan is to ask Tony to revert SR2 and SR3 and turn back on those offsets. Since the offset switches are part of SDF revert, to turn them on the plan should be to go Sitemap -> ASC -> Overview -> AS_C (bottom left) -> Turn on the offsets and save the diff in SDF.

First attachment is my saving the safe.snap file with the offsets off. Second attachment is where the offset buttons are.

Images attached to this report

H1 ISC - we suspect that something in OFI has changed

sheila.dwyer@ligo.org — Wed, 24 Apr 2024 16:11:49 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77392

LHO control room crew-

We suspect that something about the output Faraday has changed.

One observation is that the powers in HAM6 dropped 5% in Monday night's lock (see first attachment).
We spent a lot of time in SRY and single bounce, and comparing today's single bounce times to times Jennie Wright found from the last few weeks ago 77204. Jenne Driggers was able to restore the same throughput from input power to HAM6 powers in single bounce by moving SR3 and SR2 by 800 urads in yaw, 77388. We checked many witness sensors for large alignment shifts, it doesn't seem that any suspension shifted enough to explain this.
We then tried to reproduce a SQZ single bounce from 2 weeks ago OMC scans, by reseting all PSAMs and osems on ZM4/5/6 SRM, and OM1/2. This resulted in much lower power on AS_A and AS_B than two weeks ago, indicating that something is also shifting this beam. We were able to restore the power by moving in alignment into the OFI by ~200 urad in yaw or pitch of ZM5.

The only thing that seems common to these two is the OFI, a baffle in it's vicinity or something like a wire from the fast shutter impacting the beam on the way to OM1. We'd actuated the fast shutter and see no change in the AS camera, so we don't think that the fast shutter is the issue, which points us to looking at the OFI.

Editing to add that Keita points out something like a bad spot on OM1 is also a possibility.

Images attached to this report

H1 General - Wed Eve Shift Start

anthony.sanchez@ligo.org — Wed, 24 Apr 2024 16:00:09 -0700

Author: anthony.sanchez@ligo.org

Report ID: 77393

TITLE: 04/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 9mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

IFO Unlocked and down for Maintenance on potentially the OFI which may be wildly misaligned, as implied by the reduced power on the photo diodes down stream from the OFI.

Feels like an all hands on deck sort of issue.
Mr. Crouch is running TF on the OFI and I'll be taking over Initial Alignment while this is happening.

H1 CAL - Changes to pcal force coefficients EPICS variables

francisco.llamas@ligo.org — Wed, 24 Apr 2024 15:48:58 -0700

Author: francisco.llamas@ligo.org

Report ID: 77386

DriptaB, TonyS, RickS, FranciscoL

On Wednesday, April 24, we updated the EPICS variables,

for X-End OLD --> NEW:

H1:CAL-PCALX_FORCE_COEFF_RHO_R                        | 10692.3 --> 10716.6
H1:CAL-PCALX_FORCE_COEFF_RHO_T                        | 8334.52 --> 8305.09
H1:CAL-PCALX_FORCE_COEFF_RX_OPT_EFF_CORR | 0.99460 --> 0.99480
H1:CAL-PCALX_FORCE_COEFF_RX_PD_ADC_BG        | 0.25990 --> 0.71360
H1:CAL-PCALX_FORCE_COEFF_TX_OPT_EFF_CORR | 0.99350 --> 0.99380
H1:CAL-PCALX_FORCE_COEFF_TX_PD_ADC_BG        | 8.81310 --> 9.65710
H1:CAL-PCALX_XY_COMPARE_CORR_FACT                | 0.99880 --> 0.99790

For Y-End OLD --> NEW:

H1:CAL-PCALY_FORCE_COEFF_RHO_R                        | 10652.0 --> 10649.6
H1:CAL-PCALY_FORCE_COEFF_RHO_T                        | 7157.80 --> 71456.2
H1:CAL-PCALY_FORCE_COEFF_RX_OPT_EFF_CORR | 0.93100 --> 0.99340
H1:CAL-PCALY_FORCE_COEFF_RX_PD_ADC_BG        | -8.15000 --> -0.25910
H1:CAL-PCALY_FORCE_COEFF_TX_OPT_EFF_CORR | 0.92000 --> 0.99230
H1:CAL-PCALY_FORCE_COEFF_TX_PD_ADC_BG      | 1.75161 --> 1.82388
H1:CAL-PCALY_XY_COMPARE_CORR_FACT       | 1.00150 --> 1.00130

To reflect the most recent calibration of the receiving pcal power sensor (Rx) at both end stations. Screenshots of the MEDM screens show the new values on the green boxes. Attached .txt file shows the caput command used to change the values.

The total chage of -0.16% for X-End, and -0.02% for Y-End for the combined fiducial displacement factors.

We are planning on regularly updating the Pcal calibrations at a cadence of roughly 3 months since over the course of O4a we saw systematic variations on Rx sensor calibration (ct/W) by as much as +/- 0.3% at both sites. The systematic variations at LHO are shown in the 'RxprimeTrendsLHOXandYO4a_wRxTemp.pdf', the top panel for X-end and the bottom one for Y-end. The scatterplot with error bars represent Rx responsivity (units of ct/W) values from pcal end station measurements normalized to the EPICS variable entered for $\rho_R'$, where $\rho$ is the responsivity and prime denotes corrected for optical efficiency, at the beginning of O4a. Values are denoted on the left-hand side of the y-axis. The large dataset represents temperature measurements of the corresponding VEA, and the values are denoted on the right-hand side of the y-axis. These plots suggest that variations on the calibration of the Rx sensor might be due to outside temperature variations, investigations ongoing.

End station measurements allow us to monitor the change in Rx calibration over time. Every end station measurements produce a report that includes a plot in units of ct/W, along with a calibration of the working standard power sensor (WS) made on the same day. We will continue making end station measurements regularly and depending on how much the Rx calibration changes over time, we may update the Pcal EPICS variables.

CAL

Images attached to this report

Non-image files attached to this report

RxprimeTrendsLHOXandYO4a_wRxTemp.pdf

Pcal_LHO_CAPUTfile_O4brun_2024-04-23.txt

H1 ISC - Checking on SQZ to OMC power, can only get power back with ~200urad offsets

camilla.compton@ligo.org — Wed, 24 Apr 2024 15:48:48 -0700

Author: camilla.compton@ligo.org

Report ID: 77389

Sheila, Camilla, Jennie + CR

After Jenne got AS port power back with large SR2/3 yaw offsets in 77388, Sheila wanted to check we could get our SQZ beam back to the power levels we had during the SQZ to OMC scan in 77213 (~75 counts on AS_A and AS_B NSUMs).

We revered ZMs (alignment and PSAMs), SRM, OM1, OM2 to that scan time: April 16th 19:10UTC. But in the old alignment we can only see ~10 on AS_A AS_B NSUM, plot from Sheila attached. So something has changed in the alignment in the SQZ to OMC path too: SQZ, ZM4,5,6, OFI, SRM, OFI, OM1, OM2.

From this old OMC-SQZ scan alignment, by pitching ZM5 200urad (sliders) we could get back to 75 on NSUM plot (AS_AIR beam too low off camera). OR by yawing ZM5 ~150urad (190urad on sliders/ 130urad on osems) we could get back to 70 on NSUMs plot (AS_AIR camera looks better).

Reverting PSAMs back to nominal.

SQZ

Images attached to this report

H1 SUS - Comment to SUS health checks

ryan.crouch@ligo.org — Wed, 24 Apr 2024 15:20:24 -0700

Author: ryan.crouch@ligo.org

Report ID: 77390

OFI from monday

Images attached to this report

H1 ISC - Can un-clip at AS port with massive SR3 and SR2 moves

jenne.driggers@ligo.org — Wed, 24 Apr 2024 15:17:07 -0700

Author: jenne.driggers@ligo.org

Report ID: 77388

We're still working to understand why we've got problems, but we've at least found *an* alignment of SR3 and SR2 that seems to prevent clipping at the AS port when we're centered on AS_C. To get here, I had to move SR3 and SR2 by very large amounts, much more than they ever drift. In order to more accurately see changes in power levels on the AS WFS, I had the DC centering loops engaged in this single bounce off of ITMY configuration.

In the attached plot, the bottom row is the slider values for SR2 yaw and SR3 yaw (so, in microradians). As a reminder, folks have been checking all day and there is no indication from suspension sliders, OSEMs, or where applicable oplevs, that any of our optics have moved nearly this much, so this should not have been necessary. That said, we've often found that (normally at least) we have lots of leeway clipping-wise when chosing SR3 and SR2 positions. There's no reason a priori that I can think of that would prevent us from locking with these SR2 and SR3 positions, but TJ and Camilla point out that having moved SR3 this much may make it challenging to also have the HWS paths aligned. These moves are basically my moving SR3, then moving SR2 to re-center on AS_C.

The top row of the attached plot is the centering on AS_C. So, we would like to only evaluate the amount of power on AS_A or AS_C (middle row) when the beam is centered on AS_C. It turns out that it's the low-ish part of the power curves that are the values when AS_C is centered.

I have highlighted using a blue line on the AS_A curve (middle row right side) roughly the trend. When we started (at about -42 mins) the power on AS_A when AS_C is centered is at about 1.64 units on this y-axis, and as we move SR3 and SR2 in yaw, I can increase the power on AS_A to about 1.85 units. Jennie found that a time of equivalent single bounce configuration from a week ago, we had 1.87 units on this y-axis. (This y-axis is just AS_A_NSUM * 0.001). I didn't take the time to go to the 'other side', but the trend of power on AS_A seems to show that we're into the plateau region, and at the same time the AS AIR camera looked much more normal and unclipped.

EDIT to note that part of the reason it's helpful to wait to evaluate AS_A power until AS_C was centered, is that that also gave time for the DC centering loops to catch up to my big SR3 moves. I think that the reason AS_A sometimes is higher than the blue marker curve, is that the beam was clipping on AS_A while the DC centering loops were catching up.

Images attached to this report

H1 General - Locking Notes mid shift

thomas.shaffer@ligo.org — Wed, 24 Apr 2024 12:46:48 -0700

Author: thomas.shaffer@ligo.org

Report ID: 77381

Sheila, Jenne, Camilla, Jennie, Jim, Rahul, others

We continue to struggle to understand why our alignment in our output arm is suddenly so bad and cannot get back without massive offsets and noise introductions. Jim and Rahul have each looked at their respective subsystems and given the OK. Somehow our alignment have moved in the last 30 hours and we cannot recover it. Here are some summary bullets from the morning:

Unlocked the IFO trying to step the AS_C offset in Y, happened after only one step of 0.05
Locked SRC then stepped the AS_C offsets back to 0. Still bad alignment though
Decided to revert all sus alignment to 2024-04-19 05:36 UTC and run initial alignment. This didn't magically solve our problems and we are still needing a large offset in AS_C and SR2 to get SRC to lock. AS_A power is still lower than from a few days ago.
Tried moving SR3 and SR2 to help increase our AS_A power. Started around 25% lower than our normal, ended up around 13%.

H1 ISC - CAM PIT2 and YAW3 offsets not in guardian

jennifer.wright@ligo.org — Wed, 24 Apr 2024 11:58:51 -0700

Author: jennifer.wright@ligo.org

Report ID: 77385

Sheila, Jennie W

Sheila noticed our range was really high in the lock at 14:51 UTC on the 17th April.

All camera offsets are the same from the good range time (16:19:53 UTC) on the 17th (left cursor) compared to a lock from last night at 2024/04/24 13:20:30 UTC (right cursor).

The offsets for these currently (second cursor) are not in lsc_params and since we had better build-ups on the 17th (first cursor), we should fix these offsets and see if we can optimise A2L gains again in the next commissioning window after the IFO range is recovered.

The best build-ups were immediately after this good time when we changed the PIT2 and YAW3 but this made the range worse.

Images attached to this report

H1 SUS - SUS health checks

ryan.crouch@ligo.org — Wed, 24 Apr 2024 11:30:19 -0700

Author: ryan.crouch@ligo.org

Report ID: 77383

Ryan C, Rahul

Rahul and I did a bunch of SUS health checks in which we did not see anything out of the ordinary.

1) I ran the rubbing script (/opt/rtcds/userapps/release/sus/h1/scripts/SUS_TopMassOSEMs.py) comparing to a time last week, no issues.

2) We took OFI, OM1-3 spectra. We compared to spectra on monday, the OMs are experiencing some overflows (H1SUSIFOOUT) but we're not sure why, overall it looks fine.

3) QUADs: Binary I/Os, OSEMs, Voltmons. Trending over the past week didn't reveal anything except ITMX_L1_OSEM UL might be very slowly dying.

4) OPLEV sums

SUS

Images attached to this report

H1 ISC - Comment to IFO very unhappy, something likely wrong with alignment, AS_C needs strange offsets

jenne.driggers@ligo.org — Wed, 24 Apr 2024 11:27:22 -0700

Author: jenne.driggers@ligo.org

Report ID: 77384

While SRY was locked (last step in initial alignment), we moved the OFI as much as we could, by putting large offsets in the actuator filter banks. No discernable power level changes are visible. This isn't surprising given how weak the OFI actuators are, but seemed worthy of eliminating a possiblity.

Images attached to this report

H1 ISC - Comment to IFO very unhappy, something likely wrong with alignment, AS_C needs strange offsets

jennifer.wright@ligo.org — Wed, 24 Apr 2024 11:01:48 -0700

Author: jennifer.wright@ligo.org

Report ID: 77382

Jennie W, Sheila

Sheila suggested I use the oplevs for SR3, BS, ITMY, ITMX. ETMY, ETMX to compare our alignment out of lock right before we started locking the main IFO (ie. after locking green arms). I chose two times we were in FIND_IR (state 16 in ISC_LOCK).

One of these times was after a lockloss from a very high range lock from Monday afternoon (~157 Mpc).

GPS reference time in lock = 1397864624 (16:43:26 PDT)

GPS reference time in FIND_IR presumably before our current weird alignment/locking problems = 1397868549 (17:48:51 PDT)

The other time was in our last locking sequence Tuesday morning before maintenance Tuesday started. We did not get to NLN but fell out before this at ENGAGE_ASC_FOR_FULL_IFO (state 430 in ISC_LOCK).

GPS reference time in FIND_IR = 1397918790 (07:46:12 PDT)

The main OPLEVS which changed more than 1 micro-radian were ITMY PIT (down by 1.24 microradians)

ETMY PIT (up by 1.02 microradians)

ETMY YAW (down by 1.14 microradians)

ETMX PIT (up by 2.35 microradians)

ETMX YAW (up by 3.21 microradians)

H1 ISC - Last lock acquisitions last night do NOT see the 9Hz buzzing at state 557 TRANSISITON _FROM_ETMX

camilla.compton@ligo.org — Wed, 24 Apr 2024 10:17:29 -0700

Author: camilla.compton@ligo.org

Report ID: 77380

Two lock acquisitions last night do NOT see the 9Hz buzzing at state 557 TRANSISITON _FROM_ETMX seen in 77359.

Plots at 2024/04/24 04:21UTC and 07:32UTC attached. Also check the two lock acquisitions that we lost before NLN before this.

Images attached to this report

LHO VE - Wed CP1 Fill

david.barker@ligo.org — Wed, 24 Apr 2024 10:13:02 -0700

Author: david.barker@ligo.org

Report ID: 77379

Wed Apr 24 10:09:59 2024 INFO: Fill completed in 9min 56secs

Gerardo confirmed a good fill curbside.

Images attached to this report

LHO General - Comment to Ops Day Shift Start

camilla.compton@ligo.org — Wed, 24 Apr 2024 09:58:27 -0700

Author: camilla.compton@ligo.org

Report ID: 77378

We checked the HWS _PROBE_TOTAL_PIXEL_VALUE and the position of IFO beam on IX and IY HWS, from last good long range power up 2024/04/21 20:55UTC (1397768177) to last nights power up 2024-04-24 07:26UTC (1397978835). No difference in the two times seen. HWS cares about SR3.

Images attached to this report

LHO General - Comment to Ops Day Shift Start

camilla.compton@ligo.org — Wed, 24 Apr 2024 09:23:02 -0700

Author: camilla.compton@ligo.org

Report ID: 77376

TJ took no SQZ time this morning from 15:31:30 to 15:45:00UTC. Plot attached comaping now to no SQZ time from April 12th 77133

Images attached to this report

LHO General - Comment to Ops Day Shift Start

camilla.compton@ligo.org — Wed, 24 Apr 2024 09:04:22 -0700

Author: camilla.compton@ligo.org

Report ID: 77377

TJ and I looked at the OFI (plot) and over the last 5 days, the RT voltmons has changed more than usual. We aren't actively damping the OFI though so are unsure if these VOLTMONs are just reading noise...

Images attached to this report

H1 General - Well Pump Running

bubba.gateley@ligo.org — Wed, 24 Apr 2024 08:25:54 -0700

Author: bubba.gateley@ligo.org

Report ID: 77375

Well pump has been started to replenish the fire water tank. The pump will run for 4 hours.

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Wed, 24 Apr 2024 08:03:00 -0700

Author: thomas.shaffer@ligo.org

Report ID: 77374

TITLE: 04/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 0mph Gusts, 0mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY: Still locked but with a range around 120Mpc. Lots of noise in almost the entire of the spectrum.

H1 ISC - Comment to IFO very unhappy, something likely wrong with alignment, AS_C needs strange offsets

sheila.dwyer@ligo.org — Wed, 24 Apr 2024 06:56:02 -0700

Author: sheila.dwyer@ligo.org

Report ID: 77372

Adding screenshot that summarizes/ supports what Jenne is saying above.

A little over 1 day ago, there was a drop in optical gain. There isn't an indication of a shift in alignment of SR2, or the OMs at that time. AS_C QPD is in loop, so that signal being zero only shows that we weren't using any offsets at the time. The drives on OM1 + OM2 show that their alignment also didn't shift at the time. Since they are used to center the beam on AS_A and AS_B, their drives would need to shift if there is a large shift in the real beam position on AS_C. You can see that for today's lock, where there were large offsets on AS_C, the alignment of SR2 is different, as well as the alignment of OM1 + 2 (indicating that the alignment onto AS_C is different). We might be clipping on the OFI, or elsewhere at the AS port.

Here's an image of the AS camera:

before optical gain dropped: https://lhocds.ligo-wa.caltech.edu/cr_screens/archive/png/2024/04/21/05/nuc30-2.png
after the optical gain dropped but before the offsets: https://lhocds.ligo-wa.caltech.edu/cr_screens/archive/png/2024/04/22/05/nuc30-2.png
tonight with offsets in AS_C: https://lhocds.ligo-wa.caltech.edu/cr_screens/archive/png/2024/04/23/22/nuc30-2.png

you can toggle through these three in different browser tabs to see that the alignment didn't seem to shift until we added offsets. So all indications are that these offsets aren't good, and we should not be using them, except that they appear to have allowed us to lock the IFO.

Editing to add another screenshot: As Ibrahim checked several times last night, the osems indiczte that SR3 + PR3 haven't moved. In early Tuedsday lock where the optical gain first dropped, the power recycling gain was unchanged, with the introduction of offsets last night it seems slightly lower (and the optical gain also took another step down).This attachment shows that the offsets moved OM3+ OMC, which I did not expect (since the AS centering beams fix the beam axis arriving on OM3, I wouldn't have expected the AS_C offsets to have moved these optics). But they didn't move for the TUesday morning low optical gain lock.

Images attached to this report

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Wed, 24 Apr 2024 00:00:30 -0700

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 77373

TITLE: 04/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C - OWL CANCELLED
SHIFT SUMMARY:

IFO is LOCKING and in ENGAGE_DRMI_ASC

Had an hour and 16 minutes of terrible range (125 MPc) observing time following fruitless bad alignment post-maintenance troubleshooting. Details of this troubleshooting are listed in alog 77368 and its comments.
Naoki and Sheila tried improving the squeezing from around 4:25 - 5:25 UTC to no/poor avail.
More work will be done tomorrow to see why H1 is in such a bad alignment.
Jenne okayed keeping the Remote OWL off due to these issues unless "significant progress" was made - I was going to turn it on if we had stayed in observing but given the short observing time, bad range, short lock time and unstable auto-locking post lockloss, I will not be enabling the remote OWL. This is not mentioning the 21 (recorded) locklosses it took to reach this NLN Observing State
IY Violin 6 (The very annoying one that needs 5 to damp with it) has been extremely high throughout this whole 16 hr+ lock acquisition
Find SDF Diff Screenshots Below - there were 8 screens due to new offset settings that Jenne okayed for SDF change acceptance.

5:24 UTC - Reached NLN but waiting as SQZ team (Naoki) tries to better align squeezer

5:40 UTC - Observing

6:39 UTC - Lockloss DRMI

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
00:18	STROLL	Patrick	MY	N	Walkin'	01:26
01:26	PEM	Robert	LVEA	N	Ungrounding SUS Racks	01:56

Images attached to this report

LHO General - OPS Eve Midshift Update

ibrahim.abouelfettouh@ligo.org — Tue, 23 Apr 2024 20:43:50 -0700

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 77371

IFO is in LOCKING_ARMS_GREEN and still locking after maintenance.

There is a LOT of ongoing and past troubleshooting mostly summarized by Jenne in alog 77368. Since this was posted, I looked at the HAM6 Picomotors and determined that there was no suspicious activity (esp in the on/off switching) since locking issues began (approx 15 hrs ago now).

We just got to OMC Whitening but the violins were horrendous. We stayed there for 30 minutes before an unknown lockloss DRMI. Sheila is on TS helping with SQZ alignment/instructions with SQZ alignment.

H1 ISC - Comment to IFO very unhappy, something likely wrong with alignment, AS_C needs strange offsets

jenne.driggers@ligo.org — Tue, 23 Apr 2024 19:32:48 -0700

Author: jenne.driggers@ligo.org

Report ID: 77370

Oh, also, the squezing was not at all good when we locked. I suspect that it's because the squeezer alignment isn't matched to this bad-but-working alignment of the rest of the IFO. Sheila should be able to log on in a little while and can hopefully take a quick look to see if there's anything to do.

H1 ISC - IFO very unhappy, something likely wrong with alignment, AS_C needs strange offsets

jenne.driggers@ligo.org — Tue, 23 Apr 2024 19:30:17 -0700

Author: jenne.driggers@ligo.org

Report ID: 77368

[Jenne, Ibrahim, RyanS, Sheila, Robert, TJ, Elenna, Jennie, Oli, Jim, others]

Something is different with the IFO today, and it's not great. Since we haven't pinpointed what the problem is, we don't really know if it is related to our mediocre range last night and struggles to relock after that, or if it is new from maintenance day. So far, the solution to get back to (almost) NLN has been to put in *massive* offsets in AS_C. This did enable us to get locked (and avoided the ASC ringup that was causing locklosses this afternoon), but it left us with a large scatter shelf in DARM. Robert had the good suggestion that we see if, once locked, we could walk the offsets back to their nominal values of zero; doing this caused an ASC ringup, and it's probably the same thing that we'd been seeing throughout the day. So, indeed going toward the nominal offset of zero for pit and yaw on AS_C is not an okay place right now.

We began to narrow in on AS_C since, during initial alignment, it is in-loop for SR2 and SRY alignments, and it was causing SR2 to be pulled very far in yaw. We were seeing this visually on the AS_AIR camera, which looked really unusually terrible. In the end, Sheila hand-aligned SRY, and then put offsets into AS_C such that the ASC now servos to that point. But, the offsets used are +0.46 in pit and -0.85 in yaw, so really, really big. However, with these in place, we were able to let DRMI ASC run, and it ran fine.

Since that worked (the large AS_C offsets), we let the IFO relock the rest of the way, and it kept on working. Per a suggestion from Elenna from earlier in the afternoon, after we completed REDUCE_RF45 I manual-ed to ADJUST_POWER and increased the power 5W at a time (waiting for ASC to mostly converge between steps) until we were at 60W, then I manual-ed back to LOWNOISE_ASC. After that, I just selected NomLowNoise and guardian finished things. We ended up 'stuck' in OMC_WHITENING, although the violins were coming down with the damping that guardian was doing. It was around here that I tried ramping down the AS_C yaw offset with 10 sec ramp times to see if it would reduce the scatter shelf that we saw in DARM. See first attachment, with the scatter shelf circled. My first step was to -0.80, second step was to -0.70, and we had an ASC ringup and lockloss at this step. I wasn't sure after the first step, but definitely as we were ramping to the second step (before we lost lock) RyanS, Robert, and I all agreed that the scatter shelf was getting worse, not better. But, we lost lock before I could put the offset back.

We still don't understand *why* we need these large offsets in AS_C, just that we do. Since I hadn't yet SDF-ed them, we had 2 locklosses from ENGAGE_DRMI_ASC when the nominal zero-offsets were used in AS_C. I have since saved the AS_C offset values, and the offset switch being on, in both the safe.snap and observe.snap SDF files. The second and third attachments show these.

We've been trying to think through what from maintenance day could possible have had anything to do with this, and the only things we've come up with are the h1asc reboot and the grounding of SUS racks. From Jeff's alog about the h1asc changes, it seems quite clear that those are just additions of monitor points, and that shouldn't have had any effect. While we were unlocked after our one successful attempt, Robert went into the LVEA and un-grounded those two racks that Fil grounded earlier today. Robert is quite sure that he's checked the grounding of them in the past without any consequence to our ability to lock, but just in case we've got them undone for tonight. So far, that does not seem to have changed the fact that we need these crazy offsets in AS_C. Just in case, Robert suggests we consider rebooting h1asc tomorrow to back out other changes that happened today (even though those shouldn't have anything to do with anything).

For right now (as of ~7:20pm), my best plan is to see if we can get to Observing, and should a GW candidate come through, have the detchar and parameter estimation folks exclude all data below ~80 Hz. This is a really very poor solution though, since this huge scatter shelf will be quite detrimental to our data quality and could cause our search pipelines to trigger on this scattering.

Related thought, but not yet thoroughly investigated (at least by me), is whether our problems actually started sometime yesterday or last night, and aren't at all related to maintenance. As partial 'evidence' in this direction, I'll note that kappa_c has been dramatically low for the last two Observing segments last night. We haven't gotten all the way to NLN tonight yet (OMC_WHITENING didn't finish before we lost lock), but kappa_c looks like it might be even lower now than yesterday. The 4th attachment shows kappa_c for last night's locks (screenshot taken before we locked today). So, maybe we've had some clipping or severe degredation of alignment in the last day or so. Jim checked all of the ISIs, and nothing seems suspicious there.

Last thing - since we had run the dark offsets script earlier this afternoon (probably was a red herring) and I saved all of the SDFs in the safe.snap, we will have diffs for Observe.snap. All diffs that have _OFFSET in them should be accepted (and screenshot-ed).

Images attached to this report

H1 AOS - New grounding disconnected

robert.schofield@ligo.org — Tue, 23 Apr 2024 19:05:30 -0700

Author: robert.schofield@ligo.org

Report ID: 77369

Because of the locking problems, I disconnected the grounds that were installed earlier today (77350).

H1 AOS - False alarm S240420aw caused by M 2.8 earthquake about 24 km from site

robert.schofield@ligo.org — Tue, 23 Apr 2024 18:58:37 -0700

Author: robert.schofield@ligo.org

Report ID: 77367

Corey, Robert

Derek reported that S240420aw was likely caused by scattering noise so I looked into the problem. The figure shows that a large seismic pulse (~2 orders of magnitude above background) started something swinging at 1.44 Hz, with a Q of about 300. The scattering shelf's cutoff slowly dropped in frequency over ten minutes, so there were plenty of chirps reaching different frequencies. It is tempting to guess that the source of scattering is a TMS, which have transverse resonances of about 1.4 Hz, but I checked and the Qs of TMS motion were much lower than the Q of 300 of the scatter source. The time of the seismic pulse matches that of the M2.8 earthquake in Richland on Friday night, 24 surface km from the site and 8 km deep. There is quite a bit of light scattered, but at normal ground motion levels I would expect the scattering noise shelf to reach only about 5 Hz, so I don’t think this scattering noise source affects us during normal operation. Andy L. and Beverly B. noticed similar scattering noise back in 2017 ( 37947 ) for a smaller nearby quake.

DetChar

Non-image files attached to this report

CloseQuake.pdf

H1 ISC - Comment to Locklosses at state TRANSISITON _FROM_ETMX

camilla.compton@ligo.org — Tue, 23 Apr 2024 16:42:53 -0700

Author: camilla.compton@ligo.org

Report ID: 77366

Louis, Camilla. Investigations ongoing but the timing of this glitch is suspiciously when the H1:SUS-ETMX_L1_LOCK_L gain and filters are changed, tramp is 1secinds but FM2 and FM6 foton filters have a 3 seconds ramp. There is an INPUT to this filter bank before the gain and filters are turned on. Plot attached.

Images attached to this report

aLIGO LHO Logbook

H1 General - Sat Eve Ops Shift End

H1 SEI - BRS Drift Trends--Monthly

H1 CAL - PCAL EX End Station Measurements & Lab Measurements April 23rd

H1 General - Sat Eve Ops Shift Start

LHO General - Ops Day Shift Summary

H1 General - Comment to Lockloss @ 17:18 UTC

H1 General - Lockloss @ 17:18 UTC

LHO VE - Fri and Sat CP1 Fill

LHO General - Ops Day Shift Start

H1 ISC - Step in Clean range around 5:20 this morning

H1 General - 04/27 OWL Intervention

H1 General - Friday night Eve Shift End

LHO FMCS - Vibration Sensors HVAC Fans Health

H1 General - Lockloss & Fri Mid Eve shift update

X1 SUS - Searching for the perfect position for the secondary prism on the BBSS

H1 General - Friday Eve Shift Start

LHO General - Ops Day Shift Summary

H1 ISC - Comment to Ran Bruco on DARM stretch while we were at 152MPc last night

H1 ISC - OMC fringe wrapping measurement to check OFI health

H1 ISC - Comment to Ran Bruco on DARM stretch while we were at 152MPc last night

H1 ISC - Ran Bruco on DARM stretch while we were at 152MPc last night

H1 General - Comment to Lockloss @ 18:55 UTC

H1 ISC - operator request for sqz angle adjustment once IFO has thermalized

H1 ISC - Comment to Can un-clip at AS port with *massive* SR3 and SR2 moves

H1 ISC - Beam positions on SRM, SR2 after The Move

H1 ISC - attempt to retune SQZ

H1 ISC - Comment to Aligning then lock attempt coming up

H1 General - Lockloss @ 18:55 UTC

H1 ISC - AS single bounce powers April 16th vs 24th

H1 ISC - OMC alignment scan started

H1 General - H1 Out of Observing for Commissioning

H1 PSL - PSL Status Report - Weekly

H1 SQZ - Comment to ZM4, ZM5 PSAMs changed on their own at ~3am last night.

LHO General - Ops Day Shift Start

H1 General - Thurs Eve Shift End

H1 SEI - Hepi Pump Trends - Monthly

H1 General - Thurs Mid Eve Shift update

H1 SUS - Trended IM1-4 (HAUX) inmons to look for any drifts - looks fine

H1 ISC - Comment to LSC FF Meassuremnts taken with ITMY L2 L2L DRIVEALIGN LP filter off.

H1 ISC - Summary of alogs related to changes in our output arm this week

H1 General - Thurs Eve Shift Start

LHO General - Ops Day Shift End

H1 AOS - SQZ fiber demod RF max increased

H1 SQZ - Comment to SQZT0 - Laser Locking Fiber Beat Note Chassis Replaced

H1 SQZ - Comment to ZM4, ZM5 PSAMs changed on their own at ~3am last night.

H1 General - The 04/20/24 Richland earthquake as seen by the HRTS

H1 General - Observing 2105 UTC

H1 ISC - Cleaning is doing okay right now

H1 ISC - LSC FF Meassuremnts taken with ITMY L2 L2L DRIVEALIGN LP filter off.

H1 ISC - Phasing POP45

H1 SQZ - ZM4, ZM5 PSAMs changed on their own at ~3am last night.

H1 SQZ - Comment to OPS OWL report

H1 SQZ - SQZT0 - Laser Locking Fiber Beat Note Chassis Replaced

H1 ISC - A2L gains retuned

H1 ISC - Comment to CAM PIT2 and YAW3 offsets not in guardian

H1 ISC - Checked coherences with LSC and ASC loops

H1 SQZ - Comment to OPS OWL report

LHO VE - Thu CP1 Fill

H1 General - out of Observing at 1600UTC for planned commissioning

H1 General - Comment to Wed Eve Shift End

LHO General - Ops Day Shift Start

H1 SQZ - Comment to OPS OWL report

H1 SQZ - Comment to OPS OWL report

H1 SQZ - Comment to OPS OWL report

H1 SQZ - OPS OWL report

H1 General - Wed Eve Shift End

H1 General - Wed Eve Mid Shift Update back to OBSERVING @148Mpc!

H1 SQZ - Re-aligning SQZ to current AS alignment ~4.5dB, required big ZM moves

H1 General - Comment to SDF Diffs for ASC TCS & CS_AUX accepted

H1 General - SDF Diffs for ASC TCS & CS_AUX accepted

H1 ISC - Comment to Aligning then lock attempt coming up

H1 SUS - OFI Transfer functions

LHO General - Ops Day Shift End

H1 ISC - Aligning then lock attempt coming up

H1 ISC - we suspect that something in OFI has changed

H1 General - Wed Eve Shift Start

H1 CAL - Changes to pcal force coefficients EPICS variables

H1 ISC - Checking on SQZ to OMC power, can only get power back with ~200urad offsets

H1 SUS - Comment to SUS health checks

H1 ISC - Comment to Can un-clip at AS port with massive SR3 and SR2 moves

H1 ISC - Can un-clip at AS port with massive SR3 and SR2 moves