Displaying reports 1-20 of 83106.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 10:17, Saturday 05 July 2025
LHO VE
david.barker@LIGO.ORG - posted 10:17, Saturday 05 July 2025 (85557)
Sat CP1 Fill

Sat Jul 05 10:06:44 2025 INFO: Fill completed in 6min 40secs

 

Images attached to this report
H1 General (Lockloss)
anthony.sanchez@LIGO.ORG - posted 08:03, Saturday 05 July 2025 (85556)
Saturday July 5th Ops day Shift Start & Lockloss from Nominal Low Noise

TITLE: 07/05 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 5mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:
H1 has been Locked and Observing for 2 Hours & 51 min.
All systems are running smoothly.

Expected:
1830 UTC -1900 UTC  Calibration

Update:
14:40 UTC Lockloss right after I got here.

 

Images attached to this report
LHO General
ryan.short@LIGO.ORG - posted 22:02, Friday 04 July 2025 (85555)
Ops Eve Shift Summary

TITLE: 07/05 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Started the shift by troubleshooting a SQZ issue that once resolved made for a straightforward evening. Two locklosses tonight, but relocking each time went automatically. H1 has now been locked and observing for almost 2 hours.

H1 General (Lockloss)
ryan.short@LIGO.ORG - posted 18:40, Friday 04 July 2025 - last comment - 20:24, Friday 04 July 2025(85552)
Lockloss @ 00:45 UTC

Lockloss @ 00:45 UTC after almost 12 hrs lock - link to lockloss tool

No obvious cause.

Comments related to this report
ryan.short@LIGO.ORG - 19:13, Friday 04 July 2025 (85553)Lockloss

Back to observing at 02:09 UTC, then another lockloss with no obvious cause at 02:10 UTC.

ryan.short@LIGO.ORG - 20:24, Friday 04 July 2025 (85554)

Back to observing at 03:17 UTC, fully automatic relock.

LHO General (SQZ)
ryan.short@LIGO.ORG - posted 16:48, Friday 04 July 2025 - last comment - 17:32, Friday 04 July 2025(85550)
Ops Eve Shift Start

TITLE: 07/04 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 25mph Gusts, 20mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY: H1 has been locked for almost 11 hours, but currently not observing as I'm troubleshooting an issue with the SQZ filter cavity. I'm able to consistently bring everything with the squeezer up to before the FC is needed, and lock the FC up to the SQZ_FC Guardian's 'IR_FOUND' state, but every time I try moving on, the FC drops out. Investigation still ongoing.

Comments related to this report
ryan.short@LIGO.ORG - 17:32, Friday 04 July 2025 (85551)SQZ

H1 back to observing at 00:18 UTC.

Ultimately, after trying several things that didn't completely fix the issue like trending FC1/2 OSEMs, adjusting FC1/2 to maximize FC green transmission, and doing a "graceful clear history" on the filter cavity ASC, I enlisted Sheila for guidance. I ran her new 'SCAN_OPOTEMP' Guardian state to optimize the OPO temperature (then gave it a couple more steps to maximize CLF_REFL_RF6), then requested SQZ_MANAGER all the way up to 'FREQ_DEP_SQZ', which worked perfectly this time. The improvement of CLF_REFL_RF6 from 0.35 to 0.39 must have been just enough to make the filter cavity happy.

There were outstanding SDF diffs on h1ascsqzfc, possibly from my history clearing, which Sheila said were okay to just revert (screenshot attached). When I did this, I saw the green FC spot wobble, but not unlock. I then returned H1 to observing.

Images attached to this comment
H1 General (SQZ)
anthony.sanchez@LIGO.ORG - posted 16:41, Friday 04 July 2025 (85549)
Friday July 4th Ops day shift End

TITLE: 07/04 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:
H1 has been locked all day and is still locked at NLN.... But...

Dropped out of Observing at 22:54:25 UTC due to the SQZ_FC  Dropping to Down.
A few trys later it locked and H1 returned to Observing for just a second, only for the SQZ_FC to unlock again. @ 22:58:55 UTC.
Several trys after that and the FC cannot seem to lock it's self reliably. 
We have tried following the directions found in the SQZ_FC section of this SQZr Troubleshooting document.

LOG:                                                                                                           

Start Time System Name Location Lazer_Haz Task Time End
22:37 FAC Tyler Machine Shop N Checking in on machine shop status 23:06

 

H1 General (PSL)
anthony.sanchez@LIGO.ORG - posted 11:33, Friday 04 July 2025 (85548)
PSL Status Report - Weekly

PSL Status Report - Weekly FAMIS 26429

Laser Status:
    NPRO output power is 1.856W
    AMP1 output power is 69.91W
    AMP2 output power is 140.0W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 17 days, 1 hr 18 minutes
    Reflected power = 23.39W
    Transmitted power = 105.6W
    PowerSum = 129.0W

FSS:
    It has been locked for 0 days 6 hr and 52 min
    TPD[V] = 0.8037V

ISS:
    The diffracted power is around 3.6%
    Last saturation event was 0 days 6 hours and 52 minutes ago


Possible Issues:
    PMC reflected power is high

LHO VE
david.barker@LIGO.ORG - posted 11:12, Friday 04 July 2025 (85547)
Fri CP1 Fill

Fri Jul 04 10:08:40 2025 INFO: Fill completed in 8min 36secs

 

Images attached to this report
H1 General (SQZ)
anthony.sanchez@LIGO.ORG - posted 07:47, Friday 04 July 2025 - last comment - 09:17, Friday 04 July 2025(85545)
Friday July 4th Ops day shift start

TITLE: 07/04 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 5mph Gusts, 2mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:
When I Arrived H1 was in Nominal_LOW NOISE, but not Observing. Range: 120
SQZ_LO_LR was stuck in Locking_OMC[15] with an error message: Beam diverter is open but no 3 MHz on OMC, could be an alignment problem.

Things i have done already.
Init SQZ_LO_LR & then SQZ MANAGER

 

 

Comments related to this report
anthony.sanchez@LIGO.ORG - 09:17, Friday 04 July 2025 (85546)

"Beam diverter is open but no 3MHz on OMC, could be an alignment problem" - trend ZM4,5,6 alignment while trending H1:SQZ-OMC_TRANS_RF3_DEMOD_RFMON. If the alignment of any has changed, move them back slowly while aiming to increase H1:SQZ-OMC_TRANS_RF3_DEMOD_RFMON.

Found here:Troubleshooting SQZr from Ops wiki.
Slider values had not changed at all over the course of several hours but the osems had. 
Sheila called while I was setting up my ndscope to check the Osems and had mentioned that ZM5 likely didnt matter as it is ZM4 and 6 that get moved.

She had me clear the history on H1:SUS-ZM{4 & 6}_M1_LOCK_{L P Y}_OUTPUT before I  adjusted the ZM4 & 6 sliders.
H1:SUS-ZM4_M1_LOCK_L_GAIN were changed after turning up the TRamps for H1:SUS-ZM{4 & 6}_M1_LOCK_{L, P, Y}_GAIN
Then I cleared the History on those locking filters.

Once that was done I simply just move them back slowly while aiming to increase H1:SQZ-OMC_TRANS_RF3_DEMOD_RFMON as the Trouble shooting doc suggested.

Then as Sheila advised I ren SQZ_MAN through Scan_Alignment_FDS[105] wich further touched up alignment. 
After accepting SDF diffs.

We got back to Observing at 15:57 UTC @ 149 Mpc.
 

Images attached to this comment
H1 General
ryan.crouch@LIGO.ORG - posted 22:00, Thursday 03 July 2025 (85544)
OPS Thursday EVE shift summary

TITLE: 07/04 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: I did not see any PI ring ups during my shift. Ended the shift with a supervent!
LOG: No log

00:50 - 01:21 UTC I dropped Observing to run a calibration measurement

04:31 UTC Superevent S250704ab

05:00 UTC lockloss :(

 

Images attached to this report
H1 CAL (CAL)
ryan.crouch@LIGO.ORG - posted 18:25, Thursday 03 July 2025 (85543)
Thursday calibration measurement

We had been locked for just over 3 hours, the circulating power was ~378.5kW in each arm, a little under the usual 380kW.

Broadband:

Start: 2025-07-04 00:50:39

Stop: 2025-07-04 00:55:50

Data: /ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20250704T005039Z.xml

Simulines:

Start: 2025-07-04 00:56:56.978617 UTC // GPS: 1435625834.978617

Stop: 2025-07-04 01:20:13.539672 UTC // GPS: 1435627231.539672

Data:

2025-07-04 01:20:13,381 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20250704T005657Z.hdf5
2025-07-04 01:20:13,389 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20250704T005657Z.hdf5
2025-07-04 01:20:13,394 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20250704T005657Z.hdf5
2025-07-04 01:20:13,398 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20250704T005657Z.hdf5
2025-07-04 01:20:13,403 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20250704T005657Z.hdf5

 

Images attached to this report
Non-image files attached to this report
LHO General
corey.gray@LIGO.ORG - posted 16:29, Thursday 03 July 2025 (85519)
Thurs DAY Ops Summary

TITLE: 07/03 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

Today was Thursday Commissioning from 8am-1230pm, and had a locked H1 for 1hr45min of the commissioning time and had a few commissioning tasks squeezed in this time.  

H1 continues to be plagued by ringing up PI Modes that cause locklosses.  So, today different settings continued to be tried (latest & current ETMy Ring Heater setting is 1.5 W for the upper and lower).  But for some of these changes, we have had to try different violin mode settings (for ETMy Mode 20)---see this alog85527.

Also, the input pointing which was lost due to the HAM2 SEI Power supply swap on Maintenance Day, was reverted back by Elenna (alog85533).

Did not get to run the calibration suite today, so hope to do this after H1 gets to 3hrs during RyanC's shift tonight.
LOG:

H1 SQZ (OpsInfo)
sheila.dwyer@LIGO.ORG - posted 16:08, Thursday 03 July 2025 (85532)
new opo guardian state to adjust crystal temperature, SQZ ASC off and SQZ angle servo on

I started adding a state to the OPO guardian this morning while we were unlocked that scans the OPO temperature while the CLF is locked, and sets it to the temperature that maximizes CLF 6 Mz power in reflection off the OPO. 

The code is based on the SCAN_SQZ_ANG guardian state and it produces plots here: https://lhocds.ligo-wa.caltech.edu/exports/SQZ/GRD/OPOTEMP_SCAN/OPOTEMP_SCAN_250703142801.png

Screenshot shows that exmpale was a 1 minute scan with a 0.02 degree C range, this was a bit too fast for the TEC servo to keep up with so I've slowed it down to a 2 minute scan for the next time we try this out. 

Operators can use it to adjust the opo temp, by opening the SQZ_OPO_LR guardian and requesting SCAN_OPOTEMP.  I haven't tried this while squeezing was injected into the IFO, but it should work fine to do it then (not while in observing).   For future work we could add management that runs this each time the IFO relocks, but I haven't done that now.

Also note: This morning I set the sqz params to stop using SQZ ASC and start using the ADF servo for the squeezing angle.  These two can't run at the same time and I think that controlling the squeezing angle would be more beneficial right now.  However with various things we didn't get to test this and now we are observing with both ASC and the ADF servo off.  We momentarily dropped out of observing to engage the servo.  I also added to the SQZ_ANG_ADJUST guardian an if statement that updates the nominal state looking at sqzparams to check if the servo is supposed to be on or off in the guardian.   This will be compatible with the script that allows observing without squeezing for this weekend, but that script hard codes what the nominal state is, so in the long run we need to do something else.

Images attached to this report
H1 General
ryan.crouch@LIGO.ORG - posted 16:06, Thursday 03 July 2025 (85542)
OPS Thursday EVE shift start

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

H1 PSL (PSL)
rahul.kumar@LIGO.ORG - posted 15:57, Thursday 03 July 2025 (85541)
ISS PD work in Optics lab - horizontal and vertical dither measurements for calibrating the beam motion on QPD

Jennie Wright, Rahul

Earlier, we have measured the QPD readout per mm to be around 44.1V (in X direction). This afternoon we dithered the input beam (spot size, radius = 200 microns, see LHO alog 85458) in horizontal and vertical direction at 100Hz using the signal generator (amplitude 2V peak to peak and offset 2.5V). This we did after centering the beam on the QPD (output was around 10,500 counts approx.). The output voltage applied on the dither was around 80V. Given below are the results,

Horizontal dithering:-

On the QPD the dither amplitude X (peak to peak) was estimated to be 2.2V, Mean 6.5V

Beam motion estimate X= 50microns

Dither amplitude Y (peak to peak) was estimated to be 1.2V, Mean -355mV

Vertical dithering:-

On the QPD the dither amplitude X (peak to peak) was estimated to be 1.0V, Mean 4.45V

Beam motion estimate X= 20microns

Dither amplitude Y (peak to peak) was estimated to be 1.62V, Mean -7.96V.

 

H1 ISC
sheila.dwyer@LIGO.ORG - posted 10:38, Thursday 03 July 2025 - last comment - 15:47, Thursday 03 July 2025(85527)
another ring heater step, changing PI 28 damping to ETMY

Kevin, Matt, Sheila, Elenna, Corey

After yesterday's ETMY RH change to avoid the 10kHz PI 85514, we lost lock 3 times overnight due to 80kHz PIs.

Apartently the RH change also changed a violin mode damping phase for ETMY 1 kHz mode (mode 20 1000.307 Hz), 85526, which did not cause the earlier locklosses but is growing to the point where it is dominating the DCPD RMS in this lock, but responded well the Elenna's sign flip.

Kevin took a look at the 10kHz higher order modes, second attachment.  The top panel shows how the higher order modes have been thermalizing before the ring heater change, the bottom panel shows three locks since the ring heater change which is a few minutes before 2 hours into the lock, so these can be compared to the green trace in the top panel. THe x arm higher order modes are sitting around 10.6kHz at this point in the self heating thermalization, the yarm modes were below the scale on this plot before the change and are now moving up to around 10480Hz.   If they gain another 20Hz as the self heating kept thermalizing similar to the x arm, this would have put them around 10500 Hz which doesn't have a lot of accoustic modes visible here. 

We don't want to revert the ring heater change from last night as that setting had the y arm sitting right below the forest of accoustic modes.  Matt estimates that we could move the y arm below this forest of accostic modes by going to 1.5 or 1.6W per segment, but that would mean that our two arm modes are more different from each other.  First we tried lowering the power a little more, to 0.9W per segment to see if that helps the 80 Hz modes.  Then Matt estiamted that we could put the Y arm 2nd order mode in a similar location to the x arm by using 0.6W per segment, so we've now set them to that.

Matt took a reference here before the PI rang up, it looks like the PI is 80297 Hz, I got a reference that includes the peak and the lockloss transient, which shows the frequency as 80298 Hz. The signal used for the PI damping is DCPDs downconverted at 80kHz, with a bandpass that goes from 294 to 298.5 Hz, so our peak is within the bandpass. The PLL set frequency is 299Hz, we lowered this 297.5Hz. It was being sent to ETMX for damping, which did appear to work once but not as the mode grew.  We think this is a y arm PI, since we have been changing the Y arm ring heaters, so I've changed the output matrix to send this to ETMY.

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 14:37, Thursday 03 July 2025 (85537)

I SDFed the ETMY ring heater change to 1.5 W in observe.

Images attached to this comment
corey.gray@LIGO.ORG - 15:47, Thursday 03 July 2025 (85540)SUS

For this new Ring Heater power (1.5), the ETMy Mode20 violin started to ring up again with default settings (+30deg + -1.0gain). 

Took the gain to +1.0, but this also rung up the violin.

It's been about an hour, but this seeting has been damping for this mode:

  • +60deg + +1.0gain

Have not updated lscparams since we are still figuring out a Ring Heater power which works for H1.  Once we find a good Ring Heater setting, we should update lscparams (if necessary).

Displaying reports 1-20 of 83106.Go to page 1 2 3 4 5 6 7 8 9 10 End