Displaying reports 1-20 of 83002.Go to page 1 2 3 4 5 6 7 8 9 10 End
Reports until 23:25, Monday 30 June 2025
H1 SQZ
oli.patane@LIGO.ORG - posted 23:25, Monday 30 June 2025 - last comment - 23:33, Monday 30 June 2025(85450)
Ops OWL Intervention

I got called for the same issue that Tony and Sheila had earlier today where the SHG PZT hit its voltage limit. I followed the very clear instructions given in that alog and just adjusted the PZT slider, and we were able to lock the SHG. I accepted the sdf for the SHG PZT offset.

Images attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 23:33, Monday 30 June 2025 (85451)

After this, I quickly popped out of Observing to run SQZ ANG Adjust to try and get the range higher.

H1 General
anthony.sanchez@LIGO.ORG - posted 22:11, Monday 30 June 2025 (85449)
Ops EVE Shift End

TITLE: 07/01 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
SQZr trouble at the start of the lock but recovered and got to Observing at 00:07 UTC.

H1 was locked fine for 4 hours and 35 Minutes.
Then all the sudden Unknown Lockloss at 2025-07-01 03:56:04 UTC.

I tried to allow H1 to relock itself but it wanted me to find ASL-Y arm by hand and then seemed to get trapped in a PRMI loop. So after about 30 Minutes I did an Initial Alignment.
This did allow for a quick lock of DRMI_1F. 
H1 is currently at ENGAGE_SOFT_LOOPS and locking Quickly.  


LOG:

Start Time System Name Location Lazer_Haz Task Time End
00:25 PCAL F Llamas PCAL Lab yes Settign up measurements 01:13
H1 General (Lockloss)
anthony.sanchez@LIGO.ORG - posted 21:50, Monday 30 June 2025 (85448)
Lockloss from NLN

Unknown lockloss @ 3:56:07 UTC
No noticeable Seismic activity.
No PI ring Ups.
No saturations aside from HAM6 from the Fast Shutter.

Images attached to this report
H1 General
anthony.sanchez@LIGO.ORG - posted 19:39, Monday 30 June 2025 (85447)
PCAL Lab TX module Maintenance complete

On Friday Jun 27th Francisco and I went to the the PCAL lab and did a PCAL TX module maintenance according to T1600436.
AOM alignment was touched up

Results:

Laser SN05  
Date June-26-2025
Laser Shutter Check Fail
Max OFS Offset 7.2V
95% OFS Offset 6.84V
Operating OFS Offset 3.42V
Laser Output Power 1.97W
Rejected Laser Power 3.3mW
AOM Input Power 1.92W
Max Diffracted Power 1.23W
Un-Diffracted Power 0.500W
AOM Diffraction Efficiency 64%
AOM Rejected Power 3.3mW
TxPD Power 1.4mW
OFSPD Power 1.73mW
Outer Beam Power 294mW
Inner Beam Power 292mW
Output Beam Power Ratio 0.9932
OFS Gain 7.50V
OFS Phase Margin 43.7
ALOG  
Non-image files attached to this report
H1 SUS (SEI, SUS)
edgard.bonilla@LIGO.ORG - posted 17:42, Monday 30 June 2025 (85446)
Created new OSEM estimator fits for SR3 Yaw

Ivey and Edgard,

We just finshed a fit of the Yaw-to-Yaw transfer functions for the OSEM estimator using the measurements that Oli took for SR3 last Tuesday [see LHO: 85288].

The fits were added to the Sus SVN and live inside '~/SusSVN/sus/trunk/HLTS/Common/FilterDesign/Estimator/fits_H1SR3_2025-06-30.mat' . They are already calibrated to work on the filter banks for the estimator and can be installed using 'make_SR3_yaw_model.m', which lives in the same folder [for reference, see LHO: 84041, where Oli got the fits running for a test].

Attached below are two pictures of the fits we made for the estimator.

 

The first attachment shows the Suspoint Y to M1 DAMP Y fit. We made sure to fit the asymptotic behavior as well as we could, which ends up being 0.95x10^{-3} um/nm (5% lower than expected from the OSEM calibration). The zpk for this fit is

    'zpk([-0.024+20.407i,-0.024-20.407i,-0.044+11.493i,-0.044-11.493i,0,0],[-0.067+21.278i,-0.067-21.278i,-0.095+14.443i,-0.095-14.443i,-0.07+6.405i,-0.07-6.405i],-0.001)'

 

The second attachment shows the M1 drive Y to M1 DAMP Y fit. We kept the same poles that we had for the other fit, but manually fit the zeros and gain to make a good match. The zpk for this fit is

'zpk([-0.051+8.326i,-0.051-8.326i,-0.011+19.259i,-0.011-19.259i],[-0.067+21.278i,-0.067-21.278i,-0.095+14.443i,-0.095-14.443i,-0.07+6.405i,-0.07-6.405i],12.096)'

Hopefully Oli and co. will have time to test this soon!

Images attached to this report
H1 General
anthony.sanchez@LIGO.ORG - posted 16:42, Monday 30 June 2025 - last comment - 17:19, Monday 30 June 2025(85444)
Monday Ops Eve Shift report.

TITLE: 06/30 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 10mph Gusts, 4mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:

H1 Is Currently Locked at NLN {600} But not Observing due to a SQZ_SHG issue:
Error SQZ_SHG [LOCKED.run] USERMSG 0: PZT voltage limits exceeded.
Sheila is currently working on the issue.
 

Comments related to this report
anthony.sanchez@LIGO.ORG - 17:19, Monday 30 June 2025 (85445)OpsInfo, SQZ

Sheila Fixed the issue, I have attached soem pictures to help future Ops that find this issue:
Sitemap -> SQZ -> SQZ_OVERVIEW -> SQZT0 ->  PZT -> Move H1:SQZ-SHG_PZT_OFFSET slider.

We Now have a "pump fiber rej power in ham7, nominal 35e-3, align fiber pol on sqzt0" error message on SQZ-OPO_LR. nopted will do tomorrow.

Then we took SQZ_ANG_ADJUST Guardian to ADJUST_SQZ_ANG_ADF [10]  which kinda worked but didn't  improve sqzing and reverted back.

I then accepted the SDFs and now we're back in Observing at 00:07:25 UTC.

An NDScope of what the GRD-SQZ_SHG Guardian was doing.

Images attached to this comment
H1 General
ryan.crouch@LIGO.ORG - posted 16:36, Monday 30 June 2025 (85437)
OPS Monday day shift start

TITLE: 06/30 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Tony
SHIFT SUMMARY: We've had to relock twice, the second time we struggled a bit with DRMI. We're currently locked at NLN but trying to fix a SQZ SHG PZT issue.
LOG:                                                                                                                                 

Start Time System Name Location Lazer_Haz Task Time End
14:50 FAC Randy EndX N Chiller yard pump checks 16:01
15:13 FAC Kim MidY MidY Tech clean 16:20
15:14 FAC Nellie MidX N Tech clean 16:20
16:24 EE Ken Mezz N Electrical work 18:56
16:49 FAC Chris VAC Prep N Sanding 17:39
19:34 FAC Randy MidY N Inventory 20:30
20:06 FAC Tyler Mids N FAMIS checks 20:36
22:39 CAL Tony PCAL lab LOCAL Prep for tomorrows measurement 22:58
H1 CDS
jonathan.hanks@LIGO.ORG - posted 15:02, Monday 30 June 2025 (85443)
Restarted the daqd and nds processes on h1daqnds0

The h1daqnds0 system stopped accepting connections on its main nds1 port (8088).  We restarted the rts-nds and rts-daqd services around 2:59pm localtime.

There were no log messages or dmesg output.

H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 13:48, Monday 30 June 2025 (85442)
20:46 UTC lockloss

20:46 UTC lockloss

H1 ISC (SQZ)
jennifer.wright@LIGO.ORG - posted 13:07, Monday 30 June 2025 (85434)
DARM Offset Steps while changing CO2s

Jennie W, Sheila, Ryan C, Ibrahim, Corey

 

Over the last 3 weeks three DARM offstep measurements (where we change the DARM offset to look at the fraction of the light from the differential mode which makes it past the OMC) have been taken.

This is so we can get data points to compare to my model of ARM to OMC mode-matching. These were done at three different CO2 X power levels.

 

Measurement 1: 2025/06/18 20:44:55 UTC

CO2 central heating on ITMX: 1.698W

CO2 central heating on ITMY: 1.694 W

The test is run with /ligo/gitcommon/labutils/darm_offset_step/auto_darm_offset.py . The data is processed with plot_darm_optical_gain_vs_dcpd_sum.py .

Graphs of the power after the OMC vs. optical gain are in the first plot,  optical gain vs. offset and anti-symmetric port power vs. power out of the omc are in this document.

The average contrast defect is 1.07 mW, the junk light is 679 mW, the transmission of the differential mode light at the AS port by the OMC is 1/1.217 = 82.2%.

 

Measurement 2: 2025/06/20 15:11:46 UTC

CO2 central heating on ITMX: 1.698 W

CO2 central heating on ITMY: 1.711 W

The test is run with /ligo/gitcommon/labutils/darm_offset_step/auto_darm_offset.py . The data is processed with plot_darm_optical_gain_vs_dcpd_sum.py .

Graphs of the power after the OMC vs. optical gain are in the first plot,  optical gain vs. offset and anti-symmetric port power vs. power out of the omc are in this document.

The avergae contrast defect is 1.03 mW, the junk light is 677 mW, the transmission of the differential mode light at the AS port by the OMC is 1/1.212= 82.5%.

 

Measurement 3: 2025/06/30 15:06:50 UTC

CO2 central heating on ITMX: 1.698 W

CO2 central heating on ITMY: 1.721 W

The test is run with /ligo/gitcommon/labutils/darm_offset_step/auto_darm_offset.py . The data is processed with plot_darm_optical_gain_vs_dcpd_sum.py .

Graphs of the power after the OMC vs. optical gain are in the first plot,  optical gain vs. offset and anti-symmetric port power vs. power out of the omc are in this document.

The avergae contrast defect is 1.09 mW, the junk light is 694 mW, the transmission of the differential mode light at the AS port by the OMC is 1/1.212= 82.5%.

 

This is not a very good test for our purposes as I think we want a larger change in mode-matching from thermal tuning to inform our simulations of Arm->OMC mode-mis-match.

Each time we have stepped the CO2Y down (all these darm offset measurements were meant to be repeated after decreasing the CO2 power) for this test (measurement 2 on the 20th June, alog 85238 shows attempt from 23rd June, alog 85335 shows attempt from the 25th June, alog 85429 is measurement 3) we have lost lock, so we might not be able to repeat this measurement with a larger CO2 step.

 

Images attached to this report
Non-image files attached to this report
H1 SQZ
sheila.dwyer@LIGO.ORG - posted 13:03, Monday 30 June 2025 (85427)
slow range degradations due to squeezing, trying to turn on SQZ angle servo

Over the weekend the ifo range has been slowly degrading due to loss of squeezing, as noted in both Ryan and Ibrahim's shift alogs. 

The attached trend shows the range drfiting with the sqz blrms 3 (centered at 350 Hz).  We could implement servos for the squeezing angle demod phase using the ADF (error signal for this servo shown in purple), or for the OPO temperature, or both.

I stepped the sqz angle demod phase to look at the ADF error signal, using z step -s 30 H1:SQZ-CLF_REFL_RF6_PHASE_DELAYSTEP +111,24 (second attachment) I then adjusted H1:SQZ-ADF_VCXO_PLL_PHASE to get a zero crossing near where the squeezer blrms were low and repeated a smaller demod angle scan, which had the error signal crossing 0 at good squeezing. I edited the guardian to ask it to turn this servo back on, (and changed the setpoint and nominal state).  The servo was osciallting a bit so I reduced the gain from -0.5 to -0.2.  Then servo went in the wrong directon, and we lost lock. 

After relocking the servo worked well, in the early part of the lock when the SQZ ASC is off. 

LLO has done some work on automating the temperature adjustment:

Images attached to this report
H1 PSL
ryan.short@LIGO.ORG - posted 12:56, Monday 30 June 2025 (85441)
PSL 10-Day Trends

FAMIS 31092

Nothing much to report other than the FSS TPD signal has been dropping over the past week, so Jason plans to do a RefCav alignment tomorrow. PMC REFL has also come down very slightly.

Images attached to this report
H1 TCS
oli.patane@LIGO.ORG - posted 12:55, Monday 30 June 2025 (85440)
TCS Chiller Water Level Top-Off FAMIS

Closes FAMIS#27818, last checked 85024 (I am a week late)

TCSX: 30.5, no water added

TCSY: 10.6, no water added

No leak in water cup

H1 GRD (ISC)
oli.patane@LIGO.ORG - posted 12:36, Monday 30 June 2025 (85435)
PRCL2 GAIN adjustment added to THERMALIZATION guardian

Elenna, Sheila, Oli

I've added thermalization ramping for the PRCL2 gain so that it ramps from 1.0 to 1.9 over the first 75 minutes at max power. The 'unthermalized' (1.0) and 'thermalized' (1.9) values are taken from lscparams in the new dictionary 'prcl2_gain', so any changes to be made in the future to those values should be set in that dictionary, and then the THERMALIZATION guardian reloaded so that it grabs those new values.

This addition is pretty much a copy of the way we ramp the SRCL offset, but for PRCL gain of course..

This change to the THERMALIZATION guardian as well as the dictionary addition to lscparams have been committed to svn as r32157.

Images attached to this report
H1 ISC
elenna.capote@LIGO.ORG - posted 12:35, Monday 30 June 2025 (85431)
PRCL loop adjustments

We continue to have 13 Hz ringups in the LSC that cause locklosses, so I took at look at what's going on with PRCL (it's the usual culprit). I measured the OLG every few minutes after we reached NLN. I found that PRCL loses a factor of 2 gain over the first 40 minutes of NLN. The current design is set to have PRCL with a UGF of 30 Hz once the gain settles after thermalization. However, this leads to >10 dB gain peaking at the start of the lock. There's overall not a lot of phase in the loop design, and if the gain gets too low this is causing the locklosses.

I looked at the loop design, and reminded myself of Gabriele's intentions with the PRCL redesign, here. His design applied the Dcntrl filter, which means to go back to the old design we only have to disengage this filter. You can see from the design comparison in his alog that the original design has a much broader phase. We might inject more noise by going back to the old design, but I'm not sure that will be an issue, especially if we continue to run the PRCL feedforward.

Turning off the Dcntrl filter gives more phase at high frequency, meaning we can increase the PRCL UGF. I increased the PRCL2 gain to 1.9 and got a UGF of 50 Hz, with about 35 deg phase. If we don't change this gain at all, PRCL will start in the lock with a UGF of 100 Hz and a phase margin of 18 degrees if the digital gain is always set to 1.9. This will then thermalize down to 50 Hz.

I also disengaged the 3.4 Hz resgain filter, because we no longer need to suppress motion at that frequency, and hopefully we'll get back a little more phase at low frequency as well.

Oli is reworking the thermalization guardian to ramp the PRCL2 gain from 1 to 1.9 over the first hour, starting after we reach max power.

I commented out the lines in lownoise_length_control that change the PRCL shape and loop gain.

I checked the PRCL noise injection with the feedforward template, and there slightly more noise injection from 20-30 Hz, but I'm not sure that's a problem.

I updated the SDF for the filter changes, and to unmonitor H1:LSC-PRCL2_GAIN since the guardian will now update that gain.

Plot 1 shows the evolution of PRCL olg with the 30 Hz UGF design, Plot 2 shows the evolution of the loop suppression

Plot 3 and Plot 4 show the OLG and loop suppression respectively with the 50 Hz UGF design

Plot 5 compares a PRCL coupling measurement from last week with today.

Images attached to this report
H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 11:23, Monday 30 June 2025 - last comment - 12:52, Monday 30 June 2025(85432)
18:23 UTC lockloss (1h33m lock)

18:23 UTC lockloss alog85433

Comments related to this report
ryan.crouch@LIGO.ORG - 12:52, Monday 30 June 2025 (85439)

19:26 UTC back to NLN

H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 08:46, Monday 30 June 2025 - last comment - 12:52, Monday 30 June 2025(85428)
15:40 UTC lockloss (19h59m lock)

15:40 UTC lockloss while we were running the CO2 stepper. alog85429

Images attached to this report
Comments related to this report
ryan.crouch@LIGO.ORG - 12:52, Monday 30 June 2025 (85438)

16:50 UTC back to NLN

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

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