Displaying reports 41281-41300 of 88818.Go to page Start 2061 2062 2063 2064 2065 2066 2067 2068 2069 End
Reports until 07:39, Sunday 05 May 2019
H1 DetChar (DetChar)
corey.gray@LIGO.ORG - posted 07:39, Sunday 05 May 2019 - last comment - 10:54, Monday 06 May 2019(48996)
Creepy Line Sweeping On DARM For 30+ Min!

SUMMARY:  Have been locked for almost 4hrs and in the last hour noticed our range slowly taking a dip in range over a 30min span (went from 112Mpc down to 102Mpc!).  Cause for the dip was a noticeable line on DARM which was sweeping between 65-120Hz (along with a few of its harmonics).  It's gone now.

TIME Of Event:  13:27 - 14:02utc Stopped abruptly at 14:02.

DARM BLRMS Striptool really show the effect.  H1 had a normal glitch and right after the glitch the the 60-100Hz band remained elevated.  100-450Hz band would go up a little due to the harmonic, but when the fundamental swept above 100Hz, then the 100-450Hz band became the noisiest.  (nuc6 Note:  100-450Hz has been off-scale on this StripTool, so I increased the vert axis and saved the file).

I took power spectra of a quiet time (blue) & during this noisy time (red) & you can clearly see the fundamental and it's harmonics.  But like I said, it was noticeably sweeping across DARM (I seriously looked at the CDS Overview for any excitations, but everything looks green in here!).  

Attached is a screenshot showing the power spectra, DARM BLRMS StripTool, & the BNS Range.

Images attached to this report
Comments related to this report
beverly.berger@LIGO.ORG - 07:58, Sunday 05 May 2019 (48997)DetChar

This is the squeezing wandering line again. See alog 48892. For today, h(t) and the relevant SQZ channel are shown below.

Images attached to this comment
andrew.lundgren@LIGO.ORG - 08:08, Sunday 05 May 2019 (48999)DetChar, ISC, SQZ
It looks like Jenne recommended that the noise eater be turned back on because the squeezer wouldn't lock (alog 48985). It's not clear whether it can be turned off when the wandering lines appear - maybe she can clarify.
corey.gray@LIGO.ORG - 08:31, Sunday 05 May 2019 (49000)

 Oh wow, thank you for the quick reply‘s this morning! And I agree maybe we can wait for Jenne to give us input about the Noise Eater. 

edmond.merilh@LIGO.ORG - 10:56, Sunday 05 May 2019 (49004)

I'm seeing this as well. Noise eater (squeezer) is currently ON.

Images attached to this comment
jenne.driggers@LIGO.ORG - 10:54, Monday 06 May 2019 (49034)SQZ

Patrick was having a problem with the TTFSS on the squeezer not locking on Saturday night, so I (in the absence of other ideas) suggested turning on the noise eater to see if that would help, thinking that maybe the noise that it is supposed to suppress was a bit high, and that was causing problems for the TTFSS.  Turning the noise eater on seems to have let the TTFSS lock, and Patrick was able to get back to Observe. 

In hindsight, probably it would have been better to have Patrick turn the noise eater back off once the squeezer was locked.  

Also, Daniel mentioned today that it's not clear that the noise eater should do anything to help the TTFSS, so maybe there was something unrelated going on?  In any case, we should run with the squeezer's noise eater off (which it currently is).

LHO General (ISC)
corey.gray@LIGO.ORG - posted 04:39, Sunday 05 May 2019 - last comment - 14:59, Monday 06 May 2019(48995)
Mid-Shift Status: H1 Back To OBSERVING

SUMMARY:  Wish I could say I actively curred H1's issue tonight, but all I can say is my breakfast got us back to OBSERVING after ~4hrs of being DOWN.  cool Below is a summary of with highlights in bold.

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 11:02, Monday 06 May 2019 (49035)

The SRCL FF is fine the way it is with the many filters engaged.  On Thursday (alog 48950) I had reverted to the setup where only FM3 was engaged, since it seemed a teensy bit better, which is why Corey saw this diff.  But, I had only changed the filters by hand - I forgot to change the guardian code to reflect this revert, so the next time we acquired lock, guardian turned on all of the newer filters.  This isn't a much worse feedforward than using only FM3, so it's fine that we ran this way during the weekend.

To find these filter banks, go to the LSC Overview screen, then on the left side, about 2/3 of the way down the screen there is a small button called IFO_FF, as well as a little matrix next to it.  Those are the feedforward settings.

jenne.driggers@LIGO.ORG - 14:59, Monday 06 May 2019 (49041)

Since we are unlocked for the earthquake, I reloaded the ISC_LOCK guardian to use only the Feb28 FM3 for SRCLFF, and accepted this in both the safe and observe snap files, so hopefully no diffs will come up next time we try to go to observing.

LHO General (ISC)
corey.gray@LIGO.ORG - posted 00:53, Sunday 05 May 2019 - last comment - 02:05, Sunday 05 May 2019(48991)
Local EQ Recovery: Two Consecutive locklosses during ENGAGE ASC step. :-/

First attempt at locking had a lockloss at ENGAGE_ASC_FOR_FULL_IFO (where, POP90 started to increase & then a lockloss).

Giving it another try and watching during the step noted above.  If it drops out, will try an alignment.

Comments related to this report
corey.gray@LIGO.ORG - 01:05, Sunday 05 May 2019 (48992)

Snapshot of strip tool. 

Images attached to this comment
corey.gray@LIGO.ORG - 01:49, Sunday 05 May 2019 (48993)ISC

First Locking Attempt Post-Initial_Alignment

  • POP90 was a little lower than previous two locks.
  • Paused at PREP_ASC_FOR_FULL_IFO
    • PRC GAIN was lower than previous locks, but was getting noisier during this pause
  • went to ENGAGE_ASC_FOR_FULL_IFO (where we dropped out of lock previous two times)
    • PRC Gain (& most other LSC signals on striptool) immediately dropped, and 
    • LOCKLOSS.
  • Attempting to another lock...will try to quickly go through PREP_ASC_FOR_FULL_IFO without a pause....but we'll see.
  • Marking OBSERVATORY MODE to CORRECTIVE_MAINTENANCE
  • Other note is interferometer continues to not FIND_IR on its own anymore.
corey.gray@LIGO.ORG - 02:05, Sunday 05 May 2019 (48994)
  • 9:03 Another lockloss at ENGAGE_ASC...
  • I'm going to go make breakfast & revisit in a bit......
LHO General
corey.gray@LIGO.ORG - posted 00:18, Sunday 05 May 2019 (48988)
Transition to OWL Log

TITLE: 05/05 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 15mph Gusts, 12mph 5min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.34 μm/s
QUICK SUMMARY:

Arrived to see Patrick dealing with a quick and nearby earthquake (& then H1 dropped out of lock a few minutes later).  I was scared about ALSy....but it looked normal.  :) Had to manually FIND IR (Patrick also had to do that earlier). 

NOTE:  OH, I wasn't sure if our new protocol is to ALWAYS run Jenne's AS_A command after every lockloss (and run other command after things heat up for 90min).  So I just ran it when we were at LOCKING_ALS.

LHO General
patrick.thomas@LIGO.ORG - posted 00:09, Sunday 05 May 2019 - last comment - 08:57, Sunday 05 May 2019(48989)
Ops Eve Shift Summary
TITLE: 05/04 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Keita came in and fixed the issue with the ALS Y arm. Finished initial alignment. Had to find IR by hand. Had to turn on squeezer noise eater. Made it to observing. Just lost lock from an earthquake in Canada.
LOG:

23:03 UTC Changed observatory mode to corrective maintenance
23:05 UTC Jeff J. back from biking down X arm
Keita fixed ALS Y arm.
02:42 UTC Keita left. Set observatory mode to initial alignment. Starting initial alignment.

Cleared excitations on ITMY:
patrick.thomas@zotws7:~$ diag -l -c
supported capabilities: testing  testpoints  awg  
diag> awg clear 30 *
reset succeeded
diag> awg clear 30 *
reset succeeded
diag> quit
EXIT KERNEL

The excitation bit went away but there are still two test points open. Not sure how to clear them.

03:21 UTC Green WFS offloaded
03:49 UTC Initial alignment done
03:55 UTC IR not found
While changing DIFF offset to find IR, got quick flash, and guardian immediately went on. Not sure if I really found it.
Lost lock engaging DRMI ASC. POPAIR_B_RF18_I fell off.
Lock loss engaging DRM_ASC again. POPAIR_B_RF18_I fell off again.
Going back to check IR
04:29 UTC Found IR by hand

Squeezer guardian is giving 'TTFSS EOM noisy' squeezer notifications. Jenne had me turn of squeezer noise eater. Accepted SDF differences for this.

05:20 UTC Observing
06:42 UTC Ran "z step H1:ASC-AS_A_RF36_SEG1_PHASE_R +1,40 H1:ASC-AS_A_RF36_SEG2_PHASE_R +1,40 H1:ASC-AS_A_RF36_SEG3_PHASE_R +1,40 H1:ASC-AS_A_RF36_SEG4_PHASE_R +1,40 -s 1" per Jenne's alog. Took us out of observing.
06:44 UTC Observing
06:53 UTC Earthquake arriving from Canada. Switched SEI_CONF to EARTH_QUAKE. Hope it isn't too late.
06:58 UTC Lockloss
Comments related to this report
david.barker@LIGO.ORG - 08:57, Sunday 05 May 2019 (49001)

To clear a model's testpoints (using this case as an example)

diag> tp clear 30 *

H1 General
patrick.thomas@LIGO.ORG - posted 00:04, Sunday 05 May 2019 - last comment - 10:17, Monday 17 June 2019(48987)
Lockloss, Earthquake
Noticed a notification of an earthquake from Canada after seeing the DARM spectrum get noisy. Quickly transitioned SEI_CONF to EARTH_QUAKE per the plot of responses to take. Managed to hold look through the transition, but lost it a couple of minutes later.
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 10:17, Monday 17 June 2019 (49992)DetChar, SEI
Tagging @DetChar and SEI for data in seismic's sensor correction configuration transition studies.
H1 General
patrick.thomas@LIGO.ORG - posted 23:47, Saturday 04 May 2019 (48986)
Changed the phase of AS_A_36
06:42 UTC Ran "z step H1:ASC-AS_A_RF36_SEG1_PHASE_R +1,40 H1:ASC-AS_A_RF36_SEG2_PHASE_R +1,40 H1:ASC-AS_A_RF36_SEG3_PHASE_R +1,40 H1:ASC-AS_A_RF36_SEG4_PHASE_R +1,40 -s 1" per alog 48948. Took us out of observing.

Accepted attached SDF differences.

06:44 UTC Observing
Images attached to this report
H1 General
patrick.thomas@LIGO.ORG - posted 22:30, Saturday 04 May 2019 (48985)
Observing
05:20:39 UTC

Accepted the attached SDF differences. The squeezer manager was giving 'TTFSS EOM noisy' notifications and was not proceeding past LOCK_TTFSS. Jenne had me turn on the squeezer noise eater. The SDF differences in the second screenshot are for that. The differences in the first screen shot are for the RF36 phasing. They will come back after running the script in Jenne's alog 48948 in a couple of hours.
Images attached to this report
LHO General
patrick.thomas@LIGO.ORG - posted 20:01, Saturday 04 May 2019 (48983)
Ops Eve Mid Shift Status
Keita has fixed the ALS Y arm. Proceeding with initial alignment.
H1 ISC
keita.kawabe@LIGO.ORG - posted 19:38, Saturday 04 May 2019 - last comment - 21:33, Saturday 04 May 2019(48982)
Y Alignment (Ed, Patrick, Keita)

1. While working from home talking to Ed over the phone:

Changed IY, EY and TMSY alignment back to in-lock position. Then manually align things -> Y green transmission 0.6, locks, but WFS doesn't like it. Disabling DOF3 didn't help, enabling just DOF1 or just DOF2 didn't help, it just ran away.

Asked Ed to do baffle alignment but I don't see that it actually completed.

2. I came in and sit with Patrick.

Did baffle alignment for TMSY and ITMY, then manually aligned ETMY -> Y green transmission 0.9-ish, locked. Started with WFS DOF1 and DOF2, very low gain, didn't run away. Enabled DOF3 but the servo wasn't doing anything for the camera position. Increased the gain to nominal (0.2) and it worked.

Now TRY is about 1.1, looks good, ready for initial alignment.

Comments related to this report
edmond.merilh@LIGO.ORG - 21:33, Saturday 04 May 2019 (48984)

Apologies for not posting about running the ditherAlign script. As far as I could tell, it ran and brought me right back to locked on TEM00 mode at just below .6 (normalized).

LHO General
patrick.thomas@LIGO.ORG - posted 16:07, Saturday 04 May 2019 (48981)
Ops Eve Shift Transition
TITLE: 05/04 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 14mph Gusts, 11mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.11 μm/s 
QUICK SUMMARY:

Ed reported that Keita is on the way in to help with troubleshooting.
H1 General
edmond.merilh@LIGO.ORG - posted 15:56, Saturday 04 May 2019 (48979)
Shift Summary - Day

TITLE: 05/04 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: Patrick
SHIFT SUMMARY:

H1 never recovered after the near 42 hour lock. There's something amiss with the Y arm alignment. Keita and I have been on the phone for ~4 hours trying to do things remotely before deciding to come out to the site.


LOG:

17:00 Started initial alignment. Y arm alignment was way out

16:17 GRB alert - LLO contacted H1 still in alignment

16:23 Y arm locked but at the expense of ITMY - trying to correct

16:43 Dither Align TMSY

16:58 Y arm locked once again. Better but may take some time to converge ITM YAW. - still no satisfaction

22:50 Been on the phone with Keita most of the day. Y arm locking has been weak to say the least. He is on his way in now.

LHO General
corey.gray@LIGO.ORG - posted 08:27, Saturday 04 May 2019 (48973)
OWL Operator Summary

TITLE: 05/04 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 112Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:

Wildlife observed:  coyote & porcupine around parking lot.  Also noticed an owl standing just outside the Control Room entrance (it flew away as Patrick opened door to OSB main entrance.
LOG:

H1 AOS
corey.gray@LIGO.ORG - posted 06:49, Saturday 04 May 2019 - last comment - 10:41, Saturday 04 May 2019(48975)
H1 Lockloss: ALSy Issues

Symptoms:

Comments related to this report
corey.gray@LIGO.ORG - 07:08, Saturday 04 May 2019 (48976)

I forgot about Jenne's note about changing AS_A_36 phase.  So I have done that, but it didn't address the ALSy issue.

Trending oplevs for ETMy & ITMy does show some big alignment changes.  I still wonder if this is related to a WFS issue.  Will steer optics back to see what this does.  

NOTE:  I have not seen this issue before with a Y-arm misalignment like this!

corey.gray@LIGO.ORG - 08:25, Saturday 04 May 2019 (48977)

Ed's here to save the day, but I'm trying to remember what I saw & did with ALSy.

Definitely saw ITMy & ETMy both shift their alignment!  (see attached to see ITMy/ETMy pit/yaw shifts & various things I did to bring  back).

Back Story:  

  • Lockloss after 42-hr lock.
  • For relocking, immediately saw Green Y was in la la land
    • No light on ALSy video!  AND ALS-C_TRY_A_LF_OUT was dead flat at zero!  So there was no flashing in the arm!
    • Issues on ALS Y Overview
      • Green WFS spots were visibly off 
      • CAM ITM PIT Error signal was way above -0.2 (it was -1.2!).  On Jenne's old trouble-shooting document, it send to hit to hit Clear History button on the ALS Y Overview screen (but this button no longer seems to work....the clear history command/script/file is no longer in there)
    • Trended ETMy & ITMy and they shifted alot after the lockloss!
      • Because of ALS Y Overview issues due to WFS noted above, I was worried the issue was there, but since I couldn't fix anything with that, I started with moving optics.
    • Moved ETMy & ITMy back to pointing during the lock.  This finally gave baby flashes for ALS TRY.  
      • Oh!  Around this point is where I remembered to run the command Jenne alogged about on Thurs!
    • Walked ETMy, ITMy, & TMSy (by alot!) over several iterations.  Eventually had flashes over 1.0. 
    • Locked up ALS-Y (and finally gave ALSx attention).
    • Tried locking, but "IR was not found"
      • Ed came in and he found IR, but PRMI flashes looked UGLY!  He is now running an INITIAL ALIGNMENT.
Images attached to this comment
corey.gray@LIGO.ORG - 10:41, Saturday 04 May 2019 (48980)

Wanted to also mention that I clicked on the "Clear History" for each of the individual Filter Banks on the  ALS Y Overview (which I assume the non-functioning yellow Clear History button would do on this medm window).  When I did this I did not notice any change to the CAM ITM PIT Error signal.  These filter banks had their inputs OFF and their outputs were zero.  Just wanted to note that I did click their Clear Histories though.

Displaying reports 41281-41300 of 88818.Go to page Start 2061 2062 2063 2064 2065 2066 2067 2068 2069 End