Displaying reports 53941-53960 of 83227.Go to page Start 2694 2695 2696 2697 2698 2699 2700 2701 2702 End
Reports until 14:04, Friday 30 September 2016
H1 ISC (DetChar, ISC)
gabriele.vajente@LIGO.ORG - posted 14:04, Friday 30 September 2016 (30110)
Jitter coupling stable over time

BruCo scans (see here for the most recent one) showed a large coherence with IMC alignment signals, in the region between 100 and 1000 Hz. The most significant coherence is with IMC-WFS_B_DC_PIT.

I computed the transfer function between this IMC beam spot position signal and the OMC DCPD SUM signal, for a few different time periods in the past couple of days. The transfer functions are basically non changing over time in the different locks. This suggests that, if the increased coupling is due to a IFO misalignment, this is quite repeatable and constant over time (fig. 2)

Not much of a smoking gun, but some hints.

Images attached to this report
LHO VE
chandra.romel@LIGO.ORG - posted 13:55, Friday 30 September 2016 - last comment - 16:45, Friday 30 September 2016(30108)
CP4 experiment
Overfilled CP4 again:

1. Opened exhaust bypass valve
2. Doubled LLCV (66% open)
3. Took ~17 min. to fill reservoir from 92% to 100%.
4. Took another hour to see LN2 pour out the exhaust. 
5. TC 252B did not respond to temp. change (and I broke the other one yesterday)
6. Set LLCV to nominal at 32% open in manual mode after the overfill
7. Would like to see how long it takes CP to recover to 92% at nominal LLCV (but may not happen this time since it's the weekend)

I used the borescope to look at the TC junction on the exhaust to see if it's measuring the pipe or the fluid flow. I couldn't see much but I suspect it's measuring just the pipe since the time delay on CP3 is long and temps never drop below -12degC on CP3 (response is faster when heating pipe with heat gun). 

I would like to drill and tap TCs directly into the pipe and use the existing signal lines to measure a more direct temp. for CP3 automation.

Images attached to this report
Comments related to this report
chandra.romel@LIGO.ORG - 13:59, Friday 30 September 2016 (30109)
Attached is temp and pressure trend for a CP3 overfill
Images attached to this comment
chandra.romel@LIGO.ORG - 16:45, Friday 30 September 2016 (30117)
CP4 is now in PI mode with lower limit set to 32%. Need to set this back to 20% on Monday. Want to see how long it takes to fall to 92% full at this nominal value.
H1 IOO (IOO)
cheryl.vorvick@LIGO.ORG - posted 13:43, Friday 30 September 2016 (30107)
ISS Second Loop QPD orientation of pitch and yaw signals now corrected

The orientation of the ISS second loop qpd was rotated 90 degrees and reversed in sign when compared to the orientation of IM4 Trans QPD.

I changed the QPD matrix and tested the change by exercising IM1 in pitch and yaw.

I've updated SDF.

Details attached.

Images attached to this report
H1 IOO (IOO)
cheryl.vorvick@LIGO.ORG - posted 13:23, Friday 30 September 2016 (30106)
IM1-4 alignment slider gains corrected -

IM alignment slider gains were reversed, and set the urad / slider count to 0.045.

I've corrected the alignment slider gains for all IMs, and used measured values for each optic such that the urad / slider count is 0.05.

I've attached a snapshot of the new gains, and a snapshot of SDF before I acepted the new gains.

With the gain change, the slider values also change, so any burt restore prior to 30 September 2016 at 20:01UTC (13:01PT) will fail to return the IMs to their correct alignment slider values.

Images attached to this report
H1 CAL (CAL)
sudarshan.karki@LIGO.ORG - posted 12:49, Friday 30 September 2016 (30105)
Pcal beam optimization at Yend

RickS, TravisS, SudarshanK

Using the same procedure used at END-X (LHO alog 29873), we optimized the Pcal beam locations at END-Y today. 

In each of these figure, the optimal locations, 111.6 mm from the center of the face of the optic in both positive and negative y direction, are denoted by red cross and the actual pcal beam locations by cyan circle.

Attached figure (1) shows the beam before they were optimized.  The offsets ([xoffset, yoffset]) from the optimal locations for upper and lower beam were: U[1.36, 7.58] and L[3.18, -8.60] in mm and uses standard co-ordinate sign convention.

Attached figure (2) shows the beam after they were steered to their optimal positions using the Pcal transmitter module steering mirrors.  The new offsets from the optimal locations are U [-0.96, -0.67] and L[-0.59, 0.39].

 

mmoffsetx =
 
    0.9558
    0.5913
 
 
mmoffsety =
 
   -0.6705
    0.3884
mmoffsetx =
 
    0.9558
    0.5913
 
 
mmoffsety =
 
   -0.670
Images attached to this report
H1 SEI
hugh.radkins@LIGO.ORG - posted 12:39, Friday 30 September 2016 (30104)
LHO BRS Checks/Status after Power Glitch

Everything looks to have restarted on its own or taken care of by the likes of Patrick (EndX) but I haven't been able to pin him down on that.  Actually, just managed to break into those guys--the computers did not stop so there was no restart.  Manual intervention to restart at EndX would be required but this glitch did not drop the BRSs out.

The Ion Pump at EndY has been reprogrammed to restart on its own and that was verified to still be running by EE this morning as well as the drift trends.  The attached shows these trends and the medms of the BRSs.  Again, things look to be running fine.

Images attached to this report
H1 SEI (CDS, SEI)
krishna.venkateswara@LIGO.ORG - posted 12:32, Friday 30 September 2016 (30103)
All BRS' are recovered

Krishna

BRS-X, BRS-Y and c-BRS seem to be functioning normally at the moment. I don't know if they were restarted manually or on their own, but ligo-dv web shows normal looking drift channels on BRS-X and BRS-Y and CTRL channel on c-BRS (trends attached).

Images attached to this report
X1 DTS
james.batch@LIGO.ORG - posted 11:44, Friday 30 September 2016 (30100)
Restarted DTS after power glitch
Jonathan, Jim

The front end computers on the DAQ test stand have been restarted following this morning's power glitch.
H1 ISC (CDS, SYS)
jeffrey.kissel@LIGO.ORG - posted 11:44, Friday 30 September 2016 - last comment - 14:13, Friday 30 September 2016(30099)
AS Port Fast Shutter Functionality Checked
J. Kissel, K. Kawabe, T. Shaffer, C. Gray

After a message popped up on the ISC_LOCK guardian to review the last check of the AS port fast shutter, and we realize the last check should have been during the power glitch recovery, we manually checked the functionality of the fast shutter. The fast shutter appears functional, stopping light into the OMC breadboard and the GS13s show an impulse.

The manual check: 
Setup:
- The IMC is locked, and the IFO aligned enough to see flashes on the AS port camera
- Watching the OMC Breadboard QPDs MEDM screen to see a spot moving around (channels H1:ASC-OMC_A_[YAW,PIT]_OUTMON)
- Watching the HAM6 GS13s on a dataviewer session to watch for fast physical motion of the shutter (channels H1:ISI-HAM6_BLND_[X,Y,Z]_GS13_CUR_IN1_DQ)

The test:
- Use the fast shutter detail MEDM screen (sitemap > LSC > shutters > bottom middle "Detail" under the "HAM6 Fast Shutter" name)
- Hit "open" then "close" several times, watch for light to disappear from the OMC Breadboad QPDs, and watch for large impulse on GS13s.

We need to do a similar test after every power outage, no matter how small.
TJ has agreed to create a guardian "PRECHECK" state such that we can do manual check of the fast shutter functionality. (To date we've only done the automatic checks every 48 hours).
Note: There already exists a guardian check in the FAST_SHUTTER node, however, the check is programmed to fail without the IFO MUCH further into the lock acquisition sequence (i.e. DRMI locked), and we'd prefer to check the functionality far before this.
Comments related to this report
richard.mccarthy@LIGO.ORG - 14:13, Friday 30 September 2016 (30111)
Not sure of the significance of a power outage.  We often reboot computers turn on and off power supplies that control this device, do we have to do functional tests everytime?
H1 TCS
thomas.shaffer@LIGO.ORG - posted 11:27, Friday 30 September 2016 (30098)
Ring heater recovery

Post power glitch, ETMY ring heater was on with 0.55 W top and bottom. DIAG_MAIN reported that this is nominally OFF, and trends for the past few days agreed. I brought these back to 0 and double checked the others as well.

The ITM ring heaters were not checked in DIAG_MAIN so I added them. As of right now it will check if they are off or on (not for specific values), if only one half is on, and if the top and bottom differ by some threshold percentage. I'd like to add checks to make sure that they are at their correct values as well, once that seems to be in a stable state.

H1 ISC
thomas.shaffer@LIGO.ORG - posted 11:19, Friday 30 September 2016 (30096)
ALS Fiber Polarization Adjusted

X wrong polarization % before = 15

Y wrong polarization % before = 6 (then 13 after turning the box on)

-----

X wrong polarization % after = 5

Y wrong polarization % after = 3

LHO VE
chandra.romel@LIGO.ORG - posted 11:02, Friday 30 September 2016 (30095)
CP3 overfill
10am local

Took 14:30 min to overfill CP3 with 1/2 turn on bypass LLCV. Increased manual setting to 19% (from 18%).

Left exhaust bypass valve open.
H1 SEI (SEI, SUS)
jeffrey.kissel@LIGO.ORG - posted 10:42, Friday 30 September 2016 (30093)
All SEI and SUS Recovered from Power Glitch / Lightening Strike
J. Kissel, B. Weaver, C. Vorvick, C. Gray

After front-ends were recovered (LHO aLOG 30088) from last night's power glitch (LHO aLOG 30083), we slowly have gone through all SEI and SUS untripped watchdogs, recovered full isolation, restored damping and alignment. All systems appear free of damage. It is likely, however, that bounce, roll, and voilin modes of the QUADs will be rung up, so we'll be mindful of them as recovery continues.

We've also confirmed that ESDs are functional, and all bias signs are where they're supposed to be as of the most recent sign flip (LHO aLOG 29397).
H1 TCS
betsy.weaver@LIGO.ORG - posted 10:20, Friday 30 September 2016 - last comment - 12:00, Friday 30 September 2016(30092)
TCS chiller and lasers restarted

This morning around 8:30am, Nutsinee and I went out and restarted the TCS chillers and the TCS lasers.  We also took the opportunity to swap the greenish filters.  Recall, we had flushed both chillers last week, but when we installed a new set of filters we noticed that they were tinging green immediately even though we had just flushed the system.  These filters sat for ~a week and we swapped them today in hopes that whatever immediately turned them green last week was just still pushing throgh the system.  We also had to add another 750mL (to top off the half way full indicator to full) and again inspected for leaking water (none found).

We'll need to look up how to clean these recyclable filters.

Comments related to this report
alastair.heptonstall@LIGO.ORG - 11:20, Friday 30 September 2016 (30097)

Is this on top of the 500ml added yesterday?   https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=30074

vernon.sandberg@LIGO.ORG - 11:45, Friday 30 September 2016 (30101)

Added scales to the sides of the fill tubes. This will allow better monitoring of the chiller water levels. The TCS-X scale runs from 21 - 30, linearly, and the TCS-Y scale runs 0-10, linearly.

Images attached to this comment
betsy.weaver@LIGO.ORG - 12:00, Friday 30 September 2016 (30102)

I have just opened and inspected the TCSY table - All water lines look good and no puddles found.  The tubes also appear to be pretty solid with not many air bubbles.

H1 TCS (TCS)
gerardo.moreno@LIGO.ORG - posted 16:06, Thursday 29 September 2016 - last comment - 10:56, Friday 30 September 2016(30074)
H1 TCS-Y Chiller

(Betsy, Gerardo)

This morning added 500 ml of water, and walked/crawled the length of the pipe looking for water drops, none found.  The inside of the TCS-Y table was not inspected.

Comments related to this report
gerardo.moreno@LIGO.ORG - 10:56, Friday 30 September 2016 (30094)

Photo of chiller level after fill up.  Time 16:26 utc, 9/29/2016.

Images attached to this comment
Displaying reports 53941-53960 of 83227.Go to page Start 2694 2695 2696 2697 2698 2699 2700 2701 2702 End