Displaying reports 1-20 of 85646.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 21:59, Tuesday 18 November 2025
LHO General (VE)
ryan.short@LIGO.ORG - posted 21:59, Tuesday 18 November 2025 (88166)
Ops Eve Shift Summary

TITLE: 11/19 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

H1 had a lockloss from an unknown source early on in my shift, but after an alignment, relocking went easily. Since then, I've been tuning magnetic injection parameters to be used later this week. Also had an alarm for an annulus ion pump at the Y-arm BTM, so I phoned Travis as I was unsure how critical this was. He took a look into it and believes addressing this can wait until morning.

I've set the remote owl operator so that H1 will relock overnight if it unlocks for some reason so that it's ready to go in the morning, but no calls will be made for help. H1 will also start observing, if it can, on the off-chance there's a potential candidate signal.

Sheila has started a script to change the SQZ angle while in frequency independent squeezing, which should take about 90 minutes and will put settings back to nominal when done, at which point H1 should go into observing.

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 21:58, Tuesday 18 November 2025 (88167)
sqz data set FIS, nominal psams, script left running

unamplified seed: 0.0055 amplified seed: 0.052, deamplified: 0.00073 NLG = 9.45, seems too small

no sqz: 1447564297 - 1447565492
reduced seed, adjusted temp: amplified max:0.00547 minimum 8.3e-5, unamplified: 2.54e-4 NLG 21.5

FIS, ran scan sqz angle kHz, CLF 6 demod phase left at 149.7 degrees. 1447566037

I started the script to scan squeezing angles with FIS, Ryan Short gave me a pointer on how to have my script change guardian states (puts SQZ ANGLE SERVO to IDLE now).  It is set up to try the current angle +/-10 degrees, run through a bunch of angles in 20 degree steps, flip the CLF sign and run through angles again.  When finished it should request frequency dependent squeezing again and Ryan has set things up so the IFO should go to observing when that happens.  

H1 DAQ
jonathan.hanks@LIGO.ORG - posted 17:48, Tuesday 18 November 2025 (88165)
WP 12886 Reconfigure daqd systems on the DAQD 0 leg for ECR E2500314

Jonathan, Dave, Erik, Richard,

As per WP 12886 we reconfigured the DAQD 0 computers.  The goal was to combine the functionality of the data concentrator (DC0) and frame writer (FW0) into one machine, consolidating them to one machine.  This then frees up the other machine for use with pushing data into the NGDD (Next Generation Data Delivery) kafka brokers in LDAS.

At this point h1daqdc0 is no longer the data concentrator.  H1daqfw0 is the data concentrator + frame writer.

This required a few other changes:

Once this work was done and h1daqfw2 was shown to be producing identical frames to h1daqfw[01] work was able to move onto the consolidation.

The basic steps:

the H1:DAQ-DC0 epics variables are used in many places, so Dave and Jonathan configured h1daqfw0 to output H1:DAQ-DC0 epics variables, and put a small IOC together to output the set of H1:DAQ-FW0 variables we need.  This is an area we need to revisit.  One likely approach is to make use of a feature in cps_recv that outputs the daqd STATUS, CRC_CPS, CRC_SUM variables and then to move the daqd on FW0 back to outputing the FW0 variables.

This work validates that we can combine the DC and FW computers into one.

The next step is to turn the old DC machine into the producer for NGDD data.  We will run the fiber to connect it through to LDAS later this week and work on setting that system up.

My checklist for this is in the DCC https://dcc.ligo.org/T2500385

LHO General
ryan.short@LIGO.ORG - posted 15:46, Tuesday 18 November 2025 (88164)
Ops Eve Shift Start

TITLE: 11/18 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 13mph Gusts, 9mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.47 μm/s 
QUICK SUMMARY: H1 has been locked for almost 2 hours and team PEM is running measurements.

LHO General
thomas.shaffer@LIGO.ORG - posted 15:42, Tuesday 18 November 2025 (88152)
Ops Day Shift End

TITLE: 11/18 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Happy end to O4! After 4 hours of maintenance today, we relocked mostly automatic with one hiccup in the SQZ_FC guardian that was using a DC0 GPS channel that temporarily didn't exists due to the 0-leg data concentrator work that is still on going. We have been locked for almost 2 hours now and the PEM team is at work running end of run characterization.
LOG:

Start Time System Name Location Lazer_Haz Task Time End
15:37 FAC Randy Yarm n BTE sealing MY -> CS 22:54
16:00 VAC Norco EY n LN2 fill 18:51
16:20 VAC Norco MY n LN2 fill CP3 - fill complete 20:46
16:20 FAC Erik EX n Glycol inspect 16:45
16:34 CDS Fil LVEA n JAC cable pull from CER to HAM1 20:01
16:35 SUS Ryan C CR/EY/EX n SUS oplev charge meas. 18:51
16:36 FAC Tyler CS, Mids n 3IFO checks 18:06
16:39 VAC Travis, Jordan EY n Purge air line work 18:32
16:43 VAC Gerardo CS n Run purge air 19:16
16:47 FAC Nellie, Kim LVEA n Tech clean 18:12
16:54 CDS Marc LVEA n Joining Fil in the cable pulling 20:04
17:19 PEM Robert, Sam, Genevieve LVEA n Move a shaker 18:49
17:43 CDS Richard LVEA n Check on the HAM1 cable pull 18:05
17:47 PROP Christina EY n Check at EY 18:17
18:04 VAC Travis, Gerardo EX n Turning on compressor 19:20
18:12 FAC Nellie EY n Tech clean 19:12
18:12 FAC Kim EX n Tech clean 19:53
18:50 PEM Sam LVEA n Taking pictures 18:59
19:31 FAC Kim FCES n Tech clean 20:00
19:32 VAC Travis EX n Turn compressor off 19:51
19:49 PSL Jason CR n Ref cav tweak 20:00
20:01 PEM Robert LVEA n Setup meas. 20:46
20:16 SUS Oli CR n IFO quiet time 20:27
20:16 PEM Ryan S CR n PEM mag inj 22:05
20:28 PEM Sam LVEA n More pictures 20:31
21:04 ISC Daniel CER n Picture 21:08
H1 DetChar (DetChar)
emmanuelalejandro.avila@LIGO.ORG - posted 15:31, Tuesday 18 November 2025 (88163)
Data Quality Shift Report 2025-11-10 to 2025-11-10

Link to report here.

Summary:

H1 IOO
daniel.sigg@LIGO.ORG - posted 12:38, Tuesday 18 November 2025 (88162)
JAC electronics chassis

We started installing electronics chassis for JAC:

Still missing:

The necessary coax cables were also installed and terminated where possible.

H1 PSL
jason.oberling@LIGO.ORG - posted 11:59, Tuesday 18 November 2025 (88161)
PSL FSS RefCav Remote Beam Alignment Tweak

The RefCav Refl spot was off this morning and the TPD had been trending down the last several days, so I took the opportunity to tweak the beam alignment into it from the Control Room.  The ISS was ON for this work.

When I started the RefCav TPD was ~0.520 V and when I finished the TPD was ~0.548 V.  I then noticed the ISS was diffracting ~4.5%, which is higher than its norm, so I adjusted the ISS RefSignal to -2.01 V from -2.00 V.  This brought the diffracted power % down to around its normal value of ~4%.  At this diffraction % the RefCav TPD is now ~0.550 V and the PMC Trans is now ~106.9 W.

H1 SUS (SUS)
ryan.crouch@LIGO.ORG - posted 11:00, Tuesday 18 November 2025 (88157)
OPLEV charge measurements, ETMX, ETMY

I took the OPLEV charge measurements for both the ends this morning. I noticed that both of the scripts leave the L3 bias offset switch off when its should be on.

I ran into the same issue as had previously with ETMX constantly saturating no matter what amplitude I used. Jeff suggested I look at the biases and see if they're correct, the biases used for ETMX were [-9, -4, 0, 4, 9] and I changed them to [-8. -4. 0. 4. 8] in ESD_Night_ETMX.py which stopped the overflows. The L3 bias offset on ETMX is -8.9 while we're DOWN, as soon as the bias is changed to -9 I started seeing overflows. Before I changed the bias offset I was trying some different amplitudes and I was getting overflows at what looked like ~10/15k/sec for everything, i ctrl+ced out a measurement and saw that the overflows did not stop, which lead me to chech the L3 bias offset where had not correctly restored it to -8.9 as its supposed to. After changing the L3 bias offset list in the measurement code I then had to fine tune the amplitude after starting low. Amplitudes of 10000, 12000, and 20000 weren't enough, I ended up at 100,000 which gave me the best measurement I've seen in months. LR did still have some big error bars, the charge is high on LR, and UR but looks low at UL and LL, and the recent trend actually looks to be decreasing, looking at the year long trend it actually looks fairly stable considering the massive error bars on a lot of the measurements. Every quadrant is under + 100 [V].

 

ETMY also initially had some saturations but reducing the gain by 20% stopped them and still yielded good coherence. ETMY's charge is slightly high, it's just under + 100 [V] on 2/3 of the quadrants, UR is the only quadrant below +/- 50 [V], it has risen since May, but zooming out to the whole year it doesn't look to have much of a trend, May wasn't a great measurement.

Images attached to this report
H1 ISC
matthewrichard.todd@LIGO.ORG - posted 10:58, Tuesday 18 November 2025 (88155)
Summary Table of OMC Scan and Gouy Phase measurements

M. Todd, J. Wright, S. Dwyer


Here is my attempt to summarize as many of the OMC scan measurements of the input beam overlap with the OMC mode, as well as PRC and SRC gouy phases -- all at different thermal states.

Measurement Time Test Masses CO2 [W] Ring Heater (per segment) [W] SR3 [W] OM2 [W] FOM aLOG
OMC Scan - Single Bounce off of ITMY 1443895154 Cold 0 0 0 0 Mismatch = 8.3% 87461
OMC Scan - Single Bounce off of ITMX 1443894875 Cold 0.45  0 0 Mismatch = 10.4% 87461
OMC Scan - Single Bounce off of ITMY 1443889943 Cold 1.7 0 0 0 Mismatch = 10.3% 87461
OMC Scan - Single Bounce off of ITMX 1443894875 Cold 1.7  0.45  0 0 Mismatch = 13.5% 87461
OMC Scan - Single Bounce off of ITMY 1431450536 Cold 0 0 5 0 Mismatch = 7.6% 85661
OMC Scan - Single Bounce off of ITMY 1403543046 Cold 0 0 0 4.6 Mismatch = 6.6% 78701
OMC Scan - Single Bounce off of ITMX 1431449762 Cold 0 0.45 5 0 Mismatch = 9.6% 85661
OMC Scan - Single Bounce off of ITMY 1431474471 Cold 0 0 5 4.6 Mismatch = 3.1% 85698
OMC Scan - Single Bounce off of ITMX 1431474101 Cold 0 0.45 5 4.6 Mismatch = 5.1% 85698
OMC Scan - Single Bounce off of ITMY 1444515634 Hot-ish 1.7 0 0 0 Mismatch = 7.1% 87461
OMC Scan - Single Bounce off of ITMX 1444515312 Hot-ish 1.7 0.45 0 0 Mismatch = 8.9% 87461
OMC Scan - SQZ Beam 1446952255 - - - - 4.6 Mismatch = 6.8% 88060
OMC Scan - SQZ Beam 1447088389 - - - - 0 Mismatch = 2.8% 88088
Gouy Phase - PRC 1255227492 Cold ITMY = 0.9, ITMX = 0.8 ITMY = 1.4, ITMX = 0.5 0 0 OneWay Gouy Phase = 23.2 [deg] 52504
Gouy Phase - PRC 1354415805 Cold 0 0 0 0 OneWay Gouy Phase = 20.7 [deg] 66215
Gouy Phase - SRC 1354410195 Cold 0 0 0 0 OneWay Gouy Phase = 19.9 [deg] 66211
Gouy Phase - SRC 1255907203 Cold ITMY = 0.9, ITMX = 0.8 ITMY = 1.4, ITMX = 0.5 0 0 OneWay Gouy Phase = 25.5 [deg] 52658
Gouy Phase - SRC 1255829128 Cold ITMY = 0.9, ITMX = 0.8 ITMY = 1.4, ITMX = 0.5 4 0 OneWay Gouy Phase = 29 [deg] 52641

 

LHO VE
david.barker@LIGO.ORG - posted 10:31, Tuesday 18 November 2025 (88158)
Tue CP1 Fill

Tue Nov 18 10:11:33 2025 INFO: Fill completed in 11min 30secs

 

Images attached to this report
LHO FMCS (PEM)
anthony.sanchez@LIGO.ORG - posted 09:02, Tuesday 18 November 2025 (88154)
Checking HVAC Fans

Famis 27573 Vibration Sensors To Gauge Health Of HVAC Fans Site 

H0:VAC-MR_FAN6_170_1_ACC_INCHSEC seem to be going up in that few days especially the last 24 hours.
This is also the case for H0:VAC-MY_FAN2_270_2_ACC_INCHSEC in the last day saw a fairly large increase in noise.

Images attached to this report
H1 CDS
thomas.shaffer@LIGO.ORG - posted 08:24, Tuesday 18 November 2025 (88153)
h1guardian1 machine rebooted

1616UTC rebooted the h1guardian1 machine. This was originally to switch over nds1, but Erik informed me that we had already done this some time ago. Since we already had a WP in and this seemed like a good time to do it, I went for a reboot anyway.

All nodes came back up on their own, no issues seen.

 

LHO General
thomas.shaffer@LIGO.ORG - posted 07:32, Tuesday 18 November 2025 - last comment - 10:42, Tuesday 18 November 2025(88151)
Ops Day Shift Start

TITLE: 11/18 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Calibration
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.46 μm/s 
QUICK SUMMARY: Locked for 22 hours, SUS charge and PEM mag. injections running now. Maintenance today, then PEM measurements for the rest of the week, because....

O4C will end in 30 minutes. What a great run! Well done everyone!!

Comments related to this report
david.barker@LIGO.ORG - 09:38, Tuesday 18 November 2025 (88156)

I have updated the "o4" program for end of run.

              O4 started: 2023-05-24 08:00:00.000000 PDT [1368975618]
              O4   ended: 2025-11-18 08:00:00.000000 PST [1447516818]
                     now: 2025-11-18 09:36:41.000000 PST [1447522619]

               O4A_START: 2023-05-24 08:00:00.000000 PDT [1368975618]
                 O4A_END: 2024-01-16 08:00:00.000000 PST [1389456018]
               O4B_START: 2024-04-10 08:00:00.000000 PDT [1396796418]
          O4B_VENT_START: 2024-07-17 11:52:00.000000 PDT [1405277538]
            O4B_VENT_END: 2024-08-12 12:37:00.000000 PDT [1407526638]
                 O4B_END: 2025-04-01 08:00:00.000000 PDT [1427554818]
            O4C_STARTGPS: 2025-06-11 08:00:00.000000 PDT [1433689218]
                  O4_END: 2025-11-18 08:00:00.000000 PST [1447516818]
 

david.barker@LIGO.ORG - 10:41, Tuesday 18 November 2025 (88159)

DC0 is down now as part of the DAQ 0-leg upgrade. Its GPS EPICS channels was being used by many systems on the CDS Overview MEDM screen, resulting in a lot of purple boxes. I've switch these over to DC1 and restarted the nuc20 FOM. If you have purple boxes on your CDS Overviews, please restart them.

david.barker@LIGO.ORG - 10:42, Tuesday 18 November 2025 (88160)

VACSTAT is currently in the "NOT OK" condition due to missing DC0. I'll upgrade it later when Jonathan gets identical frames on the frame writers.

H1 TCS
matthewrichard.todd@LIGO.ORG - posted 23:06, Monday 17 November 2025 (88148)
Comparing models to measurements of TCS values

M. Todd, S. Dwyer


I've been polishing up the analysis of models estimating the various couplings of TCS powers to substrate and surface defocus in the test masses. This can be used to test the validity of the HWS estimate of the absorption in the ITMs. For reference, assuming the HWS are correct in their calibration of what the substrate defocus is in the test masses [ITMY = 63.5uD, ITMX = 54.5uD], and that my model is right for the coupling of substrate defocus from absorbed Watts of arm power [250 uD/W], then we have rougly 254mW of absorbed power in ITMY and 218mW of absorbed power in ITMX. Naively this seems too much, but I wanted to see if this could be consistent with measurements of the arm cavity Gouy phase.

Surface Defocus from Ring Heaters -- Models and Measurements

From both models and measurements, we have a much better idea now of how the ring heaters couple into test mass surface defocus. Fitting the HOM spacing in the YARM as a function of different ETMY ring heater powers, we obtain an estimate of the coupling factor of ETM ring heater power to surface defocus [1.53 +/- 0.2 uD/W]. The SQZ dataset which was taken at 2W, can be used to estimate the ring heater coupling as well because the HOM spacing of the YARM is purely the combination of the completely cold RoC (from galaxy) from the test masses plus the defocus from the ETMY ring heater (assuming negligible defocus from absorbed arm power) . The YARM cavity g-factor in the 2W state with ETMY ring heater on (2.93W) is calculated to be 0.8345. The cold cavity g-factor (without ring heaters or absorbed power) is calculated to be 0.8235. This yields a coupling factor (again, assuming negligible defocus from absorbed arm power) of ETM ring heater to surface defocus of 1.77 uD/W , which is almost within the bounds of the estimate above. These are both consistent, however, with modeled coupling factor [2.0 uD/W] with some imperfect efficiency of the ring heater heating. We can do the same analysis for the XARM with the caveat that we must assume a known ratio of the coupling factors of ring heater to surface defocus of the ITM and the ETM (we did not have to do this for the YARM because ITMY has no ring heater power). Assuming the coupling factors have a ratio beta = 1.73 (ITM_coupling/ETM_coupling)  and that the XARM cavity g-factor measured in the 2W state is 0.8373 then the inferred coupling factor for the ETMX ring heater to surface defocus is 1.80uD/W. This is consistent with the inference for ETMY. These values are consistent enough with each other that we can use them in the next inference, I believe.

Inferred ETM Ring Heater Coupling from YARM HOM spacing at 2W [SQZ dataset] 1.77 uD/W
Inferred ETM Ring Heater Coupling from XARM HOM spacing at 2W [SQZ dataset] 1.80 uD/W
Inferred ETM Ring Heater Coupling from YARM HOMs fit of ETMY Ring Heater Settings Sweep 1.53 uD/W
Modeled ETM Ring Heater Coupling with 100% efficieny assumed 2.03 uD/W

Surface Defocus from Absorbed Arm Power to Infer the Circulating Power in the Arms

Since now we have a good understanding of the ring heater's contribution to the surface defocus and cavity g-factor shift, we can infer the absorbed arm power's contribution using the cavity g-factor measured at 60W. The measured cavity g-factors, calculated from the HOM spacings, were 0.8173 for the XARM and 0.8228 for the YARM. Assuming all the absorptions reporteed by galaxy are correct we can use the measured cavity g-factor shift along with modeled coupling factors of absorbed arm power to defocus to infer the arm power (JAAPE = Just Another Arm Power Estimate). The absorptions for the ITMs are 0.5 ppm, ETMY is 0.21ppm and ETMX is 0.20ppm. If we assume the coupling factors for ring heater surface defocus from the SQZ dataset and the modeled coupling factors of absorbed power to surface defocus, we get an arm power estimate of 283kW in the YARM and 481kW in the XARM. These indicate that the true absorptions in the test masses are most likely different from the galaxy numbers, as these arm powers are not consistent with the arm gain inference of the arm power, especially for the XARM.

Surface Defocus from Absorbed Arm Power to check the HWS Estimate of Absorbed Arm Power

We can repeat the above analysis, but instead assume nothing about the absorptions, and instead use the HWS estimates of the absorbed power in each input test mass. Then we can infer what the absorbed powers are in the end test masses to have measured the cavity g-factor as calculated from the HOM spacing. For ITMX, the HWS estimate an absorbed power of 218mW, and for ITMY the HWS estimates 254mW of absorbed power. To have measured a cavity g-factor in the XARM as mentioned above, with the HWS estimate of ITMX absorbed power, the absorbed power in ETMX would have to be 121mW. For the YARM measurement, using the HWS estimate of the ITMY absorbed power, the ETMY absorbed power would need to be -54.5mW. This indicates the HWS may be wrong, especially the ITMY HWS, as it is physically impossible to have measured the cavity g-factor that we did and simulataneously have that much absorbed power in ITMY (assuming the coupling factors from my model are correct).

Summary

Using two different methods, I've come a round-about-way to say that it is unlikely our absorptions are exactly as reported in galaxy, but that the HWS may not be giving us any better estimate (of the absorbed power). I am currently trying to calibrate the HWS using independent measurements, but more work is needed on that. Despite the ITMX HWS SLED just recently being replaced (we thought it was miscalibrated because it was dying), the defocus reported by the two HWS for CO2 heating differs by almost a factor of 2!

I am not well versed in HWS code and I'm not totally sure how these values of defocus are calculated from the deflection of each partitioned beam but these errors may be mis-identification of the position of the centroid.


This is a table of parameters describing the various coupling factors from the modeling. 

Parameter Value [uD/W]
ITM Coating Absorption to Substrate Lensing (AiL) 250
ITM Coating Absorption to Surface Defocus (AiS) -38
ITM Ring Heater to Substrate Lensing (BiL) -27
ITM Ring Heater to Surface Defocus (BiS) 3.5
ETM Coating Absorption to Surface Defocus (AeS) -28
ETM Ring Heater to Surface Defocus (BeS) 2.0

This is a summary table using the above modeled parameters

HWS Estimate of ITM Absorbed Powers ITMY = 254mW,  ITMX = 218mW
Inferred Arm Powers using galaxy absorptions XARM = 481kW, YARM = 283kW
Inferred ETM absorbed powers from HWS Estimates ETMY = -55mW, ETMX = 121mW

Conclusion: we have much more confidence in our models of various coupling factors thanks to measurements of the ring heaters effect on surface defocus, however we do not have a very good estimate of the absorbed powers or absorptions.

Images attached to this report
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 22:01, Monday 17 November 2025 (88149)
OPS Eve Shift Summary

TITLE: 11/18 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 19:46 UTC (12 hr 40 min lock) - last time I will be writing this for a while.

Extremely calm shift and well behaved interferometer on the last EVE of O4. Wind looks great and microseism is stable.

Wishing the OWL ops a smooth shift and some more spacetime ripples.

LOG:

None

X1 SUS
ibrahim.abouelfettouh@LIGO.ORG - posted 16:23, Thursday 13 November 2025 - last comment - 23:08, Monday 17 November 2025(88095)
BBSS Baffles Installed + Status

Ibrahim, Betsy

BBSS Eliptical Baffles (D2500293) were successfully installed today. Pictures from various angles are attached.

Problems - graphics regarding these are attached as slide screenshots

Remarks: I added one of those coated screw caps to the Y-Brace (D1900589) strut fasteners since I could see it shining in the head on picture. Comparison pictures for this are below.

Images attached to this report
Comments related to this report
alena.ananyeva@LIGO.ORG - 23:08, Monday 17 November 2025 (88150)
D1900594 is called correctly. It has utility holes to hold a wire baffle if needed.
Displaying reports 1-20 of 85646.Go to page 1 2 3 4 5 6 7 8 9 10 End