Displaying reports 49841-49860 of 83150.Go to page Start 2489 2490 2491 2492 2493 2494 2495 2496 2497 End
Reports until 08:14, Monday 20 February 2017
LHO General
thomas.shaffer@LIGO.ORG - posted 08:14, Monday 20 February 2017 (34262)
Ops Day Shift Transition

TITLE: 02/20 Owl Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Unlocked
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 8mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.4 μm/s
QUICK SUMMARY: There was some PSL trouble last shift, and then the ETMX RMS WDs tripped causing a lockloss at COIL_DRIVERS just before I started my shift.

LHO General
corey.gray@LIGO.ORG - posted 08:04, Monday 20 February 2017 (34251)
OWL Operator Summary

TITLE: 02/20 OWL Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: 
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

Decent shift up until the latter half of the shift with a couple of PSL trips (see earlier alog).

LOG:

H1 PSL (PSL)
corey.gray@LIGO.ORG - posted 06:53, Monday 20 February 2017 - last comment - 17:46, Wednesday 22 February 2017(34261)
14:43 Lockloss Due to Another PSL Head 1-4 Flow Error

After 12min of OBSERVING, had another PSL trip.  

Went to the PSL Chillers and there must have been an explosion of water in there.  The Crystal Chiller cap did NOT pop off.  The Crystal & Diode chillers both have Error Alarms (Crystal has Flow Sensor Alarm & Diode has F2-Error).

Will probably call Jason shortly. 

In CORRECTIVE MAINTENANCE state.

Comments related to this report
jason.oberling@LIGO.ORG - 09:39, Wednesday 22 February 2017 (34317)

As with the first trip documented here, this one also appears to be caused by an erratic flow reading in the Laser Head 2 flow sensor.  As before, the flow reading from the head 2 sensor becomes erratic before the trip and begins to drop, eventually hitting the trip point and tripping the interlock.  The first attachment shows the 3 flow rates from the Laser Head circuit (once again, the 4th flow sensor is forced to a specific value in Beckhoff so cannot contribute to the trip).  The 2nd attachment is a zoomed in view of the Laser Head 2 flow sensor signal. 

As for the F2 error on the diode chiller, this error did not cause the chiller to turn off.  I remotely turned it off and asked Corey to power cycle the chiller.  This cleared the error.

Images attached to this comment
jeffrey.bartlett@LIGO.ORG - 17:46, Wednesday 22 February 2017 (34333)
  The plug not popping off can be a problem. When the pump stops there is a back surge of water into the reservoir, which is what blows off the plug and sends a shower of water onto the floor. If the plug is too tight to allow the pressure from the back surge to relieve, there is a chance of cracking the reservoir. 

   I will call Technotrans to see if there is a better way to relieve this back pressure. Until I hear from them PLEASE DO NOT reef down tight on the plug. Leave it lose. Cleaning up a bit of water on the floor is a lot better than swapping out a damaged chiller.     
H1 PSL
corey.gray@LIGO.ORG - posted 06:33, Monday 20 February 2017 (34260)
14:31 Back To OBSERVING

accepted SDF Diff for ISS Ref Signal change (from -1.10 to -1.08), with Jason's approval.

H1 AOS (DetChar, SUS)
miriam.cabero@LIGO.ORG - posted 06:12, Monday 20 February 2017 (34258)
Possible new sub-set of blip glitches related to ETMY L2 coil driver?

Recently I looked at the highest SNR (>100) blip glitches from the low-latency monitors and noticed that most of them looked very similar in the autoscaled spectrogram (they have a lot of excess noise in the whitened spectrogram so they do not look like blip glitches there, but they are short like blip glitches).

When I generated the full omega scans, they all had in common some excess noise in the SUS-ETMY_L2_NOISEMON channels (the times I looked at -Feb 10 to Feb 14- are in https://ldas-jobs.ligo-wa.caltech.edu/~miriam.cabero/blips/O2_loud/ ). This is not true for all blip glitches, which makes me think that this might be a new sub-set whose origin could be related with the coil driver. And they are not only very loud blips, I also found other quieter ones that show something in the noisemon channels:

https://ldas-jobs.ligo-wa.caltech.edu/~tdent/wdq/H1_1165129095.9

I have looked at past aLogs and it seems like there was found a possible correlation between periods of extreme glitchiness and the ETMY L2 driver. The glitches I looked into are from last week, not from a particularly noisy period like the few days in mid December or beginning of January.

Andy was saying ( aLog 32730 ) that noisemons will show glitches whenever DARM does, and indeed there are some blips where the noisemon sees the same as DARM (e.g. https://ldas-jobs.ligo.caltech.edu/~thomas.massinger/wdq/ER10_loudest/1163443424.81/ ), but it looks somehow different for the times I mention above (and not all the blips show something in the noisemons).

So I am writing here to ask if this information is relevant for blip-glitch studies, or if the information found in the periods of extreme glitchiness is helpful for this. There seemed to be the conclusion that humidity might be the problem, as had been observed in O1 ( aLog 32885 ). That could indeed be the case for a particular time of high glitchiness, but what about the rest of the time? If the humidity is normal and we still have these kind of glitches, what could we do?

 

 

H1 DetChar (DetChar)
miriam.cabero@LIGO.ORG - posted 05:33, Monday 20 February 2017 (34257)
Blip glitch low-latency monitor

Using PyCBC Live we have created a low-latency blip glitch hunter to possibly help DetChar investigations on site.

Lists of times and SNR are generated daily in

https://ldas-jobs.ligo.caltech.edu/~miriam.cabero/blips_live/lists/

and pages in the style of the summary pages are updated every five minutes:

https://ldas-jobs.ligo.caltech.edu/~miriam.cabero/blips_live/H1/day/20170220/detchar/pycbc_live/

(note that these pages are not available from the main summary pages yet, but they might be added in the near future).

 

P.S: I am not cleaning up these lists like I did in O1, so there can be some times that do not show a blip. However, I expect these times to be a small percentage.

H1 PSL (PSL)
corey.gray@LIGO.ORG - posted 05:06, Monday 20 February 2017 - last comment - 09:19, Wednesday 22 February 2017(34256)
H1 Lockloss: PSL Is Down (looking into why)

13:01utc:  H1 & the H1 PSL Front End went down.

Will make a call to Jason.

Comments related to this report
corey.gray@LIGO.ORG - 06:23, Monday 20 February 2017 (34259)

On the PSL SYSSTAT medm, we had the Oscillator/Head 1-4 flow error in a Fault/red state.  Jason said this meant that we had a "glitch in laser head flow sensors".  Jason brought back the PSL remotely.  I topped off the PSL Chiller (the cap did NOT pop off) with 375mL of water.  

  • ISS was oscillating afterward, so we adjusted the REFSIGNAL (from -1.1 to -1.5).  
  • But later noticed DIAG_MAIN message saying the NOISE_EATER was faulted.  So I went out to toggle this on/off.  
  • ISS was oscillating again and this time took REFSIGNAL to a more reasonable -1.08.

13:58 Back to LOCK ACQUISITION

FRS #7460 Filed For ~1hr of CORRECTIVE_MAINTENANCE DOWN time.

jason.oberling@LIGO.ORG - 09:19, Wednesday 22 February 2017 (34316)

Cause appears to be a trip of the Laser Head 1-4 Flow interlock, specifically Head 2.  The first attachment shows the 3 laser head flow rates (the 4th is currently being forced to a value in the Beckhoff software, so cannot contribute to the trip).  It is clear that head 2 became erratic and began to drop in flow, eventually passing below the trip point and tripping the laser.  The 2nd attachment shows a zoomed in view of only the Head 2 flow.  Possible debris passing through the flow sensor?

Images attached to this comment
H1 SEI (SEI)
corey.gray@LIGO.ORG - posted 04:13, Monday 20 February 2017 (34255)
HEPI Monthly Trends (FAMIS#4529)

Pressure 1 values for the EY & EX look more glitchy than the flat-lined PS1-PS4 channels.

CONTROL_VOUT values don't show anything odd over the last 45 days.

Trends are attached.  This closes out FAMIS 4529.

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 04:07, Monday 20 February 2017 (34254)
Mid Shift Status

Out of Observing for 32min for a lockloss around 9:37utc (1:37amPST).  

For this current lock, the range has drifted down a few Mpc over the first 2hrs.  A2L looks fine.  I did not had to do anything for PI modes for this lock so far.

Other than the lockloss bit of excitement, it's been a quiet night on the H1 front.

H1 ISC
corey.gray@LIGO.ORG - posted 01:55, Monday 20 February 2017 - last comment - 02:25, Monday 20 February 2017(34252)
H1 Lockloss, No Observable Culprit So Far

H1 drops lock 24hrs after lockloss during Travis OWL shift last night.  Nothing obvious on our wall monitors (Striptools normal, SEIS BLRMS quiet).

HAM6 ISI tripped, and I forgot to untrip the WD, so I paused the ISC_LOCK at DRMI ON POP to get HAM6 ISI back to ISOLATED.

Comments related to this report
corey.gray@LIGO.ORG - 02:25, Monday 20 February 2017 (34253)

Yesterday we had a lockloss at just before 1am PST local time & tonight we had a locklos just after 1:37amPST local time.  Hmmmm...

LHO VE (VE)
corey.gray@LIGO.ORG - posted 01:36, Monday 20 February 2017 - last comment - 08:15, Monday 20 February 2017(34250)
EX Vacuum Gauge Still Off (i.e. PT524)

Starting my shift, one check we do is the Alarm Handlers.  The Vacuum one has an alarm for the EX PT524 vacuum gauge.  Chandra noted this went down on Tues (Fire Dept Glitch?) & looks like it's remained down ever since.  Since other gauges look good with pressures of 1e-9Torr at EX, I'll assume we do not need to pay any mind to this alarm for the moment.

Comments related to this report
chandra.romel@LIGO.ORG - 08:15, Monday 20 February 2017 (34263)

These cold cathode gauges sometimes take a while to turn back on at low pressures. 

LHO General (DetChar)
corey.gray@LIGO.ORG - posted 00:15, Monday 20 February 2017 (34249)
Transition To OWL

TITLE: 02/20 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.29 μm/s

Nice and warm out and no fog to worry about.  useism looks like it's been increasing a little over the last 6hrs.
QUICK SUMMARY:

As Jeff was handing off, saw no issues, except a 5.4 Peruvian EQ popped up (followed by a 4.9 New Zealand EQ) on USGS webpage---Terramon webpage apears to be down.  Will monitor these.

Jeff mentioned an A2L would be useful to run if the opportunity arises.

Fundamental violin modes are down near 3e-19.

Have noticed that the H1 & L1 Summary Pages have been down for the last ~12hrs.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 00:03, Monday 20 February 2017 (34248)
Ops Evening Shift Summary
Ops Shift Log: 02/19/2017, Evening Shift 00:00 – 08:00 (16:00 - 00:00) Time - UTC (PT)
State of H1: Locked at NLN, with 64.9 Mpc of range.  
Intent Bit: Observing
Support: N/A
Incoming Operator: Corey

Shift Summary: A2L DTT script shows pitch elevated between 20 and 25 Hz. Will run the A2L script if LLO drops out of lock.

Mostly a smooth shift. Have been Observing for the past 22.5 hours. With the exception of A2L pitch, the interferometer has been humming along all shift. There was a GRB alert, which LLO received but LHO did not. As both sites were in observing, observed the one hour stand down. Environmental and seismic conditions remain favorable.    

Activity Log: Time - UTC (PT)
00:00 (16:00) Take over from Jim
00:20 (16:20) Run A2L – Pitch is high
06:35 (22:35) GRB Alert – Reported by LLO - LHO did not receive notice
06:35 (22:35) One hour stand down for GRB alert
07:35 (23:35) End GRB alert stand down
08:00 (00:00) Turn over to Corey

 

H1 General
jeffrey.bartlett@LIGO.ORG - posted 20:06, Sunday 19 February 2017 (34247)
Ops Evening Mid-Shift Summary
   IFO in Observing for 18.5 hours. The A2L Pitch is well above the reference and Yaw is starting to climb as well. Will run the A2L script at the first appropriate opportunity. No other problem or concerns apparent at this time.  
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:29, Sunday 19 February 2017 (34246)
Ops Evening Shift Transition
Ops Shift Transition: 02/19/2017, Evening Shift 00:00 – 08:00 (16:00 - 00:00) - UTC (PT)
State of H1: IFO locked at NLN, at 29.0W and 67.5 Mpc  
Intent Bit: Observing
Weather: Wind is Calm to a Light Breeze (0 - 7 mph), lower 50s and clear 
Primary 0.03 – 0.1Hz: Currently at 0.09um/s
Secondary 0.1 – 0.3Hz: Currently at 0.8um/s 
Quick Summary: Locked and observing. All appears normal.   
Outgoing Operator: Jim
H1 General
jim.warner@LIGO.ORG - posted 16:01, Sunday 19 February 2017 (34245)
Shift Summary

TITLE: 02/19 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:
LOG:

Quiet shift. Robert connected remotely, that's been pretty much the only excitement.

 

H1 General
travis.sadecki@LIGO.ORG - posted 08:00, Sunday 19 February 2017 (34244)
Ops Owl Shift Summary

TITLE: 02/19 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 69Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY:  Observing for 6.5 hours.  No issues since relocking early in the shift.
LOG:  See previous aLogs.  I left a message with Bubba regarding the fire panel alarm.

 

H1 General
travis.sadecki@LIGO.ORG - posted 03:50, Sunday 19 February 2017 - last comment - 07:39, Sunday 19 February 2017(34240)
Fire system panel alarming

At 11:34 UTC, I heard a sustained alarm tone near the door of the control room.  I tracked it down to the fire system panel in the Computer User's Room.  Other than the tone, I noticed that the "System Trouble" light was blinking.  I'll call Bubba when it get closer to normal waking hours.

Comments related to this report
travis.sadecki@LIGO.ORG - 05:57, Sunday 19 February 2017 (34242)

Seems to have fixed itself as it is no longer alarming. 

travis.sadecki@LIGO.ORG - 07:39, Sunday 19 February 2017 (34243)

The alarm stopped for an hour or so, but has since started again.  I'll call Bubba now.

Displaying reports 49841-49860 of 83150.Go to page Start 2489 2490 2491 2492 2493 2494 2495 2496 2497 End