Displaying reports 5221-5240 of 83916.Go to page Start 258 259 260 261 262 263 264 265 266 End
Reports until 08:28, Monday 04 November 2024
H1 PSL
ryan.short@LIGO.ORG - posted 08:28, Monday 04 November 2024 (81045)
PSL 10-Day Trends

FAMIS 31058

Trends are all over the place in the last 10 days due to several incursions, but I motsly tried to focus on how things have looked since we brought the PSL back up fully last Tuesday (alog80929). Generally things have been fairly stable, and at least for now, I dn't see the PMC reflected power slowly increasing anymore.

Images attached to this report
LHO General
ryan.short@LIGO.ORG - posted 07:39, Monday 04 November 2024 (81044)
Ops Day Shift Start

TITLE: 11/04 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 28mph Gusts, 19mph 3min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.56 μm/s
QUICK SUMMARY: H1 has been sitting in PREP_FOR_LOCKING since 08:05 UTC. Since the secondary microseism has been slowly decreasing, I'll try locking H1 and we'll see how it goes.

H1 General
ryan.crouch@LIGO.ORG - posted 22:01, Sunday 03 November 2024 - last comment - 06:48, Monday 04 November 2024(81036)
OPS Sunday eve shift summary

TITLE: 11/04 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Microseism, LOCK_ACQUISITION
INCOMING OPERATOR: Corey
SHIFT SUMMARY:

We spent most of the day with the secondary microseism mostly above the 90th percentile, it started to decrease ~8 hours ago but still remains about half above the 90th percentile. The elevated microseism today is from both the storms by Greenland and the Aleutians as seen by the high phase difference for both the arms with the corner station (bottom plot).

We keep losing it at the beginning of LOWNOISE_ESD_ETMX, I see some ASC ringups on the top of NUC29 (CHARD_P I think?), no FSS glitches before the locklosses, no tags on the lockloss tool besides WINDY. It's always a few seconds into the run method, I was able to avoid this by slowly stepping through some of the higher states (PREP_ASC, ENGAGE_ASC, MAX_POWER, LOWNOISE_ASC). I'm not sure which of these is the most relevent to not see the ringup, probably not the ASC states as when I paused there but forgot MAX_POWER I still saw the ringup.

LOG: No log.

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 06:48, Monday 04 November 2024 (81043)

For OWL shift, received 12:03amPT notification, but I had a phone issue.

H1 General
oli.patane@LIGO.ORG - posted 16:39, Sunday 03 November 2024 (81041)
Ops Day Shift End

TITLE: 11/04 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Microseism
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Currently still trying to relock, and at POWER_25W. All day we've been working on getting back up, but the secondary microseism is so high. It is slowly coming down though. At one point, we were in OMC_WHITENING for over an hour trying to damp violins so we could go into NLN,  but we lost lock before we could get there.
LOG:

15:30 In DOWN due to very high secondary useism
15:38 Started relocking with an initial alignment
    - When we got to PRC, I had to do the Pausing-PSL_FSS-Until-IMC-Is-Locked thing again (see 81022)
    - 16:04 Initial alignment done, relocking
    - Lockloss from ACQUIRE_DRMI_1F, OFFLOAD_DRMI_ASC, ENGAGE_ASC_FOR_FULL_IFO, TRANSITION_FROM_ETMX
    - 18:07 Sitting in DOWN for a bit
    - 18:45 Started relocking
    - More locklosses
    - 21:48 Lost lock after sitting in OMC_WHITENING damping violins for over an hour
    - More trying to lock and losing lock                                                                                                                                               

Start Time System Name Location Lazer_Haz Task Time End
17:37 PEM Robert CER n Improving ground measurement 17:44
H1 General (Lockloss)
oli.patane@LIGO.ORG - posted 16:34, Sunday 03 November 2024 - last comment - 10:25, Monday 04 November 2024(81037)
Looking at locklosses from over the weekend

 Most of the locklosses over this weekend have the IMC tag and those do show the IMC losing lock at the same time as AS_A, but since I don't have any further insight into those, I wanted to point out a few locklosses where the causes are different from what we've been seeing lately.

2024-11-02 04:17UTC

2024-11-02 17:13 UTC

2024-11-02 18:38:30.844238 UTC

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 10:25, Monday 04 November 2024 (81046)

I checked during some normal NLN times and the H1:PSL-ISS_AOM_DRIVER_MON_OUT_DQ channel does not normally drop below 0.31 while we are in NLN (plot). In Oli's times before in lockloss, it drops to 0.28 when we loose lock. Maybe we can edit the PSL glitch scripts 80902 to check this channel.

Images attached to this comment
H1 General
ryan.crouch@LIGO.ORG - posted 16:30, Sunday 03 November 2024 (81039)
OPS Sunday EVE shift start

TITLE: 11/03 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Microseism
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 22mph Gusts, 18mph 3min avg
    Primary useism: 0.13 μm/s
    Secondary useism: 0.60 μm/s
QUICK SUMMARY:

H1 TCS
oli.patane@LIGO.ORG - posted 16:13, Sunday 03 November 2024 (81040)
TCS Chiller Water Level Top-Off FAMIS

Closes FAMIS#27801

Last checked a week ago by Camilla, but since the water swap was done recently, I am doing the next check only a week later.

CO2X

CO2Y

There was no water in the leak cup.

LHO VE
david.barker@LIGO.ORG - posted 10:54, Sunday 03 November 2024 (81035)
Sun CP1 Fill

Sun Nov 03 10:13:13 2024 INFO: Fill completed in 13min 10secs

 

Images attached to this report
H1 General
oli.patane@LIGO.ORG - posted 07:39, Sunday 03 November 2024 - last comment - 10:09, Sunday 03 November 2024(81033)
Ops Day Shift Start

TITLE: 11/03 Day Shift: 1530-0030 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: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.09 μm/s
    Secondary useism: 0.72 μm/s
QUICK SUMMARY:

Looks like we have been sitting in PREP_FOR_LOCKING since a relocking lockloss at 10:52UTC(81032). I just started an initial alignment. The secondary microseism is really high so not sure how far we'll get

Comments related to this report
oli.patane@LIGO.ORG - 10:09, Sunday 03 November 2024 (81034)

18:07 UTC - going to sit in DOWN for a bit since we haven't been able to get locked because of the high secondary useism (we were able to get up to TRANSITION_FROM_ETMX once, but the majority of locklosses have been from low locking states)

H1 General (Lockloss, SEI)
ryan.short@LIGO.ORG - posted 02:30, Sunday 03 November 2024 - last comment - 03:11, Sunday 03 November 2024(81031)
Ops Owl Shift Update

H1 has been having a hard time locking tonight due to very high microseismic motion. Unlocked at 05:43 UTC (lockloss tool) and has been down since; highest state I've seen H1 reach is TRANSITION_FROM_ETMX, alignment doesn't seem to be the problem.

Images attached to this report
Comments related to this report
ryan.short@LIGO.ORG - 03:11, Sunday 03 November 2024 (81032)

Since H1 hasn't had any success locking and the microseism doesn't look like it's going to come down anytime soon, I'm leaving H1 in DOWN until the morning when hopefully conditions will be better.

H1 General (SQZ)
ryan.crouch@LIGO.ORG - posted 22:03, Saturday 02 November 2024 (81023)
OPS Saturday eve shift summary

TITLE: 11/03 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:Short locks, the IMC kept losing lock during SDF_REVERT/READY/LOCKING_GREEN as it did yesterday. Primary useism has been increasing over the last few hours (there's been more small US EQs today than normal... Missouri, Idaho, Nevada all in the 3s).
LOG: No log

Images attached to this report
H1 SQZ
ryan.crouch@LIGO.ORG - posted 21:12, Saturday 02 November 2024 - last comment - 21:59, Saturday 02 November 2024(81027)
SQZ not locking

The FC keeps losing IR lock, it says "LO SERVO RAILED" pretty much as soon as the LO_LR grd startings working after the FC locks IR.

Comments related to this report
ryan.crouch@LIGO.ORG - 21:55, Saturday 02 November 2024 (81029)

RyanC, Vicky

I tried bringing SQZ_MANAGER to FDS_READY then I tried to set FC{1,2} back to where they were the last good SQZ lock ~5 hours ago according to top mass OSEMs... same issue. Trending the ZMs showed some drifting over the past 5 hours, I was thinking about moving these back just as with FC2 then Vicky suggested to try Clearing ASC history. I tried this following Camillas alog80519, but the issue persisted as clearing ASC also cleared FC ASC which misaligned the FC. Vicky then logged on and starting trying to manually lock everything, successfully.

To summarize

  • SQZ AS42 ASC got misaligned between locks
  • clearing ASC also cleared FC ASC, so then FC was misaligned too
  • Vicky manually walked ZM6 P/Y, then when was some sign on OMC RF3 TRANS, locked the LO loop, then manually enabled SQZ AS42 ASC
  • then SQZ_MANAGER to FREQ_DEP_SQZ worked
  • then manually lowered FC ASC trigger threshold, so get FC_ASC to turn on
victoriaa.xu@LIGO.ORG - 21:59, Saturday 02 November 2024 (81030)

Ryan C, Vicky 

What I think was the issue and what I did:

  • SQZ AS42 ASC got misaligned (see how the range ran away at the start of lock)
    • This is likely because squeezer ASC ran away, which I think is related to SQZ angle ADF servo running away. When I found it, the SQZ angle (as controlled by H1:SQZ-CLF_RF6_PHASE_PHASEDEG) was railed at 268 deg, whereas normally the RF6 demod phase is around 195 degrees. Because the known SQZ angle to ASC coupling, the ADF Angle servo running away could likely cause ASC to run away, which causes LO loop not to lock, and then FC-IR can't lock.
  • Ryan cleared ASC as he described above
    • TO-DO for us next week: We should clean up what the SQZ ASC clearing does.
  • First, I manually walked ZM6 P/Y to get some signal on OMC RF3 TRANS (manually walked the RF3_MON up from -22 to -10 or so). Then I was able to lock the LO loop (LO loop was railing when SQZ ASC had it totally misaligned). Then I manually enabled SQZ AS42 ASC, and it worked to align ZM4/6 to maximize RF3_MON.
  • I then adjusted OPO temperature to optimize RF6_ABS, see screenshot. Here I just wanted to make sure the OPO temperature being wrong did not cause the SQZ angle to be wrong, which in turn could've caused ASC to run away.
  • After locking the LO loop, then SQZ_MANAGER to FREQ_DEP_SQZ worked, and SQZ_FC locked successfully.
  • But FC ASC did not turn on, because FC was misaligned (the issue described above). I manually lowered FC ASC trigger threshold (FC_ASC screen > TRIG: I lowered H1:SQZ-FC_ASC_TRIGGER_THRESH_ON from nominal 3 to 1.5), in order to force FC_ASC to turn on and align FC1 and FC2 for us.
  • Then I reverted the SDF's on FC_INJ_ANG_{GAIN,TRAMP}, which (I didn't realize) then applied the FC_ASC offsets stored in the filter bank histories to ZM3. This was good actually. Restoring this ZM3 alignment restored the FC_REFL power.
  • Then all SDF's were clear, and Ryan could go to observe.
Images attached to this comment
H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 20:47, Saturday 02 November 2024 (81026)
02:28 UTC lockloss

02:28 UTC lockloss, IMC tag

Images attached to this report
H1 General (Lockloss)
ryan.crouch@LIGO.ORG - posted 17:51, Saturday 02 November 2024 - last comment - 19:00, Saturday 02 November 2024(81024)
00:44 UTC lockloss

00:44 UTC lockloss, ASC_AS_A and IMC lost lock ~10 ms apart.

Images attached to this report
Comments related to this report
ryan.crouch@LIGO.ORG - 19:00, Saturday 02 November 2024 (81025)

02:00 UTC Observing

H1 ISC (ISC)
marc.pirello@LIGO.ORG - posted 15:12, Tuesday 17 September 2024 - last comment - 20:25, Sunday 03 November 2024(80147)
SUS-ETMX Ligo DAC 32 (LD32) testing at EX (continued)

Building on work last week, we installed a 2nd PI AI chassis (S1500301) in order to keep the PI signals separate from the ESD driver signals.  Original PI AI chassis S1500299.

We routed the LD32 Bank 0 thorugh the first PI AI chassis to the ESD drive L3, while keeping the old ESD driver signal driving the PI through the new PI AI chassis.

We routed the LD32 Bank 1 to the L2 & L1 suspension drive.

We did not route LD32 Bank 2 or Bank 3 to any suspensions.  The M0 and R0 signals are still being driven by the 18 bit DACs.

The testing did not go as smoothly as planned, a watchdog on DAC slot 5 (the L1&L2 drive 20 bit DAC) continousouly tripped the ESD reset line.  We solved this by attaching that open DAC port (slot 5) to the PI AI chassis to clear the WD error.

Looks like we made it to observing.

F. Clara, R. McCarthy, F. Mera, M. Pirello, D. Sigg

Comments related to this report
jenne.driggers@LIGO.ORG - 17:54, Tuesday 17 September 2024 (80157)DetChar-Request

Part of the implication of this alog is that the new LIGO DAC is currently installed and in use for the DARM actuator suspension (the L3 stage of ETMX).  Louis and the calibration team have taken the changes into account (see, eg, alog 80155). 

The vision as I understand it is to use this new DAC for at least a few weeks, with the goal of collecting some information on how it affects our data quality.  Are there new lines?  Fewer lines?  A change in glitch rate?  I don't know that anyone has reached out to DetChar to flag that this change was coming, but now that it's in place, it would be helpful (after we've had some data collected) for some DetChar studies to take place, to help improve the design of this new DAC (that I believe is a candidate for installation everywhere for O5).

tabata.ferreira@LIGO.ORG - 20:25, Sunday 03 November 2024 (81042)DetChar

Analysis of glitch rate:

We selected Omicron transients during observing time across all frequencies and divided the analysis into two cases: (1) rates calculated using glitches with SNR>6.5, and (2) rates calculated using glitches with SNR>5. The daily glitch rate for transients with SNR greater than 6.5 is shown in Figure 1, with no significant difference observed before and after September 17th. In contrast, Figure 2, which includes all Omicron transients with SNR>5, shows a higher daily glitch rate after September 17th.

The rate was calculated by dividing the number of glitches per day by the daily observing time in hours.

Images attached to this comment
Displaying reports 5221-5240 of 83916.Go to page Start 258 259 260 261 262 263 264 265 266 End