Displaying reports 241-260 of 83527.Go to page Start 9 10 11 12 13 14 15 16 17 End
Reports until 09:21, Monday 14 July 2025
H1 AOS
elenna.capote@LIGO.ORG - posted 09:21, Monday 14 July 2025 - last comment - 09:30, Monday 21 July 2025(85738)
LOWNOISE ASC Locklosses

I previously noted a glitch about 30 seconds before lockloss in LOWNOISE ASC, 85685. However, we had two more locklosses from this state last night and I do not see such a glitch so that is a random coincidence. One of those locklosses appears to be caused by an earthquake. However, since 6/11, we have had 9 locklosses in this state that occurred exactly 47 seconds into the state, which seems suspicious, one of those occurred last night, and the lockloss with the glitch was the same.

This seems to be coincident with the engagement of a few DHARD P filters:

2025-07-14_14:26:54.641531Z ISC_LOCK executing state: LOWNOISE_ASC (522)
2025-07-14_14:26:54.642230Z ISC_LOCK [LOWNOISE_ASC.enter]
2025-07-14_14:26:54.655894Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_PIT3_OSC_CLKGAIN => 300
2025-07-14_14:26:54.656325Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_PIT4_OSC_CLKGAIN => 300
2025-07-14_14:26:54.656732Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_PIT5_OSC_CLKGAIN => 300
2025-07-14_14:26:54.657043Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_YAW3_OSC_CLKGAIN => 300
2025-07-14_14:26:54.657438Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_YAW4_OSC_CLKGAIN => 300
2025-07-14_14:26:54.657892Z ISC_LOCK [LOWNOISE_ASC.main] ezca: H1:ASC-ADS_YAW5_OSC_CLKGAIN => 300
2025-07-14_14:26:54.658134Z ISC_LOCK [LOWNOISE_ASC.main] timer['LoopShapeRamp'] = 5
2025-07-14_14:26:54.658367Z ISC_LOCK [LOWNOISE_ASC.main] timer['pwr'] = 0.125
2025-07-14_14:26:54.783581Z ISC_LOCK [LOWNOISE_ASC.run] timer['pwr'] done
2025-07-14_14:26:59.658298Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:26:59.719537Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y_GAIN => 200
2025-07-14_14:26:59.720456Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y_SW1 => 256
2025-07-14_14:26:59.846249Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y_SW2 => 20
2025-07-14_14:26:59.971686Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_Y => ON: FM3, FM8, FM9
2025-07-14_14:26:59.972384Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_Y_SW1 => 5392
2025-07-14_14:27:00.098073Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_Y_SW2 => 4
2025-07-14_14:27:00.223528Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_Y => ON: FM1, FM3, FM4, FM5, FM8
2025-07-14_14:27:00.224135Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CSOFT_P_SMOOTH_ENABLE => 0
2025-07-14_14:27:00.224497Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CSOFT_Y_SMOOTH_ENABLE => 0
2025-07-14_14:27:00.224868Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_P_SMOOTH_ENABLE => 0
2025-07-14_14:27:00.225188Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_Y_SMOOTH_ENABLE => 0
2025-07-14_14:27:00.225433Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10
2025-07-14_14:27:10.225728Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:27:10.281803Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_TRAMP => 5
2025-07-14_14:27:10.408120Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_SW2 => 16
2025-07-14_14:27:10.533563Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P => OFF: FM9
2025-07-14_14:27:10.534285Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_SW1 => 256
2025-07-14_14:27:10.660088Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_SW2 => 4
2025-07-14_14:27:10.785453Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P => ON: FM3, FM8
2025-07-14_14:27:10.786315Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-CHARD_P_GAIN => 208
2025-07-14_14:27:10.786535Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 5
2025-07-14_14:27:15.786858Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:27:15.847152Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_Y_TRAMP => 5
2025-07-14_14:27:15.847580Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_Y_GAIN => 5
2025-07-14_14:27:15.848666Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DSOFT_P_GAIN => 5
2025-07-14_14:27:15.848917Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 5
2025-07-14_14:27:20.849050Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:27:20.906577Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMX_M0_DAMP_Y_TRAMP => 10
2025-07-14_14:27:20.907206Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ETMX_M0_DAMP_Y_TRAMP => 10
2025-07-14_14:27:20.907700Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMY_M0_DAMP_Y_TRAMP => 10
2025-07-14_14:27:20.908422Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMX_M0_DAMP_Y_GAIN => -0.5
2025-07-14_14:27:20.908830Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ETMX_M0_DAMP_Y_GAIN => -0.5
2025-07-14_14:27:20.909148Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ITMY_M0_DAMP_Y_GAIN => -0.5
2025-07-14_14:27:20.909562Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-ETMY_M0_DAMP_Y_GAIN => -0.5
2025-07-14_14:27:20.909789Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10
2025-07-14_14:27:30.910055Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:27:30.968166Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_P_GAIN => -0.2
2025-07-14_14:27:30.968527Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_Y_GAIN => -0.2
2025-07-14_14:27:30.968806Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_L_GAIN => -0.2
2025-07-14_14:27:30.969073Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_R_GAIN => -0.2
2025-07-14_14:27:30.969343Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_T_GAIN => -0.2
2025-07-14_14:27:30.969606Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:SUS-SR2_M1_DAMP_V_GAIN => -0.2
2025-07-14_14:27:30.969838Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10
2025-07-14_14:27:40.970003Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] done
2025-07-14_14:27:40.972085Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_P_SW1 => 1024
2025-07-14_14:27:41.097962Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_P_SW2 => 4
2025-07-14_14:27:41.223313Z ISC_LOCK [LOWNOISE_ASC.run] ezca: H1:ASC-DHARD_P => ON: FM4, FM8
2025-07-14_14:27:41.223637Z ISC_LOCK [LOWNOISE_ASC.run] timer['LoopShapeRamp'] = 10
2025-07-14_14:27:41.593743Z ISC_LOCK [LOWNOISE_ASC.run] Unstalling IMC_LOCK
2025-07-14_14:27:41.765955Z ISC_LOCK JUMP target: LOCKLOSS

I will take a look and see if there is anything unstable about these filters. Whatever is occurring seems to be too fast to be seen in the ASC signals themselves, and at first glance I don't see anything strange in the suspension channels either.

DHARD FM4 is engaged with a 10 second ramp- this is a change I made on 6/11: 84973 because we had lost lock on that day twice in the same spot. Two of the locklosses at 47 seconds occurred before that change. Then, later that day on 6/11 I reengaged a boost in DHARD P, which only has a 5 second ramp, 84980. Engaging that boost shouldn't be unstable, but maybe something bas occurrs when they ramp at different times. I'm lengthing the ramp to 10 seconds.

Comments related to this report
elenna.capote@LIGO.ORG - 11:44, Tuesday 15 July 2025 (85766)
Link

We had another lockloss from this state at the 00:47 mark last night, 1436615757 so I'm not sure this fixed the problem.

 However, the lockloss was proceeded by a glitch about 30 seconds before, like another lockloss I noticed in this state. This could be coincidence again, but it's looking a little suspicious!

elenna.capote@LIGO.ORG - 11:58, Tuesday 15 July 2025 (85768)
Link

The glitch appears to be occuring due to the CHARD P change. We ramp a boost off with 2 seconds, and a new shaping and low pass on with 2 seconds, and then change the gain with 5 seconds. Looking at the step response of the shaping and lowpass filter, this ramp should probably be 10 seconds, and the gain also 10 seconds to match. I will keep the boost at 2 seconds to ramp off though. I increased the wait timer to 10 seconds to match this ramping. Model and guardian changes saved and loaded.

I am still not sure what is going on with DHARD P, but as a test I've now separated the low pass and loop shape from the engagement of the boost, since we know those individually are stable to engage. We now engage FM4 with a 10 second ramp and wait time, then engage FM8 with a 5 second ramp and wait time. I edited the ramps and gaurdian code to do so, svaed and loaded. This is kind of annoying, but it might help me debug what's going wrong here.

elenna.capote@LIGO.ORG - 13:49, Tuesday 15 July 2025 (85776)
Link

I watched the signals during lownoise ASC, and this time I saw no glitch in CHARD during its lownoise transition. However, I saw a glitch when the DHARD P FM4 filter was engaged, and no glitch when FM8 was engaged. Maybe the ramp of FM4 should be even longer than 10 seconds. I increased the filter ramp to 15 seconds and increased the guardian wait timer to match. Both changes saved and loaded.

elenna.capote@LIGO.ORG - 09:30, Monday 21 July 2025 (85888)
Link

We haven't had a lockloss in this state since this fix (but we've had plenty of locks), so I am going to declare this problem fixed!

H1 PSL
ryan.short@LIGO.ORG - posted 08:34, Monday 14 July 2025 - last comment - 11:21, Monday 14 July 2025(85735)
PSL 10-Day Trends

FAMIS 31094

FSS TPD signal has been dropping over the past week, so it could probably do with some RefCav alignment adjustments soon. Otherwise, not much else to report.

Images attached to this report
Comments related to this report
jason.oberling@LIGO.ORG - 10:15, Monday 14 July 2025 (85739)
Link

I plan on taking a look at RefCav alignment during maintenance tomorrow; Ryan will perform a remote RefCav alignment today ONLY if a valid T.O.O. presents itsefl (i.e. a large EQ has us down for some time).  The last time I did a remote alignment on July 1st I was not able to get back to the previous TPD voltage, an indication that something upstream of the picomotors is moving (this something is usually the double-pass AOM).  Further, the RefCav REFL spot on the PSL Quad Display (the lower-left image) hints that an enclosure incursion may be necessary; the central spot is mostly centered between the upper and lower lobes (which hints that the alignment into the RefCav is likely OK), but the lobes themselves are much brighter than normal.  This is generally an early indication that an on-table RefCav beam alignment is in our near future.

The plan at this point is for me to try a remote alignment early in the maintenance period, unless Ryan is able to try it during a T.O.O. today.  Should the TPD return to above 0.8 V then nothing further happens, we will continue to monitor this as we normally do; but if it cannot then I will go into the enclosure and perform and on-table RefCav beam alignment (I have filed WP 12683 in case I do have to go into the enclosure).  The IMC will need to be UNLOCKED while I am working on the RefCav, regardless of if I'm in the Control Room or in the PSL enclosure (same goes for if Ryan gets a T.O.O. to do the remote alignment today).

ryan.short@LIGO.ORG - 11:21, Monday 14 July 2025 (85744)
Link

A M6.6 EQ out of Panama knocked H1 out of lock this morning, so I took that opportunity to touch up the RefCav alignment. I was only able to increase the signal on the TPD from about 0.700 V to 0.764 V, so not quite back to what it was before, meaning Jason will need to adjust alignment on-table tomorrow as planned.

LHO General
ryan.short@LIGO.ORG - posted 08:00, Monday 14 July 2025 - last comment - 08:49, Monday 14 July 2025(85734)
Ops Day Shift Start

TITLE: 07/14 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 18mph Gusts, 13mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: H1 looks to have been down most of the night (since 04:00 UTC during last night's evening shift). High winds combined with an earthquake made for difficult locking with only a few attempts making it to LOWNOISE_ASC before a lockloss. Currently trying to lock DRMI.

Comments related to this report
ryan.short@LIGO.ORG - 08:49, Monday 14 July 2025 (85737)
Link

H1 relocked back to low noise at 15:42 UTC. Jumping straight into planned commissioning time which is scheduled until 19:00 UTC.

H1 General
anthony.sanchez@LIGO.ORG - posted 07:16, Monday 14 July 2025 (85732)
IFO needed assistance since earthquake.

I woke up, with my alarm clock and started an initial alignment since H1 needed assistance. Around 6am.
Once
Going throught the locking proccess now.

H1 General (CDS, SUS)
ryan.crouch@LIGO.ORG - posted 22:02, Sunday 13 July 2025 (85729)
OPS Sunday EVE shift summary

TITLE: 07/14 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Wind/Aligning
INCOMING OPERATOR: Tony
SHIFT SUMMARY: The TCSY laser tripped off then we lost lock in the last hour, the winds rose to around 40mph after this. H1 is trying to do an intial alignment as of 05:00 UTC as the DRMI flashes weren't great, the winds have calmed a bit so hopefully it goes well and the arms can stay locked.
LOG: No log.

 

H1 General (Lockloss, TCS)
ryan.crouch@LIGO.ORG - posted 21:04, Sunday 13 July 2025 - last comment - 21:39, Sunday 13 July 2025(85730)
Lockloss 04:00 UTC

TCS CO2Y tripped and dropped us out of Observing at 03:58 UTC then we lost lock 2 minutes later, lockloss. The lockloss appears to have been an ETMX glitch.

Comments related to this report
ryan.crouch@LIGO.ORG - 21:39, Sunday 13 July 2025 (85731)
Link

Following the WIKI and TJ's instructions I went into the LVEA (TJ was my phone buddy) to restart the controller than I went into the mechanical room and reset the power supply which was reading a current and voltage of 0 when I arrived. There were no flow/chiller alarm nor RTD/IR sens alarm.

H1 AOS
robert.schofield@LIGO.ORG - posted 18:29, Sunday 13 July 2025 (85728)
New suggested settings for ITMY compensation plate offsets, pitch: -317, yaw: -122

The pumps were still running last month when I  suggested preliminary CP-Y settings (85084). I wanted to get back to it with a little higher sensitivity after the pumps were shut off. As a result of this second look, I suggest new settings of Pitch: -317 and Yaw: -122; They represent only a slight reduction in scattering noise coupling, but the new settings don't  consume as much actuator range.

The technique I used to pick a minimum was the same as used here: https://alog.ligo-wa.caltech.edu/aLOG/uploads/76969_20240404184914_Fig3-Sensitivity-To-IY-CP-Yaw-Also-Bright-Spot.pdf

The structure in the coupling variation was like it was before the break (see link), at a scale of about 20 microradians in CP angle. The maximum coupling in the CP sweeps after the vent was about half of what it was in the sweeps before the vent, so maybe there was some improvement.

I made videos of the beam spot on the HAM3 ballast baffle and its support before and after the compensation plate adjustment. The compilation video uses the same slider program (see details in video description) before and after the compensation plate move:

https://youtu.be/nbZ7da6LE9s

LHO General
ryan.short@LIGO.ORG - posted 16:30, Sunday 13 July 2025 (85726)
Ops Day Shift Summary

TITLE: 07/13 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Major excitement of the day was a lockloss caused by a power glitch which necessitated a recovery of end station HEPI pump controllers. Aside from that, calibration sweeps were run opportunistically and relocking went very smoothly.

H1 General
ryan.crouch@LIGO.ORG - posted 16:00, Sunday 13 July 2025 - last comment - 16:41, Sunday 13 July 2025(85725)
OPS Sunday EVE shift start

TITLE: 07/13 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 8mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

Comments related to this report
ryan.crouch@LIGO.ORG - 16:41, Sunday 13 July 2025 (85727)
Link

We dropped observing from 23:30 - 23:38 UTC as the SQZ PMC lost lock, I also ran a SCAN_SQZ ang

H1 General
ryan.short@LIGO.ORG - posted 12:19, Sunday 13 July 2025 - last comment - 08:42, Monday 14 July 2025(85722)
Lockloss @ 18:53 UTC - Power Glitch

Lockloss @ 18:53 UTC from site power glitch, trend attached. This tripped the end station HEPI pump controllers (and so far nothing else, that I've noticed), so I consulted with Jim and he walked me through what needs to be done to reset them. Heading out to the end stations now.

Images attached to this report
Comments related to this report
ryan.short@LIGO.ORG - 13:36, Sunday 13 July 2025 (85723)
Link

Pump stations and all seismic systems fully recovered. Starting an initial alignment now.

ryan.short@LIGO.ORG - 14:52, Sunday 13 July 2025 (85724)
Link

H1 back to observing at 21:50 UTC. Initial alignment and lock acquisition both ran fully automatically and without issues.

david.barker@LIGO.ORG - 07:43, Monday 14 July 2025 (85733)
Link

FRS34721

Note that none of the UPS units emailed us regarding this event, which is unusual for a glitch which caused HEPI pump controller issues.

david.barker@LIGO.ORG - 08:42, Monday 14 July 2025 (85736)
Link

Jonathan checked the front panel on the MSR UPS and confirmed it logged nothing at the time of this power glitch.

H1 SQZ
ryan.short@LIGO.ORG - posted 11:32, Sunday 13 July 2025 (85721)
OPO Temperature Adjusted

After running calibration sweeps this morning while L1 was out of lock, I also took the opportunity to touch up the OPO temperature with the SQZ_OPO_LR Guardian as I noticed the range gradually decreasing over this lock stretch. This went well, improving CLF_REFL_RF6 a bit and gaining H1 about 6-8Mpc of BNS range.

H1 returned to observing at 18:19 UTC.

Images attached to this report
H1 CAL
ryan.short@LIGO.ORG - posted 11:27, Sunday 13 July 2025 (85720)
Broadband and Simulines Calibration Sweeps

Since the scheduled calibration time was missed yesterday due to a lockloss, while L1 was out of lock this morning, I took the opportunity to drop observing at 17:38 UTC and run the broadband and Simulines sweeps. Calibration report and screenshot of the calibration monitor screen are attached.

Broadband: 17:39 to 17:44 UTC

Simulines: 17:45 to 18:08 UTC

2025-07-13 18:08:34,702 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250713T174519Z.hdf5
2025-07-13 18:08:34,709 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250713T174519Z.hdf5
2025-07-13 18:08:34,714 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250713T174519Z.hdf5
2025-07-13 18:08:34,719 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250713T174519Z.hdf5
2025-07-13 18:08:34,723 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250713T174519Z.hdf5

Images attached to this report
Non-image files attached to this report
H1_calibration_report_20250713T174519Z.pdf
LHO VE
david.barker@LIGO.ORG - posted 10:27, Sunday 13 July 2025 (85719)
Sun CP1 Fill

Sun Jul 13 10:08:24 2025 INFO: Fill completed in 8min 20secs

 

Images attached to this report
Displaying reports 241-260 of 83527.Go to page Start 9 10 11 12 13 14 15 16 17 End