Displaying reports 161-180 of 85556.Go to page Start 5 6 7 8 9 10 11 12 13 End
Reports until 01:10, Sunday 02 November 2025
H1 General
oli.patane@LIGO.ORG - posted 01:10, Sunday 02 November 2025 - last comment - 06:00, Sunday 02 November 2025(87906)
OPS OWL Intervention pt 2: please go down secondary microseism

Got called again because we can't get past OFFLOAD_DRMI_ASC due to excessively high secondary microseism. We've had three DRMI catches in the last hour, all three of which died before finishing offloading DRMI ASC. Locklosses were from TRANSITION_DRMI_TO_3F, TURN_ON_BS_STAGE2, and DRMI_LOCKED_CHECK_ASC. It definitely looks like the issue is the high secondary microseism. The secondary microseism isn't as bad as it was earlier today, but it's still pretty high (nuc5). Looking at the secondary microseism channels in the Z direction (since that's where it's moving us the most), it looks like the level of microseism that we're seeing right now is the level that we last lost lock at (although we didn't lose lock because of the high microseism - there was some weird wiggle).

So since the secondary microseism looks to be heading downward, if this current DRMI can't catch and we lose lock, I'm going to put the detector in DOWN for now and come back in a couple hours to try again. Hopefully by then the secondary microseism will have gone down a bit further and we'll be able to lock.

Images attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 03:23, Sunday 02 November 2025 (87907)

Time to try relocking again. Going to give this a couple hours to try getting past DRMI, and if it can't I'll put the detector in IDLE for the rest of the night.

oli.patane@LIGO.ORG - 06:00, Sunday 02 November 2025 (87908)

Still no luck with getting past DRMI_LOCKED_CHECK_ASC, but secondary microseism levels look to be at a similar level to what we relocked with last time, so I'll let it keep trying. It has been catching multiple times, but it can't stay locked more than a few seconds most times. The length of DRMI locks and places in the code were it loses lock are different every tme, so I don't think it's a different issue?

Going to keep letting the IFO try relocking.

H1 SEI
oli.patane@LIGO.ORG - posted 22:21, Saturday 01 November 2025 (87905)
OPS OWL Quick Call

Got called 6 minutes into my OWL shift due to the BSC2 ST2 ISI stages tripping during MICH_BRIGHT_LOCKED (in INITAL_ALIGNMENT). The rest of the inital alignment finished fine, so we're attempting to lock now, although I know the very high microseism has been making that really hard today.

H1 General
ryan.crouch@LIGO.ORG - posted 22:00, Saturday 01 November 2025 (87904)
OPS Saturday EVE shift summary

TITLE: 11/02 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Microseism
INCOMING OPERATOR: Oli
SHIFT SUMMARY: The secondary microseism is at about the same level as the start of the shift but the wind is much lower. We have not been able to lock DRMI or PRMI for more than a few seconds this shift. The alignment keeps running away, we get stuck in a loop of PRMI to CHECK_MICH. I also adjusted the SQZ SHG_FIBR_REJ power while we we're trying to get DRMI.
LOG: No log.

00:02 UTC IA

After going into CHECK_MICH then back to PRMI it looks worse

02:08 UTC IA

04:50 UTC IA

H1 General
anthony.sanchez@LIGO.ORG - posted 16:33, Saturday 01 November 2025 (87903)
Ops Day shift report.

TITLE: 11/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Microseism
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
H1 has been locked and Observing for 0 hours all day due to High microseism & High wind speeds.
Microseism seems to be slowly coming down.
No calibration was done today.
LOG:
No Log

 

H1 PSL
anthony.sanchez@LIGO.ORG - posted 16:30, Saturday 01 November 2025 (87902)
PSL Status Report - Weekly

FAMIS 27401 PSL Status Report - Weekly
Laser Status:
    NPRO output power is 1.836W
    AMP1 output power is 70.51W
    AMP2 output power is 139.2W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 2 days, 1 hr 40 minutes
    Reflected power = 24.68W
    Transmitted power = 107.0W
    PowerSum = 131.7W

FSS:
    It has been locked for 0 days 0 hr and 42 min
    TPD[V] = 0.5318V

ISS:
    The diffracted power is around 3.4%
    Last saturation event was 0 days 4 hours and 37 minutes ago


Possible Issues:
    PMC reflected power is high

H1 General
ryan.crouch@LIGO.ORG - posted 15:37, Saturday 01 November 2025 (87901)
OPS Saturday EVE shift start

TITLE: 11/01 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Microseism
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 24mph Gusts, 16mph 3min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.83 μm/s 
QUICK SUMMARY:

H1 General
anthony.sanchez@LIGO.ORG - posted 13:56, Saturday 01 November 2025 (87900)
Mid shift update

TITLE: 11/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Microseism
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 39mph Gusts, 30mph 3min avg
    Primary useism: 0.11 μm/s
    Secondary useism: 0.77 μm/s 
QUICK SUMMARY:

No calibration was done due to, being unlocked.
H1 hasn't been able to get past DRMI all morning.
Secondard microseism has fallen a little bit.... but the wind has picked up the slack. :(
The wind's forcast is not looking great either.

LHO VE
david.barker@LIGO.ORG - posted 10:35, Saturday 01 November 2025 (87899)
Sat CP1 Fill

Sat Nov 01 10:08:48 2025 INFO: Fill completed in 8min 44secs

 

Images attached to this report
H1 General
anthony.sanchez@LIGO.ORG - posted 08:08, Saturday 01 November 2025 (87898)
Sat Morning Ops Shift Report.

TITLE: 11/01 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 3mph Gusts, 1mph 3min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.87 μm/s 
QUICK SUMMARY:

Walking in H1 was unlocked and had been for a while.
Looks like it was a H1 called the Ryan S and gave him a  rough 2ndairy useism night for the Owl Shift last night.

I took OPS_Observatory mode back to Microseism since the useism is still elevated unfortunately. I was however able to lock DRMI for a short stint before a lock loss. 
We have a 28ft waves in the Gulf of Alaska, and 17ft waves off the coast of WA. Let's see what sort of locking we can do. 
But on the bright side.... the STS BLRMS dont look as bad, the wind is low, and I can get DRMI to lock! Maybe we can get locked and stay locked throughout this. 
 

Images attached to this report
H1 General
ryan.short@LIGO.ORG - posted 02:48, Saturday 01 November 2025 - last comment - 04:09, Saturday 01 November 2025(87896)
Ops Owl Assistance

H1 called for assistance at 08:20 UTC as it was struggling to relock. Understandable, as the secondary microseism has been rising today and is now to the point where all STS BLRMS are well into the red. After 90 minutes, I finally got H1 to lock DRMI despite good-looking alignment, but it fell apart as it was checking ASC. I'll keep at it for a while, but if the microseism doesn't improve, I may leave H1 down for the night.

Images attached to this report
Comments related to this report
ryan.short@LIGO.ORG - 04:09, Saturday 01 November 2025 (87897)

Not having much luck. Had a couple more unsuccessful attempts at DRMI before running an initial alignment, which doesn't seem to be helping much. I've set H1_MANAGER to try relocking again on its own and I'll check back again in abit.

H1 General
ryan.crouch@LIGO.ORG - posted 22:00, Friday 31 October 2025 (87894)
OPS Friday EVE shift summary

TITLE: 11/01 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: One lockloss with an easy relock, I've left damping off for EX mode1. We've been locked for just over 2 hours.
LOG:

01:29 UTC lockloss

03:41 While in ADS_TO_CAMERAs I saw the 1Hz start so I brought us to ASC Hi Gn and sat for a few minutes before reverting, I slowly stepped through states above LASER_NOISE

03:48 UTC Observing

04:20 UTC The DARM fom started to timeout and lose connection and would stop displaying the data periodically

04:55 UTC Restarted NUC25 to try to revive pimon which I noticed was not running, running just the launch.sh gave an error for it. (The restart did not work either)

H1 AOS (Lockloss)
ryan.crouch@LIGO.ORG - posted 18:31, Friday 31 October 2025 - last comment - 20:50, Friday 31 October 2025(87893)
01:29 UTC lockloss

01:29 UTC lockloss, there was a wiggle in PR_GAIN right before the LL. Lockloss tool looks to be offline for the last hour.

Comments related to this report
ryan.crouch@LIGO.ORG - 20:50, Friday 31 October 2025 (87895)

03:48 UTC Observing

H1 General
anthony.sanchez@LIGO.ORG - posted 16:40, Friday 31 October 2025 (87892)
Spooky Halloween Ops Day Shift Report.

TITLE: 10/31 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
H1 stayed locked througout the entire shift But there was some DARM commotion from 20 ~40 Hz today 
The "Control Room Collectived" decided, warrantlessly, to blame the person slowly driving the boom lift down the length of the beam tube sealing cracks in the top of the beam tube.
We got him on the phone, and the PEM expert asked him to dance do a Seismic injection [18:08 UTC] while we watched him from the roof cameras. 
Turns out the 20-40 Hz noise was not from the boom lift  & may have been from the artillery range west of here.
 

18:59 Superevent Candidate S251031cq  !!



LOG:
                                                                                                                                                                                                                                                                                                

Start Time System Name Location Lazer_Haz Task Time End
15:01 FAC' Randy MidX N Caulking Beam tube & Robert's Seismic Injection test 20:05
18:06 FAC Kim Receiving N Lifting receiving door 18:11
20:04 SPI Ryan S Optics lab N Cleaning opitcs 20:50
22:38 OPS RyanC Optics lab N Swap dust monitors for huddle test 22:47
H1 General
ryan.crouch@LIGO.ORG - posted 15:55, Friday 31 October 2025 (87891)
OPS Friday EVE shift start

TITLE: 10/31 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 149Mpc
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 8mph Gusts, 6mph 3min avg
    Primary useism: 0.11 μm/s
    Secondary useism: 0.48 μm/s 
QUICK SUMMARY:

Images attached to this report
H1 General
matthewrichard.todd@LIGO.ORG - posted 15:12, Friday 31 October 2025 (87890)
POP measurements vs model

M. Todd, S. Dwyer


Overall Summary: we cannot learn enough from the POP measurements in HAM1 to constrain the values of PR2 and PR3.


We double checked all the distances reported from alog 84307 and the distances of the POP lens in the model, and we found a 3(ish) cm discrepancy. We corrected this discrepancy before doing any fitting or analysis. We use the portion of the measurements in front of the POP lens (towards the POP LSC diode),  as they contain enough information at each Gouy phase region in the beam evolution, to fit for a q-parameter in front of the POP lens. We can propagate this to where the other measurements are behind the POP lens to get an understanding of the focal length of the POP lens. Figure 1 shows a plot of the fitted q from the portion of measurements compared to the ones not used.

We saw that this q-parameter was not well collimated behind the POP lens, making us think that the focal length may not be exactly what is in the model/reported. We adjusted the focal length by +2% (reducing lensing power) as is listed in the tolerance of the optic (see D1300313), and found much better agreement with the un-fitted measurements. This is shown in Figure 2, which shows that the overlap with the measurements before the POP lens is better, but the overlap with the model q-parameter is not as good as we would like.

We then increased the radius of curvature of ROM RH3 mirror (in HAM3) by +1%, and saw that the model beam becomes well overlapped with the fitted q-parameter fromt the measurements. This is shown in Figure 3.

Overall, I think this tells us that because we can tweak the parameters of the lenses in the POP path within their specs to give us the overlap we want with the Input mode through the PRC, we cannot use these measurements as a constraint on the values of the PRC telescope optics. It would be great if we could get a few beam profile measurements in transmission of PR2, without the POP lens or RH3 mirror but getting the IMC locked while HAM3 is vented seems unlikely.

Images attached to this report
H1 DetChar (DetChar)
joan-rene.merou@LIGO.ORG - posted 15:03, Friday 31 October 2025 (87889)
Correlation between ITMX and ITMY ESD bias settings and near-30 Hz near-100 Hz line amplitudes
[Joan-Rene Merou, Alicia Calafat, Sheila Dwyer, Robert Schofield]

We have analyzed the evolution of the near-30 Hz and near-100 Hz comb amplitudes, continuing with the work on aLOG 87414. In that alog was shown how there appeared to be a correlation between the ITMY ESD bias and the amplitude of the near-30 Hz and near-100 Hz combs.

In this study, we first listed all time intervals between ITMX and ITMY bias changes from the study Robert Schofield did and reported on aLOG 78925 and the associated entries. Robert changed the biases in a number of occasions "for determining the ITM biases that minimize coupling of electronics ground noise". We wanted to see if this was also true for minimizing the amplitude of lines in DARM.

The full list of constant-bias segments in-between changes is shown in the following table, which defines the start and end GPS times, along with the corresponding ITMX and ITMY bias values. We have added a few data points in between the ones shown in the related Robert aLOGs.

const_start_gps const_end_gps ITMX_bias ITMY_bias
1403650000140365110000
140365122014036534480-39
140365356914036556790170
140365579914036576400-222
1403657760140380407000
14038041921403804365077
140380448914038076290-80
140380775114038095550-20
14038098161403812204-40-40
1403812324140381690736-40
14038171271403820880360
1403821000140391219300
1403912517140391451820-20
14039146841403917205-1919
1403917405140431782300
14043179791404319278-20-22
1404319453140432082920-20
1404320940140434141400
140434152614043429910-20
140434311714043445330-40
1404344655140434618740-40
1404346300140441322100
140441314714044160770-40
1404416200140441720000
For each of these intervals, we performed custom Fscan analyses using DARM and the 5-26 ADC channel as input data with 128 s Tsft. Each Fscan job covered one of the constant-bias segments, allowing us to investigate whether higher ITM biases corresponded to larger spectral peaks in the resulting spectra. The attached plots show the relative amplitude of the first harmonic for the two strongest combs identified near 30 Hz and 100 Hz. In these color scatter plots the X and Y axes represent the ITMX and ITMY bias voltages, respectively. The color scale encodes the relative amplitude ratio (or signal-to-noise ratio) of the selected comb harmonic. These plots correspond to DARM (GDS-CALIB-STRAIN-CLEAN). From the visual inspection, there appears to be a consistent trend where higher absolute ITMY bias values correspond to larger peak amplitudes, the same could be true for ITMX values, but the data does not appear to be conclusive. It would be interesting to get data points with much higher absolute values of ITMX bias. Here is one example for the first harmonic of the highest near-30 Hz combs: Near-30 Hz plot DARM Although these results currently refer only to the first harmonic of each comb, this correlation already suggests a relationship between ITMY bias magnitude and the peak amplitude. We also generated the same set of plots for the H1:PEM-CS_ADC_5_26_2K_OUT_DQ ADC channel, to test whether the observed trend in DARM is also visible in the ground current monitor. From these additional plots, the correlation appears less clear. For the near-30 Hz comb. It appears that changing ITM bias values does not change the comb amplitude in the ground monitor. Showing an example for the same comb as before: Near-30 Hz plot ADC_5_26 The current analysis only considers a single harmonic per comb. The next steps are to extend the study to higher harmonics of these combs and check whether the same behavior is observed in other comb families beyond the 30 Hz and 100 Hz series.
Images attached to this report
Non-image files attached to this report
Displaying reports 161-180 of 85556.Go to page Start 5 6 7 8 9 10 11 12 13 End