Displaying reports 57601-57620 of 88977.Go to page Start 2877 2878 2879 2880 2881 2882 2883 2884 2885 End
Reports until 13:16, Tuesday 06 December 2016
H1 CAL (DetChar)
jeffrey.kissel@LIGO.ORG - posted 13:16, Tuesday 06 December 2016 (32253)
PCALX Roaming Calibration Line Frequency Changed from 3501.3 to 4001.3
J. Kissel

Continuing the schedule of roaming PCALX line. We'll run this line for one more day, so that we get two points at 4001.3 Hz with a 30 [W] IFO to check consistency between the two repeats of the schedule, and then shut off the line until further notice.


Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 28 2016 17:20:44 UTC  Nov 30 2016 17:16:00 UTC         days    @ 30 W  
1501.3       35k                      02:00                   39322.0           Nov 30 2016 17:27:00 UTC  Nov 30 2016 19:36:00 UTC         02:09   @ 30 W         
2001.3       35k                      02:00                   39322.0           Nov 30 2016 19:36:00 UTC  Nov 30 2016 22:07:00 UTC         02:31   @ 30 W
2501.3       35k                      05:00                   39322.0           Nov 30 2016 22:08:00 UTC  Dec 02 2016 20:16:00 UTC         days    @ 30 W
3001.3       35k                      05:00                   39322.0           Dec 02 2016 20:17:00 UTC  Dec 05 2016 16:58:57 UTC         days    @ 30 W
3501.3       35k                      05:00                   39322.0           Dec 05 2016 16:58:57 UTC  Dec 06 2016 21:09:56 UTC         ~15:00  @ 30 W
4001.3       40k                      10:00                   39322.0           Dec 06 2016 21:09:56 UTC
4301.3       40k                      10:00                   39322.0                
4501.3       40k                      10:00                   39322.0           
4801.3       40k                      10:00                   39222.0           
5001.3       40k                      10:00                   39222.0         

Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 11 2016 21:37:50 UTC    Nov 12 2016 03:28:21 UTC      ~several hours @ 25 W
1501.3       35k                      02:00                   39322.0           Oct 24 2016 15:26:57 UTC    Oct 31 2016 15:44:29 UTC      ~week @ 25 W
2001.3       35k                      02:00                   39322.0           Oct 17 2016 21:22:03 UTC    Oct 24 2016 15:26:57 UTC      several days (at both 50W and 25 W)
2501.3       35k                      05:00                   39322.0           Oct 12 2016 03:20:41 UTC    Oct 17 2016 21:22:03 UTC      days     @ 50 W
3001.3       35k                      05:00                   39322.0           Oct 06 2016 18:39:26 UTC    Oct 12 2016 03:20:41 UTC      days     @ 50 W
3501.3       35k                      05:00                   39322.0           Jul 06 2016 18:56:13 UTC    Oct 06 2016 18:39:26 UTC      months   @ 50 W
4001.3       40k                      10:00                   39322.0           Nov 12 2016 03:28:21 UTC    Nov 16 2016 22:17:29 UTC      days     @ 30 W (see LHO aLOG 31546 for caveats)
4301.3       40k                      10:00                   39322.0           Nov 16 2016 22:17:29 UTC    Nov 18 2016 17:08:49 UTC      days     @ 30 W          
4501.3       40k                      10:00                   39322.0           Nov 18 2016 17:08:49 UTC    Nov 20 2016 16:54:32 UTC      days     @ 30 W (see LHO aLOG 31610 for caveats)   
4801.3       40k                      10:00                   39222.0           Nov 20 2016 16:54:32 UTC    Nov 22 2016 23:56:06 UTC      days     @ 30 W
5001.3       40k                      10:00                   39222.0           Nov 22 2016 23:56:06 UTC    Nov 28 2016 17:20:44 UTC      days     @ 30 W (line was OFF and ON for Hardware INJ)  
Images attached to this report
LHO General
patrick.thomas@LIGO.ORG - posted 13:05, Tuesday 06 December 2016 (32252)
LVEA swept for observing mode
Unplugged an unused extension cord (maybe two).
Turned off a power strip that a computer was plugged into. The computer appeared off but I wanted to make sure.
The left door on the left table enclosure behind the black laser safe curtains near the H1 PSL is unlocked. I did not have a key with me to lock it.
Went through the PSL science mode check list hanging next to the air handling controls for the H1 PSL enclosure. Did nothing for the H2 PSL enclosure.
Was not certain of the procedure for checking ISC table fans. Did not hear humming.
The pump near BSC8 is still running. There is a tall ladder against BSC8.
Made sure both card readers were off.
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 12:47, Tuesday 06 December 2016 (32250)
CDS Maintenance summary, Tuesday 6th December 2016

6388 Power cycle cdsfs0

Jim, Dave, Ryan, Carlos:

cdsfs0 (NFS server for /ligo) was powered down, RAID controller card and cables inspected, and powered back up between 11:42 and 12:02 PDT. This is the first action in an investigation of recent periods of /ligo unavailability.

6383 outbuilding WAP disconnects

Carlos, Jim, Dave:

The WAP ethernet cables were disconnected from the local switch at all outbuildings (EX, EY, MX, MY). These switch ports were then reactivated, permitting future use of CDS WiFi if the cables were to reconnected to local switch port #12.

6382 MSR TCS Hartmann Wavefront Sensor

Nutsinee:

The problem of the ITMX HWS image being glitched by running the ITMY camera could not be reproduced. If this problem re-appears, we will install a second camera card in h1hwsmsr. For now, no further action will be taken.

H1 CDS
david.barker@LIGO.ORG - posted 12:40, Tuesday 06 December 2016 (32249)
recent history of /ligo problems

looking at the logs on cdsfs0 over the past week, here are the number of times an error is reported which could have lead to /ligo being unavailable for a short period of time:

Wed Nov 30 04:43
Wed Nov 30 05:51
Wed Nov 30 18:37
Wed Nov 30 20:50
Fri Dec 2 04:40
Mon Dec 5 03:48
Mon Dec 5 14:52
Mon Dec 5 16:17
Mon Dec 5 17:32
Mon Dec 5 19:15
Tue Dec 6 10:42

H1 General
jeffrey.bartlett@LIGO.ORG - posted 12:24, Tuesday 06 December 2016 (32248)
Ops Mid Shift
   Maintenance activities are complete. 
   Reset Fiber Polarization on X-Arm. 
   Starting relocking.
H1 CDS (CDS)
carlos.perez@LIGO.ORG - posted 12:19, Tuesday 06 December 2016 (32247)
CDSFS0 power off due to NFS failures
After detecting failures on /Ligo, We power off CDSFS0, review all cable connections and verified that the controller card was plugged correctly on the board, after power back on we manually remounted and exported /Ligo. We also verified all workstations were connected again.
H1 CDS (ISC)
evan.hall@LIGO.ORG - posted 11:40, Tuesday 06 December 2016 (32245)
SRM digital camera refocus

Richard, Patrick, Evan

We refocused the SRM digital camera (cam17) while watching IR flashes on the SRM. The camera aperture was also stopped down a bit.

H1 CDS (CDS, DetChar, ISC)
keita.kawabe@LIGO.ORG - posted 11:22, Tuesday 06 December 2016 (32244)
Unmonitored ASC DC5 input matrix elements in OBSERVE

I've unmonitored all elements of ASC DC5 input matrix for OBSERVE in a hope that this is somewhat useful for passive ASC sensing measurement.

Unmonitored channels are H1:ASC-INMATRIX_P_16_XX and H1:ASC-INMATRIX_Y_16_XX where XX is 1, 2, 3, ... 33.

DC5 is not used at LHO, output of DC5 filters are still monitored (attached), and as soon as the output is turned on we're kicked out of observing, so this has zero impact on the IFO performance.

Images attached to this report
H1 CDS
james.batch@LIGO.ORG - posted 09:43, Tuesday 06 December 2016 - last comment - 12:09, Tuesday 06 December 2016(32242)
WAP at EX, EY unplugged
WP 6383

Carlos, Jim

The wireless access points at EX and EY have been unplugged and the switch ports turned on.  To reactivate the WAP for CDS access, the red ethernet cable will need to be plugged in to the switch as outlined in the VEAsWirelessAccess page in the CDS Wiki.  

Please remember to disconnect it when done!
Comments related to this report
david.barker@LIGO.ORG - 12:09, Tuesday 06 December 2016 (32246)

I've unplugged both mid stations as well.

H1 PEM
jeffrey.bartlett@LIGO.ORG - posted 09:40, Tuesday 06 December 2016 (32241)
End-Y Icy
   Carlos reports the parking lot at End-Y is very icy. Please be careful.
H1 General
jeffrey.bartlett@LIGO.ORG - posted 09:37, Tuesday 06 December 2016 (32240)
LockLoss
  17:31 Lockloss due to maintenance activities
H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:30, Tuesday 06 December 2016 (32238)
Ops Day Shift Transition
Ops Shift Log: 12/06/2016, Day Shift 16:00 – 00:00 (08:00 - 16:00) Time -  UTC (PT)
State of H1: IFO locked at NOMINAL_LOW_NOISE, 27.9W, 62.1MPc
Intent Bit: Observing
Wind: Is ranging from a Light to Moderate Breeze (7-14mph), with Light snow
0.03 – 0.1Hz: Currently between 0.09 – 0.03um/s  
0.1 – 0.3Hz:  Currently at 0.8um/s
Outgoing Operator: TJ
LHO General
thomas.shaffer@LIGO.ORG - posted 08:00, Tuesday 06 December 2016 (32232)
Ops Owl Shift Summary

TITLE: 12/06 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 59.5354Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Aside from one lockloss that I can't explain, we have been locked the whole shift. The range fell starting around 12:30 and has come up a bit, but not fully. I have ran the DARM_a2l_passive.xml every once in a while and it came out with different results almost every time. So I wasn't sure if I should run it in the beginning of the shift, but I ran it after LLO dropped out and the range wasn't recovering. Not sure if it helped.

TCSY chiller flow has been an issue throughout the night, but seems to get stable for a few hours at a time.
LOG:

*All Observing times are with ion pump near BSC8 running.

LHO General
thomas.shaffer@LIGO.ORG - posted 06:04, Tuesday 06 December 2016 (32236)
Ops 3/4 Shift Report

Observing with a 3.5hr lock. Range has taken a dip that seems to be coincident with the Hanford traffic again, but is on its way back up. LLO is also Observing after a long night of close tries.

Be care for those driving in, the roads are icy.

LHO General
thomas.shaffer@LIGO.ORG - posted 02:13, Tuesday 06 December 2016 - last comment - 19:03, Tuesday 06 December 2016(32233)
Lockloss @ 10:06 UTC

Not sure of the cause yet, everything seemed all good and normal. Running lockloss plots now though and I'll update if I find anything.

Comments related to this report
thomas.shaffer@LIGO.ORG - 02:53, Tuesday 06 December 2016 (32234)

But don't worry, we are back to Observing at 10:36 UTC.

I haven't seen anything of note for the lockloss. I checked the usual templates, with some screenshots of them attached.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 12:54, Tuesday 06 December 2016 (32251)Lockloss, OpsInfo

This seems like another example of the SR3 problem. (alog 32220 FRS 6852)

If you want to check for this kind of lockloss, zoom the time axis right around the lockloss time to see if the SR3 sensors change fractions of a second before the lockloss. 

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 17:28, Tuesday 06 December 2016 (32274)CDS, DetChar, Lockloss, SUS
J. Kissel, B. Weaver, T. Sadecki

Just for reference, I include a lockloss that was definitely *not* caused by the SR3 glitching for future comparison and distinction of whether this SR3 glitch has happened or not.

Also, remember, although the OPS wiki's instructions suggest that one must and can only use lockloss2, not everyone has the alias yet for this more advanced version. You can make the plots, and do everything you need with the more basic version:

    lockloss -c /ligo/home/ops/Templates/Locklosses/channels_to_look_at_SR3.txt select

It would also be great to get the support of @DetChar on this one. The fear is that these glitches begin infrequently, but get successively more frequent. Once they do, we should consider replacing electronics.

The fishy thing, though, is that LF and RT are on separate electronics chains, given the cable layout of HAM5 (see D1101917). Maybe these glitches are physical motion? Maybe with statistics of two, it's unclear whether it's that LF and RT just *appear* to be the culprit whether it may be a random set of OSEMs glitching.
Images attached to this comment
betsy.weaver@LIGO.ORG - 18:27, Tuesday 06 December 2016 (32279)

See my note in alog 32220, namely that Sheila and I looked again and we see that the glitch is on the T1 and LF coils, which share a line of electronics.  The second lockloss TJ started with in this log (12/06) are somewhat unconclusively linked to SR3 - no "glitches" like the first one 12/05, but instead all 6 top mass SR3 OSEMs show motion before lockloss.

 

Sheila, Betsy

betsy.weaver@LIGO.ORG - 19:01, Tuesday 06 December 2016 (32280)

Attached is a ~5 day trend of the SR3 top stage OSEMs.  T1 and LF do have an overall step in the min/max of their signals which happened at the time of that lockloss which showed the SR3 glitch (12/05 16:02 UTC)...

betsy.weaver@LIGO.ORG - 19:03, Tuesday 06 December 2016 (32281)

Images attached to this comment
H1 General
travis.sadecki@LIGO.ORG - posted 22:23, Monday 05 December 2016 - last comment - 10:30, Tuesday 06 December 2016(32222)
Lockloss 6:09 UTC

Lockloss due to PSL tripping off.  Currently on the phone with Jason working to remotely restart if possible.  Will update as I know more.

Comments related to this report
travis.sadecki@LIGO.ORG - 22:36, Monday 05 December 2016 (32223)

Jason noticed that the chiller was complaining about low water level as he was bringing it back up.  This is apparently due to the fact that when the chiller trips off, it burps a bunch of water onto the floor.  I topped the Xtal chiller off with 300 mL H2O.

travis.sadecki@LIGO.ORG - 22:56, Monday 05 December 2016 (32224)

Filed FRS ticket 6853 for this trip.

travis.sadecki@LIGO.ORG - 22:57, Monday 05 December 2016 (32225)

Also, back to Locking now.

travis.sadecki@LIGO.ORG - 23:09, Monday 05 December 2016 (32226)

Also, Rana and photographer are on site.  I let them onto the Observation Deck to take pics while we are relocking.

peter.king@LIGO.ORG - 08:18, Tuesday 06 December 2016 (32237)
Sorting through the myriad of signals leads me to think that the laser trip was due to the NPRO passing out.
Although it is possible that the flow rate in head 3 dipped below the 0.4 lpm limit.  Head3FlowNPRO.png
suggests that the NPRO tripped out before the flow rate in head 3 reached its limit.
Images attached to this comment
jason.oberling@LIGO.ORG - 09:28, Tuesday 06 December 2016 (32239)PSL

When restarting the laser last night, the status screen on the PSL Beckhoff PC indicated a trip of the "Head 1-4 Flow" interlock; although looking at the graphs Peter posted above it appears that the laser lost power before any of the flow sensors dropped below the trip threshold.

jason.oberling@LIGO.ORG - 10:30, Tuesday 06 December 2016 (32243)

Further forensics:  Attached are trends of the laser head temperatures around the time of last night's PSL trip.  To my eye nothing looks out of the ordinary.

Images attached to this comment
LHO VE
chandra.romel@LIGO.ORG - posted 17:38, Monday 05 December 2016 - last comment - 05:33, Tuesday 06 December 2016(32214)
corner pressure

PT170 and PT180 were installed in March 2016 when the X/Y beam manifold volumes were vented. PT140 was installed in Sept. 2016. Attached is trend from time of installation. Looks like PT170 & PT180 have been drifting up since after closing and re-opening isolation GVs 5/7 for HAM6 vent. We burped in accumulated gas from gate annuli but I'm not sure what the second hump is from April 9th. No log entry found.

Images attached to this report
Comments related to this report
chandra.romel@LIGO.ORG - 05:33, Tuesday 06 December 2016 (32235)
Could be water accumulation on gauge ion grid is causing drift.
Displaying reports 57601-57620 of 88977.Go to page Start 2877 2878 2879 2880 2881 2882 2883 2884 2885 End