Displaying reports 56301-56320 of 88198.Go to page Start 2812 2813 2814 2815 2816 2817 2818 2819 2820 End
Reports until 00:12, Wednesday 21 December 2016
H1 General
edmond.merilh@LIGO.ORG - posted 00:12, Wednesday 21 December 2016 (32802)
Shift Summary - Owl Transition
TITLE: 12/21 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 74.4192Mpc
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 6mph Gusts, 5mph 5min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.77 μm/s 
QUICK SUMMARY:
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 00:07, Wednesday 21 December 2016 (32800)
Ops EVE shift summary

TITLE: 12/21 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC

STATE of H1: Observing at 74.4192Mpc

INCOMING OPERATOR: Ed

SHIFT SUMMARY: Been Observing for 4 hours and counting. Quiet shift so far. Lockloss a little bit after Robert went in to LVEA (I forgot to log this one), coincide with a 6.7M earthquake in East Timor but the earthquake didn't show up that high on the FOM (only 1um/s max). 

LOG:

0:27 Kyle back from mid Y

0:30 Kyle going back out

0:44 Robert out doing opportunistic injection in PSL and LVEA (LLO is down).

1:55 Kyle back

02:54 Observe

3:11 Out of Observe. LLO is down so Jeff is doing an opportunistic calibration work.

03:14 Lockloss. ASC signals went unstable. Jeff suspect high useism.

04:12 Observe

H1 TCS (TCS)
nutsinee.kijbunchoo@LIGO.ORG - posted 23:30, Tuesday 20 December 2016 - last comment - 09:27, Thursday 22 December 2016(32801)
Second PCI-e card didn't solve the glitch problem

Carlos, Jim B, Dave, Nutsinee

Follow up of WP6382

I took advantage of the earlier down time to test the HWS stream images script and swapping CLink around. The original set up after Carlos installed the second PCI-e card was HWSY CLink was plugged into the new card and HWSX CLink remained the same (plugged to old card). HWSX streamed live images without problem while HWSY can't get any sensible image at all (see attachment). So I tried a few more configurations:

We have come to the conclusion that the spare card might be busted. The next thing to try is to order a new card and try again. This way we will know for sure that the card actually works. We don't know where the spare card came from and whether or not it has been tested.

Images attached to this report
Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 16:30, Wednesday 21 December 2016 (32820)

Only HWSX code is left running for now.

aidan.brooks@LIGO.ORG - 09:27, Thursday 22 December 2016 (32835)

The cards were all ordered at the same time for aLIGO but were not individually tested.

It's probably the capture card but It might also be the actual PCI slot on the bus. Have you tried swapping the two cards around?

  • card one in slot one, card two in slot two (FAIL)
  • card one in slot two, card two in slot one (??)
LHO VE
kyle.ryan@LIGO.ORG - posted 19:17, Tuesday 20 December 2016 - last comment - 07:42, Wednesday 21 December 2016(32797)
Applied vacuum to CP4's clogged level sensing line
This has not been attempted previously to CP3 or CP4 though it is not a new or original idea.  

Both CP3 and CP4 are thought to be experiencing the same issue, i.e. an obstructed level sensing line.  This could be due to the accumulation and clumping of "snow flakes" of water ice.  It may be that the relative buoyancy in LN2 of these "snow flakes" is concentrating them near the bottom of the LN2 pump which is also where the lower sensing line enters the pump and samples the LN2.  With an increasingly dense concentration over time it is easy to imagine these "snowflakes" interlocking and forming clumps which eventually restrict the ID of the sensing line (the "cholesterol" theory!) to the point of complete obstruction.    

In the past we had applied UHP N2 (various pressures/durations -> Max. of 180 psi) to these clogged lines in an attempt to "push" this obstruction back into the 80K pump.  These attempts gave no indication of a resulting movement of the obstruction nor flow of the applied UHP N2.  Today, while changing the most recently depleted cylinder of UHP LN2 (leak into the room), I decided to reconnect the sensing line to the local differential pressure gauge.  I noticed that it indicated a differential pressure of 5" of water.  I repeated the process of decoupling the line from the gauge and exposing it to atmosphere for a period then reconnecting it to the gauge.  Each time the pressure difference increased by ~0.5" of water.  This got me thinking..... 

Considering the relatively large mass of water that can be extracted from food in the freeze drying process while exposed to vacuum and in such a relatively short amount of time, I discussed with John W. the risks and possible benefits of applying vacuum to our clogged CP4 line.  The hope is to encourage the sublimation of the "ice plug".  It was decided that applying a vacuum to the sensing line would be low risk at this point.   

So, late in the day, I hooked up a small diaphragm pump and pumped on the sensing line for a few minutes.  After reconnecting it to the differential pressure gauge and CDS level transducer I found that the indicated pressure difference had increased.  Repeated cycles produced repeated benefit (see attached image).  Of particular note is that an audible release of built-up gas could be heard each time the sensing line connection was loosened to do the next round of vacuum pumping.  This suggests that the CDS indicated pressure difference is due to a real pressure difference and that, perhaps, the vacuum pumping has established a flow path through the plug!  Or, that the ice plug has been pulled into a warm area.

Gerardo and I will continue tomorrow.  Chandra R. will be back after the new year. 
Non-image files attached to this report
Comments related to this report
michael.zucker@LIGO.ORG - 07:42, Wednesday 21 December 2016 (32809)

Wow!

chandra.romel@LIGO.ORG - 04:10, Wednesday 21 December 2016 (32805)
Nice work, Kyle!
LHO FMCS
kyle.ryan@LIGO.ORG - posted 18:06, Tuesday 20 December 2016 (32796)
Continued work at 2K IMC annulus ion pump
Resumed pumping 2K IMC annulus ion pump volume with pump carts during the maintenance period today.  Energized ion pump controller after an hour or so of pump cart-only pumping and the combination got the ion pump current down to 5ma -> Left ion pump controller on but had to shut down the assisting pump carts at the end of the maintenance period.  As of this writing, it looks like the ion pump current is just now coming back on scale so, perhaps, additional assisted pumping won't be required.
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 16:46, Tuesday 20 December 2016 (32795)
CDS maintenance summary, Tuesday 20th December 2016

WP6399 cdsfs0 raid firmware update

Carlos:

cdsfs0 raid controller card firmware was updated. The /ligo file system was offline for a short period of time

WP6382 add second camera card in h1hwsmsr

Carlos, Nutsinee:

The spare HWS camera pci-e card was installed in h1hwsmsr and one of the camera was moved over to it (see photo)

WP6407 start robo-alog code

Jonathan, Ryan, Dave:

The new robo-alog entry system was tested and is ready for use by the vacuum autofill process.

Images attached to this report
H1 SEI (SEI)
cheryl.vorvick@LIGO.ORG - posted 16:25, Tuesday 20 December 2016 (32793)
HEPI Pump Trends

Attached:

Some drop in presure - possibly due to temperature.

Images attached to this report
H1 General
jim.warner@LIGO.ORG - posted 16:03, Tuesday 20 December 2016 (32792)
Shift summary

 

TITLE: 12/20 Day Shift: 16:00-0:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: NLN
INCOMING OPERATOR: Nutsinee
SHIFT SUMMARY: Normal maintenance day, recovery hampered by alignment issues
LOG:
 
16:30 Kyle to LVEA
17:00 PeterK out of PSL
17:00 Jason to ITMX oplev to recenter
17:00 JeffB to Diode room
17:00 Betsy to LVEA for TCSY work
17:30 JeffK doing PUM measurement on ETMY
17:30 Kyle to MY
18:00 Gerardo to EX
18:30 Kyle back to LVEA
18:30 Karen to EY
18:30 Robert to LVEA
22:00 Start LVEA sweep, Betsy found 1 phone in the west bay that was powered on & EY has a LCD monitor on the vac beckhoff that can be seen on in the security cam
22:30 Kyle to MY
 
Started relocking about 22:30, initial alignment was fine until SRC steps, where it seemed it was necessary to go through a step at a time to get SRC stable. DRMI was poorly aligned when we were back to locking proper, and took a bit of tweaking PRM and BS to recover. ITMY bounce and roll modes were both high as well, when we got near DC_readout.
 
 
H1 General
vernon.sandberg@LIGO.ORG - posted 16:02, Tuesday 20 December 2016 (32791)
Work Permit Summary for 2016 December 13 Maintenance
Work Permit Date Description alog/status
6411.html 2016-12-20 13:46 Add CS, EX and EY chiller supply water temps to cell phone alarm system.  
6410.html 2016-12-20 11:23 Turn off remote access restrictions 4pm PST Thu 22 Dec 2016. System will be in monitoring only mode over the holidays. Reactivate restrictions 08:00 Tue 03 Jan 2017  
6409.html 2016-12-19 16:53 Realign ALS DIFF path to recover the beat note power.  
6408.html 2016-12-19 15:14 Land signal wires for new LPC type controller installed last week under WP#6396.  32784
6407.html 2016-12-19 14:16 Update aLOG config to make sure scripted/robo posts can run. There is a request to do robo-posts by the vacuum group over the break. 32786  & 32787
6406.html 2016-12-19 10:33 Re-center the ITMx optical lever. The optic needs to be in its Aligned state for the duration of this work. No viewports will be exposed.  32775
6405.html 2016-12-19 08:09 Update the calibration code to gstlal-calibration-1.1.3-v1 on the DMT. This release includes an improved bug fix to prevent the pipeline from hanging when run offline. In the previous version "there is the slight possibility of inadequate gating of the time-dependent calibration factors due to a 20 second timestamp offset, as described in this aLOG: https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=30439 This version also fixes the issue addressed by version 1.1.2, but it does not introduce this 20 second delay.  32772
6404.html 2016-12-14 12:48 We've lost lock because HAM5 ISI capacitive position sensors (CPS) have suddenly started going terribly glitchy and saturating. Jim and Fil are investigating, but this'll likely involve some electronics power cycling, if not swapping. Stay tuned for further details. Originally reported in LHO aLOG 32568.  32568 & 32572
6403.html 2016-12-14 12:43 Test script to overfill CP4.  32639 & 32573
6402.html 2016-12-14 10:39 Test script to overfill CP3. ECR E1600324. 32639 & 32573
       
Previous W.P.      
6381.html 2016-12-05 12:18 Replace the TCSY Flow meter. Turn TCSY laser off, valve out piping volume, remove yellow paddle wheel flow meter, install new one (same version/model number). Check flow, get laser going again - will need to stabilize. 32776
H1 CDS
david.barker@LIGO.ORG - posted 15:45, Tuesday 20 December 2016 (32789)
unmonitored ecat c1plc1 timing master port 7 status

Now the test timing system in the EE lab is powered down, h1ecatc1plc1 reported a difference for the master on port 7. Since this is a test system, we unmonitored this channel.

Logbook Admin General
logbook/robot/script0.cds.ligo-wa.caltech.edu@LIGO.ORG - posted 15:37, Tuesday 20 December 2016 (32787)
test robo post 2
This is a test of posting from script0 using robot credentials.

Logbook Admin General
logbook/robot/script0.cds.ligo-wa.caltech.edu@LIGO.ORG - posted 15:28, Tuesday 20 December 2016 - last comment - 15:49, Tuesday 20 December 2016(32785)
test robo post
This is a test of posting from script0 using robot credentials.
Have a very nice day.
Comments related to this report
david.barker@LIGO.ORG - 15:33, Tuesday 20 December 2016 (32786)

WP6407

Jonathan, Ryan, Dave:

we are testing the robot alog-entry system.

david.barker@LIGO.ORG - 15:49, Tuesday 20 December 2016 (32790)

We would like to remind the general reader that robotic entries can be filtered by using the "exclude robot entries" button in the search window.

Note that robotic entries which have non-robotic comments will not be filtered.

Images attached to this comment
LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 15:18, Tuesday 20 December 2016 (32784)
Signal Cables Landed For IP12 at X-End

After a little fix, moving cables to their correct block assignment (II cables were swapped at the box by the controller), the new cable was landed for ion pump IP12.

We are connected to the EI/II522A channels (all others not connected because they are not used anymore), work done per WP 6408.

Next, code will need to be updated, both in Beckhoff and MEDM world, to show upgrade to the new LPC Gamma type controller (positive polarity).

H1 IOO (IOO)
cheryl.vorvick@LIGO.ORG - posted 14:54, Tuesday 20 December 2016 - last comment - 16:35, Tuesday 20 December 2016(32781)
IM1, IM2, and IM3, changing alignment targets during the ramp up to O2, now have nominal values

The IM alignments were adjusted many times in the commissioning ramp up to O2, so IMs have not had nominal values for some time, and DIAG_MAIN values were not consistant with the current IM values.

I adjusted IM1-3 alignments after taking some measurements during maintenance today, and in looking at the IM alignment history.

I saw the IM1 pitch had bee restored to the DIAG_MAIN value yesterday, and this was not a correct value.

The current nominal values for IM1-3 OSEM alignments, as deemed good on Dec 8th at 09:00UTC, after a discussion with Jenne, are:

  pitch yaw
IM1 180 1120
IM2 608 -320
IM3 1961 -2

These are also listed in the IM Nominal Alignment medm (IOO sitemap list), and are updated in the DIAG_MAIN code.

To check IM alignment:

Images attached to this report
Comments related to this report
cheryl.vorvick@LIGO.ORG - 16:35, Tuesday 20 December 2016 (32794)

13 day trend - beginning of plots is where IM nominal alignment was set - after that, multiple ISI trips - some drift away from nominal - IM1 pitch change and recovery

Images attached to this comment
H1 General
betsy.weaver@LIGO.ORG - posted 14:17, Tuesday 20 December 2016 - last comment - 18:56, Tuesday 20 December 2016(32783)
Today's LVEA sweep, post Tues maintenance

Today, I performed the LVEA sweep after everyone finished their Tues maintenance work.  I confirmed everything on the list, except for 2 of the 3 crane parking placements - we didn't use any cranes today and they have been parked in the same place for over a week.  I also only glanced at the electronics racks, since we also had done a nice sweep to disconnect miscellaneous stuff from racks prior to the run starting.  I did not see any new dangling pieces of test equipment or other interesting looking stuff.

 

I did unplug the West bay phone along the wall - likely on since the start of O1 since it's a somewhat unfamiliar phone to people.  Here is the full list of LVEA phones I found and their status as of now (which should be added to the sweep checklist):

 

1) Inside H1 PSL enclosure - OFF

2) On tool box or table near H1 PSL enclosure - OFF

3) West bay along wall near crane parking sign - now OFF

4) On table near HAM7 East door - OFF

5) Along wall near HAM6 North - OFF

6) In Squeezer Bay on table - OFF

7) Back corner of electronics room, on floor - OFF

8) I suspect possibly one is inside H2 PSL enclosure - called it, didn't see it on HAM7 mic, unconclusive if it exists...

Comments related to this report
peter.king@LIGO.ORG - 18:56, Tuesday 20 December 2016 (32798)
The H2 phone is definitely powered off.  I checked it last week by trying to make a
call from it.  Dead as a door knob.
H1 TCS
betsy.weaver@LIGO.ORG - posted 12:20, Tuesday 20 December 2016 - last comment - 15:25, Tuesday 03 January 2017(32776)
TCSY In-line Flow Sensor replaced

This morning, Jason, Mark and I swapped the assumed-to-be failing TCSY flow sensor which has been showing epochs of glitching and low readout (while other indicators show normal flow, alogs 32712 and 32230).  The process to do this was such:

 

1) Key laser off at control box in rack, LVEA

2) Turn RF off at mezzanine rack, Mech room

3) Turn chiller off on mezzanine, Mech room

4) Turn power off on back of controller box in rack, LVEA (we also pulled the power cable to the sensor off the front of the controller, but it was probably overkill)

5) Close in-line valves under BSC chamber near yellow sensor to-be-swapped, LVEA

6) Quick-disconnect water tubes at manifold near table, LVEA

7) Pulled yelow top off of yellow sensor housing under BSC at the piping, LVEA

8) Pulled the blue and black wires to the Power recepticles inside the housing (see pic attached).  Pulled full grey cable out of housing.

9) While carefully supporting blue piping*, unscrewed large white nut holding housing/sensor to piping (was tough, in fact so tough that we later removed all of the teflon tape which was unneeded in his join)

10) Pull* straight up on the housing (hard) and it comes out of the piping.

11) Reverse all above steps to insert new housing/sensor, wires and turn everything back on.  Watch for rolled o-rings on the housing and proper alignment of the noth feature when installing the new sensor.  Verify mechanical flow sensors in piping line show ~3-4 G/m readout when flow/chiller is restored to functionality.

12) Setup new flow sensor head with Settings:  Go to the other in-use sensor, pull off the top and scroll through the menu items (red and white buttons on the unit (shown in pic).  Set the new head to these values.

13) Verify the new settings on the head are showing a ~3 G/m readout on the medm screen.  If not, possibly there is setting on the sensor that needs revisited.

14) Monitor TCS to see that laser comes back up and stabilizes.

* Blue piping can crack so be careful to always support it and avoid torque torque

 

Note - with the sensor removed, we could see alot of green merk in the blue piping where the paddle wheel sits.  Still suffering green sludge in this system...

Images attached to this report
Comments related to this report
peter.king@LIGO.ORG - 12:57, Tuesday 20 December 2016 (32777)
A few pictures to add to those already posted.

The O-ring closest to the paddle wheel had a cut to it.  Not near the electronics,
plus there's the other O-ring so it doesn't look like water was getting into where
the electronics is housed.

Some kind of stuff stuck to each blade (paddle?) of the paddle wheel.  Not a good
sign if the cooling water for the laser is meant to be clean.
Images attached to this comment
marc.pirello@LIGO.ORG - 13:20, Tuesday 20 December 2016 (32778)

Settings were as follows:

FLO Unit (Flow Unit) = G/m (default was L/m)

FActor (K-Factor) = 135.00 (default was 20)

AVErage (Average) = 0

SEnSit (Sensitivity) = 0

4 Set (4mA Set Point) = 0 G/m

20 Set (20mA Set Point = 10 G/m (default was 160)

ContrAST (Contrast) = 3

betsy.weaver@LIGO.ORG - 14:05, Tuesday 20 December 2016 (32782)

Here's both TCS system laser power and flow for the past day.  The drop out in the ITMY data is our few hour sensor replacement work.  So far no glitching or low droops.  Although, there weren't any for the last 24 hours on the old sensor either.

Images attached to this comment
jason.oberling@LIGO.ORG - 15:17, Tuesday 03 January 2017 (32931)

Attached is a 14 day duration minute trend of the TCSy chiller flow rate and CO2 laser power since our swap of tthe TCSy flow sensor.  There have been 7 glitches below 2 GPM, with 3 of those glitches being below 1 GPM; all 7 glitches occured in the last week.  Unless the spare flow sensor is also faulty (not beyond belief, but still a hard one to swallow) the root cause of our TCSy flow glitches lies elsewhere.

Images attached to this comment
alastair.heptonstall@LIGO.ORG - 15:25, Tuesday 03 January 2017 (32932)

It might be a good idea to try swapping the laser controller chassis next.  The electronics path for this flow meter is very simple - just the controller and then into the EtherCAT chassis where it's read by an ADC.

Displaying reports 56301-56320 of 88198.Go to page Start 2812 2813 2814 2815 2816 2817 2818 2819 2820 End