Displaying reports 50561-50580 of 83117.Go to page Start 2525 2526 2527 2528 2529 2530 2531 2532 2533 End
Reports until 11:41, Saturday 21 January 2017
H1 General
corey.gray@LIGO.ORG - posted 11:41, Saturday 21 January 2017 - last comment - 13:38, Saturday 21 January 2017(33480)
H1 Lockloss

No obvious seismic jolt for lockloss, BUT we had been riding some high useism.

Locking Notes:

1) IMC not locking!  (it did look misaligned on Trans when it tried grabbing lock)

2) H1 Locking Status:  Have had a couple of failed attempts after & before CARM Reduction steps.

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 11:56, Saturday 21 January 2017 (33481)

Have had a few more DRMI locklosses drop before the CARM steps & earlier.

Going to try an Initial_Alignment and see if this changes any results here.  If not, will return to investigation of steps before CARM REDUCTION.

corey.gray@LIGO.ORG - 12:23, Saturday 21 January 2017 (33482)

Mode Cleaner continues to be a pain. 

This is my third instance of needing to Clear Histories.  (mainly the Pitch outputs were high).

Going back to Initial Alignment.

edmond.merilh@LIGO.ORG - 13:01, Saturday 21 January 2017 (33483)

When you get it re-locked, try letting it be for about 15-20 minutes to give the loops time to optimize the alignment, maybe. That's what I do.

corey.gray@LIGO.ORG - 13:38, Saturday 21 January 2017 (33484)

18:23 - 21:23 Out for Locking & Alignment (during high useism)

Assuming the lockloss could be related to our high useism (no jolts seen on any of our BLRMS seis bands).

Tried to do what I could to get it back up w/o a full Initial Alignment (by tweaking MCs to get IMC back & then usual BS/PRM), but after several locklosses after DRMI, I opted to give an Alignment.

After the alignment, dropped a handful of times, but went step by step in Guardian and finally got through the CARM reduction steps (I never got to a point where I needed to run Guardian line by line...talking with Jim we just wanted to get it through the CARM steps in this high useism).  At any rate, finally made it past the CARM reduction steps and up to NOMINAL_LOW_NOISE!

Did notice a few SDF Diffs that I ACCEPTED:

  1. PSL ISS REFSIGNAL (had a tiny diff...not sure why since I didn't touch this channel)
  2. IMC WFS GAIN:  I did touch this gain when clearing WFS histories.  I apparently took it to a paltry 0.004 instead of returning it to the normal 0.04.  So, I slowly walked the gain back in 0.001 steps & then had a teeny tiny SDF diff--which I ACCEPTED.

Ed:  What step were you suggesting I should have paused?

The IMC was a bit frustrating through all of this.  Have not had to be so hands-on to it in my experience over last few months.

Currently running at 66Mpc. and can certainly useism oscilltion on LSC signals on Strip Tools,  the Tidal StripTool, and even PI Mode28. 

H1 PSL (PSL)
corey.gray@LIGO.ORG - posted 09:03, Saturday 21 January 2017 (33478)
Weekly PSL Chiller Resevoire Top-Off

Crystal Chiller topped off with 265mL this morning (Diode Chiller had GREEN light for its level).  This closes FAMIS 6506.

LHO General
corey.gray@LIGO.ORG - posted 08:31, Saturday 21 January 2017 (33477)
Transition To DAY

TITLE: 01/21 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.19 μm/s
    Secondary useism: 0.87 μm/s
QUICK SUMMARY:

Not much to hand-off from Patrick other than the Configuration Change note for H1OAF on the CDS Overview. 

useism has inched up in the last 8-10hrs (above the 90percentile and almost clearing it!) & you can see the signal on the Tidal Striptool (nuc1).

Beautiful clear morning with no issues driving in & a crisp 28degF out.

LHO General
patrick.thomas@LIGO.ORG - posted 08:12, Saturday 21 January 2017 (33476)
Ops Owl Shift Summary
TITLE: 01/21 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY: Remained in observing the entire shift. The filter changed by Sheila that Cheryl reported in her shift summary remains unloaded.
LOG:

09:14 UTC Damped PI mode 28 by changing sign of gain
14:45 UTC GRB alert
LHO General
patrick.thomas@LIGO.ORG - posted 04:01, Saturday 21 January 2017 (33475)
Ops Owl Mid Shift Report
Have remained in observing. No issues to report.
LHO General
patrick.thomas@LIGO.ORG - posted 00:32, Saturday 21 January 2017 (33474)
Ops Owl Shift Transition
TITLE: 01/21 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 3mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.67 μm/s 
QUICK SUMMARY:

No issues to report.
H1 General
cheryl.vorvick@LIGO.ORG - posted 00:09, Saturday 21 January 2017 (33472)
Ops Eve Summary

TITLE: 01/21 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 61Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY:

Images attached to this report
H1 DAQ (CDS, DAQ)
keith.thorne@LIGO.ORG - posted 19:31, Friday 20 January 2017 - last comment - 19:33, Friday 20 January 2017(33452)
Frame Data Rates at L1, H1 during early O2
I have determined new frame data rates for H1 and L1.  This was last updated during ER10 ( see LHO aLOG 31567  )

You can find the scripts (work at either site) at https://llocds.ligo-la.caltech.edu/data/keith.thorne/DataRates
You can find the L1 data at https://llocds.ligo-la.caltech.edu/data/keith.thorne/DataRates/2017-01-20/, the H1 data at https://lhocds.ligo-wa.caltech.edu/exports/keith.thorne/DataRates/2017-01-20/.

I have attached the summary data sheets in PDF and XLS formats as well as channel lists. These are all raw (uncompressed) rates.

The raw H1 fast data size has shrunk from 45.59 to 43.47 MB/s (decrease of 5%). [Removal of now-unneeded spurious 64KHz channels from PI models]
The raw L1 fast data size has increased slightly from 40.56 to 40.60 MB/s (increase of 0.1%)

The raw H1 fast data rates are now 7% larger than L1 fast data rates
Sub-systems leading to higher H1 rates are PSL (0.5 MB/s), SUS (0.5 MB/s), ISC (1.0 MB/s), PEM (1.0 MB/s)

From DAQ MEDM screens during lock
H1 frames are ~1630 MB / 64 sec -> 25 MB/s
L1 frames are ~1420 MB / 64 sec -> 22 MB/s
Non-image files attached to this report
Comments related to this report
keith.thorne@LIGO.ORG - 19:33, Friday 20 January 2017 (33471)CDS, DAQ
Updated H1 result as I had mis-read new rate table removing the 6 'spurious' 64KHz channels from the PI models. Only H1 spreadsheets changed.  Many thanks to Stuart Aston for noting this.
H1 AOS
cheryl.vorvick@LIGO.ORG - posted 19:20, Friday 20 January 2017 (33470)
GRB - 3:11UTC - standing down until 4:11UTC

LHO VE
kyle.ryan@LIGO.ORG - posted 17:46, Friday 20 January 2017 - last comment - 18:27, Saturday 21 January 2017(33456)
Revisiting CP4's obstructed sensing line
Background - 
Both CP3 and CP4 are experiencing obstructed "high side" sensing lines which prevent their level transducers from measuring the level of LN2 in the 80K pumps.  We consider that this is due to accumulated ice at the bottom of the pumps inner LN2 vessel where the "high side" sensing line transitions from the relatively large ID aluminum tube to the relatively small ID stainless tube near a 90 degree elbow.  While Chandra R. has developed a procedure for a permanent post-O2 fix, we, nevertheless, would like to pursue more accommodating fix attempts in the meantime.  One of these is to see if by applying a vacuum (for a prolonged period) to the sensing line enough ice could be liberated through reverse sublimation that the obstruction could then be freed by alternating applications of modestly pressurized UHP N2 followed by vacuum pumping.  

Today - 
WP #6442 
Kyle R., Chandra R., Dave B., Gerardo M., Marc P.
I reconnected the "clogged" sensing line (with added parallel valved line used for vacuum pumping and a parallel valved line used for back filling) to the CDS level transducer (Rosemont model 1151DP4E52B404).  I then applied various "on-scale" pressure differentials via the back fill line (as indicated by the parallel connected magnahelic DP gauge) while Chandra R., Dave B. and Gerardo M. monitored the CDS MEDM screen. This confirmed that the transducer was operating and was in rough agreement with the mechanical gauge.  I also switched to the application of vacuum and they noted that the 4-20ma transducer output fell to 0 mA or something less than 4 mA (thought 4 mA output was minimum output?).  I then rearranged the plumbing fittings so as to permit selecting between a vacuum pump or a back fill line (10 psi UHP N2 @ 2 LPM) without the need to undo any tubing fittings as had been the case initially.  During this plumbing rearrangement, the sensing line was open to the room and began to flow GN2 past the obstruction.  This phenomenon had been observed on previous dislodge attempts (see entries from last month?) the difference this time was the significant increase in volume and duration - "Almost got it!"  I experimented with various durations of pumping and back filling etc. and observed on a few occasions that the audible gas load to the diaphragm pump would change spontaneously if let alone for several minutes.  

Anyway, this is all very encouraging and will likely be continued next week.  I halted tonight's attempts in observance of the Vacuum Team's Friday Rule and to allow others (the larger vacuum community) to consider if this approach is thermally cycling the bi-braze joint and poses a risk.  I am leaving the sensing line back filled to 10 psi and isolated from both the vacuum line and back fill line.  
Comments related to this report
kyle.ryan@LIGO.ORG - 18:27, Saturday 21 January 2017 (33486)
Uh...make that sublimation or reverse deposition
H1 General
cheryl.vorvick@LIGO.ORG - posted 17:40, Friday 20 January 2017 (33469)
GRB - 1:37:38UTC - standing down until 2:37UTC

LHO VE (CDS)
david.barker@LIGO.ORG - posted 16:06, Friday 20 January 2017 - last comment - 00:19, Saturday 21 January 2017(33467)
WP6442, CP4 pump channels added to cell phone alarms, errors detected, channels removed from cell phone alarms

WP6442, alarm on positive LN2 level in CP4 pump

Chandra, Kyle, Gerardo, Dave

CP4 LN2 Pump Level channels were added to the cell phone text alert system ( H0:VAC-MY_CP4_LT250_PUMP_LEVEL_PCT,  H0:VAC-MY_CP4_LT250_PUMP_LEVEL_PCT_ERROR).

Unfortunately the ERROR channel was in Error this afternoon which caused many cell phone alerts. Trending this channel shows that over the past month it has been transitioning between Error and No Error states, which the majority of the time being in Error.

Until this channel's intermittent errors can be resolved, we cannot rely on this as a critical alarm. WP6442 work has been postponed until Monday.

Comments related to this report
david.barker@LIGO.ORG - 17:00, Friday 20 January 2017 (33468)

here is a second  trend plot of the CP4 pump level and its Beckhoff error signal over the past 6 hours.

Images attached to this comment
patrick.thomas@LIGO.ORG - 00:19, Saturday 21 January 2017 (33473)
As Dave noted in his email to me, this is a 4-20 mA signal. From the attached trends it appears that the error signal is reflecting excursions out of this range.
Non-image files attached to this comment
LHO General
thomas.shaffer@LIGO.ORG - posted 16:03, Friday 20 January 2017 (33449)
Ops Day Shift Summary

TITLE: 01/21 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 62Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: 2 locklosses, one I'm not sure of the cause, the other was from PI mode 27. I changed a BP filter for the PI and it seemed to have fixed it.
LOG:

H1 DetChar
thomas.shaffer@LIGO.ORG - posted 14:57, Friday 20 January 2017 - last comment - 22:36, Monday 23 January 2017(33464)
CS Card Reader Found ON, Now Off

Kyle went to grab a Helium tank just past the card reader at 22:51 UTC and found the card reader already ON. This is on our LVEA Sweep checklist but must have been missed. It is now OFF

Comments related to this report
corey.gray@LIGO.ORG - 15:02, Friday 20 January 2017 (33465)DetChar

It would be good to know if we should keep these Readers OFF or ON.  Originally we had been turning them OFF after LVEA Sweeps, but the Sweep checklist had this crossed out & it marked with "ON" (So, the most recent version of the Checklist had the Card Reader line removed). 

Maybe these Card Readers are not an issue?  Maybe I heard Robert say these Card Readers were negligible.

michael.landry@LIGO.ORG - 22:36, Monday 23 January 2017 (33554)

Robert Schofield's investigations showed no coupling from the card reader in O1. These should be left ON, as they are used by the RRT for site status reconstruction in trigger evaluation.

H1 General
thomas.shaffer@LIGO.ORG - posted 13:01, Friday 20 January 2017 - last comment - 15:04, Friday 20 January 2017(33460)
Observing @21:00

I changed the PI BP and accept the difference in SDF, let's try it this way.

Comments related to this report
edmond.merilh@LIGO.ORG - 13:33, Friday 20 January 2017 (33463)

Were you able to damp with the filter shift?

thomas.shaffer@LIGO.ORG - 15:04, Friday 20 January 2017 (33466)

The new BP seemed to have worked. I only had to change the phase.

Displaying reports 50561-50580 of 83117.Go to page Start 2525 2526 2527 2528 2529 2530 2531 2532 2533 End