Displaying reports 36561-36580 of 89200.Go to page Start 1825 1826 1827 1828 1829 1830 1831 1832 1833 End
Reports until 08:02, Thursday 02 January 2020
H1 General
edmond.merilh@LIGO.ORG - posted 08:02, Thursday 02 January 2020 (54235)
Shift Summary - Owl

TITLE: 01/02 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 109Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY:
LOG:

H1 locked and Observing without incident the entire shift


LOG:

H1 General
edmond.merilh@LIGO.ORG - posted 05:38, Thursday 02 January 2020 (54236)
PSL Status Report - Weekly FAMIS# 11045

 Laser Status:
    Front End Power is 32.45W (should be around 30 W)
    70W Output Power is 69.29W
    Front End Watch is GREEN
    70W Watch is GREEN

    PMC:
    It has been locked 0 days, 18 hr 45 minutes (should be days/weeks)
    Reflected power = 11.64Watts
    Transmitted power = 51.84Watts
    PowerSum = 63.48Watts.

    FSS:
    It has been locked for 0 days 12 hr and 38 min (should be days/weeks)
    TPD[V] = 5.563V (min 0.9V)

    ISS:
    The diffracted power is around 2.5%
    Last saturation event was 0 days 12 hours and 38 minutes ago (should be days/weeks)


    Possible Issues:

H1 General
edmond.merilh@LIGO.ORG - posted 00:25, Thursday 02 January 2020 (54232)
Shift Transition - Owl

TITLE: 01/02 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 109Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 23mph Gusts, 20mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.60 μm/s
QUICK SUMMARY:

H1 locked and Observing @ 108Mpc 

LHO General
corey.gray@LIGO.ORG - posted 23:59, Wednesday 01 January 2020 - last comment - 03:09, Thursday 02 January 2020(54222)
EVE Shift Summary

TITLE: 01/02 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ed
SHIFT SUMMARY:

LOG:

Comments related to this report
chandra.romel@LIGO.ORG - 03:09, Thursday 02 January 2020 (54233)

FAC staff are aware of that water leak in outdoor pipe.

H1 TCS (TCS)
corey.gray@LIGO.ORG - posted 20:50, Wednesday 01 January 2020 (54230)
TCS Chillers FAMIS Task (#11481)

Addressed TCS Chillers (4:50pm local & with Ethan as my Buddy):

H1 PSL (PSL)
corey.gray@LIGO.ORG - posted 20:48, Wednesday 01 January 2020 (54229)
PSL Chiller Water Level Top-Off (FAMIS #10542)
Topped off Crystal Chiller with 50 mL.  Diode Chiller OK.  
Filters look fine (slight yellow tint of Crystal filter [known item]).
LHO General
corey.gray@LIGO.ORG - posted 20:46, Wednesday 01 January 2020 - last comment - 03:11, Thursday 02 January 2020(54227)
Site Walk-Through: Tumbleweeds & Water

As I arrived for my shift, I wanted to perform a Site-Walkthrough while there was still light.  I'm attaching photos of tumbleweeds down the arms, 

Tumbleweed Situation:

After #Tumblegeddon, wanted to assess our tumbleweed situation on the site.  There were moderate piles around the OSB, but nothing blocking doors.  Staging Bldg had a pile at the bottom door which needed to be moved to enter.

Water Leaking Near Fire Water Tank

While checking out the Woodshop building, noticed some puddles in the Fire Pump room, but I couldn't tell where it was coming from.  This led me to go outside to see if I could find any water leaks.  I ended up finding a water leak in the piping between the Large Fire Tank & the Wood shop building.  There was a big puddle out there and some extension cords nearby, but maybe this is normal.  I texted pics to Richard M & we chatted.  He mentioned there is a possibility that the tank might be overfilling.  I looked on the FMCS computer and it says the level of the tank is ~17' (and the Max level alarm is set for 21').  I mentioned this leak to Cheryl upon my return to the Control Room, and she mentioned she & Ed noticed this leak a few weeks ago.  See attached photos/video if you're curious.

Other Notes:

Images attached to this report
Non-image files attached to this report
Comments related to this report
chandra.romel@LIGO.ORG - 03:11, Thursday 02 January 2020 (54234)

FAC staff are aware of the water leak in outdoor pipe.

LHO General
corey.gray@LIGO.ORG - posted 20:30, Wednesday 01 January 2020 - last comment - 21:07, Wednesday 01 January 2020(54228)
Mid Shift Status

H1's been locked 2.5+hrs.  Range has been hovering around 108Mpc.

Chatted with LLO & Virgo operators to let them know our situation before we locked.  Asked William P about L1's lock.  They are set to break a new aLIGO locking record in the next 4hrs or so!  Woo Woo!

Comments related to this report
corey.gray@LIGO.ORG - 21:07, Wednesday 01 January 2020 (54231)

Winds have picked up over the last 30min.  Averaging just under/at 20mph.  :-/

H1 General
corey.gray@LIGO.ORG - posted 18:49, Wednesday 01 January 2020 (54224)
H1's Back!!

SummaryH1 was DOWN (at CORRECTIVE MAINT) for 38hrs & 2mins due to computer crash + heavy winds.

Dolphin Crash:  On Tues Morning (12/31/19) at about 4am local time (12utc) H1 went down due to a corner station Dolphin crash (alog & FRS); most of the recovery from this was complete during Ed's graveyard & Cheryl's Day shift (but there were some lingering items which have come up over the last few days as well).

Wind:  On top of computer crash, there was:  WIND!!  (w/ a dash of microseism).  Sustained winds over 20mph started basically 2hrs after the computer crash (6am or 14utc on 12/31) and we remained windy until about only a few hours ago (3pm/23utc today).  #Tumblegeddon was fierce.

THANKS!!:  Ed, Dave, Cheryl, Keita, Jim, Jenne, & Sheila for getting H1 back!!

Back To NOMINAL_LOW_NOISE (at 2:05utc/6:02pm Local)

For most of the day Cheryl was working on H1 with Sheila/Keita over the phone today.  When I got handoff from Cheryl, H1 and I hung around at ENGAGE DC VIOLINS.  Hung out here, because the most recent plan of attack was to do the MOVE SPOTS step later in the ISC_LOCK order (basically, would first power up H1 to 10W, then MOVE SPOTS, and then continue to 20W).  Sheila (remotely) walked H1 through these steps.  Once we were at 20W, Sheila gave me the OK to continue on to NLN like normal and we made it there minutes later with no problem.

(Operator Note:  in the background, Sheila updated Guardian code (& I LOADed ISC_LOCK) so that operators should be able to proceed through ISC_LOCK like normal for the next lock.)

This lock started with the fundamental violin mode noticeably a little high (above 10^ -16 on the running DARM, but the VIOLIN DAMPING node has been bringing them down.

There were some IFO notifications (seen on the Intent Bit).  Two of them were related to an SPM diff for ISI ITMx St2 RX & RY filter banks having a T Ramp of 5 (vs 0)...I took them to 0 to clear this.  The other notifications are due to Violin Mode damping & IMC WFS not being centered (we've been living with these as of late.

SDF Diffs:

Upon getting back to NLN, had a few SDF diffs.  I took a screenshot of all of them (1st attachment).  I then ACCEPTED all the known ones (with Sheila observing remotely)....basically:  IMC PZT offset change due to computer crash & Time Ramps.

There were some ISI diffs for HAM2 & ITMx (see 2nd attachement).  I went ahead and ACCEPTED these as well, but Jim/Hugh should review this.

Images attached to this report
H1 General (GRD)
sheila.dwyer@LIGO.ORG - posted 18:46, Wednesday 01 January 2020 (54219)
summary of relocking and some temporary guardian changes

Ed, Cheryl, Corey, Sheila, Keita,

We are relocked.  The keys to relocking today seemed to be: waiting for the wind to calm down, powering up to 10W before moving the spots to their high power positions, and fixing the FSS common gain which was accidentally low.  

A general summary of the last ~38 hours:

My understanding of the ~38 hours of down time we've had:  After the dolphin crash, some time was spent recovereing the IMC, I don't really know what was done, but it does seem that we now need rather different offsets on the IMC PZT than we did before the crash, and this was found.  We had already been down for about 16 hours when Corey got in touch about lockosses at ENGAGE_ASC and MOVE spots last night.  We tried a few rounds of initial alignment, including reverting changes to the IMC sus sliders, which didn't seem to make much of a difference.  For initial alignment, we found that we had to reduce the trigger threshold for SRCL in SRY from 0.5 to 0.3, we didn't implement this in the gaurdian but it helped more than once so probably do want to make this change permanent.  Corey had about 1 attempt at locking after we had exhusted the initial alignment possibiltes, and lost it with a similar fast lockloss while ADS was moving.   Then the winds picked up, which made locking durring Ed's shift impossible and closed SR240 with tumbleweeds, gusty wind continued this morning on Cheryl's shift, so we could probably estimate that about 14 hours of this down time is environmental.  The FSS gain was accidentally low for about 6 hours, which prevented power up.  The remained of the down time which isn't due to the dolphin crash, the wind, or the FSS was due to the problem we had moving spots.  It took us an long time to find a workaround for this because of the other problems.  

More details about today's efforts:

Cheryl and I were able to get to DC readout by commenting out the lines in the gaurdian state MOVE_SPOTS which change the A2L gains and actually cause the spots to move.  We tried made a few attempts to move the spots in smaller steps, or to move some of the spots first then others, and to try moving the spots part of the way then adjusting the SRC1P offset to improve the POP18 build up, none of which worked.  Some of the locklosses that we had in these attempts could have been coincdent with wind gusts, but there was a pretty consistent pattern that we'd loose lock a few minutes after moving spots, without any apparent oscillations in ASC or LSC loops.  The sideband build ups have always dropped when we do the spot move, and the drop in power before locklosses in the last day has been similar to the drops we had in sucsesfull locks before the computer crash. 

We also made three attempts to power up without moving the spots, but lost lock very suddenly.  Keita and I looked at FSS, which is a good suspect for sudden locklosses during the power increase.  The alignment looks good, but the gain was reduced earlier today, durring a time when the FSS wouldn't lock.  This is something that is unmonitored in the SDF, which is why Cheryl and I didn't catch this earlier when we checked SDF, but it isn't set by the guardian.  (It used to be hard coded in the guardian but the PSL team sometimes changes the FSS gain when the reference cavity alignment drfits, so I edited the guardian a few years ago so that it just checks the gain setting, lowers the gain if the FSS is oscillating, and then puts it back that the setting it found).  Keita set this to be monitored in SDF.  

After fixing the FSS gain, we left the spot moves commented out of the guardian but left the SRC1P offset handled as it has been, used when ASC is engaged but turned off just before power up.  We were able to increase the power to 10W using INCREASE_POWER, and then manually moved the spots by setting the ADS gains to half their full power settings, waiting for things to settle, and then setting them to the nominal gains.  In October Craig added a guardian servo to the MOVE_SPOTs state that adjusts the TMS alignment to center on the TMS QPDs, we didn't use this doing things manually and the most off center QPD is around 0.6 now.  After doing this manually Corey was able to relock to nominal low noise.  

I put the A2L gain changes into increase power, and have left them commented out of MOVE_SPOTS for now, they should happen in one step at the same time as the DHARD loop shaping in increase power.  I am leaving it this way for tonight, but I think that tomorow it would make sense to change the guardian to split INCREASE power into 2 states and move MOVE_SPOTS to 10W.  

Things that still need follow up:

SRY triggering, moving the move spots gaurdian state to 10W.  

H1 General
cheryl.vorvick@LIGO.ORG - posted 18:17, Wednesday 01 January 2020 - last comment - 18:21, Wednesday 01 January 2020(54223)
OPS Day Summary

TITLE: 01/02 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Corey
SHIFT SUMMARY:  H1 is locking well, but not making it to NLN

LOG:

Comments related to this report
cheryl.vorvick@LIGO.ORG - 18:21, Wednesday 01 January 2020 (54225)

NLN!!!  Violin gains increased on the 4 modes in the attached plots, temporary, will revert next lock.

Images attached to this comment
LHO General
corey.gray@LIGO.ORG - posted 17:13, Wednesday 01 January 2020 (54221)
Transition to Eve Summary

TITLE: 01/02 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 18mph Gusts, 14mph 5min avg
    Primary useism: 0.12 μm/s
    Secondary useism: 0.57 μm/s 

Much less windy tonight!  Microseism is at the 90th percentile (i.e. ~0.5um/s).
QUICK SUMMARY:

H1 General
cheryl.vorvick@LIGO.ORG - posted 12:38, Wednesday 01 January 2020 - last comment - 18:49, Wednesday 01 January 2020(54217)
Mid-Day Update

Alignment of H1, given the current intput alignment, is good, relocking well, I have not adjusted any optic alignments.

I completed the restoration of the SEI HEPI and ISI TRAMP differences. BS ISI ST2 DAMP, with TRAMPS set at 1, are now returned to the running value of 3.

H1 has made it to ENGAGE_ASC_FOR_FULL_IFO and MOVE_SPOTS, but it has not made it any further.

Attached are plots of ASC and some other channels for the 21 seconds before H1 lost lock in Move Spots.

Images attached to this report
Comments related to this report
cheryl.vorvick@LIGO.ORG - 12:58, Wednesday 01 January 2020 (54218)

The input pointing has changed quite a bit, and in the attached plots, the plots across the top show that there has been some change in the beam coming from the PMC, however, the left most plots int eh second row show the PZTs, which are not back at their pro-dolphin crash values.   MC1-3 Mi pitch yas signals ae plotted, and across the bottom are the IMC WFS, where the Y axis span is the same, and the bottom most right plot shows a 0.6 change on WFS B Yaw, which is is about 3 times larger than any other WFS change.

Images attached to this comment
cheryl.vorvick@LIGO.ORG - 16:07, Wednesday 01 January 2020 (54220)
Images attached to this comment
sheila.dwyer@LIGO.ORG - 18:49, Wednesday 01 January 2020 (54226)

Thanks to Cheryl for posting this screenshot above so I could look at it.  Opening this screen crashes my remote desktop.  

Displaying reports 36561-36580 of 89200.Go to page Start 1825 1826 1827 1828 1829 1830 1831 1832 1833 End