aLIGO LHO Logbook

LHO General - Ops Eve Shift Summary

ryan.short@ligo.org — Fri, 20 Dec 2024 22:00:20 -0800

Author: ryan.short@ligo.org

Report ID: 81933

TITLE: 12/21 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: H1 has been locked and observing for about 4.5 hours. Been a quiet evening since H1 relocked early this shift.

00:11 - Lockloss - alog81930
01:38 - Observing

LHO FMCS - HVAC Fan Vibrometers Check - Weekly

ryan.short@ligo.org — Fri, 20 Dec 2024 21:44:50 -0800

Author: ryan.short@ligo.org

Report ID: 81932

FAMIS 26348, last checked in alog81819

All fans look well within acceptable noise levels and largely unchanged from last check.

PEM

Images attached to this report

H1 General - Comment to Lockloss @ 00:11 UTC

ryan.short@ligo.org — Fri, 20 Dec 2024 17:47:27 -0800

Author: ryan.short@ligo.org

Report ID: 81931

H1 back to observing at 01:38 UTC; fully automatic relock.

H1 General - Lockloss @ 00:11 UTC

ryan.short@ligo.org — Fri, 20 Dec 2024 16:47:40 -0800

Author: ryan.short@ligo.org

Report ID: 81930

Lockloss @ 00:11 UTC - link to lockloss tool

Locked for about 1.5 hours. No obvious cause, but interestingly the first saturating suspension here was ETMY L2, which I don't think is typical.

Lockloss

H1 General - OPS Friday day shift summary

ryan.crouch@ligo.org — Fri, 20 Dec 2024 16:33:55 -0800

Author: ryan.crouch@ligo.org

Report ID: 81925

TITLE: 12/21 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: 2 locklosses, recovering from the last one currently. New o4b record of 47 hours?
LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
16:53	SAF	LVEA	LVEA	YES	LVEA IS LASER HAZARD	22:08
16:12	FAC	Kim	Optics lab & Vac prep	N	Tech clean	16:55
18:29	CAL	Francisco	PCAL lab	LOCAL	PCAL work	18:39
21:24	FAC	Christina	OSB recieving	N	Roll up door	21:49
21:49	OPS	Oli	LVEA	Y -> N	Transition	22:08
21:49	SEI	Jim	LVEA	Y	Look for parts around biergarten	21:56
22:08	OPS	LVEA	LKVEA	N	LASER SAFE	15:07
23:39	SQZ	Camilla	Optics lab	N	Put away stuff	00:30

20:59 UTC lockloss from a 47 hour lock which I think is the new O4b record. Easy relock with an IA, which I had to help out inbetween SR2 and SRY align as it got couldn't get SRY (lots of SRM sats), I reran SR2 and them SRY was fine.

00:11 UTC lockloss

LHO General - Ops Eve Shift Start

ryan.short@ligo.org — Fri, 20 Dec 2024 16:04:50 -0800

Author: ryan.short@ligo.org

Report ID: 81929

TITLE: 12/21 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.41 μm/s
QUICK SUMMARY: H1 has been locked for just over an hour. If there's a lockloss this evening, I plan to adjust the ISS RefSignal to bring the diffracted power back up to around 4% (currently down to around 2.5%).

Wind is low; secondary microseism moderate
LAB2 dust monitor error (known)

H1 DetChar - "Safe" channel CS MAG EBAY LSCRACK Y found to be unsafe when looking at 2 week duration

jason.levelle@ligo.org — Fri, 20 Dec 2024 15:45:34 -0800

Author: jason.levelle@ligo.org

Report ID: 81928

New calibration lines turned on 7/25/2023 resulted in unexpected additional inter-modulation products. These new calibration lines were turned off on 8/9/2023.

When looking at coherence data between the main detector and safe channels, we expect no change in the before-during-after periods of the new calibration lines and additional inter-modulation products. However, in “safe” channel CS MAG EBAY LSCRACK Y, we see coherence jump at the specific frequencies of the calibration lines and inter-modulation products. This indicates that the channel may actually be unsafe.

Plots for H1_PEM-CS_MAG_EBAY_LSCRACK_Y_DQ before / during / after

Research Presentation: https://dcc.ligo.org/G2402592

Images attached to this report

H1 General - Comment to Lockloss 20:59 UTC 47 hour lock

ryan.crouch@ligo.org — Fri, 20 Dec 2024 14:54:01 -0800

Author: ryan.crouch@ligo.org

Report ID: 81927

22:53 UTC back to Observing

H1 General - Lockloss 20:59 UTC 47 hour lock

ryan.crouch@ligo.org — Fri, 20 Dec 2024 13:02:29 -0800

Author: ryan.crouch@ligo.org

Report ID: 81926

ETMX glitch lockloss tool

Lockloss

LHO VE - Fri CP1 Fill

david.barker@ligo.org — Fri, 20 Dec 2024 10:28:12 -0800

Author: david.barker@ligo.org

Report ID: 81924

Fri Dec 20 10:11:13 2024 INFO: Fill completed in 11min 10secs

TC-B is still elevated by about +30C compared to TC-A and did not reach the trip temp.

Images attached to this report

H1 SEI - HEPI Pump Trends Monthly FAMIS

oli.patane@ligo.org — Fri, 20 Dec 2024 10:18:22 -0800

Author: oli.patane@ligo.org

Report ID: 81923

Closes FAMIS#26473, last checked 81396

HEPI pump trends looking as expected(ndscope). There is a period of rapid change in the pressure at EX 28 days ago, right after TJ put in his alog (linked above) about the pressure being a bit weird, and that's because Jim and Mitchell had gone out to investigate it (81399).

Images attached to this report

H1 General - Comment to OPS Friday DAY shift start

ryan.crouch@ligo.org — Fri, 20 Dec 2024 07:41:12 -0800

Author: ryan.crouch@ligo.org

Report ID: 81921

Range looks fairly steady around just under 160 for the whole lock, the coherence check yielded.

Images attached to this report

H1 General - OPS Friday DAY shift start

ryan.crouch@ligo.org — Fri, 20 Dec 2024 07:24:05 -0800

Author: ryan.crouch@ligo.org

Report ID: 81920

TITLE: 12/20 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 160Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT
    Wind: 3mph Gusts, 2mph 3min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.32 μm/s
QUICK SUMMARY:

We've been locked for 41.5 hours!
2ndary microseism is steady, low wind, theres a small EQ shaking us (5.5 from Vanuatu)
PMR and PR2 cameras are blue
If we lose lock we want to transition the LVEA back to laser safe

H1 General - Thursday Eve shift End

anthony.sanchez@ligo.org — Thu, 19 Dec 2024 22:04:49 -0800

Author: anthony.sanchez@ligo.org

Report ID: 81919

TITLE: 12/20 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
H1 Still locked for 32 hours! Currently Observing.
Aside from the breif Internet outage nothing really happened.
Violins looking good, No Pi's ringing up or nothin.
This is a good start going into the holidays.

H1 CDS - CDS & GC outbound internet connection interuption.

anthony.sanchez@ligo.org — Thu, 19 Dec 2024 18:38:39 -0800

Author: anthony.sanchez@ligo.org

Report ID: 81918

TITLE: 12/20 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 7mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.34 μm/s
QUICK SUMMARY:
CDS & GS internet connectivity to the outside world went down. Issues due to Core Switch work?
Outage lasted from 2:00 UTC to ~ 2:24 UTC.

IFO stayed locked during that time, We now have a 28+ Hour lock.
Control over the IFO was maintained throughout the entire outage.
Local networks stayed up and running just fine.
I called Dave & Jonathan, Jonathan told me to wait it out, as it's just a switch updating , rebooting, and falling back to another network.
I presume the falling back to the other network bit took some time.

All systems recovered the way Jonathan said they would. He advised me to wait it out if there is another one, and to call him again if things went down after 3 :00 UTC (7pm local) .
So far so good.

H1 ISC - Calibrated Angle to Length Coupling from HARD loops

elenna.capote@ligo.org — Thu, 19 Dec 2024 17:36:08 -0800

Author: elenna.capote@ligo.org

Report ID: 81917

This alog follows up LHO:81769 where I calibrated the ASC drives to test mass motion for all eight arm ASC control loops. Now, I have taken the noise budget injections that we run to measure the ASC coupling to DARM, and used that to calibrate an angle-to-length coupling function in mm/rad. I have only done this for the HARD loops because the SOFT loops do not couple very strongly to DARM (notable exception to CSOFT P, which I will follow up on).

The noise budget code uses an excess power projection to DARM, but instead I chose to measure the linear transfer function. The coherence is just ok, so I think a good follow up is to remeasure the coupling again and drive a bit harder/average longer (these are 60 second measurements). This plot shows the noise budget injection into calibrated DARM/ASC PUM drive [m/Nm] transfer function, and the coherence of the measurement.

I followed a similar calibration procedure to my previous alog:

Go from "H1:ASC-[DOF]_[P/Y]_OUT_DQ" to Nm of PUM torque using G1100968
- I made sure that I corrected by an erroneous factor of two that I found previously
- Some of these injections were done after the ETMX DAC change. However, Daniel noted this alog for me, 80023, so the calibration for the ASC should not change significantly.
transform this N*m PUM drive to radians of test mass motion using the PUM-TST state space suspension model transfer function, which is calibrated into real units (radian/Nm)
- I did all of this in python, so I used Kevin's exported quad state space model, found here: T2300299
- I used the damped model which applies the ETMX top mass damping filters
Multiply by 1e3 to convert to mm/rad

I did not apply the drive matrix here, so the calibration is into ETM motion only (factor of +/-1), whereas the calibration into ITM motion would have an additional +/- 0.74 (+/- 0.72 for yaw) applied.

HARD Pitch Angle to Length coupling plot

HARD Yaw Angle to Length coupling plot

Overall, the best-measured DOF here is CHARD Y. In both CHARD Y and DHARD Y, there seem to be two clear coupling regions: one fairly flat region above 20 Hz in CHARD Y and above 30 Hz in DHARD Y, reaching between 20-30 mm/rad. Below, there is a steep coupling. This is reminiscient of the coupling that Gabriele, Louis, and I measured back in March and tried to mitigate with A2L and WFS offset. We found that we could reduce the flatter coupling in DHARD Y by adjusting the A2L gain, and the steeper coupling by applying a small offset in AS WFS A yaw DC. We are currently not running with that WFS offset. The yaw coupling suggests that we have some sort of miscentering on both the REFL and AS WFS which causes a steep low frequency coupling which is less sensitive to beam centering on the test mass (as shown by the A2L tests); meanwhile, the flat coupling is sensitive to beam miscentering on the test mass, which is expected (see e.g. T0900511).

The pitch coupling has the worst coherence here, but the coupling is certainly not flat. It appears to be rising with about f^4 at high frequency. I have a hard time understanding what could cause that. There is also possibly a similar steep coupling at low frequency like the yaw coupling, but the coherence is so poor it's hard to see.

Assuming that I have my calibration factors correct here (please don't assume this! check my work!), this suggests that the beam miscentering is higher than 1 mm everywhere and possibly up to 30 mm on the ETMs (remember this would be ~25% lower on the ITMs). This seems very large, so I'm hoping that there is another errant factor of two or something somewhere.

My code for both the calibrated motion and calibrated coupling is in a git repo here: https://git.ligo.org/ecapote/ASC_calibration

Non-image files attached to this report

DARM_PUM_ASC_drive.pdf

DARM_ASC_TST_coupling_pitch.pdf

DARM_ASC_TST_coupling_yaw.pdf

H1 General - Thursday Eve shift start

anthony.sanchez@ligo.org — Thu, 19 Dec 2024 16:49:59 -0800

Author: anthony.sanchez@ligo.org

Report ID: 81916

TITLE: 12/20 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.32 μm/s
QUICK SUMMARY:
H1 has been locked for over 26 Hours.
Current plan: stay in Observing.

Note:
Dust mon LAB2 still not reporting back correctly.

LHO General - Ops Day Shift End

thomas.shaffer@ligo.org — Thu, 19 Dec 2024 16:27:40 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81905

TITLE: 12/20 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 162Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Locked for 26.5 hours so far. We took calibration measurements this morning, followed by 3 hours of commissioning time.
LOG:

1630 Out of Observing to start calibration measurement and then commissioning
2007 Observing

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
16:53	SAF	LVEA	LVEA	YES	LVEA IS LASER HAZARD	00:38
15:38	PCAL	Francisco	PCAL lab	local	Check on meas	15:43
16:54	FAC	Tyler	High Bay	N	While we are not observing	17:24
17:08	SEI	Jim, Mitchell	EY	n	Wind fence check	18:54
18:21	-	Richard	OSB	n	Opening receiving rollup	18:36
18:44	FAC	Kim	H2 build	n	Tech clean	19:02
20:19	VAC	Janos	MX, MY	n	Taking measurements	21:44
22:12	PCAL	Rick, Francisco, Dripta	PCAL lab	local	PCAL meas	01:12

H1 ISC - Comment to Test mass motion from ASC drives

elenna.capote@ligo.org — Thu, 19 Dec 2024 15:58:11 -0800

Author: elenna.capote@ligo.org

Report ID: 81915

The attached plots are corrected by the erroneous factor of two mentioned above, which has an overall effect of reducing the motion by 2.

Non-image files attached to this report

H1 SUS - SR3,SRM OSEM Noise Injections

joshua.freed@ligo.org — Thu, 19 Dec 2024 15:07:25 -0800

Author: joshua.freed@ligo.org

Report ID: 81914

J. Freed,

SRM M1 stage bosems (speciffically T2, T3) show strong coupling below 10Hz. SR3 M1 had some on LF, RT bosems between 10-15Hz

Today I did damping loop injections on all 6 BOSEMs on the SR3 and SRM M1. This is a continuation of the work done previously for ITMX, ITMY, PR2, PR3, PRM, SR2. As with PRM, gains of 300 and 600 were collected for SR3 (300 is labled as ln or L). Only a gain of 600 was collected for SRM due to time constraints. Calibration lines were on for SR3.

The plots, code, and flagged frequencies are located at /ligo/home/joshua.freed/bosem/SR3/scripts. While the diaggui files are at /ligo/home/joshua.freed/bosem/SR3/data for SR3. I used Sheila code located under /ligo/home/joshua.freed/bosem/SR2/scripts/osem_budgeting.py to produce the sum of all contributions as well as the individual plots.

SRM.png Shows SRM M1 bosems contribution to DARM at 600 amplitude on each bosems excitation channel. Only T2 and T3 seem to have a noticible effect.

SR3.png Shows SR3 M1 bosems contribution to DARM at 600 amplitude. Besides the bounce mode at 9Hz, SR3 only had some coupling from 10-15Hz on the LF and RT BOSEMs. Might have more behind the calibration lines

main.png Shows the current version of the sum of the BOSEM contributions. Only PR3, PRM, SR2, SR3, SRM are included so far.

Side note:

Screenshot_60Hz_background.png Shows SRM M1 T3 out channel is giving an unusual strong 60Hz signal during quiet time. All BOSEM on SRM were giving this signal. Unsure if this is a continuous issue. Unlikely to have affected this measurment but worth pointing out.

reference number in diaggui files for SR3

Background time: (ref0 DARM, ref1 LF_out, ref2 RT_out, ref3 SD_out, ref4 T1_out, ref5 T2_out, ref6 T3_out)
LFL time:                (ref7 DARM, ref8 LF_out)
LF time:                (ref9 DARM, ref10 LF_out)
RTL time:           (ref11 DARM, ref12 RT_out)
RT time:             (ref13 DARM, ref14 RT_out)
SDL time:      (ref15 DARM, ref16 SD_out)
SD time:          (ref17 DARM, ref18 SD_out)
T1L time:            (ref19 DARM, ref20 T1_out)
T1 time:            (ref21 DARM, ref22 T1_out)
T2L time:          (ref23 DARM, ref24 T2_out)
T2 time:                (ref25 DARM, ref26 T2_out)
T3L time:             (ref27 DARM, ref28 T3_out)
T3 time:             (ref29 DARM, ref30 T3_out)

reference number in diaggui files for SRM

Background time: (ref0 DARM, ref1 LF_out, ref2 RT_out, ref3 SD_out, ref4 T1_out, ref5 T2_out, ref6 T3_out)
LF time:                (ref7 DARM, ref8 LF_out)
RT time:             (ref9 DARM, ref10 RT_out)
SD time:          (ref11 DARM, ref12 SD_out)
T1 time:            (ref13 DARM, ref14 T1_out)
T2 time:                (ref15 DARM, ref16 T2_out)
T3 time:             (ref17 DARM, ref18 T3_out)

SEI, SUS

Images attached to this report

H1 SQZ - Comment to SCAN_PSAMS.py script ran, PSAMS changed by looking at OAF-RANGE_BAND2 and Range

camilla.compton@ligo.org — Thu, 19 Dec 2024 14:35:55 -0800

Author: camilla.compton@ligo.org

Report ID: 81913

Vicky asked to check the HOM plot and wide plot, don't see a big difference, if anything it's worse with larger HOM peaks after the PSAMS change. We can see that the 20-35Hz in DARM looks a little better, though this does drift throughout the lock as Sheila showed in 81843.

Images attached to this report

H1 ISC - Comment to Test mass motion from ASC drives

elenna.capote@ligo.org — Thu, 19 Dec 2024 14:05:40 -0800

Author: elenna.capote@ligo.org

Report ID: 81912

I have just realized I mixed up the DACs and ADCs (again) and the correct count-to-torque calibration should be:

for PUM: 20 V /2**20 ct [DAC] * 0.268 mA / V [drive strength] * 0.0309 N / A [force coeff] * 70.7 mm [lever arm], pit/yaw lever arm is the same for the PUM

So these plots are wrong by a factor of 2. I will correct this in my code and post the corrected plots shortly.

H1 General - Back to Observing 2007UTC

thomas.shaffer@ligo.org — Thu, 19 Dec 2024 12:11:56 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81911

Commissioning wrapped up, back to Observing 2007UTC.

Locked for 22 hours.

H1 General - Dust monitor swap

ryan.crouch@ligo.org — Thu, 19 Dec 2024 11:59:15 -0800

Author: ryan.crouch@ligo.org

Report ID: 81910

This morning I swapped out the dust monitor in the VAC prep lab for a spare that was calibrated earlier this year. After swapping the connection issues remain.

H1 GRD - SUS_PI guardian now increases ETMY ESD bias to help damp PI24

oli.patane@ligo.org — Thu, 19 Dec 2024 11:51:04 -0800

Author: oli.patane@ligo.org

Report ID: 81909

Since we've been having issues with PI24 ringing up lately we decided to change the SUS_PI guardian code to increase the bias offset on ETMY L3 LOCK. That bias offset value is normally -4.9, and we noticed that when damping PI24, we typically start hitting our damping limit when PI24 RMSMON exceeds a value of 10. I have turned the PI_DAMPING state into a generator function so it can now make two different states, PI_DAMPING and EXTREME_PI_DAMPING. When in PI_DAMPING, pi24 will be damped with our normal bias until we reach an RMSMON average value of 20. Once that happens, the guardian will jump to a state called INCREASE_BIAS (what it does is self-explanatory), and then goes into XTREME_PI_DAMPING, where it continues damping and changing phase as needed until we are back under an RMSMON value of 4(pi24 script logic). Once we are good the guardian will take us through DECREASE_BIAS (guess what that does) and then back into PI_DAMPING(node graph, states list).

Because the nominal state for Observing is PI_DAMPING, when we move into one of these other states we will be taken out of Observing (tagging OPS). Once we are back in PI_DAMPING we will automatically go back into Observing as long as we are in AUTOMATIC.

Occasionally we do get small quick ringups that go up above 20 that are capable of being damped by regular damping and just changing the phase - ndscope1(versus the slower ringups that cannot - ndscope2), so with these script changes, when these happen we will be taken out of Observing as the SUS_PI guardian jumps to up the bias and damp harder. These don't happen very often so we are okay for now, but a future to-do is to edit the script to keep it from increasing the bias at least until it's tried all phase changes.

ISC, OpsInfo, SUS

Images attached to this report

H1 SQZ - SCAN_PSAMS.py script ran, PSAMS changed by looking at OAF-RANGE_BAND2 and Range

camilla.compton@ligo.org — Thu, 19 Dec 2024 11:42:51 -0800

Author: camilla.compton@ligo.org

Report ID: 81908

Camilla, Sheila, Following on from 81852.

Today I re-ran the sqz/h1/scripts/SCAN_PSAMS.py script, with SQZ_MANAGER guardian paused (so it's not forcing the ADF servo on). The script worked as expected (setup by turning off ADF servo and increasing SQZ ASC gain to speed up, then changed ZM PSAMS, waited 120s for ASC to coverage, turned off ASC, scanned sqz angle and saved data and then repeated) and took ~3m30 per step.

The results are attached (heatmap, scans) but didn't show an obvious direction to move in. Maybe the steps were too small but are already larger than those use at LLO LLO#72749: 0.3V vs 0.1V per step.

Our initial ZM4/5 PSAMs values were 5.6V, -1.1V and looking at the attached data, we took them to 5.2V, -1.5V. We then decided ther range looked better when the PSAMs were higher to went to 6.0V, -0.4Vthis seemed to gain improve the range ~5MPc, we checked by going back to 5.2V, -1.5V and the range again dropped, main change appears to be in orange BAND_2 OMC BLRMs which is 20-34Hz, the places with glitches in OAF BLRMS are noisy times from Robert's injections. Then went further in this direction to 6.5V, 0.0V, this didn't help the range so we are staying at 6.0V, -0.4V, sdf's attached. This seemed to be a repeat-able change that gave us a few MPc's in range! Success for PSAMS: zoomed out and zoomed in plots attached.

Future work: we could run the SCAN_PSAMS.py script with small 0.1V changes as LLO does.

Images attached to this report

LHO VE - Thu CP1 Fill, issues with Thermocouple-B

david.barker@ligo.org — Thu, 19 Dec 2024 10:27:25 -0800

Author: david.barker@ligo.org

Report ID: 81907

Thu Dec 19 10:15:29 2024 INFO: Fill completed in 15min 25secs

Gerardo confirmed a good fill curbside.

TC-B suddenly jumped up in temperature at 04:16 this morning by +15C. Gerardo took a look, both TCs are currently encased in ice (see photo).

TC-mins for today's fill (trip temp = -65C) TC-A = -116C, TC-B = -56C. Which means only TC-A was able to stop the fill by exceeding the trip temp.

Images attached to this report

H1 PEM - Comment to TCS-Y chiller is likely hurting Crab sensitivity

keith.riles@ligo.org — Thu, 19 Dec 2024 10:19:16 -0800

Author: keith.riles@ligo.org

Report ID: 81902

The further reduced flow rate seems to have given the Crab band more isolation from nearby peaks, although I'm not sure I understand the improvement in detail. Attached is a spectrum from yesterday's data in the usual form. Since the zoomed-in plots suggest (unexpectedly) that lowering flow rate moves an offending peak up in frequency, I tried broadening the band and looking at data from December 7 (before 1st flow reduction), December 16 (before most recent flow reduction) and December 18 (after most recent flow reduction). If I look at one of the accelerometer channels Robert highlighted, I do see a large peak indeed move to lower frequencies, as expected. Attachments: 1) Usual daily h(t) spectral zoom near Crab band - December 18 2) Zoom-out for December 7, 16 and 18 overlain 3) Zoom-out for December 7, 16 and 18 overlain but with vertical offsets 4) Accelerometer spectrum for December 7 (sample starting at 18:00 UTC) 5) Accelerometer spectrum for December 16 6) Accelerometer spectrum for December 18

Images attached to this report

H1 CAL - Calibration Sweep 1630 UTC

thomas.shaffer@ligo.org — Thu, 19 Dec 2024 09:02:29 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81906

Following the new instructions but on the usual wiki, I ran a broad band and then a new version of simulines like Corey did last week (alog81828).

Simulines start:

PST: 2024-12-19 08:37:18.337770 PST
UTC: 2024-12-19 16:37:18.337770 UTC
GPS: 1418661456.337770

End:

PST: 2024-12-19 09:01:04.771446 PST
UTC: 2024-12-19 17:01:04.771446 UTC
GPS: 1418662882.771446

Files:

2024-12-19 17:01:04,693 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_2024
1219T163719Z.hdf5
2024-12-19 17:01:04,700 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_S
S_20241219T163719Z.hdf5
2024-12-19 17:01:04,704 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_S
S_20241219T163719Z.hdf5
2024-12-19 17:01:04,708 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_S
S_20241219T163719Z.hdf5
2024-12-19 17:01:04,712 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_S
S_20241219T163719Z.hdf5

H1 CDS - VACSTAT BSC3 sensor glitch reset

david.barker@ligo.org — Thu, 19 Dec 2024 07:36:39 -0800

Author: david.barker@ligo.org

Report ID: 81904

VACSTAT detected another BSC3 PT132 sensor glitch at 00:53 Thu 19dec2024. I reset vacstat_ioc.service on cdsioc0 at 07:32 to clear it.

Images attached to this report

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Thu, 19 Dec 2024 07:34:12 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81903

TITLE: 12/19 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 7mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.35 μm/s
QUICK SUMMARY: Locked for 17.5 hours, range stable, environment calm. Planned calibration and commissioning today starting at 0830PT (1630UTC).

H1 General - Wednesday Eve shift End

anthony.sanchez@ligo.org — Wed, 18 Dec 2024 22:12:48 -0800

Author: anthony.sanchez@ligo.org

Report ID: 81901

TITLE: 12/19 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
H1 has been locked all shift!
A few small earthquakes rolled though and we survived.
Other wise it's been a quiet night.

LHO VE - Temperature Fluctuations Noted by Vacuum Pressure

gerardo.moreno@ligo.org — Wed, 18 Dec 2024 16:20:41 -0800

Author: gerardo.moreno@ligo.org

Report ID: 81900

Just an FYI, the vacuum pressure is affected by the temperature fluctuations inside the VEA, probably due to warm day(s), see attached plot. Noted on both Mids.

Images attached to this report

H1 General - Wednesday Eve shift start

anthony.sanchez@ligo.org — Wed, 18 Dec 2024 16:00:43 -0800

Author: anthony.sanchez@ligo.org

Report ID: 81898

TITLE: 12/18 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.38 μm/s
QUICK SUMMARY:
Locked And Observing for 8 minutes.

Notes about IFO config:
EY Ring heater is bumped up 0.1Watts/sec so we have a chance of surviving a a 10K PI ring up. Alog about this: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=81891

H1 ISC - Comment to Three locklosses since 9th Dec from PI24 Ringup

thomas.shaffer@ligo.org — Wed, 18 Dec 2024 15:58:45 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81899

Very quick shot of the 10.4k homs 2 hours into the first lock with the EY ring heater bumped up to 1.2W from 1.1W. This will need to be checked again later, but it's promising so far.

Images attached to this report

LHO General - Ops Day Shift End

thomas.shaffer@ligo.org — Wed, 18 Dec 2024 15:54:28 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81894

TITLE: 12/18 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Strong wind this morning with gusts into the 50s slowed down locking, but we made it up around the middle of the day. We are running with the EY ring heaters at 1.2W vs their usual 1.1W to avoid PIs. The LVEA was transitioned to laser hazard so Robert could go back out to the floor and check on some beam spots. Relocking was automatic, we've now been locked for 2 hours.

Locking notes
- Once initial alignment was started, the FSS was struggling to relock. Eventually I turned the autolocker off, waited a handful of seconds, then back on, and it caught right away.
- Robert guided the initial alignment along as he watched for spot moves at a viewport.
- There were a few lock losses at DRMI and one at transition from ETMX, but these seem to be wind induced. Eventually made it up without me touching anything.
2157 Observing

LOG:

Start Time	System	Name	Location	Lazer_Haz	Task	Time End
16:53	SAF	LVEA	LVEA	YES	LVEA IS LASER HAZARD	00:38
17:15	PEM	Robert	LVEA	n	Moving test setup	17:20
17:39	SAF	Oli	LVEA	n->YES	LVEA laser hazard transition	18:04
17:44	PEM	Robert	LVEA	YES	Beam spot investigation	19:47
18:06	FAC	Tyler, Richard, MacMiller	MY, EY	n	Chiller inspections	18:31
19:48	PCAL	Francisco, Dripta	PCAL lab	local	PCAL meas	22:36

H1 General - Observing 2157UTC

thomas.shaffer@ligo.org — Wed, 18 Dec 2024 14:06:36 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81897

The wind has calmed down and we were able to relock automatically.

We have a new ETMY ring heater setting, so we'll see if PI24 is a problem this time.

H1 CDS - Pico Motor Control MEDMs, motor selection buttons invisible when controller is busy

david.barker@ligo.org — Wed, 18 Dec 2024 12:26:17 -0800

Author: david.barker@ligo.org

Report ID: 81896

FRS32910

In alog_81849 Sheila and Camilla found a bug in the picomotor controller code, whereby if the motor to be controlled is changed while the controller is busy with the current move command, the motor change is not accepted resulting in the wrong motor being driven during subsequent commands.

As a quick work around until such time as the code can be fixed, I've made a change to the MEDMs which hides the motor selection buttons when the controller is busy.

Attached screenshots show a test case, left shows the normal situation where the controller is not busy and the selection buttons are all visible. The right screen shows a simulation of the controller being busy (INUSE=1), the selection buttons are replaced by rectangular blocks.

Images attached to this report

H1 TCS - Comment to CO2 Lasers Spectrum Locked vs Unlocked

camilla.compton@ligo.org — Wed, 18 Dec 2024 12:20:26 -0800

Author: camilla.compton@ligo.org

Report ID: 81868

Gabriele, Camilla.

We are not sure if this measurement makes sense.

Attached is the same spectrum with the CO2X laser turned off to see the dark noise. It appears that measurement is limited to dark noise of the diode above 40Hz. The ITMX_CO2_ISS_IN_AC channel dark noise is actually above the level when the laser is on, this doesn't make sense to me.

Is there anything strange happening in models or chassis? No.
- The filters in the DC _OUT channels include a CountstoVolts gain(0.000610352) and UndoGain gain(0.00196078) which is 1/510 from the PD electronics D1201111 as expected
- The AC _OUT channel includes a CountstoVolts gain(0.000610352) and de-whiten zpk([20], [0.01], 0.011322, "n").
- There is nothing else in the h1hsccs model.
- Looking at the TCS block diagram E1100892, the ISS PD outputs go though the TCS ISS and Interface Chassis D1300649 (D1300015 shows there nothing happening to the signals inside this chassis), before going to the ADC. So the model should see the signals as if they were coming straight from the PD DB9 output + counts to volts gain.
Does DC value of 7e-3 V make sense? Yes.
- In CIT#389 saw saw -1V (DCMON so gain of 255) for 60mW of laser power (can jump ~by a factor of 2 dependent on wavelength/polarization/how the laser is feeling). From this, expect 1mV from diode (before electronics gain) is 15mW of laser power. So that the DC value measured of 7e-3 V would be around 100mW of power on the PD (within a factor of 2 is 50mW to 200mW). This makes sense as we would expect around 250mW on the ISS PD (50W out of laser x 99/1 BS x 50/50 BS).
Does Dark noise value make sense: Unsure.
- In CIT#541, Gabriele shows DC dark noise values of 4e-7 /rHz, this is straight out of the diode (DCMON so x gain of 255) so the comparable value to our _OUT channels would be 1.5e-9 /rHz. This is a factor of 3 different from the 5e-9/rHz dark value we measure at LHO on the DC OUT.
- Debatable math: The power noise of the diode is 1e-8 W/rHz (from Keita's computations attached to CIT#549). So the RIN should be noise-limited to 1e-8 W/rHz / 0.250W = 4e-8 /rHz. We are measuring down to 5e-9/rHz on the DC channel which is a factor of 10 lower than expected possible

Images attached to this report

H1 ISC - Comment to Three locklosses since 9th Dec from PI24 Ringup

vladimir.bossilkov@ligo.org — Wed, 18 Dec 2024 10:48:16 -0800

Author: vladimir.bossilkov@ligo.org

Report ID: 81895

You cannot just use L1's lockloss code for the tagging universally [should work for the 10kHz PI though].

Because of the way LHO changed their readouts for the OMC, digging into the simulink model will reveal the PI is reading in only the first 32kHz band, for the RMS calculations

You simply have no aliasing down of the full band to utilise it in the way we do; and it will never see 80kHz PI.
Also your scaling is using calibrated DARM units by the look of things; while we use a counts scale; so the numbers in the RMS readouts are different many orders of magnitude.

H1 ISC - Comment to Three locklosses since 9th Dec from PI24 Ringup

camilla.compton@ligo.org — Wed, 18 Dec 2024 10:46:54 -0800

Author: camilla.compton@ligo.org

Report ID: 81892

Plotted is the location of the arm higher order modes around 10kHz. They have moved so that the central frequency is the same as the spikes around 10.4kHz, this excites the PI's more.

In the first plot we see that since November and the start of December, the center of the lower HOM peak has drifted down in frequency to be underneath the 10.kHz PI modes: compare black (now) to red and brown.
- I tried to check more times to see exactly when this change happened in the 4th attached plot but this is tricky as the location and shape of the HOM depends on how warm the IFO is (i.e. was it DOWN a logn time before locking as in ref 7: Cold IFO). It sees like the change started 6th/7th Dec and was done by 10th Dec.
In the second plot we see what happened in September when we increased the ETMY Ring Heater (as we repeated today 81891), both HOM peaks moved up in frequency, which is the direction we want.

Maybe an unrelated point is that since the start of October, the circulating arm power has drifted down ~4kW (~1%) from 389 to 285kW when thermalized, plot attached. It's hard to know what's caused this, the IM4 TRANS drifted ~2% but was misaligned so would see alignment shifts 81735, the POP also drifted ~1% before it was recentered 81329. Input power measured by IMC_PWR_IN remained constant.

Images attached to this report

LHO VE - Wed CP1 Fill

david.barker@ligo.org — Wed, 18 Dec 2024 10:18:36 -0800

Author: david.barker@ligo.org

Report ID: 81893

Wed Dec 18 10:12:11 2024 INFO: Fill completed in 12min 7secs

Today we had low TC mins [-156C,-155C] because of an unusually warm outside air temp of 56F, 14C.

Images attached to this report

H1 ISC - EY ring heater bumped from 1.1W to 1.2W

thomas.shaffer@ligo.org — Wed, 18 Dec 2024 09:11:03 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81891

To hopefully help combat our recent bouts of PI24 ring ups (alog81890), we've bummped the ETMY ring heater power from 1.1W per segment to 1.2W. The safe.snap and observe.snap are updated.

We also have a plan to update the PI guardian to temporarily increase the ETM bias to hopefully give us more range to damp the PI. We will need to be out of Observing for this, but we could hopefully save the lock. TBD.

OpsInfo, TCS

Images attached to this report

H1 ISC - Three locklosses since 9th Dec from PI24 Ringup

camilla.compton@ligo.org — Wed, 18 Dec 2024 09:10:18 -0800

Author: camilla.compton@ligo.org

Report ID: 81890

Sheila, TJ, Camilla

We've had 3 locklosses since 9th Dec from PI24 ringing up (10.4kHz on ETMY): last night 81883, Tuesday AM 81862 and the 9th Dec, plot of all.

We had locklosses like this in September after the vent, Oli has a timeline in 80299. We increased the ETMY RH on September 26th 80320 and didn't have any PI locklosses since.

We normally damp this PI during the start of thermalization and successfully damped this after a 13 hours locked on 10th Dec, plot.

We can see a 25Hz wiggle in DARM just before the lockloss, e.g. 81862. The lockloss tool isn't tagging these as DCPD Saturation so we should implement LLO's PI code: Locklost Issue #198

Lockloss, SUS

Images attached to this report

H1 General - Two lock losses last night with ETMX glitch behavior

thomas.shaffer@ligo.org — Wed, 18 Dec 2024 07:57:07 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81889

We had two short locks under an hour last night and both seemed to have lost lock from the ETMX glitches that we see (1418536304 and 1418541959). The former was tagged as an ETM glitch and is clearly much more obvious, the latter was moore minor but still looks like there was something odd going on a few tenths of a second before the lock loss.

Lockloss

Images attached to this report

LHO General - Ops Day Shift Start

thomas.shaffer@ligo.org — Wed, 18 Dec 2024 07:39:30 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81888

TITLE: 12/18 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Wind
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 42mph Gusts, 32mph 3min avg
    Primary useism: 0.09 μm/s
    Secondary useism: 0.45 μm/s
QUICK SUMMARY: I just brought the IFO to IDLE since we are getting wind gusts into the 40s and ALS won't stay locked.

H1 General - Tuesday Eve Shift End

anthony.sanchez@ligo.org — Tue, 17 Dec 2024 22:15:14 -0800

Author: anthony.sanchez@ligo.org

Report ID: 81887

TITLE: 12/18 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
Unknown lockloss at 5:51 UTC.
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1418536304
Screenshot attached below

Current Locking state: Carm_Offset_reduction.

Lockloss

Images attached to this report

H1 DAQ - Comment to Previous/spare timing master

daniel.sigg@ligo.org — Tue, 17 Dec 2024 21:53:14 -0800

Author: daniel.sigg@ligo.org

Report ID: 81886

Today's readback voltage is at -2.511V

H1 ISC - Comment to LSC POP found to be clipping, PR3 being moved to improve this.

sheila.dwyer@ligo.org — Tue, 17 Dec 2024 21:14:54 -0800

Author: sheila.dwyer@ligo.org

Report ID: 81885

Please see Tony's comment about DRMI lock acquisition times here: 81879

When we moved PR3, we inceased the level of light on the POPAIR B diode. That does two things, first it means that the LSC controls were triggered at a lower percentage of the full buildups, which could cause difficulty locking DRMI (we want to maintain the trigger thresholds similar to what was documented in 44348. ). Also, the alignment check that Tony describes won't work well, because we didn't update the threshold the guardian used to decide that the alignment was poor and we needed to do PRMI.

From Tony's historgrams I'm not sure which of these is the main impact on DRMI locking times, if it's the triggering or the alignment check. We updated the trigger levels today, but not the threshold for the alignment check.

In the future we should check all these levels again 44348 when we have a change in power on POPAIR.

H1 ISC - Comment to Updated DRMI locking trigger thresholds

sheila.dwyer@ligo.org — Tue, 17 Dec 2024 21:03:21 -0800

Author: sheila.dwyer@ligo.org

Report ID: 81884

Here's a reference from 2018 of what trigger levels were as a percentage of the locked build ups for DRMI at a time when it was locking well. 44348

I added a comment here, 81885, pointing to Tony's alog. The main point is that we probably may also need to update the check that tells the guardian to run a PRMI alignment for the higher flashes.

H1 General - PI24 Lockloss

anthony.sanchez@ligo.org — Tue, 17 Dec 2024 20:29:17 -0800

Author: anthony.sanchez@ligo.org

Report ID: 81883

TITLE: 12/18 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 1mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.35 μm/s
QUICK SUMMARY:
Lockloss from a PI24 Ring up
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1418526747

Pi monitor tried to Damp it but couldn't turn it around at all for over 15 minuts, where I attempted to mannually damp it.... this was not a successfully activity.

Lockloss

Images attached to this report

LHO General - Ops Day Shift End

thomas.shaffer@ligo.org — Tue, 17 Dec 2024 16:57:15 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81877

TITLE: 12/18 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Just got back to Observing with the POP Beam diverter open. We plan to leave this beam diverter open until the end of Tony's shift at 0600UTC. Relocking had three bits of testing, slowing the process down. There was some ALS testing (alog81870), SRCL OLG (alog81872), and DRMI locking (alog81880), then a lock loss closing the beam diverter...I pressed the wrong the button. Relocking was straight forward after that.
LOG:

2227 lock loss from Inject squeezing while closing beam diverters, I pressed the wrong button. Sorry all.
0021 Observing

DetChar

H1 General - Tuesday Eve Shift Start

anthony.sanchez@ligo.org — Tue, 17 Dec 2024 16:54:38 -0800

Author: anthony.sanchez@ligo.org

Report ID: 81882

TITLE: 12/18 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 5mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.35 μm/s
QUICK SUMMARY:

IFO is locked, and Observing for 26 Minute now.

Note about the Configuration tagging DetChar & PEM:
The CORNER_POP Beam Diverter is currently OPEN and When I leave tonight I will make sure to close the beam diverters, after saying "The Beam Diverters Are About To Close" in my best imitation of the verbalarams voice.
Beam Diverter close instructions for future self:
Sitemap -> LSC -> Beam_Diverters -> Corner -> Corner_POP close button.

The Dust mon in the Vac prep lab is still not working.

DetChar, PEM

H1 ISC - Updated DRMI locking trigger thresholds

thomas.shaffer@ligo.org — Tue, 17 Dec 2024 16:52:14 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81880

Sheila D, TJ

Recently we've been having very long DRMI acquisition times. Sheila remembered that this might have to do with her PR3 changes on Nov 18 (alog81329). Tony confirmed this with some sleuthing (alog81879). Looking at the height of the POP air inputs to the MICH, SRCL, and PRCL triggers, this has almost doubled since the change on Nov 18th. So, we bumped up the triggers for these in lscparams.py by double.

GRD, OpsInfo

H1 ISC - Comment to DRMI PRCL gain change

anthony.sanchez@ligo.org — Tue, 17 Dec 2024 16:31:01 -0800

Author: anthony.sanchez@ligo.org

Report ID: 81879

Using the Summary pages I was able to get a quick google sheet to give me before and after Histograms of how long ISC_LOCK was in DRMI 1F.

https://docs.google.com/spreadsheets/d/1xVmvYJdEq8GfKVcSzPj1fyeS95cIWrAkFjI23AxtsAQ/edit?gid=286373047#gid=286373047

First Sheet's data is before Nov 18th 2024, consisting of 100 gpstimes and durations where ISC_LOCK was in AQUIRE_DRMI_1F.
Second Sheet's data is After Nov 18th 2024. Consisting of 100 gpstimes and durations where ISC_LOCK was in AQUIRE_DRMI_1F

Interesting notes about ISC_LOCK.
ISC_Lock will request PRMI or Check MITCH Fringes some where between 180 seconds and 600 seconds, depending on how much light is seen on AS_AIR.
If AS_AIR sees flashes above 80 then ISC_LOCK will not kick us out of DRMI until 600 seconds.

So it looks like one of the changes that happened on or around Nov18th made the Flashes on AS_Air higher but we are still not actually locking DRMI.
We had fewer Aquire DRMI durations, over 180 Seconds before Nov 18th's changes.

Images attached to this report

H1 CDS - TW0 raw minute trend offload completed

david.barker@ligo.org — Tue, 17 Dec 2024 16:06:23 -0800

Author: david.barker@ligo.org

Report ID: 81881

WP12249

Jonathan, Dave:

The offloading of the past 6 months of raw minute trend files from h1daqtw0 SSD-RAID to permanent archive on HDD-RAID is completed.

nds0 restart	11:41 Mon 16dec2024
file copy	12:06 Mon 16dec2024 - 12:59 Tue 17dec2024	24hr 53min
nds0 restart	13:27 Tue 17dec2024
old file deletion	13:38 - 15:56 Tue 17dec2024	2hr 18min

TW0 raid usage went from 91% to 2%. Jonathan made the DAQ puppet change to configure nds0's daqdrc file with the new archive.

H1 CDS - DUST Monitor LAB2 not working

david.barker@ligo.org — Tue, 17 Dec 2024 14:36:47 -0800

Author: david.barker@ligo.org

Report ID: 81878

Currently Dust LAB2 is not working, 0.3u count is NaN, 0.5u count is flatline zero.

FRS32930

H1 PSL - Comment to FSS Autolocker Investigations

ryan.short@ligo.org — Tue, 17 Dec 2024 14:33:19 -0800

Author: ryan.short@ligo.org

Report ID: 81876

As part of my FSS work this morning (alog81865), I brought the State 2 delay down from 1 second to 0.5, and so far today every FSS lock attempt has been grabbed successfully on the first try. I'll leave in this "Band-Aid" fix until we find a reason to change it back.

H1 PEM - Comment to TCS-Y chiller is likely hurting Crab sensitivity

thomas.shaffer@ligo.org — Tue, 17 Dec 2024 14:16:35 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81875

The flow of the TCSY chiller was further reduced to 3.3gpm. This should push the chiller peak lower in frequency and further away from the crab nebula.

H1 CDS - Comment to Slow controls Beckhoff device issue

david.barker@ligo.org — Tue, 17 Dec 2024 13:13:13 -0800

Author: david.barker@ligo.org

Report ID: 81874

New CDS Overview has GREEN DEV1 when device count = 21, RED otherwise.

H1 PSL - PSL Status Report - Weekly

ryan.crouch@ligo.org — Tue, 17 Dec 2024 12:59:14 -0800

Author: ryan.crouch@ligo.org

Report ID: 81873

Laser Status:
    NPRO output power is 1.842W
    AMP1 output power is 70.15W
    AMP2 output power is 138.6W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 0 days, 2 hr 46 minutes
    Reflected power = 23.78W
    Transmitted power = 105.4W
    PowerSum = 129.2W

FSS:
It has been locked for 0 days 0 hr and 33 min
TPD[V] = 0.8228V

ISS:
The diffracted power is around 3.2%
Last saturation event was 0 days 0 hours and 33 minutes ago

Possible Issues:
PMC reflected power is high, its a little higher after the FSS/PMC work today

PSL

Images attached to this report

H1 ISC - SRY OLG measured

thomas.shaffer@ligo.org — Tue, 17 Dec 2024 12:56:29 -0800

Author: thomas.shaffer@ligo.org

Report ID: 81872

Sheila D, TJ

To help understand why we've been having inconsistent locking of SRY lately, Sheila and I took an OLG of SRCL with SRY locked this morning. I stopped ALIGN_IFO at WFS_CENTERING_SRY so it was locked but not fully aligned. Compared to the last reference (July 2018) that was on the template, things look a bit worse off. We plan to have someone look at this and try to tune the loop a bit better.

Images attached to this report

H1 General - LVEA swept

ryan.crouch@ligo.org — Tue, 17 Dec 2024 12:37:32 -0800

Author: ryan.crouch@ligo.org

Report ID: 81871

The LVEA has been swept, the FARO is left plugged in in the East bay.

H1 PSL - PSL FSS On-Table Alignment (WP 12250)

ryan.short@ligo.org — Tue, 17 Dec 2024 12:33:17 -0800

Author: ryan.short@ligo.org

Report ID: 81865

We've been seeing the FSS RefCav TPD signal dropping over recent weeks (not surprising for this time of year), so I went into the PSL enclosure this morning to tune up the FSS path alignment in advance of the holiday break.

To start, I attempted to touch up alignment into the PMC remotely using the picomotors right before it with the ISS off, but I wasn't able to get much of any improvement, so I turned the ISS back on and made my way out to the enclosure. Once there, I started with a power budget of the FSS path using the 3W-capable Ophir stick head:

FSS In: 280.4 mW
AOM In: 274.0 mW
AOM Out (single-pass): 180.3 mW
- SP Diffraction Efficiency: 65.8%
AOM Out (double-pass): 130.2 mW
- DP Diffraction Efficiency: 72.2%
EOM Out: 129.2 mW

The largest (and least surprising) area of power loss I noticed was in the AOM diffraction efficiencies, so I started there. I adjusted the AOM stage itself, mostly in pitch, to improve the single-pass, and M21 to improve the double-pass. I also checked that the beam was passing nicely through the FSS EOM (it was, no adjustment needed here). The final power budget:

FSS In: 280.4 mW
AOM In: 274.0 mW
AOM Out (single-pass): 195.9 mW
- SP Diffraction Efficiency: 71.4%
AOM Out (double-pass): 139.5 mW
- DP Diffraction Efficiency: 71.2%
EOM Out: 138.6 mW

Having made good improvements, I proceeded to adjust M23 and M47, the picomotor-controlled mirrors before the RefCav, to align the beam back onto the alignment iris at the input of the RefCav. That done, I then instructed the FSS autolocker to lock the RefCav. As seen before and noted most explicitly in alog81780, the autolocker could briefly grab the TEM00 mode but then lose it. I lowered the autolocker's State 2 delay (which determines how long to wait before turning on the temperature control loop after finding resonance) from 1.0 seconds to 0.5, and the autolocker was immediately successful. I've accepted this shorter delay time in SDF; screenshot attached. The TPD was reporting a signal of 0.515 V with the RefCav locked, so I used the pictomotors to improve alignment, finishing with a TPD signal of 0.830 V.

Seeing the beam spot on the RefCav REFL camera was now more than half out of view, I rotated the camera in its mount slightly to center the image. I then unlocked the FSS and used M25 to tweak up the alignment onto the RFPD, improving the voltage when using a multimeter from 0.370 V to 1.139 V, then locked the FSS again to get an RFPD voltage of 0.213 V. This gives a visibility of the RefCav of 81.3%. I wrapped up in the enclosure, turned the environmental controls back to science mode, and returned to the control room. After about an hour while maintenance activities were finishing, I turned the ISS back on; currently diffracting around 3.3%.

This closes WP 12250.

Images attached to this report

H1 GRD - minor edit to ALS arm guardians

sheila.dwyer@ligo.org — Tue, 17 Dec 2024 12:32:47 -0800

Author: sheila.dwyer@ligo.org

Report ID: 81870

While Oli was ding initial alignment, I saw that the Y arm guardian was in the state ENABLE_WFS although the arm wasn't locked and wasn't well enough aligned to lock. looking at the code, there was no check that the arm was locked before the locking state returned true, it only checks for errors. I've changed the return true to happen if H1:ALS-Y_REFL_LOCK_STATUS = 1

After doing this I caused an issue by trying to cycle through these states while the INIT_ALIGN guardian was still managing the arm guardians. The X arm had already run the WFS and completed, but the initial alignment guardian saw that it wasn't locked, and requested it to scan_alignment. Perhaps this check could be made to only happen if the arm hasn't already offloaded, or if the arm has been in the locking state for a certain amount time.

H1 CDS - Comment to Slow controls Beckhoff device issue

david.barker@ligo.org — Tue, 17 Dec 2024 12:18:23 -0800

Author: david.barker@ligo.org

Report ID: 81869

Robert has powered down the chamber illuminator control chassis in the LVEA. This chassis permits remote control of the chamber illuminators via ethernet, which is not needed during O4. There is a worry that these chassis, even when in stand-by mode, could be a source of RF noise.

On the CDS overview I will change DEV1's display logic to be GREEN if the dev count is 21 of 23 and RED if any other value.

H1 CDS - Slow controls Beckhoff device issue

david.barker@ligo.org — Tue, 17 Dec 2024 11:41:52 -0800

Author: david.barker@ligo.org

Report ID: 81867

Fil, Fernando, Patrick, Dave:

We are investigating a Beckhoff device error on the CS-AUX PLC, DEV1 on the CDS Overview. Device went into error at 11:21 PST.

Images attached to this report

H1 PEM - Comment to TCS-Y chiller is likely hurting Crab sensitivity

camilla.compton@ligo.org — Tue, 17 Dec 2024 11:34:58 -0800

Author: camilla.compton@ligo.org

Report ID: 81866

TJ touched the CO2 flow on Dec 12th around 19:45UTC 81791 so the flowrate further reduced to 3.55 GPM. Plot attached.

TCS

Images attached to this report

H1 TCS - CO2 Lasers Spectrum Locked vs Unlocked

camilla.compton@ligo.org — Tue, 17 Dec 2024 10:29:50 -0800

Author: camilla.compton@ligo.org

Report ID: 81863

Looked at the spectum of th 50W CO2 lasers on the fast VIGO PVM 10.6 ISS detectors when the CO2 is locked (using the laser's PZT) and unlocked/ free running: time series attached. Small differences <6Hz, see spectrum attached.

The filter banks suggest that the _OUT signals used have been converted from counts to volts and de-whitened. Looking at the spectrum 50Hz -1kHz and using the DC level of 7e-3, we get a RIN of 4.5e-9 / 7e-3 = 6 x 10^-7.

This is better than the L5L free running RIN of 10^-5 at 100Hz and 10^-6 at 1kHz measured in CIT#389

Images attached to this report

LHO VE - Tue CP1 Fill

david.barker@ligo.org — Tue, 17 Dec 2024 10:08:33 -0800

Author: david.barker@ligo.org

Report ID: 81864

Tue Dec 17 10:02:58 2024 INFO: Fill completed in 2min 56secs

Quick fill, coincident with dewar filling.

Images attached to this report

H1 General - Range drop before lockloss at 11:34UTC could have been due to unknown glitches

camilla.compton@ligo.org — Tue, 17 Dec 2024 08:45:43 -0800

Author: camilla.compton@ligo.org

Report ID: 81862

Ryan S noticed that the range drop before the lockloss at 11:34UTC could be related to the glitches we've been seeing as Omicron sees similar glitches screenshot. DARM looks worse 30-100Hz plot.

Besfreo the lockloss we see a 26-28Hz wobble in DARM (not in the other LSC loops) plot.

Lockloss

Images attached to this report

H1 General - OPS TUES Day Shift Start

camilla.compton@ligo.org — Tue, 17 Dec 2024 07:37:13 -0800

Author: camilla.compton@ligo.org

Report ID: 81861

TITLE: 12/17 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.39 μm/s
QUICK SUMMARY:

IFO re-locked itself twice overnight and is currently running magnetic injections before we start maintenance activities.

Slight strangeness that the IFO mode was in "relocking" H1:ODC-OBSERVATORY_MODE = 21 when I arrived.

LHO General - OPS Eve Shift Summary

ibrahim.abouelfettouh@ligo.org — Mon, 16 Dec 2024 22:00:26 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 81860

TITLE: 12/17 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
LOG:

IFO is in INITIAL_ALIGNMENT and ENVIRONMENT

Still recovering from the 7.4 EQ today in Vanuatu. After this, there were many 5+ Mag aftershocks and our primary microseism is still above the 0.1 line. We briefly left EQ mode for 5 or so minutes before another earthquake (Atlantic Ocean this time) caused us to reactivate.

I began locking at 05:22 UTC and managed to get to PRMI but had no flashes. A few minutes later, another EQ hit and we lost lock. At this point, I started initial alignment. I believe IFO will be able to lock very soon since seismic conditions are coming down quickly.

Lockloss Alog 81859

Other:

As the pacific plate shook, Robert took the time to conclude his viewport work, meaning we are capable of transitioning to LASER SAFE once again. I have informed the morning operator independently too.

H1 PEM - Lockloss 01:58 UTC

ibrahim.abouelfettouh@ligo.org — Mon, 16 Dec 2024 18:07:39 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 81859

Interesting LL that happened between the detection of a 7.4 mag EQ but before any picket fence or STS detection. So I don't think it's EQ caused but seems suspicious. Either way, we're riding out a huge EQ right now and will attempt locking afterwards.

Lockloss

H1 SUS - Comment to In-Lock SUS Charge Measurements for December 10th FAMIS

camilla.compton@ligo.org — Mon, 16 Dec 2024 16:44:57 -0800

Author: camilla.compton@ligo.org

Report ID: 81858

Checked that the measurements for ITMX bias are running and the same magnitude for bias in and bias off. They are at a lower magnitude than the quadrant injection on the ESDAMON/LVEASDAMON so we could think about increasing the magnitude if we are not happy with the 81688 no charge build-up on the test mass conclusion. We also still have a pending "to do" from Vlad in 79597: explicitly cast DARM data to np.float64

Images attached to this report

LHO General - Mon DAY Ops Summary

corey.gray@ligo.org — Mon, 16 Dec 2024 16:32:16 -0800

Author: corey.gray@ligo.org

Report ID: 81841

TITLE: 12/16 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:

Today H1 has been locked the entire shift (over 18hrs!) with the main activity being H1 out of Observing for the Monday Commissioning work (which went 30min over for the period of 1630-2006utc).

Microseism has mostly been flat just under the 95th percentile.
LOG:

Vacuum Prep's Dust Monitor (H1:PEM-CS_DUST_LAB2) continues to alarm on the Alarm Handler (white/invalid alarm) & comes up as NOT OK/Error on the Dust_Monitor script check.

1615-1632 optics lab/vacuum prep cleaning (karen)
- 1645-1715 PCal cleaning w/ Tony escort (karen)
- 1720-1833 MY cleaning (karen)
1628-1717 MX cleaning (kim)
1630-2006 MONDAY COMMISSIONING!!!!
- 1630-1720 no-squeezing measurements (camilla)
- 1635 viewport work which includes removing PR2 camera---Dave was on top of this asking what happened to it. (robert)
  - LVEA is HAZARD and for Robert's work there is aluminum foil covering the viewports he was working on (if there is a lockloss, he can reinstall the viewport covers). Tomorrow at the start of Maintenance
- Commissioning extended 30+min for L1 & H1.
1942 Beginning to make free disk space via nds0 over next multiple days--will not affect work in control room (dave via WP#12249)
1944-2052 Working on Tractor Tire near water tank (tyler, les schwabb)
2213-2220 Measurements in PCal Lab (tony)
2253-2255 Receiving roll-up (christina)
2335 Closing a Mechanical Room HVAC fan door which was ajar---RyanS/Jason noticed it (tyler)

H1 SEI - ISI CPS Noise Spectra Check Weekly FAMIS

oli.patane@ligo.org — Mon, 16 Dec 2024 16:18:53 -0800

Author: oli.patane@ligo.org

Report ID: 81857

Closes FAMIS#26020, last checked 81715

Things to note:

On HAM7 around 50 Hz, V1/V2/V3 have a large spike that wasn't there last week
On ITMX Stage1, new spike in V3 around 48 Hz
On ITMY Stage1, new spike in V2/V3 around 48 Hz
On BS Stage1, new spike in V2/V3 around 48 Hz
On ETMX Stage2, V2/V3 spike at 30 Hz is a bit larger

Non-image files attached to this report

CPS_spectra_15:27-12_16_2024.pdf

LHO General - OPS Eve Shift Start

ibrahim.abouelfettouh@ligo.org — Mon, 16 Dec 2024 15:59:40 -0800

Author: ibrahim.abouelfettouh@ligo.org

Report ID: 81856

TITLE: 12/16 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.36 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 6:34 UTC (17hr 30 min lock!)

Environment looks good.

H1 CDS - Comment to NDS0 restarted as part of TW0 raw minute trend offload

david.barker@ligo.org — Mon, 16 Dec 2024 15:19:50 -0800

Author: david.barker@ligo.org

Report ID: 81855

At time of writing copy is 32/256 dirs copied, which gives an ETA around 13:00 tomorrow, Tue 17th Dec.

H1 ISC - Comment to pico'd on POP QPDs

david.barker@ligo.org — Mon, 16 Dec 2024 15:18:39 -0800

Author: david.barker@ligo.org

Report ID: 81854

FRS32910

H1 SUS - Checking last large earthquake to confirm no acquired charges on test masses

oli.patane@ligo.org — Mon, 16 Dec 2024 13:09:07 -0800

Author: oli.patane@ligo.org

Report ID: 81853

Back on December 05th 2024 we had a really large earthquake come through from northern California. This large nearby earthquake reminded Sheila of an old script that checked to see if the test masses had acquired any charge from hitting an earthquake stop during an earthquake. This script had been used to discover hysteresis after particularly large earthquakes in 2017 (37799) and in 2020 (55880). We decided it would be a good idea to check for this earthquake, so we wrote a quick python script move_all_quads_pitch.py that changed the OPTICALIGN pitch for 110 seconds before moving everything back. I then took the matlab script from 2020, check_hysteresis_2020.m and edited the times and channels so that it would grab minute trends for the DAMP_IN and COILOUTF_OUT channels for the week leading up to the earthquake, and then grabbed raw trends for those same channels after the earthquake and during the period of time where we had moved the OPTICALIGN pitch. I plotted the OSEM readings (DAMP_IN) versus the applied force (COILOUTF_OUT) for both times against each other for each test mass and got this plot. Looking at this in addition to the pitch drift plots from the summary pages(ITMX, ITMY, ETMX, ETMY), it doesn't look like any of the test masses encountered any hysteresis as a result of any earthquake stop hits.

All these scripts and results can be found in userapps/sus/h1/scripts/check_hysteresis_after_EQ and have been committed to svn.

Images attached to this report

H1 SQZ - Comment to SQZ vs No SQZ, FC Beam spot control Enabled

camilla.compton@ligo.org — Mon, 16 Dec 2024 12:15:29 -0800

Author: camilla.compton@ligo.org

Report ID: 81852

While other work was going on, I tried the sqz/h1/scripts/SCAN_PSAMS.py script from 81516, this time with the SQZ ASC turned back on each time. I turned up the ASC gain to 1.5 and shuffled the wait times so that the ASC converges before the data is taken. We should test it again on a subset of PSAMS settings before starting a long scan. Each setting takes 4-5 minutes. Eg. 3 ZM4 settings and 3 ZM5 settings in 'PSAMS_ZM4/5_LIST' would take ~ 9 total settings x 5 minutes each = around 45 minutes. Each setting still scans the sqz angle, but the best angle didn't change much ~187 to 192deg with ZM4/5 changing 0.4V so we could try to leave SQZ_ANG_ADJUST running and remove the scan sqz ang step.

H1 TCS - Some ETMX HWS signal after replacing fiber collimator last week

camilla.compton@ligo.org — Mon, 16 Dec 2024 12:03:02 -0800

Author: camilla.compton@ligo.org

Report ID: 81851

After TJ and I replaced the fiber collimator for the ETMX HWS signal last week, we can see some believable ETMX HWS signals. Ther is still something strange happening as we power up (maybe retroflections off ITM before we move spots), but once we reach 60W we can see the test mass change curvature as expected. See attached ETMX signals at 3 minutes, 5 minutes, 20 minutes and trends. We don't expect this HWS signal to be accurate as have done no calculating of the mode matching after we removed a lens in 81734 but we took the data to do so.

There's a dead pixel we should remove but the code has an error "Plotting error: Object Array cannot be loaded when allow_pickle= False" that's not letting me see the Original image.

Images attached to this report

H1 ISC - pico'd on POP QPDs

sheila.dwyer@ligo.org — Mon, 16 Dec 2024 12:02:52 -0800

Author: sheila.dwyer@ligo.org

Report ID: 81849

Camilla, Sheila

We pico'd to center on the POP QPDs, which we were falling off. POP A QPD is used during DRMI ASC, we had been using a large offset. Now in full lock POPA is centered, and in the sdf safe and observe files I've accepted turning off the offset and setting it to 0.

We also noticed a bug with the picomotor code, which is that if someone changes the current motor while the H1:SYS-MOTION_C_PICO_A_INUSE (yellow box on medm) is showing, the current motor channel changes and the medm makes it look like the current motor has changed, but clicking will move the wrong motor. The second screenshot shows this happening, at the time of thei first time cursor, the current motor was 6 but motor 5 was moving.

Images attached to this report

H1 CDS - NDS0 restarted as part of TW0 raw minute trend offload

david.barker@ligo.org — Mon, 16 Dec 2024 11:55:40 -0800

Author: david.barker@ligo.org

Report ID: 81850

WP12249

In preparation for the TW0 raw minute trend offload of data accumulated since 18th June 2024 (6 months) TW0 was configured to freeze the old data and write to a new location and NDS0 was configured to serve the past 6 months a trends from their temporary location.

NDS0 DAQD was restarted at 11:41 PDT. This is not the default NDS, so it should have had no impact on control room or FOM.

H1 ISC - Tried SRCL ASC and LSC offsets again, decided not worth continuing

camilla.compton@ligo.org — Mon, 16 Dec 2024 10:56:29 -0800

Author: camilla.compton@ligo.org

Report ID: 81848

Shiela and I put back in the SRCL ASC and LSC offsets we found in 81792 to maximize thew coupled cavity poll. Again, the range didn't increased, the FCC increased ~3HZ but hkappa_C decreased ~0.5%. We planned to improved OMC alignment to bring back up the range and kappa_C. Plot attached.

We started repeating the OMC ASC injections form 78616, but this saturated the OMC SUS so we aborted and decided that any gains made would be very small and not worth the time. Reverted SRCL ASC and LSC offsets.

Images attached to this report

LHO VE - Mon CP1 Fill

david.barker@ligo.org — Mon, 16 Dec 2024 10:20:30 -0800

Author: david.barker@ligo.org

Report ID: 81847

Mon Dec 16 10:15:30 2024 INFO: Fill completed in 15min 27secs

Gerardo confirmed a good fill curbside.

Images attached to this report

H1 SQZ - SQZ vs No SQZ, FC Beam spot control Enabled

camilla.compton@ligo.org — Mon, 16 Dec 2024 10:17:06 -0800

Author: camilla.compton@ligo.org

Report ID: 81843

Sheila, Camilla

In 81760 we saw that SQZ was adding noise 20-40Hz. I repeated today FDS and no sqz and don't see the same added noise, only a very small amount around 20Hz. See attached (4 minute 0.1Hz average). We're not sure what would be changing. It's possible that the range correlates with FC beamspot, see attached plot. This morning Sheila showed that the ~5MPc drift in the range during the last locks is mainly around 20-40Hz dtt.

I re-enabled FC beamspot control plot as in 80970, edited sqzparams, reloaded SQZ_FC and accepting sdfs. We have not checked the offsets.

Images attached to this report

H1 DetChar - injections

sheila.dwyer@ligo.org — Mon, 16 Dec 2024 10:15:11 -0800

Author: sheila.dwyer@ligo.org

Report ID: 81846

Sheila, Brice

Brice asked for some injections to check for bicoherence, and to check the bicoherence code that his group is working on.

At 17:49 UTC we injected into LSC-DARM2 at 3e-2 counts at 23Hz and 25 Hz, and 1e-2 at 48 Hz. (red 4 +5)

At 18:00:30-18:04 UTC we injected into LSC-MICH1 at 25 Hz at 3e-3 counts, LSC-SRCL1 at 23 Hz at 3e-3, and LSC DARM2 at 48 Hz amplitude 1e-2. (ref 6-8)

At 18:10 UTC we injected into LSC-SRCL at 23 Hz at 3e-3, and ASC-DHARD_P at 25 Hz, and LSC-DARM2 at 48 Hz at 1e-2.

Template is saved at /sheila.dwyer/Noise/line_injections/line_injections_dec16_2024.xml

LHO General - Comment to OPS Eve Shift Summary

david.barker@ligo.org — Mon, 16 Dec 2024 09:23:31 -0800

Author: david.barker@ligo.org

Report ID: 81845

FRS32903 has been created for cdsxegw0 power supply issue and closed as resolved.

H1 PSL - PSL 10-Day Trends

ryan.short@ligo.org — Mon, 16 Dec 2024 09:20:10 -0800

Author: ryan.short@ligo.org

Report ID: 81844

FAMIS 31064

The PMC mode-matching check done in the enclosure last Tuesday is clearly seen on many trends.

PMC REFL is still steadily increasing along with a steadily decreasing RefCav TPD and ISS diffracted power percentage. It's possible this is due to alignment drifting into the PMC, so if time allows during maintenance tomorrow, I'll try an alignment adjustment along with the already planned FSS path tuneup.

Images attached to this report

LHO General - Comment to OPS Eve Shift Summary

jonathan.hanks@ligo.org — Mon, 16 Dec 2024 09:07:35 -0800

Author: jonathan.hanks@ligo.org

Report ID: 81842

I noticed the alarm tone as well while visiting the MSR. Upon investigation it was a failed power supply on the CDS external EPICS gateway machine. I replaced the power supply with a spare. The alarm tone is gone.

LHO General - Mon DAY Ops Transition

corey.gray@ligo.org — Mon, 16 Dec 2024 07:40:51 -0800

Author: corey.gray@ligo.org

Report ID: 81840

TITLE: 12/16 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 7mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.31 μm/s
QUICK SUMMARY:

H1's been locked 9.25+hrs and microseism is just touching up on the 95th percentile. Rainy drive on the way in.