Ops Day Shift Start

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

Detector relocking and at LOWNOISE_ASC.

Lockloss at 13:11UTC

https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi/event/1396789891

The LL webpage hasnt been loading for me today so I haven't looked very closely at these 2 locklosses from this morning

OPS OWL shift report

H1 called for assistance at 14:15UTC in INITIAL_ALIGNMENT as SRY align was stuck again so I did the same as before to get out of IA. Back in regular locking now

Lockloss at 07:21 utc

https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1396768899

OPS OWL shift report

H1 called for assistance at 08:20 UTC in INITIAL_ALIGNMENT as SRY align was stuck, "Find By Hand" message in the log for ALIGN_IFO. After touching it up by hand with SRM to get AS_AIR looking the best, I left IA and went back to locking. My nomachine session on OPSlogin0 was being very laggy and kept freezing for a few seconds at a time.

Relock #1:

Couldnt get DRMI, went to PRMI, then was able to get DRMI

Reaquired NLN at 09:24UTC and back into Observing at 09:27UTC

Ops Eve Shift Summary

TITLE: 04/10 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Some time lost observing due to locklosses at higher locking states, otherwise an uneventful evening.

• 23:08 - Started observing
• 23:28 - Dropped observing for 3 seconds to load ISC_LOCK
• 00:40 - Lockloss; no obvious cause
• 01:50 - Lockloss from LOWNOISE_LENGTH_CONTROL
• 02:03 - Starting initial alignment after multiple failed DRMI lock attempts
• 02:26 - Initial alignment finished (skipped SRC align steps after getting good spot via camera during ACQUIRE_SRY; see alog77064)
• 03:13 - Lockloss from TRANSITION_FROM_ETMX
• 04:01 - Reached NLN; nothing changed from previous attempt
• 04:03 - Started observing

H1 has now been locked at NLN for 3 hours.

LOG:

No log for this shift.

Ops Eve Mid Shift Report

Following a lockloss at 00:40 UTC with an unkown cause, H1 has now had two unsuccessful lock attempts, both losing lock during or soon after TRANSITION_FROM_ETMX with ETMY and ITMX saturations. Higher winds may be contributing to the issues; gusts have been up to 30mph. I'll continue to monitor this lock attempt.

Alternate PSAMs settings lead to flatter FDS and FDAS spectra

Naoki, Camilla, Eric, Vicky

While looking through some old FDS/FDAS data, we noticed that the spectra taken on March 17 2024 seemed to have the flattest antisqueezing spectra seen during ER16 (to be discussed in upcoming log post).  The PSAMS were adjusted between March 17 and March 20th, and since that date we have seen sizeable frequency dependence in our antisqueezing spectra.  Several other changes were made around this time as well, so the story isn't completely clear, but the PSAMS seem a likely suspect. 

The PSAM strain gauge values from March 17 (7.5,0.5) were not covered during our recent scans.  Shortly before the observing run this afternoon, we moved our PSAMS to (7.5,0.5), realigned, and took quick FDS and FDAS datasets.  Indeed we see that the spectra appear to have less frequency dependence.  More thorough analysis with classical noise subtraction and careful normalization/calibration will be performed in the coming days to quantify the change.  For now, we have reverted back to the old PSAM values (8.8,-0.7) for the observing period. 

It seems that our overall level of antisqueezing is a bit lower than in previous days, but there are other likely causes for this besides the PSAM settings.  We will come back to this PSAM setting later on and try to optimize further to see if we can match or exceed our best ever spectra. 

Datasets:

• 9/4/2024 22:33:00-22:38:00 UTC:  FDAS at (7.5,0.5)
• 9/4/2024 22:44:00-22:49:00 UTC:  FDS at (7.5,0.5)

running A2L decoupling script

Jennie W, Sheila D

We decided to try Gabriele's angle to legnth decouplig script, which was in regular use before we started to use ADS (44532).  This is needed again because we found that the camera servos were not keeping the A2L couplings small, and because we are changing the camera offsets to be different from the set points found by ADS. 

To get the script working we:

• changed the channel names for A2L to A2L_SPOT because of changes in the drivealign matrix that have been made since we were last regularly using this script.
• The notches for the 30 Hz excitation were previously in the HARD ASC filter banks, they have been overwritten since.  We added 30Hz elliptic band stops in the SUS L3 ISCINF filter banks for all four quads, and added turning these notches off to the "clean exit" function.
• We reduced the amplitude from 300 to 30, after testing the injections using awggui.

The script is at  userapps/isc/h1/scripts

there is a bash script that runs this and sets the A2L gains for all 4 test masses, called run_all_a2l.sh  This calls the my_a2l.py script for each optic for pitch and yaw.

The screenshot here shows that last night the yaw noise coupling to DARM was bad, as expected because Jennie moved the camera servo setpoint to improve build ups 77033.  Running this script now (early in the lock, while waiting for violin modes in OMC_whitening) seems to have fixed the low frequency noise for now.  We probably want to rerun this script with a more thermalized IFO. 

After running this script (several times), we've set the A2L gains for 'FINAL' in lscparams:

'FINAL':{
            'P2L':{'ITMX':-0.9709, #+1.0,
                   'ITMY':-0.3830, #+1.0,
                   'ETMX':4.1183,
                   'ETMY':4.6013}, #+1.0},
            'Y2L':{'ITMX':2.7837, #+1.0,
                   'ITMY':-2.3962, #+1.0,
                   'ETMX':4.9315,
                   'ETMY':3.0610 },#+1.0},# Centered on the optic #removed offsets from EY IX IY 220705 gm jd ec
                    }#spots that are the center of the optic
            }#close a2l gains dict

And accepted these values in OBSERVE.snap.

The second attached screenshot here shows HARD loop coherence with DARM after running this script, there is still CHARD Y coherence below 20Hz, but this is much better than last night.

We spent a few minutes in NLN_CAL_MEAS with nominal sqz settings starting at 22:44:31- 22:55 UTC  (1396737889)

CBC hardware injections for NonSENS cleaning review

Just before we went into Observing, I (finally) ran the cbc hardware injections that are necessary for the final NonSENS review sign-off.  LLO ran these injections during O4a (LLO alog 69132), but I ran out of time before the commissioning break.  While the IFO is improved since the end of O4a, the cleaning parameters that are in place during the time of that test are all the same as were present for the last several months of O4a. In particular, both jitter cleaning and laser noise cleaning were turned on during this test (even though later I turned off laser noise cleaning for O4b, see alog 77069).

injection start GPS: 1396738718.28

Below is the output of the terminal during this test, which ran for about 93 seconds.

---

jenne.driggers@cdsws31:~$ hwinj --run cbc clean-test-short
ifo: H1
waveform root: /ligo/groups/cal/H1/hwinj
config file: /ligo/groups/cal/H1/hwinj/hwinj.yaml
GraceDB url: https://gracedb.ligo.org/api/
GraceDB group: Detchar
GraceDB pipeline: HardwareInjection
excitation channel: H1:CAL-INJ_TRANSIENT_EXC
injection group: cbc
injection name: clean-test-short
reading waveform file...
injection waveform file: /ligo/groups/cal/H1/hwinj/cbc/O4_CLEANING_MULTI_CBCHWINJ_20s_H1.txt
injection waveform sample rate: 16384
injection waveform length: 93.0 seconds
injection start GPS: 1396738718.28
H1:CAL-INJ_TINJ_TYPE => 1
H1:CAL-INJ_TINJ_TYPE => 1
H1:CAL-INJ_TRANSIENT_SW2 => 1024
H1:CAL-INJ_TRANSIENT_SW2 => 1024
H1::CAL-INJ_TRANSIENT => ON: OUTPUT
H1::CAL-INJ_TRANSIENT => ON: OUTPUT
=== EXECUTING AWG INJECTION ===
this will wait until the injection is nearly complete...
ndshosts: h1daqnds1 and h1daqnds0
getting host by name: h1daqnds1
found host
testpoint_client 1.0.0
found version 4 or newer test point interface
H1:CAL-INJ_TRANSIENT_SW2 => 1024
H1:CAL-INJ_TRANSIENT_SW2 => 1024
H1::CAL-INJ_TRANSIENT => OFF: OUTPUT
H1::CAL-INJ_TRANSIENT => OFF: OUTPUT
H1:CAL-INJ_TINJ_TYPE => 0
H1:CAL-INJ_TINJ_TYPE => 0
=== INJECTION COMPLETE ===
jenne.driggers@cdsws31:~$ 

NonSENS cleaning of high frequency laser noise OFF during Observing

I have turned off the laser noise NonSENS cleaning in Observing.  The last week or so it's been adding noise, rather than subtracting noise.  I haven't yet found (although I also haven't really tried very much) a set of cleaning parameters that make the high frequency noise better than no cleaning at all, so I've just turned off the laser noise cleaning.

This means that in Observing, we now only have jitter noise being cleaned out. 

To disable the laser noise cleaning, I modified the NOISE_CLEAN guardian to not turn on the laser noise cleaning, and committed it to the svn.  I also accepted the SDF diff, see attached.

DARM2 tramp SDF diff

Found a LSC-DARM2_TRAMP sdf diff that was changed from 10s to 3s on March 7, then back to 10 today. I haven't found any alogs stating why it went either direction and it doesn't seem to be in guardian. I've accepted it as 10s since that's what it ran as for O4a.

Ops Day Shift End

TITLE: 04/09 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Relatively quiet maintenance day, and recovery was fairly straight forward except for bad SRY sensor alignment (alog77064). We have wrapped up commissioning and are back to observing.
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
15:04	ISC	Jeff	LVEA	n	OMC DCPD meas at rack	16:56
15:04	FAC	Karen, Kim	FCES	n	Tech clean	15:48
15:04	-	Mitchell	EX, EY	n	FAMIS checks	16:13
15:09	PSL	Jason	CR	n	Adjust pump diode current temp	15:55
15:12	IAS	Tyler, Jason, Ryan C	LVEA	n	Faro, RyanC in @ 16:15	18:36
15:12	VAC	Jordan	MY, EY	n	Turbo test	18:02
15:35	SQZ	Daniel	LVEA	n	SQZ rack meas	15:51
15:39	FAC	Eric	EX	n	Check on sensor	16:37
15:40	FAC	Bubba	LVEA	n	Dewpoint sensor	17:24
15:41	CDS	Fil	LVEA	n	PSL/IMC rack meas for SPI	17:28
15:48	FAC	Karen	EX	n	Tech clean	16:33
15:49	FAC	Kim	EY	n	Tech clean	17:21
15:54	VAC	Gerardo	LVEA	n	Check on h0lx computer	16:56
16:03	ISC/SQZ	Daniel	LVEA	n	IMC rack meas	16:19
16:47	SEI	Jim, Mitchell	LVEA	n	SEI rack organization and prep	18:36
16:50	FAC	Eric	MY,EY	n	Check glycol levels in mech room	17:17
16:54	VAC	Janos	FCES	n	Find Ken	18:59
16:59	SQZ	Sheila, Jenny, Eric O	CR	n	OMC scan	19:04
17:22	FAC	Karen, Kim	LVEA	n	Tech clean	18:39
17:23	FAC	Chris	FCES	n	FAMIS checks	18:19
17:29	CDS/ISC	Sheila, Fil	LVEA	local	Adjust refl camera, check connections	18:29
17:47	FAC	Ken	FCES	n	Electrical work	19:12
18:00	FAC	Chris	EX, EY	n	Looking for N2 tanks	18:56
18:01	SUS	Camilla	CR	n	Charge meas debugging	18:20
18:11	PCAL	Rick	PCAL lab	local	PCAL lab work	ongoing
18:36	PSL	Jason	PSL encl	local	Dust monitor reboot, measure fiber	18:54
18:48	-	Camilla	LVEA	n	Sweep	19:08
19:48	FAC	Ken	FCES	n	Cable tray	21:48

Ops Eve Shift Start

TITLE: 04/09 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 18mph Gusts, 12mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY: H1 has been locked for almost 30 minutes, will be entering observing shortly.

• IMTY violin modes are rung up; will monitor damping
• All other systems look good

SRY initial alignment should probably move off of POP A sensor

During initial alignmet this morning, I was unable to get SRY to lock. I could move SRM to maximize AS_A and the AS air camera flashes looked pretty good. To maybe save time, I ended up just moving past this state to see if we could lock without it. Sheila looked later and saw that there was no fringing seen on H1:ASC-POP_A_NSUN_OUT_DQ during the time SRY was trying to lock. It's possible we've fallen off POP A, and Sheila suggests that we move to AS_A or similar.

If we move to a different sensor for this part, we will need new trigger thresholds. I don't think it would be too difficult to come up with some numbers based on past SRY acqusitions, then we can test it out another time since we've relocked at this point.

SPI Pick-off Fiber Length

WP 11805
ECR E2400083

Lengths for possible SPI Pick-off fiber. Part of ECR E2400083.

PSL Enclosure to PSL-R2 - 50ft
PSL-R2 to SUS-R2 - 100ft
SUS-R2 to Top of HAM3 (flange D7/D8) - 25ft
SUS-R2 to HAM3 (flange D5) - 20ft

J. Kissel [for J. Oberling]

Jason also took the opportunity during his dust monitoring PSL incursion today to measure the distance between where the new fiber collimator would go on the PSL table to the place where it would exit at the point Fil calls the PSL enclosure.

He says 
SPI Fiber Collimator to PSL Enclosure = 9ft.

J. Kissel [for F. Clara, J. Oberling]

After talking with Fil I got some clarifications on how he defines/measures his numbers:
   - They *do* include any vertical traversing that the cable might need to go through,
   - Especially for rack-to-rack distances, always assumes that the cable will go to the bottom of the rack (typically 10 ft height from cable tray to rack bottom), 
   - He adds two feet (on either end) such that we can neatly strain relieve and dress the cable.

So -- the message -- Fil has already built in some contingency into the numbers above. 
(More to the point: we should NOT consider them "uncertain" and in doing so add an addition "couple of feet here" "couple of feet there" "just in case.")

Thanks Fil!

P.S. We also note that, at H1, the optical fibers exit the PSL at ground level on the +X wall of the enclosure between the enclosure and HAM1, underneath the light pipes. Then the immediately shoot up to the cable trays, then wrap around the enclosure, and then land in the ISC racks at PSL-R2. Hence the oddly long 50 ft. number for that journey.

Jason also reports that he rounded up to the nearest foot for his measurement of the 9ft run from where the future fiber collimator will go to the PSL enclosure "feed through."

Upon discussion with the SPI team, we want to minimize the number of "patch panel" "fiber feedthrough" connections in order to minimize loss and polarization distortion.

As such, we prefer to go directly from the "SPI pick-off in the PSL" fiber collimator directly to the Laser Prep Chassis in SUS-R2.
That being said purchase all of the above fiber lengths, such that we can re-create a "fiber feedthrough patch panel full" system as contingency plan.

So, for the baseline plan, we'll take the "original, now contingency plan" PSL-R2 to SUS-R2, 100 ft fiber run and use that to directly connect the "SPI pick-off in the PSL" fiber collimator directly to the Laser Prep Chassis in SUS-R2.

I spoke with Fil and confirmed that 100 ft is plenty enough to make that run (from SPI pick-off in PSL to SUS-R2).

PSAMS coarse scan trial (2)

Naoki, Eric, Camilla

We continued the PSAMS coarse scan in 76925. Yesterday, IFO was not thermalized, but today IFO is thermalized at least for 7 hours. It seems our nominal 140/90 (strain voltage 7.22/-0.71) would be close to optimal. The detail analysis will follow.

This time, after we moved PSAMS, we compensated the alignment change caused by the PSAMS change by looking at OSEM. This works well for ZM4, but not for ZM5 and we need to touch ZM5 in addition to the compensation. This might be related to the beam miscentering in ZM5 as reported in 75770.

no sqz (10 min)

PDT: 2024-04-04 08:06:30 PDT
UTC: 2024-04-04 15:06:30 UTC
GPS: 1396278408

asqz 200/115 (strain voltage 9.59/-0.702) (5 min)

PDT: 2024-04-04 08:41:34 PDT
UTC: 2024-04-04 15:41:34 UTC
GPS: 1396280512

sqz 200/115 (5 min)

PDT: 2024-04-04 08:49:14 PDT
UTC: 2024-04-04 15:49:14 UTC
GPS: 1396280972

asqz 200/200 (strain voltage: 9.59/2.67) (5 min)

PDT: 2024-04-04 09:28:12 PDT
UTC: 2024-04-04 16:28:12 UTC
GPS: 1396283310

sqz 200/200 (5 min)

PDT: 2024-04-04 09:36:04 PDT
UTC: 2024-04-04 16:36:04 UTC
GPS: 1396283782

asqz 100/200 (strain voltage 6.83/2.72) (5 min)

PDT: 2024-04-04 09:55:09 PDT
UTC: 2024-04-04 16:55:09 UTC
GPS: 1396284927

sqz 100/200 (5 min)

PDT: 2024-04-04 10:02:23 PDT
UTC: 2024-04-04 17:02:23 UTC
GPS: 1396285361

asqz 0/200 (strain voltage 2.2/2.72) (5 min)

PDT: 2024-04-04 10:27:25 PDT
UTC: 2024-04-04 17:27:25 UTC
GPS: 1396286863

sqz 0/200 (5 min)

PDT: 2024-04-04 10:35:27 PDT
UTC: 2024-04-04 17:35:27 UTC
GPS: 1396287345

asqz 140/90 (strain voltage 7.22/-0.71) (5 min)

PDT: 2024-04-04 11:04:22 PDT
UTC: 2024-04-04 18:04:22 UTC
GPS: 1396289080

sqz 140/90 (5 min)

PDT: 2024-04-04 11:12:41 PDT
UTC: 2024-04-04 18:12:41 UTC
GPS: 1396289579

asqz 170/90 (strain voltage 8.80/-0.70) (5 min)

PDT: 2024-04-04 11:55:59 PDT
UTC: 2024-04-04 18:55:59 UTC
GPS: 1396292177

sqz 170/90 (5 min)

PDT: 2024-04-04 12:03:26 PDT
UTC: 2024-04-04 19:03:26 UTC
GPS: 1396292624

asqz 75/90 (strain voltage 5.77/-0.71) (5 min)

PDT: 2024-04-04 12:24:44 PDT
UTC: 2024-04-04 19:24:44 UTC
GPS: 1396293902

sqz 75/90 (5 min)

PDT: 2024-04-04 12:31:39 PDT
UTC: 2024-04-04 19:31:39 UTC
GPS: 1396294317

asqz 130/125 (strain voltage 7.21/0.26) (5 min)

PDT: 2024-04-04 14:58:24 PDT
UTC: 2024-04-04 21:58:24 UTC
GPS: 1396303122

sqz 130/125 (5 min)

PDT: 2024-04-04 15:06:03 PDT
UTC: 2024-04-04 22:06:03 UTC
GPS: 1396303581

asqz 130/83 (strain voltage 7.22/-1.2) (5 min)

PDT: 2024-04-04 15:39:41 PDT
UTC: 2024-04-04 22:39:41 UTC
GPS: 1396305599

sqz 130/83 (5 min)

PDT: 2024-04-04 15:46:36 PDT
UTC: 2024-04-04 22:46:36 UTC
GPS: 1396306014

Attached are the averaged squeezing and anti-squeezing DARM spectra for each PSAM value we've measured so far.  Based on the course scan, we see that our initial PSAM values (strain voltages of 7.22/-0.71 for ZM4/ZM5) appear to be roughly optimal, giving roughly -5.2 dB of squeezing and 15.6 dB antisqueezing at 2 kHz.  So far we've noticed that any significant movement of the PSAM setting for ZM5 seems to de-optimize things and we are relatively insensitive to changes in ZM4 when ZM5 is held fixed at its initial value.    

Values from yesterday afternoon are also included.