Displaying reports 65001-65020 of 77211.Go to page Start 3247 3248 3249 3250 3251 3252 3253 3254 3255 End
Reports until 13:50, Tuesday 01 July 2014
H1 CDS
cyrus.reed@LIGO.ORG - posted 13:50, Tuesday 01 July 2014 (12573)
Vacuum EPICS Gateway Changes
This morning I changed the configuration of the EPICS gateway processes that serve the vacuum subnet IOC PVs to limit the allowed PVs to those actually available from the vacuum IOCs.  This is to eliminate the additional broadcast traffic that occurs when the gateway searches for PVs that do not exist in this subnet (and it does this a lot, each time a client broadcasts for a non-vacuum channel).  Searches are now limited to channels starting with "HVE-" or "H0:FMC-" (this last should probably be constrained further, but this is a good start).  Attached is a plot of the reduction in broadcast traffic as a result; the 'mini-peaks' that still occur near the start of the hour are probably from the hourly burt backup for H0:FMC channels not in the vacuum subnet.
Images attached to this report
H1 SYS (CDS, ISC, SEI, SUS)
jeffrey.kissel@LIGO.ORG - posted 13:39, Tuesday 01 July 2014 - last comment - 13:51, Tuesday 01 July 2014(12572)
All Corner Station SEI, SUS, and ISC Guardians Are Now Paused.
J. Kissel, A. Pele

Given the confusion of installation status vs what guardians are running what and why, I've brought all corner station guardians down to their equivalent SAFE or OFFLINE or UNLOCKED or DOWN state, and then paused them. These should not be unpaused again until we close up a given chamber and the install is complete. 

ETMX and EMTY should still be maintained under guardian control, and operators should make sure that they are fully isolated / aligned at all times until further notice.
Images attached to this report
Comments related to this report
jameson.rollins@LIGO.ORG - 13:51, Tuesday 01 July 2014 (12574)

I'm not exactly sure what happened to instigate all of this, but "guardctrl stop" should be safer than PAUSE.  PAUSE is not preserved across reboots of the guardian machine.  "guardctrl stop" on the other hand should actually prevent the node from being started after a reboot, which may be what you want in this case (assuming that's what happened).

X1 SUS
arnaud.pele@LIGO.ORG - posted 12:39, Tuesday 01 July 2014 - last comment - 09:31, Wednesday 02 July 2014(12546)
QUAD08 after blades change

The latest results from the X1 QUAD08 tfs -after Joe Odel/Jeff B/Andres R reworked on the quad to replace the top mass blades and rebalance the masses- are attached below and compared with the previous measurements from last week. This work was initiated to resolve the 10% discrepancy seen between the measured and modeled 2nd pitch mode frequency (1.32Hz) cf 5th page of 1st attachment. Though, the comparison shows this mode has stayed unchanged, except for a new pitch to vertical coupling at 2.25Hz.

Non-image files attached to this report
Comments related to this report
betsy.weaver@LIGO.ORG - 09:31, Wednesday 02 July 2014 (12585)

And here's Arnaud's plot comparing this Q8 M0 TF to other QUADs of the same species.

Non-image files attached to this comment
H1 PSL (PSL)
richard.savage@LIGO.ORG - posted 12:13, Tuesday 01 July 2014 - last comment - 13:29, Tuesday 01 July 2014(12569)
Water hose burst inside PSL High Power Oscillator box
PeterK, MattH, ChrisM, RickS

This morning, Peter found that the Crystal Chiller would not restart (apparently the laser has been down since last Friday).

He went to the Laser Area Enclosure and found a puddle on the floor near the High Power Oscillator.

Removing the HPO covers revealed that a small (~3/16" ID) hose had separated and was leaking.

Hose was replaced, water mopped up, chiller restarted, water level topped off.

More details and photos to follow.
Comments related to this report
peter.king@LIGO.ORG - 13:29, Tuesday 01 July 2014 (12571)PSL
Just prior to the 08:15 meeting I noticed that the laser was off.  I pulled up the laser status screen and the "NPRO running", "Flow error (WD)" and "Frontend flow" indicators were red.  I went into the chiller room to find the crystal chiller indicating a flow error and that the water level was close to minimum.  I restarted the chiller from the diode room.  No sooner than I had reached the door the crystal chiller stopped indicating a flow problem.  This time the water level was below minimum, so I added enough water to bring it back to the maximum level.  I restarted the chiller and after a few seconds the chiller stopped and the water level was back below minimum.  Either we had a leak somewhere or we were getting rid of air bubbles in the plumbing.

I went into the H1 Enclosure to check up on the high power oscillator and noticed a couple of large puddles on the floor, a few droplets on the side of the table.  Putting the laser into service mode, enabled me to remove the cover of the laser.  It was then that I noticed there were some small puddles inside the laser and the burst section of tubing.

The tubing was replaced.  The flow sensor was removed and examined.  No blockages or debris was found in the flow sensor.
The system was re-assembled and the crystal chiller restarted.  After topping up the water, the crystal chiller seems to be okay.

The lid of the high power oscillator will be left off for a few hours to let the laser dry out.
Images attached to this comment
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 12:09, Tuesday 01 July 2014 (12568)
CDS model and DAQ restart report, Monday 30th June 2014

model restarts logged for Mon 30/Jun/2014
2014_06_30 10:45 h1iopsush2a
2014_06_30 10:46 h1suspr3
2014_06_30 10:46 h1susprm
2014_06_30 10:48 h1susmc1
2014_06_30 10:48 h1susmc3
2014_06_30 10:49 h1iopsush34
2014_06_30 10:50 h1suspr2
2014_06_30 10:50 h1sussr2
2014_06_30 10:52 h1iopsush56
2014_06_30 10:52 h1susmc2
2014_06_30 10:54 h1susomc
2014_06_30 10:54 h1sussr3
2014_06_30 10:54 h1sussrm
2014_06_30 10:56 h1hpiham1
2014_06_30 10:56 h1hpiham6
2014_06_30 10:56 h1iopseih16
2014_06_30 10:56 h1isiham6
2014_06_30 10:58 h1iopseih23
2014_06_30 10:59 h1isiham2
2014_06_30 10:59 h1isiham3
2014_06_30 11:01 h1hpiham2
2014_06_30 11:01 h1hpiham3
2014_06_30 11:02 h1iopseih45
2014_06_30 11:04 h1hpiham5
2014_06_30 11:04 h1isiham4
2014_06_30 11:04 h1isiham5
2014_06_30 11:06 h1hpiham4

no unexpected restarts. Install of SWWD on HAMs

H1 CDS (SEI, SUS)
david.barker@LIGO.ORG - posted 12:01, Tuesday 01 July 2014 (12567)
New IOP SWWD installed on BSC1,2,3

Jeff, Patrick, Dave.

I installed the latest IOP SWWD models on the following systems: h1iopsusb123, h1iopseib1, h1iopseib2, h1iopseib3. All SUS and SEI models on these front ends were stopped (using guardian to first put them into a safe state) and then restarted.

This completes the SWWD FE install, I am now cleaning up the MEDM screens.

H1 INS
calum.torrie@LIGO.ORG - posted 11:50, Tuesday 01 July 2014 (12566)
Contamination Control Kits

In the corner of the "cleaning area" adjacent to the door to the LVEA there is now a fully stocked Contamination Control (CC) Area and 3x fully stocked Contamination Control Portable Kits.

These are available for all to use. In fact if you have an open chamber there is no reason you shouldn't have a Contamination Control Portable Kits. How do I know what a Contamination Control Portable Kits looks like? Don't worry they are the BIG PINK Really Useful boxes, and as such pretty noticeable. See attached pdf  for picutres of the portable kits and the main CC area.

Further details can be found here LIGO-T1400310: Contamination Control Kits - Parts list, poster and kiting plan and use. At this DCC link you will find slides descirbing the area, a poster of all of the items included in the kits, a correspoding parts list, labels and a chamber entrance guide.

Please see Jeff Bartlett if you have any questions and liaise with Jeff for re-stocking of the portable kits and areas.

Calum Torrie

Non-image files attached to this report
H1 INS
calum.torrie@LIGO.ORG - posted 11:39, Tuesday 01 July 2014 (12565)
The Green Lantern

Last week at LHO (Travis, Betsy, Kate and Calum) tested the TM Green Lantern, LIGO-D1400060-v4, on the ITM in the WBSC3 chamber. The Test Mass (TM) Green Lantern gives a system which allows us to: -

i) Illuminate the optic (in chamber) in a consistent manner at grazing angle to face of optic. (The TM Green Lantern can be installed while first contact (FC) in place. In addition the FC can be removed while TM Green Lantern is in place.)

ii) Highlight dust on the surface of the optic cf. previous methods of illumination (flashlight) which couldn't operate at grazing angle. As such the previous methods illuminatated substrate defects instead of dust on the surface.

iii) Image the dust on the optic (as a result of the effective illumination).

iv) See (and image) the effectiveness of the FC on a dusty optic. (This has not yet been tested.)

The TM Green Lantern is now on site at LHO (class B) under Betsy's ownership. See attached image below.

Calum Torrie (and team listed above).

Images attached to this report
H1 SUS
betsy.weaver@LIGO.ORG - posted 10:57, Tuesday 01 July 2014 - last comment - 11:21, Tuesday 01 July 2014(12563)
Guardian Question

After this mornings boots (just happened, see more from Dave I suspect shortly), I see that the guardians for all of the SUSes come back in EXEC mode.  THey were previously set to PAUSE or other state.  Why does it reset to EXEC after boots?

Comments related to this report
jameson.rollins@LIGO.ORG - 11:21, Tuesday 01 July 2014 (12564)

Guardian nodes come up in EXEC after restart.  Their state is not preserved across restarts.  I understand why this would be an issue, though, so maybe I should work on a way to preserve state across restarts.

Why did the nodes restart, though?  Did the guardian machine get rebooted?

Presumably the problem here was that the nodes came up in EXEC, and then went to their default ALIGNED state, which disturbed the optic alignment happening in chamber.  One way around this would have been temporarily modify the SUS nodes to come up with the initial request as SAFE.  This would have prevented the damping loops from being engaged and the alignment offsets from being enabled.

H1 AOS (INS, SEI, SUS)
jason.oberling@LIGO.ORG - posted 10:29, Tuesday 01 July 2014 (12562)
ITMx Final Alignment Numbers

Since we got the "All Clear" from SUS this morning on ITMx suspension health, the following are the final alignment numbers for the ITMx and CPx.  For ACB final alignment numbers see alog 12542.

ITMx

CPx

H1 SEI
patrick.thomas@LIGO.ORG - posted 08:42, Tuesday 01 July 2014 (12558)
OPS: reset of HEPI L4C Accumulated WD Counters Tuesday 1st July 2014
reset ITMX and ETMY
BS and ETMX IPS are close to trip levels, did not reset
LHO General
patrick.thomas@LIGO.ORG - posted 08:30, Tuesday 01 July 2014 (12557)
Morning meeting notes
ITMX suspension is healthy, ready for handoff
TCS installing computer at end X, connecting to camera, running ring heater to test the Hartmann sensor
Richard: cabling at end stations
H1 PSL
patrick.thomas@LIGO.ORG - posted 08:12, Tuesday 01 July 2014 (12556)
added 650 mL of H2O to the H1 PSL crystal chiller
This brought the level to just about the max.
H1 General
matthew.heintze@LIGO.ORG - posted 18:48, Monday 30 June 2014 (12554)
HAM2 particle counts

In cleanroom start of 4pm session:

All counts zero

 

In chamber start of 4pm session

0.5um...20 counts

remainder....zero counts

 

In chamber end of session:

0.5um...30 counts

remainder...zero counts

H1 SUS
jeffrey.kissel@LIGO.ORG - posted 17:28, Monday 30 June 2014 - last comment - 17:10, Monday 07 July 2014(12544)
H1 SUS ITMX Discrepant Drive Strength Fixed.
J. Kissel, A. Pele, T. Sadecki, B. Weaver,

After another day's worth of fumbling and hand-waving, we've finally traced the discrepant transfer function magnitude to a loose cable connection at the air-side of the feedthrough. In the course of attempted fixes, we measured a few more things, moved a few more things, replaced the R0 F2 and F3 OSEMs, but the only thing that fixed it was the cable connection. This flaw with the electronics chain should have been found earlier with our cable swap on Friday, with remeasuring the open light current, and with Arnaud's DC actuation test below, but frustratingly, it did not. But we found it. 

I'm in the process of getting formal transfer function measurements now, but I'm confident from what I'm seeing thus far that this SUS is read for close-out. Will post comparison TFs once they're finished.
We have exORSIIIIIIIZED the demons. This SUS is clee-uh.

Details (In rough chronological order)
-------
- Arnaud compared the ETMY and ITMX R0 F2 to F2 and F3 to F3 drive at DC using the alignment offsets (the only QUADs available, so take ERM and TCP chain comparison with a grain of salt), and concluded that the chains are driving with comparable and within a chain F2 and F3 are of comparable strength with such a quick study. 
- Betsy retook an L2L transfer function (just for sanity's), saw the same discrepant factor of two -- and some more Yaw resonant cross-coupling. Still F2 shows the majority of the badness.
- Decided just to swap the OSEMs, and hopefully move on. Below are the new serial numbers, open light current, and compensation gains and offsets. These *have* been installed. We'll take a new safe.snap this evening after all the commotion has died down.
- Betsy & Travis poked at this, looked at that, iterated with measurements several times on the floor.
- At last, Betsy went a long the signal chain, and made sure all connections were secure, and finally found this bad connection at the in-air connection at the feedthrough.
- Simultaneously, Travis loosened up the the cable loop from the optical table to the top mass. This may have alleviated the extra Yaw peaks that had shown up today. 

Open light current values and serial numbers for the new OSEMs.
      Raw    New     New        S/N
      ADC    Gain    Offset      
R0F2 25646   1.170   -12823     077
R0F3 26554   1.130   -13277     147

We'll also update the OSEM chart and grab a new safe.snap once transfer functions are finished.
 
Comments related to this report
jeffrey.kissel@LIGO.ORG - 21:57, Monday 30 June 2014 (12555)
TFs look great. For some reason the comparison script is failing on my laptop; will post comparisons tomorrow. But, for all intents and purposes, H1 SUS ITMX is ready for close-out. A victory for team SUS!
Non-image files attached to this comment
jeffrey.kissel@LIGO.ORG - 09:00, Tuesday 01 July 2014 (12560)
Comparison plots. All looks well, as expected. To demonstrate the problem, I also include the prior *bad* measurements of the reaction chain (2014-06-27_2117).
Non-image files attached to this comment
arnaud.pele@LIGO.ORG - 17:10, Monday 07 July 2014 (12634)

More transfer function measurements were taken on the lower stages of ITMX last tuesday.

Interesting things to notice :

1. The measurements with no top mass damping (1st and 3rd attachments) appear to show resonnances which are not predicted by the model. Those are most certainly resonnances of the reaction chain moving because of the reaction force (e.g. 3rd page of 1st attachment : resonnance at 0.66Hz is not predicted by the model, but matches with the frequency of the first yaw mode measured on the top mass reaction chain, cf this measurement from alog 12555).

2. There is a factor of 2ish discrepancy between the model and the measurement for both UIM and PUM

Non-image files attached to this comment
H1 SUS
jeffrey.kissel@LIGO.ORG - posted 11:59, Monday 30 June 2014 - last comment - 09:47, Tuesday 01 July 2014(12534)
Open light current values gathered for H1 SUS ITMX R0 F2 and F3
B. Weaver, T. Sadecki, A. Pele, J. Kissel

In hopes of find a smoking gun in a dead OSEM LED or photo-diode, we backed off the H1 SUS ITMX's R0 F2 and F3 OSEMs and gathered a new measurement of their open light current. Sadly, the difference is at most 5-10%, and does not explain the factor of two seen last Friday (LHO aLOG 12522). Thus far we haven't changed the OSEMINF compensation values to match the new reading, because we're not sure if we're gunna swap out the OSEMs yet. Or next step is to drive alignment offsets and compare against other suspensions to see if the coil / actuation side of the OSEM is the culprit. We'll also measure coil resistance. (Remember, the electronics chain has been exonerated with the cable swap test we did on Friday).

For reference:
      Raw   New    New      Former   Former
      ADC   Gain   Offset   Gain     Offset
R0F2 28600  1.049  -14300   1.003    -14958
R0F3 26320  1.140  -13160   1.063    -14114

Obtained using the following matlab script:
/ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/
[resultstring gains offsets] = prettyOSEMgains('H1','ITMX');
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:47, Tuesday 01 July 2014 (12561)
Note that these numbers were never installed, and now obsolete since we replaced these two OSEMs. See LHO aLOG 12544 for new OSEMs and open light current values.
X1 SUS
mark.barton@LIGO.ORG - posted 12:53, Thursday 26 June 2014 - last comment - 12:36, Tuesday 01 July 2014(12494)
QUAD08 TFs

Joe and Andres finished adjusting QUAD08 so I started a round of TFs on both chains at 12:52. Order is undamped M0, R0, then damped M0 and R0.

Comments related to this report
arnaud.pele@LIGO.ORG - 16:53, Thursday 26 June 2014 (12502)

First set of measurement failed. Started them again at 23:52:23 UTC.

arnaud.pele@LIGO.ORG - 15:46, Friday 27 June 2014 (12520)

Transfer functions ran yesterday in the staging building are showing clear sources of rubbing especially in the pitch/length/yaw degrees of freedom for the reaction chain. Main chain has large unexpected cross couplings in pitch.

arnaud.pele@LIGO.ORG - 12:36, Tuesday 01 July 2014 (12570)

Andres and Jeff realized the cover was on during that measurement, which is why results were bad. We started them again Friday overnight.

Displaying reports 65001-65020 of 77211.Go to page Start 3247 3248 3249 3250 3251 3252 3253 3254 3255 End