Displaying reports 2281-2300 of 85678.Go to page Start 111 112 113 114 115 116 117 118 119 End
Reports until 17:06, Friday 18 July 2025
LHO General
corey.gray@LIGO.ORG - posted 17:06, Friday 18 July 2025 (85842)
Fri Ops DAY Shift Summary

TITLE: 07/18 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

H1's been locked the entire Day shift with a lock of over 10hrs!  Fairly quiet day with decent triple coincidence.  There was a forecast of a Red Flag wind day, but it's not been horrible---Corner Station gusts have gotten over 30mph, but nothing worse than that so far.

Did not get to offload the SR.....SCRATCH THAT!  H1 had a lockloss right at the end of the shift, so I took the opportunity to Offload the SR3 Pitch Offset (see alog 85855)....but SDF Revert took the Offset back to 32.3.  
LOG:

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 16:56, Friday 18 July 2025 - last comment - 16:02, Monday 25 August 2025(85852)
first look at sqz dataset, limit on IFO to OMC mode mismatch

I've taken a first look at the data that Camilla and Matt took in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=85813

In the past, I've started modeling these data sets by assuming a fixed arm power, and finding IFO readout losses that are needed to fit the measured shot noise without squeezing at 2kHz.  This time, inspired in part by a comment from Begum, I instead used only the known IFO readout losses and attributing the rest to mode mismatch between the IFO and OMC, this allows us to make an upper limit on the mode mismatch from the IFO to the OMC.

From the google sheet , I will include SRC losses as a known readout loss (although the are listed as sqz injection losses, I think for the IFO they are readout losses), 0.99(SRC)*0.995(OFI)*0.9993(OM1)*0.985(OM3)*0.9904(QPD)*0.956(OMC)*0.98(QE) = 10% known readout losses.  The known injection losses (not including SRC losses) are then 0.985(OPO)*0.99^3 (3 SFI passes)0.99 (FC QPDs)*0.99(other HAM7 loss) *0.99 (OFI)= 7.2%

Fitting the level of squeezing and anti-squeezing at 2kHz suggests an NLG of 13.2 (fairly close to Camilla's measurement of 13.4), and a total efficiency of 0.752 using the Aoki equations (treating mismatches as losses).  Looking at the interactive sqz gui, the IFO to OMC mismatch reduces the measured sqz anf anti squeezing at 2kHz, but the mismatch phase only has an impact below about 400Hz. 

Using only the known readout (10%) and injection losses (7.2%), perfect sqz to OMC mode matching, we can get some limit on the amount of OMC to IFO mode mismatch that can be compatible with our 2kHz squeezing.  5.1% mismatch (which would imply 355kW in the arm cavity) seems too high to be compatible with our squeezing, while a mode mismatch of 3.7% with 350kW in the arm does seem compatible if the sqz to OMC mode matching is perfect. So, we can take 3.7% as an upper limit on the IFO to OMC mode matching that is compatible with known squeezing losses.  The data could be compatible with mode mismatches as low as 2.3% (345kW in arms) without introducing any extra losses.   Any unknown squeezer losses, like excess crystal losses, will reduce this amount.  The arm power of upper limit that we'd infer from this is 350kW, but this depends sensitvely on what we assume the non quantum noise is at 2kHz.  I will try to redo this estimate soon using the cross correlation data that Elenna is working on to have more confident limits on the arm power.

These first two plots show that this model isn't well tuned at a few hundred Hz, I haven't tried to set either the SRCL offset or homodyne angle yet, or the OMC to IFO mismatch phase.  At first glance it does not seem like I will be able to make this match well by adjusting the mismatch phase. 

The last two plots show the squeezing level in dB, just so that we have a plot we can look at.  The script to make these plots are committed here

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 16:02, Monday 25 August 2025 (85942)

Posting this comment which has been saved in my drafts, which I thought I'd posted a while ago:

I've taken a second quick look at this data, constructing a model in the same way that I've done in the past without any mode mismatches.  This works OK, and suggests that for 347kW arm power we'd have 2.5% unknown readout losses and

This data can be fit reasonably well without frequency independent losses, no mode mismatch and an SRC detuning, simliar to previous data sets.  This doesn't mean that there's not a mode mismatch, but there's not new evidence for mode mismatch here.  Kevin did mention that I should look at scenarios where we have both SQZ to OMC mismatches and IFO to OMC mismatch.  Indeed, when I do that the mismatch phase is important for the sqz and anti-sqz level at 2kHz. 

Images attached to this comment
H1 SUS (SUS)
corey.gray@LIGO.ORG - posted 16:54, Friday 18 July 2025 (85855)
SR3 Offset Offload

Lockloss toward the end of the shift, but took the opportunity to do the SR3 Pitch Offset Offload (per Oli's alog 85830). 

Sheila ran me through what we should change the SR3 Pitch to once we zero/offload the SR3 Dither Offset:

Made the change above, but an SDF Revert undid the Offset change!  So, I zeroed the SR3 Pit Dither Offset once again.  Now we are waiting for DRMI to lock.

Attached are screenshots of the (1) ndscope showing the offload and (2) medms involved.

Images attached to this report
H1 PSL (PSL)
corey.gray@LIGO.ORG - posted 13:52, Friday 18 July 2025 (85850)
PSL Status Report (FAMIS #26431)

This is for FAMIS #26431.

Laser Status:
    NPRO output power is 1.87W
    AMP1 output power is 70.35W
    AMP2 output power is 141.0W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 3 days, 2 hr 42 minutes
    Reflected power = 23.67W
    Transmitted power = 105.6W
    PowerSum = 129.3W

FSS:
    It has been locked for 0 days 8 hr and 10 min
    TPD[V] = 0.8367V

ISS:
    The diffracted power is around 3.8%
    Last saturation event was 0 days 8 hours and 10 minutes ago


Possible Issues:
    PMC reflected power is high

H1 AOS (DetChar)
preeti.sharma@LIGO.ORG - posted 10:46, Friday 18 July 2025 - last comment - 15:57, Tuesday 29 July 2025(85848)
Investigation of Lock losses due to Earthquakes

Preeti, Gaby

With the help of Ashley Patron's Eqlock script, we calculated the locklosses caused due to EQs for each observing runs. This is a part of the study of investigating the correlation between the microseism and duty-cycle (alog), so we chose winter months (Nov, Dec, Jan and Feb) of each observing run and calculated the vertical velocity of the ground from z-channel and horizontal velocity which is the quadrature sum of x and y channels at the time of locklost due to an EQ. We also did the same study for LLO (alog). 

Conclusion:

Images attached to this report
Comments related to this report
preeti.sharma@LIGO.ORG - 12:04, Thursday 24 July 2025 (85964)

After removing EQ events which happend during the locklosses, the probability of surviving lock during an EQ in O2 winter was found to be 54%, O3b winter was 64%, O4a winter was 73% and O4b winter was 41%. 

preeti.sharma@LIGO.ORG - 15:57, Tuesday 29 July 2025 (86082)

Some corrections have been done in the script after getting Derek's feedback and have attached the updated scatter plot between peak horizontal ground motion and peak vertical ground motion of Earthquake events, also data table including total number of EQs and lock probability in each observing runs' winters. Although, the number of surviving EQ events are still lower in O4 than O3. 

Images attached to this comment
LHO VE
david.barker@LIGO.ORG - posted 10:43, Friday 18 July 2025 (85849)
Fri CP1 Fill

Fri Jul 18 10:09:26 2025 INFO: Fill completed in 9min 23secs

Gerardo confirmed a good fill curbside.

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 07:41, Friday 18 July 2025 - last comment - 10:40, Friday 18 July 2025(85841)
Fri Ops Day Transition

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

H1's been locked for 1.25hrs w/ 4 locklosses over night each with decent recovery times.  Microseism is trending down over last 24hrs; forecast is for high winds (redflag warning) in the afternoon.

Comments related to this report
elenna.capote@LIGO.ORG - 10:25, Friday 18 July 2025 (85846)

The lockloss that occurred at 2025-07-18 08:00 UTC (not tagged as a glitch) was preceded by what appears to be a large kick in the yaw ASC. First attachment shows the CSOFT Y and CHARD Y signals a few seconds before the locklosses. This is also apparent in the test mass L2 signals in the second attachment.

Images attached to this comment
corey.gray@LIGO.ORG - 08:06, Friday 18 July 2025 (85843)

Of the 4 locklosses overnight, we had (1) ETMx Glitch lockloss.

elenna.capote@LIGO.ORG - 10:40, Friday 18 July 2025 (85847)

The other two locklosses last night seem by eye to have the same behavior (2025-07-18 12:07:24 UTC and 2025-07-18 04:20:15 UTC). Within ~100 ms of the lockloss time, there is something glitchy in the darm error signal where the error signal drops sharply. It looks like the glitchy behavior starts in DARM IN1 slightly before ETMX L3 starts behaving weirdly, but that's hard to tell since I'm just looking at ndscopes.

Images attached to this comment
H1 General
oli.patane@LIGO.ORG - posted 22:01, Thursday 17 July 2025 (85840)
Ops Eve Shift End

TITLE: 07/18 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

Relocking and in MOVE_SPOTS. Relocking after the first lockloss of my shift was hands off, and this relock has been hands off this time so far too, so it's been easy. I did not get a chance to offload the SR3 dither offset onto the sliders (85830), but that can easily be done later, especially since it's already been like that for over 5 years!

We had GRB-Short E581624 come in while we were Observing earlier

LOG:

23:30UTC Observing and have been Locked for 3 hours
    00:14 GRB-Short E581624
02:02 Lockloss
03:34 NOMINAL_LOW_NOISE
    03:36 Observing
04:20 Lockloss

H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 21:21, Thursday 17 July 2025 (85839)
Lockloss

Lockloss at 2025-07-18 04:20 UTC after 46 minutes locked

H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 19:03, Thursday 17 July 2025 - last comment - 20:38, Thursday 17 July 2025(85837)
Lockloss

Lockloss at 2025-07-18 02:02 UTC after 5.5 hours locked

Comments related to this report
oli.patane@LIGO.ORG - 20:38, Thursday 17 July 2025 (85838)

03:36 UTC Observing

During relocking I reloaded the h1asc model filters in so Elenna's new filters could be added (diffs).

Images attached to this comment
H1 CDS
david.barker@LIGO.ORG - posted 17:25, Thursday 17 July 2025 (85836)
H1 in STANDDOWN

H1 is in stand-down which gave me the opportunity to test the notification on the CDS Overview MEDM

Images attached to this report
LHO General
thomas.shaffer@LIGO.ORG - posted 16:32, Thursday 17 July 2025 (85826)
Ops Day Shift End

TITLE: 07/17 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Locked for 3 hours. We had one lock loss that I'm still not sure of the cause, and relocked was straight forward with an initial alignment.
LOG:

H1 General
oli.patane@LIGO.ORG - posted 16:28, Thursday 17 July 2025 (85834)
Ops Eve Shift Start

TITLE: 07/17 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 10mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.20 μm/s
QUICK SUMMARY:

Observing at 145Mpc and have been Locked for almost 3 hours. Everything is looking good.

H1 PSL (IOO)
jennifer.wright@LIGO.ORG - posted 11:56, Thursday 17 July 2025 - last comment - 15:32, Monday 21 July 2025(85795)
ISS array work - horizontal scan

Jennie, Rahul

On Tuesday Rahul and I took the measurements for the horizontal coupling in the ISS array currently on the optical table.

The QPD read 9500 e-7 W.

The X position was 5.26 V, the Y position was -4.98 V.

PD DC Voltage [mV] pk-pk AC Voltage [mV] pk-pk
1 600 420
2 600 380
3 600 380
4 600 420
5 800 540
6 800 500
7 600 540
8 800 540

After thinking about this data I realise we need to retake it as we should record the mean value for the DC coupled measurements. This was with a 78V signal applied from the PZT driver and an input dither signal of 2 Vpp at 100Hz on the oscilloscope and I think 150 mA pump current on the laser.

Comments related to this report
jennifer.wright@LIGO.ORG - 16:14, Friday 18 July 2025 (85853)

Rahul, Jennie W

 

Yesterday we went back into the lab and retook the DC and AC measurements while horizontal dither was on while measuring using the 'mean' setting and without changing the overall input pointing from what it was in the above measurement.

 

PD DC Voltage [V] mean AC Voltage [V] mean
1 -4.08 -0.172
2 -3.81 0.0289
3 -3.46 0.159
4 -3.71 0.17
5 -3.57 -0.0161
6 -3.5 0.00453
7 -2.91 0.187
8 -3.36 0.0912

 

 

QPD direction Mean Voltage [V] Pk-Pk Voltage [V]
X 5.28 2.20
Y -4.98 0.8

QPD sum is roughly 5V.

 

Next time we need to plug in the second axis of the PZT driver so as to take the dither coupling measurement in the vertical direction.

jennifer.wright@LIGO.ORG - 15:12, Monday 21 July 2025 (85890)

horizontal dither calibration = 10.57 V/mm

dither Vpk-pk on QPD x-direction = 2.2V

dither Vpk-pk on QPD y-direction = 0.8V

dither motion in horizontal direction in V on QPD = sqrt(2.2^2 + 0.8^2)

motion in mm on QPD that corresponds to dither of input mirror = sqrt(2.2^2 + 0.8^2) / 4.644 = 0.222 mm

Code is here for calibration of horizontal beam motion to QPD motion plus calibration of dither measurements.

Non-image files attached to this comment
jennifer.wright@LIGO.ORG - 15:32, Monday 21 July 2025 (85891)

To work out the relative intensity noise:

RIN = change in power/ power

= ( change in current/ current) / responsivity of PD

= (change in voltage/voltage) / (responsitvity * load resistance)

 

Therefore to minimise RIN we want to minimise change in voltage / voltage for each PD.

To get the least coupling to array input alignment we work out

relative RIN coupling = (delta V/ V) / beam motion at QPD

 

This works because the QPD is designed to be in the same plane as the PD array.

 

PD DC Voltage [V] mean AC Voltage [mV] pk-pk Beam Motion at QPD [mm] Relative Coupling [1/m]
1 -4.08 420 0.222 465
2 -3.81 380 0.222 450
3 -3.46 380 0.222 496
4 -3.71 420 0.222 511
5 -3.57 540 0.222 683
6 -3.5 500 0.222 645
7 -2.91 540 0.222 838
8 -3.36 540 0.222 726

 

These are all a factor of 50 higher than those measured by Mayank and Shiva but after discussion with Keita either we need higher resolution measurements or we need to further optimise input alignment to the array to minimise the coupling.

H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 21:33, Wednesday 16 July 2025 - last comment - 08:38, Friday 18 July 2025(85805)
Lockloss

Lockloss at 2025-07-17 04:11 UTC due to a power issue with ETMX and TMSX. Currently in contact with Dave and Fil is on his way in.

ETMX M0 and R0 watchdogs tripped

ETMX and TMSX OSEMs are in FAULT

ETMX ESD off

ETMX HWWD notified that it would trip soon, so SEI_ETMX was preemptively put into ISI_OFFLINE_HEPI_ON to keep ISI from getting messed up when it trips

 

Comments related to this report
david.barker@LIGO.ORG - 21:46, Wednesday 16 July 2025 (85806)

H1SUSETMX ADC channels zeroed out at 21:11:39. SWWDs did not trip because there is no RMS on the OSEM signals, but the HWWD completed its 20 minute countdown and powered down the three ISI coil drivers at 21:32. This indicates ETMX's top stage OSEMs have lost power.

I've opened WP12692 to cover Fil going to EX to investigate.

david.barker@LIGO.ORG - 23:43, Wednesday 16 July 2025 (85807)

During the recovery the +24VDC power supply for the SUS IO Chassis was glitched which stopped all the h1susex and h1susauxex models. To recover I first did a straight forward reboot of h1susauxex (no Dolphin), it came back with no issues.

To reboot h1susex was more involved, remember that the EX Dolphin switch was damaged by the 06 April 2025 power outage and has no network control. The procedure to reboot h1susex I used was:

  • caput H1:IOP-SEIEX_REMOTE_IPC_PAUSE 1
  • caput H1:IOP-ISCEX_REMOTE_IPC_PAUSE 1
  • caput H1:IOP-SUSEX_REMOTE_IPC_PAUSE 1
  • on h1susex:
  • rtcds stop --all
  • sudo systemctl reboot

When h1susex came back, I verified all the IO Chassis cards were present (they were all there)

I unpaused the SEI and ISC IPC by writing a 0 to their IPC_PAUSE channels.

The HWWD came back in nominal state.

I reset the SUS SWWD DACKILLs and unbypassed the SEI SWWD.

DIAG_RESET to clear all the IPC errors (it did so) and clear DAQ CRCs (they cleared).

Handed systems over to control room (Oli and Ryan S).

david.barker@LIGO.ORG - 23:50, Wednesday 16 July 2025 (85808)

From Fil:

-18VDC Power supply had failed and was replaced.

Power supply is in rack VDD-2, location U25-U28, right-hand supply, label [SUS-C1 C2]

old supply (removed) S1202024

new supply (installed) S1300288

 

david.barker@LIGO.ORG - 08:47, Thursday 17 July 2025 (85814)

Last night's HWWD sequence is shown below. Reminder that at +40mins the SUS part of the HWWD trips, which sets bit2 of the STAT. This opens internal relay switches, but since we don't route the SUS drives through the HWWD unit (too noisy) this has no effect on operations. The delay between 22:52 and 23:20 is because h1iopsusex was down between 23:01 and 23:20.

Images attached to this comment
david.barker@LIGO.ORG - 09:23, Thursday 17 July 2025 (85816)
filiberto.clara@LIGO.ORG - 16:34, Thursday 17 July 2025 (85835)

Fan motor seized on failed power supply.

david.barker@LIGO.ORG - 08:38, Friday 18 July 2025 (85844)

Wed16Jul2025
LOC TIME HOSTNAME     MODEL/REBOOT
23:15:13 h1susauxex   h1iopsusauxex
23:15:26 h1susauxex   h1susauxex  
23:20:21 h1susex      h1iopsusex  
23:20:34 h1susex      h1susetmx   
23:20:47 h1susex      h1sustmsx   
23:21:00 h1susex      h1susetmxpi 
 

Displaying reports 2281-2300 of 85678.Go to page Start 111 112 113 114 115 116 117 118 119 End