Displaying reports 1481-1500 of 84282.Go to page Start 71 72 73 74 75 76 77 78 79 End
Reports until 13:18, Monday 23 June 2025
H1 ISC
elenna.capote@LIGO.ORG - posted 13:18, Monday 23 June 2025 - last comment - 16:29, Thursday 26 June 2025(85250)
Noise Budget injection inventory

I have been running opportunistic noise budget injections:

So far there seems to be no noise contribution from DC6 P and PRC2 P and Y. CHARD noise contributions are also down significantly with the ISI in place.

 

Comments related to this report
elenna.capote@LIGO.ORG - 16:48, Wednesday 25 June 2025 (85347)

I ran SRCL and MICH injections today as a part of determining if the feedforward is performing well, but I repurposed those injection times in the noise budget templates so now SRCL and MICH are complete as well.

elenna.capote@LIGO.ORG - 16:29, Thursday 26 June 2025 (85372)

After running some PRCL injections to test the feedforward I was also able to update the PRCL noise budget template.

I also reran the jitter noise coupling measurement, since it seemed like the coupling was overestimated at low frequency. The jitter noise had been run very early on in vent recovery, so I am not sure what changed to affect the low frequency coupling (could be the pumps, LSC feedforward, ASC, etc) but now the low frequency coupling is very reduced.

H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 12:59, Monday 23 June 2025 - last comment - 14:26, Monday 23 June 2025(85249)
Lockloss

Lockloss at 2025-06-23 19:58 UTC. A commissioner was running a jitter noise injection at the time of the lockloss, but doesn't think that was the cause of the lockloss.

Comments related to this report
elenna.capote@LIGO.ORG - 13:24, Monday 23 June 2025 (85253)

The DARM signals look very noisy just before the lockloss because I was injecting jitter noise. I don't think that caused the lockloss. The tool is tagging this as "ETM GLITCH" which I also think is wrong because the extra noise was bringing the DARM signal above threshhold for the glitch checker.

oli.patane@LIGO.ORG - 14:26, Monday 23 June 2025 (85257)

21:25 UTC Back to Observing

H1 ISC
elenna.capote@LIGO.ORG - posted 10:52, Monday 23 June 2025 - last comment - 15:53, Monday 23 June 2025(85246)
20 minutes of X corr data taken

We took 20 minutes of no-squeezing data for a cross correlation measurement today. I ran a script to collect the full 524 kHz data from DCPD A and B. The data is currently saved in 1 second hdf5 frames in /ligo/home/elenna.capote/OMC_DCPD/252306-092558_xcorr_data

Comments related to this report
elenna.capote@LIGO.ORG - 15:53, Monday 23 June 2025 (85259)

I was able to read in each 1 second frame and generate a gwpy timeseries for each DCPD data set that I then saved as a single .gwf file. I also used the gwpy resample function to decimate the data to 64k so there is a smaller version. Both sets of files are saved in the same directory and can be read in with gwpy, which should also include metadata with sample rate, gps start, and channel name.

LHO VE
david.barker@LIGO.ORG - posted 10:22, Monday 23 June 2025 (85240)
Mon CP1 Fill

Mon Jun 23 10:11:08 2025 INFO: Fill completed in 11min 4secs

 

Images attached to this report
H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 10:20, Monday 23 June 2025 - last comment - 10:29, Monday 23 June 2025(85239)
Lockloss

Lockloss at 2025-06-23 17:18 UTC during commissioning after nearly 14 hours of being Locked. Unknown cause

Comments related to this report
oli.patane@LIGO.ORG - 10:28, Monday 23 June 2025 (85241)

Looks like it was due to a 13Hz ringup in the LSC channels (ndscope). Elenna and I had found a couple other recent locklosses that also had ringups at 13Hz in 85167

Images attached to this comment
david.barker@LIGO.ORG - 10:29, Monday 23 June 2025 (85243)

I took the opportunity to update h1hpiham1's safe.snap to the latest channel list, removing 47 not-found chans as part of Jim's model cleanup.

H1 TCS (ISC)
camilla.compton@LIGO.ORG - posted 10:15, Monday 23 June 2025 - last comment - 10:46, Monday 23 June 2025(85238)
Stepped CO2 powers down from 1.7W to 0.9W each into IFO

Elenna, Sheila, Kevin, Matt, Camilla

For some thermalization tests, at 17:05UTC we stepped CO2 powers down from 1.7W to 0.9W each into IFO. Expect majority of thermalization to take ~1hour.

Beforehand, Sheila plugged in the freq noise injection cables in the LVEA PSL racks and Elenna turned on the AWG_LINES guardian.

Comments related to this report
elenna.capote@LIGO.ORG - 10:46, Monday 23 June 2025 (85245)DetChar

I'm adding a detchar tag here in case anyone is wondering where all the lines are coming from in the data around this time- these are purposefully injected lines. If AWG_LINES is injecting, it will be in state 10. When IDLE (no injections), it is in state 2.

H1 SQZ
camilla.compton@LIGO.ORG - posted 10:08, Monday 23 June 2025 - last comment - 13:19, Monday 23 June 2025(85237)
SQZ FIS Data set
Sheila, Camilla

After Kevin did some 10kHz SQZ ADF scans, we look some SQZ FIS data. The best ASQZ and SQZ didn't look as good as usual, but we found our NLG was low. We didn't check the NLG first so that we had a direct comparison to Kevin's dataset.

Roughly following 83594 with slightly different data taken.

DTT saved as camilla.compton/Documents/sqz/templates/dtt/20250623_FIS.xml and screenshot attached.

Type Time (UTC) Angle DTT Ref
FIS Mean SQZ 15:53:00 - 15:56:00 N/A ref 1
FIS + Mid SQZ (aimed +7dB @1kHz) 15:58:30 - 16:01:30 (-) 242 ref 2
FIS - Mid SQZ (aimed +7dB @1kHz) 16:03:00 - 16:06:00 (-) 94 ref 3
FIS ASQZ 16:08:30 - 16:11:30 (-) 63 ref 4
FIS SQZ 16:13:30 -16:16:30 (-) 122 ref 5
No SQZ 16:26:00 -  16:46:00 N/A ref 0
 
Checked while in NO SQZ, also adjusted the SHG pump waveplates to reduce the HAM7 rejected power, but I did this less than a week ago:
OPO Setpoint Amplified Max Amplified Min UnAmp Dark NLG OPO Gain Note
95uW 0.001504 6.71 e-5 0.0002828 -2.52e-5 4.9 -8 Without changing OPO temp
95uW 0.002317 8.69e-5 0.0002828 -2.52e-5 7.5 -8 With changing OPO temp

Last week 85000, NLG was measured to be 18.9, now it's measured to be <8. We will look into why is it low.

Ran SCAN_SQZANG_FDS before doing a CO2 step.

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 13:19, Monday 23 June 2025 (85252)

 I measured the NLG with a few different opo pump powers to follow up on Camilla's observation that the NLG was low. 

OPO trans power [uW] maximum minimum nlg
95 2.26e-3 8.195e-5 8.5
80 2.25e-3 8.795e-5 8.2
60 1.902e-3 8.866e-5 6.93

dark level 2e-5, unamplified 2.914e-4

I tried to lower the seed power to see if we have some pump depletion making us underestimate the NLG, but the half wave plate was already set to minimize the seed power.

Since the NLG looks to be about the same with 80 uW as 95uW, I set it to 80 uW for now. 

H1 General
oli.patane@LIGO.ORG - posted 07:37, Monday 23 June 2025 (85235)
Ops Day Shift Start

TITLE: 06/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 142Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 1mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

Observing at 140Mpc and have been locked for just over 11 hours. We have commissioning today starting at 15:00UTC.

LHO General
ryan.short@LIGO.ORG - posted 22:01, Sunday 22 June 2025 (85234)
Ops Eve Shift Summary

TITLE: 06/23 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: One lockloss this shift which took a while to come back from, but overall a fairly quiet evening. H1 has been locked for 1.5 hours.

H1 General (Lockloss)
ryan.short@LIGO.ORG - posted 18:42, Sunday 22 June 2025 - last comment - 20:52, Sunday 22 June 2025(85232)
Lockloss @ 00:59 UTC

Lockloss @ 00:59 UTC after almost 23 hours locked - link to lockloss tool

No obvious cause.

Comments related to this report
ryan.short@LIGO.ORG - 20:52, Sunday 22 June 2025 (85233)SQZ

Back to observing at 03:45 UTC.

As has been the norm recently, D/PRMI took a very long time to catch despite good alignment and buildups. There were also a few low-state locklosses due to the ALS-X PLL beatnote having an error, which would then take a few minutes to fix itself, so with everything together this was a lengthy relock (but I did not need to run an alignment; just some slight adjustments of PRM and BS).

After reaching low noise, SQZ couldn't lock because the SHG PZT voltage was low at around 3.4V and Guardian would not proceed. Relocking the SHG did not seem to move the PZT to a better place, so I simply lowered the minimum SHG PZT voltage threshold in SQZ_MANAGER from 5 to 3 and loaded the Guardian. After that, the SQZ_SHG Guardian is still giving a warning about the PZT voltage being low, but SQZ_MANAGER was able to make it to 'FRED_DEP_SQZ' and otherwise things looked okay, so I took H1 into observing. This may need to be reverted or addressed properly tomorrow. [Tagging SQZ]

LHO General
ryan.short@LIGO.ORG - posted 14:41, Sunday 22 June 2025 (85231)
Ops Eve Shift Start

TITLE: 06/22 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 15mph Gusts, 5mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: H1 has been locked for 19.5 hours and all's quiet.

LHO General
corey.gray@LIGO.ORG - posted 14:39, Sunday 22 June 2025 (85229)
Sun DAY Ops Summary

TITLE: 06/22 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

A nice very quiet shift!  H1 has been humming along (currently at 19.5hr lock), and no intervention was needed during the shift.  Breezes have increased slightly through the day.
LOG:  n/a

LHO VE
david.barker@LIGO.ORG - posted 10:13, Sunday 22 June 2025 (85230)
Sun CP1 Fill

Sun Jun 22 10:09:56 2025 INFO: Fill completed in 9min 52secs

 

Images attached to this report
H1 CAL (CAL)
corey.gray@LIGO.ORG - posted 12:11, Saturday 21 June 2025 - last comment - 08:40, Monday 23 June 2025(85217)
Saturday H1 Calibration Measurement (broadband headless + simulines)

Measurement NOTES:

Attached is a screenshot of the Calibration Monitor + pdf of Pydarm Report

Images attached to this report
Non-image files attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 08:40, Monday 23 June 2025 (85236)

I've been adding the broadband measurements to this template which exists in [userapps]/cal/h1/dtt_templates

Images attached to this comment
H1 ISC (Lockloss)
elenna.capote@LIGO.ORG - posted 17:21, Wednesday 18 June 2025 - last comment - 12:36, Monday 30 June 2025(85167)
Two ~13 Hz ring up locklosses identified

Oli, Elenna

Oli and I combed through some of the recent locklosses by hand, and noticed that there are at least two that have a 13 Hz oscillation in the LSC channels just before the lockloss.

1434317297

1434276630

This is reminiscent to us of PRCL losing gain due to thermalization which has caused 11 Hz ring ups before. We should keep an eye out. Note that one of the above locklosses has the "earthquake" tag, but it's very clear that the ring up caused the lockloss.

Oli and I went back about 1 week and checked the NLN locklosses by eye and only found these two so far.

To start, we can periodically check PRCL OLG or other LSC OLGs during thermalization to make sure we aren't losing significant optical gain. Or we can inject a line during commissioning.

Images attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 10:28, Monday 23 June 2025 (85242)

Another 13 Hz ringup here: 85239

ryan.crouch@LIGO.ORG - 12:36, Monday 30 June 2025 (85436)

Another one: alog85428

H1 CDS
david.barker@LIGO.ORG - posted 16:42, Wednesday 18 June 2025 - last comment - 10:44, Monday 23 June 2025(85164)
DAQ DC0 crash

At 16:14:31 PDT h1daqdc0 crashed. Its EPICS IOC stopped running resulting in white boxes on MEDM. Last log was 15:56.

I connected a monitor to its VGA port, its console was showing the login prompt. The cursor was not flashing and an attached keyboard was unresponsive.

Erik and I rebooted the machine by pressing the front panel RESET button. It booted and started with no problems.

Currently we don't know why dc0 froze this way.

Comments related to this report
david.barker@LIGO.ORG - 08:44, Thursday 19 June 2025 (85177)

FW0 full frame gap due to crash and restart:

Jun 18 16:14 H-H1_R-1434323584-64.gwf
Jun 18 16:26 H-H1_R-1434324288-64.gwf
 

david.barker@LIGO.ORG - 10:44, Monday 23 June 2025 (85244)
Displaying reports 1481-1500 of 84282.Go to page Start 71 72 73 74 75 76 77 78 79 End