Displaying reports 481-500 of 83107.Go to page Start 21 22 23 24 25 26 27 28 29 End
Reports until 22:06, Sunday 15 June 2025
H1 General
ryan.crouch@LIGO.ORG - posted 22:06, Sunday 15 June 2025 - last comment - 10:29, Monday 16 June 2025(85063)
OPS Sunday EVE shift summary

TITLE: 06/16 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: 1 lockloss with an automated relock without an IA, at the start of both locks today the SQZers' ASC took us in the wrong direction and degraded the range. I was not able to recover it the second time.
LOG: No log

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 10:29, Monday 16 June 2025 (85072)

There was two issues with the SCAN_ALIGNMENT_FDS alignment scans:

  1. In the the first scan, the LO was unlocked so during the whole time we just had mean SQZ so nothing was changing and all SQZ plots were flat. I'm unsure why this happened, but I have added the @LO_checker_FDS (and other checkers from FDS) to SCAN_ALIGNMENT_FDS and SCAN_SQZANG so that in the future the GRD would catch this, and relock the LO.
  2. Also, SCAN_ALIGNMENT_FDS currently uses an outdated value for ASQZ of (-)100deg to start the ASQZ optimization scan. This meant that all the second scan didn't optimize the ZMs or angle at best ASQZ, then after the scan was finished (for both), the sign was flipped to (+) which is also outdated and took us to even worse SQZ.

SQZ_ALIGNMENT_FDS is outdated as we haven't used it since we got the SQZ_ASC working well.

To do: find the optimum value/sign of ASQZ and put into SQZ_ALIGNMENT_FDS. Then we can try to rerun this and compare with where SQZ ASC takes us.

While adding checkers to SCAN_ALIGNMENT_FDS and SCAN_SQZANG_FDS also made an @LO_checker_FIS and added it to FIS, see changes in svn rev31848.
Also over the weekend, after running RESET_SQZ_ASC, if the sqz angle is outside of 150 to 250, it gets reset to 190, however optimal SQZ angle this last week has been 140-165 deg. So I edited this to reset the SQZ angle to 150deg if it's outside of 120 to 220 instead. Seen this as the Operator team have been using the state RESET_SQZ_ASC as the ASC has been unstable at the start of the lock (another issue we are planning to solve). 
H1 CDS
david.barker@LIGO.ORG - posted 19:22, Sunday 15 June 2025 - last comment - 07:18, Monday 16 June 2025(85064)
CDS DNS and GC WIFI issues

Ryan C, Jonathan, Dave:

Starting around 18:28 Sun 15jan2025 the control room reported name resolution issues within CDS. Also the GC WIFI went offline.

The CDS alarm system froze up at 18:28, which agrees with the time the other services went offline.

Jonathan is reporting issues contacting GC DNS and managment machines, indicating this could be a GC issue. 

Comments related to this report
david.barker@LIGO.ORG - 19:32, Sunday 15 June 2025 (85065)

Jonathan is heading to the site to investigate. 

david.barker@LIGO.ORG - 19:44, Sunday 15 June 2025 (85066)

From the control room perspective:

teamspeak continues to run on the verbal machine.

phones continue to work

alog is accessible if the IP number is used, not the name.

scripts are failing if they need to resolve names, this is preventing squeezer work and H1's range is down to the 80s.

the alarm/alert system cannot resolve twilio's address, so no alarm texts/emails can be sent.

jonathan.hanks@LIGO.ORG - 20:28, Sunday 15 June 2025 (85067)

The issue has been resolved by power cycling the sw-osb163-0 switch.  This is what DNS and a few other key services hang off of.

I restarted the switch around 8:14pm local time.  Ryan C. confirms that he has access to the alog.  I can get to the management machines and the dns servers, both locally and via offsite routes.

david.barker@LIGO.ORG - 21:02, Sunday 15 June 2025 (85068)

Alarms restarted itself at 20:20 and I restarted alerts at 20:54. Test messages confirmed these services are working correctly.

david.barker@LIGO.ORG - 07:18, Monday 16 June 2025 (85069)

Opened FRS34439 to cover this, specifically how it impacted on control room operations.

H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 17:17, Sunday 15 June 2025 (85062)
Lockloss 00:16 UTC

00:16 UTC lockloss

LHO General
ryan.short@LIGO.ORG - posted 16:27, Sunday 15 June 2025 (85059)
Ops Day Shift Summary

TITLE: 06/15 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Mostly quiet day with one lockloss in the afternoon and an easy reacquisition. After relocking, we've been having to touch up SQZ a couple of times. H1 has now been locked for 1.5 hours.

H1 General
ryan.crouch@LIGO.ORG - posted 16:02, Sunday 15 June 2025 - last comment - 16:12, Sunday 15 June 2025(85060)
OPS Sunday EVE shift start

TITLE: 06/15 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 122Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 6mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:

Comments related to this report
ryan.crouch@LIGO.ORG - 16:12, Sunday 15 June 2025 (85061)

ASC ran away and gave a notification to reset it, 23:07 we dropped observing to do so. We had to move the angle back as well as it was reset.

23:10 UTC Observing

H1 General
ryan.short@LIGO.ORG - posted 14:16, Sunday 15 June 2025 - last comment - 15:38, Sunday 15 June 2025(85057)
Lockloss @ 20:52 UTC

Lockloss @ 20:52 UTC after just under 15 hrs locked - link to lockloss tool

No obvious cause.

Comments related to this report
ryan.short@LIGO.ORG - 15:38, Sunday 15 June 2025 (85058)

Ran an initial alignment doing PRC align by hand, then main locking was fully automatic.

Once at low noise and before observing, I noticed SQZ looked poor, and the SQZ BLRMs were worse than at the start of the last lock stretch. I cycled SQZ_MANAGER through 'SCAN_SQZANG_FDS' to try and find a better SQZ angle, but the Guardian wasn't able to find a place that made the BLRMs and BNS range both look good, so I manually searched around at different angles and eventually settled on 139 with a "cleaned" range of 153Mpc. Started observing at 22:34 UTC.

H1 General
ryan.short@LIGO.ORG - posted 12:01, Sunday 15 June 2025 (85056)
Ops Day Mid Shift Report

State of H1: Observing at 151Mpc

H1 has now been locked and observing for 13 hours. Earthquake rolled through a couple hours ago, but otherwise a quiet morning.

LHO VE
david.barker@LIGO.ORG - posted 10:34, Sunday 15 June 2025 (85055)
Sun CP1 Fill

Sun Jun 15 10:12:39 2025 INFO: Fill completed in 12min 35secs

 

Images attached to this report
H1 PSL
ryan.short@LIGO.ORG - posted 09:45, Sunday 15 June 2025 (85054)
PSL Status Report - Weekly

FAMIS 26426

Laser Status:
    NPRO output power is 1.852W
    AMP1 output power is 70.39W
    AMP2 output power is 140.6W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 27 days, 1 hr 38 minutes
    Reflected power = 23.08W
    Transmitted power = 105.6W
    PowerSum = 128.7W

FSS:
    It has been locked for 0 days 11 hr and 32 min
    TPD[V] = 0.8236V

ISS:
    The diffracted power is around 4.0%
    Last saturation event was 0 days 12 hours and 51 minutes ago


Possible Issues:
    PMC reflected power is high

LHO General
ryan.short@LIGO.ORG - posted 07:48, Sunday 15 June 2025 (85053)
Ops Day Shift Start

TITLE: 06/15 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 4mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY: H1 has been locked and observing for almost 9 hours and range looks good.

H1 General
ryan.crouch@LIGO.ORG - posted 22:00, Saturday 14 June 2025 (85051)
OPS Saturday EVE shift summary

TITLE: 06/15 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: We stayed locked or most of the shift, ~6.75 hours. I ran a coherence measurement, there's a lot of >10Hz CHARD_P, and <10Hz CHARD_Y. We're currently relocking at DRMI.
LOG: No log

Images attached to this report
H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 20:54, Saturday 14 June 2025 (85052)
03:52 UTC lockloss

03:52 UTC lockloss

LHO General
ryan.short@LIGO.ORG - posted 16:29, Saturday 14 June 2025 (85050)
Ops Day Shift Summary

TITLE: 06/14 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Only one lockloss today and two purposeful drops from observing for calibration sweeps and SQZ fixing. DARM high frequency still doesn't look amazing, so there might need to be some SQZ angle adjustment. H1 has now been locked for 2.5 hours.

H1 General
ryan.crouch@LIGO.ORG - posted 16:08, Saturday 14 June 2025 (85049)
OPS Saturday EVE shift start

TITLE: 06/14 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 20mph Gusts, 9mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

Displaying reports 481-500 of 83107.Go to page Start 21 22 23 24 25 26 27 28 29 End