Displaying reports 47761-47780 of 83264.Go to page Start 2385 2386 2387 2388 2389 2390 2391 2392 2393 End
Reports until 16:38, Tuesday 30 May 2017
LHO FMCS
bubba.gateley@LIGO.ORG - posted 16:38, Tuesday 30 May 2017 (36536)
End Station Temperautre Control
While looking at temperature averages at the end stations just before noon, I noticed that the B Temperature sensor at each end station was reading ~1 degree F higher than the other 3 sensors. I took the B sensor out of the equation to try and help stabilize the temperature. 

I made one other change and that was to switch the supply air temp control from manual to auto reset.

During this upgrade to the entire HVAC controls system, many of the older programs were copied and because of the nature of the older system, many of the points were set to manual. We have been working diligently at trying to catch all of these settings but inevitably some have slipped through. We continue looking.    
H1 CDS (VE)
david.barker@LIGO.ORG - posted 16:21, Tuesday 30 May 2017 - last comment - 16:46, Tuesday 30 May 2017(36535)
autofill of CP3 and CP4 will now run daily

WP7007

Chandra, Dave:

the vacuum users crontab on vacuum1 has been changed to run the CP3 and CP4 overfill scripts daily instead of only Monday, Wednesday and Friday. The crontab is now:

# Change to daily, WP7007 30 May 2017
# CP3 autofill
01 11 * * * /opt/rtcds/userapps/release/cds/h1/scripts/run_autofill_cp3.bsh &
# CP4 autofill
02 11 * * * /opt/rtcds/userapps/release/cds/h1/scripts/run_autofill_cp4.bsh &

 

Comments related to this report
ryan.blair@LIGO.ORG - 16:46, Tuesday 30 May 2017 (36537)

For those who do not natively speak crontab(5), the fields before the command are: minute, hour, day of month, month, day of week, with '*' being all (a/k/a first-to-last).

LHO General
patrick.thomas@LIGO.ORG - posted 16:18, Tuesday 30 May 2017 (36534)
Ops Eve Shift Transition
TITLE: 05/30 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 20mph Gusts, 17mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY:

Jenne and Vaishali working on locking ALS on X arm.
H1 General
edmond.merilh@LIGO.ORG - posted 15:57, Tuesday 30 May 2017 (36532)
Shift Summary - Day

TITLE: 05/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Patrick
SHIFT SUMMARY:
LOG:

15:10 Cleaning crew to end stations

15:!5 Jeff out to the cleaning area

15:15 HFD on site to do some testing

15:18 more Fire system maintenance people

15:22 more fire system maintenance people

15:30 Keita and Sigg out to EX for ALS LASER swap

16:10 Sensor correction for both ends is turned off.

16:23 Chris to CER to erect more scafolding.

16:23 Richard back from EX

16:24 Karen leaving EY

16:29 Sigg back from EX

16:35 TJ to LVEA

16:37 Nutsinee to LVEA

16:39 Norco on site for LN2 deleivery to vessel 80 (EX)

16:44 Kyle to MY

17:00 More fire dept on site

17:06 Keita is back from EX for now but is going back.

17:12 Pep to EY

17:20 Keita, Sigg and McCarthy back at EX

17:40 Fire bell testing at EX. The crew working on ALS have ben notified.

18:02 Carlos heading to EX

18:06 Jeff B heading to end stations

18:09 Chris and Bubba done in the CER

19:34 Hanford Monthly Emergency Test phone call.

20:03 Keita and Daniel are back from EX

20:04 Sheila and Kiwamu are going to EX

20:32 Fred in LVEA with a tape measure.

20:46 Fred out

21:19 Fil to EY

21:43 Hugh into LVEA

21:57 Hugh out

22:07 Called EY to "kick" Fil out so we can start locking.

H1 ISC
daniel.sigg@LIGO.ORG - posted 15:01, Tuesday 30 May 2017 - last comment - 11:47, Wednesday 31 May 2017(36528)
EX ALS laser swapped

Temp A: 24.4 ºC
Temp B: 21.6 ºC
Diode: 1.80A
Laser Crystal Temp: 29.60 ºC
Doubler Temp: 33.62 ºC

Images attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 15:14, Tuesday 30 May 2017 (36529)

Changed set points:

H1:ALS-X_FIBR_A_DEMOD_RFMAX: 10 from 4
H1:ALS-X_FIBR_LOCK_BEAT_RFMIN: -10 from -15
H1:ALS-X-LASER_HEAD_LASERDIODEPOWERNOMINAL: 1.80
H1:ALS-X-LASER_HEAD_LASERDIODEPOWERTOLERANCE: 0.2

daniel.sigg@LIGO.ORG - 15:21, Tuesday 30 May 2017 (36530)

The cable to the H1:ALS-X_LASER_IR_DC photodetector is intermittent and needs to be re-terminated. Currently, the readback is broken.

keita.kawabe@LIGO.ORG - 18:19, Tuesday 30 May 2017 (36541)

S/N (on the controller) Pulled out -> 2011B, Installed -> 2011A

Interlock cable was installed by Filiberto.

Handles on the controllers were swapped as the new one didn't have the tapped holes necessary for mounting on the table enclosure extension. The untapped handles will be drilled and tapped later.

sheila.dwyer@LIGO.ORG - 19:31, Tuesday 30 May 2017 (36544)

Kiwmau and I went out the end station after they swapped the laser and tweaked the beatnote alignment. We ended up with more power on the BBPD than before the laser swap (20mW now  compared to 19mW  from the old laser before the power dropped on sunday evening.)  We also moved the lens in the laser path before teh beatnote beam splitter 1.5 inches closer to the beamsplitter. This increased the beat note power to 8dBm, compared to about 0dBm from the old laser before Sunday evening. 

kiwamu.izumi@LIGO.ORG - 05:37, Wednesday 31 May 2017 (36554)

After we finished up the hardware work on the ISCTEX table, Jenne and Ed aligned the X arm for the green laser, which resulted in a highest (normalized) transmission of roughly 0.8 when it was fully resonant. Therefore the amount of light power reaching the corner station decreased from what it used to be by 20%. Since the output power of the new laser at that point was lower than it had been with the old laser by 10%, the half of the reduction in the transmission can be explained by the reduced laser power. I think the remaining 10% is due to mode-matching loss.

jeffrey.kissel@LIGO.ORG - 11:47, Wednesday 31 May 2017 (36564)CDS
Opened FRS Ticket 8249 regarding broken readback of ALS X IR PD.
H1 FMP (DetChar, ISC, PEM)
jeffrey.kissel@LIGO.ORG - posted 14:49, Tuesday 30 May 2017 (36527)
End-Station Temperature Update: Drifting Colder; 0.5 [deg C] diurnal oscillation because of Flipped Zone A?
J. Kissel

Checking in on the End station temperatures after the HVAC upgrade. I think I may have found a clue looking into the individual temperature sensors that comprise the average at each end station, which is what's used for the error signal in the FMCS HVAC control servo. Namely, it may be that the first zone is hooked up with a sign flip, or is somehow 180 deg out of phase with the other three zones, which makes the average seem more stable than reality, so the HVAC servo doesn't do anything about it.

In addition to these diurnal oscillations, the overall temperature is trending colder over the past 5-6 days (as reported by the suspensions displacement [first two attachments] and in temperature units, the PCAL temperature sensor), even though the FMCS HVAC error signal is holding steady.

Check out the associated attachments for proof. I've divided up the past 25 days [second two attachments] into several more detailed zooms [the rest of the attachments]: 
    - A pre-upgrade long (~5-6 day) trend
    - A pre-upgrade zoom of one day           -- this shows that all four zones used to be relatively in sync
    - A post upgrade long (~5-6 day) trend    -- this shows that zone A is ~180 out-of-phase with zones B, C, and D

I'll get in touch with Bubba to see if this sign-flipped Zone A is possible, and what we can do about the overall drift.
Images attached to this report
H1 CDS (VE)
david.barker@LIGO.ORG - posted 14:39, Tuesday 30 May 2017 - last comment - 15:31, Tuesday 30 May 2017(36526)
cell phone alarms, beam tube pressure alarm levels lowered

WP7008

Chandra, Dave:

The high alarm level for beam tube vacuum was lowered from 5.0e-08 to 5.0e-09 Torr for all beam tube gauges except for LX and LY, which are kept temporarily high following the corner station vent. Chandra will open a service-request FRS to request these alarm levels remain high until such time they can be reduced. The FRS will act as a reminder that LX and LY are out-of-configuration.

On Chandra's request I also added CP3's pump LN2 level back into the daily status texts to support ongoing CP3 work (example report shown below).

cp1=92.0  cp2=92.2  cp3=5.6  cp4=0.0  
cp5=92.0  cp6=92.0  cp7=92.0  cp8=92.0  

Comments related to this report
chandra.romel@LIGO.ORG - 15:31, Tuesday 30 May 2017 (36531)
H1 PSL (PSL)
travis.sadecki@LIGO.ORG - posted 13:43, Tuesday 30 May 2017 - last comment - 13:55, Tuesday 30 May 2017(36524)
PSL Weekly

Laser Status:
SysStat is good
Front End Power is 34.02W (should be around 30 W)
HPO Output Power is 157.9W
Front End Watch is GREEN
HPO Watch is GREEN

PMC:
It has been locked 5 days, 5 hr 57 minutes (should be days/weeks)
Reflected power = 15.33Watts
Transmitted power = 59.06Watts
PowerSum = 74.39Watts.

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

ISS:
The diffracted power is around 3.6% (should be 3-5%)
Last saturation event was 0 days 4 hours and 23 minutes ago (should be days/weeks)

Possible Issues:
Head 1-4 flow error, see SYSSTAT.adl

 

Comments related to this report
jason.oberling@LIGO.ORG - 13:55, Tuesday 30 May 2017 (36525)

Regarding the Head 1-4 Flow error, this is a known issue.  Short version: When the PSL was restarted after last week's work on the new air bleed trap, the flow for laser head 3 did not come back to its previous value, and is low enough to trigger the warning error (but not low enough to trip the system).  We can as of right now find no reason for this to have occurred, and there is nothing we can do about it without opening up the PSL cooling system (which is highly invasive).  We are continuing to monitor this.

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 13:38, Tuesday 30 May 2017 (36523)
DAQ update

h1fw0 had file write issues Friday afternoon. I power cycled the Solaris LDAS-QFS writer machine h1ldasgw0 and h1fw0 has been stable since then.

At the time h1ldasgw0 was rebooted it had been running since 14 Dec 2016 (163 days). For comparison, h1ldasgw1 has an uptime of 250 days. So we don't seem to be seeing a "running too long" issue and there is no explanation for h1ldasgw0's problem other than we have seen this  before with the same solution.

LHO VE
kyle.ryan@LIGO.ORG - posted 11:48, Tuesday 30 May 2017 (36519)
CP3 update
Chandra had to run some errands on the way to work but is on her way.  

As found this morning, the GN2 flow into CP3 via the sensing line hookup had increased overnight from > 2 LPM to > 5 LPM this morning (0950 hrs. local).  The GN2 bottle still had 1200 psi this morning and the regulator output (when adjusted for near zero flow) was still as left, i.e., 25 psi.  ->   I valved-in the parallel connected magnahelic diff. pressure gauge and it was in good agreement with the pressure transducer used by CDS.  I manually filled CP3 via CDS by changing the LLCV %open from 20% to 50%.  The exhaust thermocouples responded in 1 1/2 minutes or so.  Thinking that the 2 LPM contribution from the GN2 may have caused the T/Cs to respond prematurely, I went outside and opened the LLCM bypass valve 1/2 turn and observed LN2 at the exhaust after a minute or so.  So, CP3 is full.  I experimented by increasing the regulator output to 40 psi and increasing the GN2 flow to >> 5 LPM (5 LPM is max on this flow meter).  

I am leaving the setup at 40 psi regulator output, 3 LPM flow and the magnehelic gauge valved-out.  
H1 CDS (CDS)
jonathan.hanks@LIGO.ORG - posted 11:40, Tuesday 30 May 2017 (36518)
WP 7006 nds2 client update

Updated the NDS2 client to 0.14.2 (the code that should be pushed to the LSC repos as 0.14.2 later today).

This addresses problems in:

H1 TCS
nutsinee.kijbunchoo@LIGO.ORG - posted 10:57, Tuesday 30 May 2017 - last comment - 13:34, Tuesday 30 May 2017(36516)
CR HWS end testmass reflection test

TJ, Nutsinee

Per Aidan's request we misaligned ITMs and moved ETMs around to see if the CR HWS sees any reflection from the ETM surface. HWSY streamed images didn't appear to have any residuals from the ETMY but HWSX saw some light from the ETMX.

Here's HWSX with only ITMX misaligned (ITMX delta YAW = -191.3u)

And here's HWSX with both ITMX and ETMX misaligned (ETMX delta YAW = -110.5u)

 

We also appeared to have this mesh-looking feature on the left hand side. Stray light?

Images attached to this report
Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 12:17, Tuesday 30 May 2017 (36520)

TJ, Nutsinee

We went in and move top+bottom periscope to get ride of the reflection. Here's what it looks like now:

 

HWSX with ETM

 

HWSX without ETM

 

HWSX with ETM and ITM

Images attached to this comment
aidan.brooks@LIGO.ORG - 13:18, Tuesday 30 May 2017 (36521)

Alignment looks good. How much did you guys have to move these mirrors?

nutsinee.kijbunchoo@LIGO.ORG - 13:34, Tuesday 30 May 2017 (36522)

I moved the top periscope at least one whole turn (probably something like 1 turn and a half) to get rid of the dim shape of the test mass. Then I moved the bottom periscope to bring back the return SLED beam.

The Hartmann plates are back on and the codes are running.

LHO VE
chandra.romel@LIGO.ORG - posted 00:13, Monday 29 May 2017 - last comment - 09:05, Wednesday 31 May 2017(36479)
Mid-Y pressure rise

We had a potentially scary situation tonight at mid-Y and through crazy coincidence managed to fix it before it became a serious problem. Sheila contacted me around 10 pm local time about a verbal pressure alarm that was going off in control room for BSC7 (gauge PT-170). I checked the MEDM screen from home and didn't see anything abnormal - except that the pressure is a bit high since the vent (7e-8 Torr). Most likely it's alarming because of set point setting.

This alarm made me look at our site pressure trend (48 hr trend here) and noticed that PT-210 at mid-Y was quickly drifting up starting around 7pm. Suspected CP3 and/or CP4 were warming up due to very hot temperatures we've had this weekend. Gerardo was unable to remotely log into CDS to initiate a remote overfill even though we were supposed to have permission until June 1. I drove out to the site to manually overfill both cryopumps at the skid by opening the bypass valve 1/2 turn (just like the good ole days). Filled CP3 first and observed an almost immediate drop in pressure. Took 50 min. to overfill (verified by watching LN2 pour out of exhaust). As soon as I started the fill, the exhaust flow increased to turbulent. CP4 didn't exhibit the same turbulent behavior, and took 30 minutes to overfill. Conclusion is CP3's valve actuator setting from Friday was too low at 15% open. I reset to 18%. Also increased CP4 from 37% to 39% open. Tomorrow is supposed to be 98F!

Need to learn what the current pressure alarms are set to; I propose we tighten these just for mid-Y so vacuum staff is alerted quickly when pressure starts to rise. I also suggest we try to maintain seconds vs. minutes of overfill time as we approach a hot summer.

Images attached to this report
Comments related to this report
chandra.romel@LIGO.ORG - 00:22, Monday 29 May 2017 (36480)

Based on this log entry from last June 24, it took 35 minutes to overfill CP4 until LN2 poured out the exhaust. This was before CP4 clog - we were experimenting with durations and flow rates to create a work-around for CP3.

https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=27950

kyle.ryan@LIGO.ORG - 01:22, Monday 29 May 2017 (36481)
Tonight's real life scenario has been my nightmare for the past 18 months (since ice plugs have required manual filling of CP3 and CP4).  It happened on my watch and I am responsible for it.  In my defense, this was not the result of inattention or a false sense of security on my part.  I had lowered CP3's manual LLCV %open value to 15% open, down from 17% open, in response to Friday's automated fill having only taken 17 seconds.  This would have been an appropriate response, perhaps, for springtime ambient temperature conditions but proved too much of a reduction/correction for this weekend's warmest-of-the-year weather.  

I look at the vacuum site overview screen multiple times on non-work days and am quite familiar with what the "normal" values are.  Today was no different. At around 07:30 pm local time, I looked and noticed that PT243 was 3.97 x 10-9 torr which is higher than normal and caught my attention.  I reasoned that this was probably hydrogen emitting from the BT steel on this "hot" day but was concerned enough that I resolved to check it again before going to bed.  At approx. 10:30 pm local time, I looked and saw that PT243 had fallen to 2.?? x 10-9 torr.  Minutes later, I checked my phone before going to bed and became aware of a text thread between Chandra R. and Gerardo M. which had been in progress for the previous 30 minutes.  So, the reduction in PT243 at 10:30 pm was the result of the fact that Chandra was already on site and had started filling CP3 manually via the opening the LLCV bypass valve.  

Had Sheila D. not contacted Chandra at approx. 09:50 pm and Chandra not responded by doing a manual fill, the pressure shown by PT243 10:30 pm would have been much higher than the previuosly "concerning" value seen at ~07:30 and I feel that I would have responded appropriately.  Still, this didn't have to happen.  As Chandra reminded me, pressure trends are available (new location) for remote viewing and, had I reviewed these in addition to the Vacuum Site Overview, I would have noticed that the Y-mid values were increasing independent of the rest of the site pressures.  This would have dispelled my "hydrogen" theory at 07:30 and I would have done a manual refill then.  



chandra.romel@LIGO.ORG - 03:57, Monday 29 May 2017 (36482)

Kyle, you shouldn't feel responsible. I'm usually the one who manipulates the LLCV settings based on temperature fluctuations and fullness of Dewar and have a better feel for adjustments. Sorry I didn't explain that better before I left. We can start to think about the next level of automation on this system which would increase/decrease valve setting based on how long it took to fill the previous time. Folks should also recognize that the work we're proposing to do post O2 by either decommissioning and/or regenerating these CPs will eliminate these risks.

Also, I doubt PT-170 alarming was actually a crazy coincidence. I forgot to trend its pressure but am guessing it was also starting to increase due to loss of cryopump action at MY. And because its pressure was already high from vent, it alerted us before we had to wait for -8 torr range alarms in arm. Thank goodness Sheila was in the lab at the time to catch it!

 

michael.zucker@LIGO.ORG - 08:44, Monday 29 May 2017 (36484)

Good save, I should have thought of this. The dominant boiloff load is (should be) blackbody radiation from the tube, which is at BTE ambient temperature. I will make a number for the fractional effect on liquid mass flow per degree, so we can add that % on to our "open-loop estimate". 

EDIT: see post 36496

Worth noting, though, the high ambient (BTE ) temp is raising the hydrogen diffusion flux, which doubles every 6 C or so (harmlessly, as long as we have ion pumps). So the pressure trend (and particularly, any attribution to the CP) has to be interpreted carefully.  

Even before today, the ice plugs gave me nightmares. We have to fix them, and stop any more from happening. 

chandra.romel@LIGO.ORG - 08:59, Monday 29 May 2017 (36485)

Dave Barker suggested increasing to daily auto overfills rather than Mon-Wed-Fri. I like this idea. We'll discuss with vacuum group this week.

david.barker@LIGO.ORG - 09:04, Monday 29 May 2017 (36486)

The cell phone alarm system currently monitors the vacuum gauge pairs at the ends of the 2km beam tube sections. For MY those are PT243 (closest to corner) and PT246 (closest to EX). I can certainly add all the other gauges in MY (PT244, PT245, PT210) to the system if needed.

david.barker@LIGO.ORG - 09:16, Monday 29 May 2017 (36487)

I've created a remote access permit for the vacuum group, good through the end of the year.

david.barker@LIGO.ORG - 11:32, Tuesday 30 May 2017 (36517)

No cell phone alarms were raised for this event, their upper alarm range is 5.0e-08 torr, an order of magnitude higher than what MY saw Sunday night (trend attached).

Gerardo was able to remotely log into CDS from home, he had a permit open. He was unable to directly log into the vacuum1 machine to make vacuum changes due to recent ssh cert changed. I recommend that every week the vacuum group test remote log into vacuum1 to verify this is possible.

 

Images attached to this comment
chandra.romel@LIGO.ORG - 16:05, Tuesday 30 May 2017 (36533)

More clues....or confusion. MidY IP9 current plotted with PT-210 pressure increase from Sunday evening. Strange behavior in IP.

Images attached to this comment
chandra.romel@LIGO.ORG - 08:44, Wednesday 31 May 2017 (36557)

Trended PT-170 over the weekend to understand the verbal alarm Sheila heard in control room. PT-170 pressure has steadily been falling since the vent, but at about 9:30pm local time on Sunday, it was crossing over the 7e-8 Torr alarm threshold causing the verbal alarm. What luck!

Images attached to this comment
chandra.romel@LIGO.ORG - 09:05, Wednesday 31 May 2017 (36558)

Outside temperature plotted over 30 days along with PT-243 at mid-Y.

Images attached to this comment
Displaying reports 47761-47780 of 83264.Go to page Start 2385 2386 2387 2388 2389 2390 2391 2392 2393 End