Sheila, Kiwamu

We spent some time this evening to find the POP beam. We successfully found the POP beam and managed to extract it to ISCT1.

We realigned the down stream because we had touched PR3 to get the POP beam. Now REFL, POP and AS beams are all coming out of the chambers.

POP beam:

With the use of an analog camera, we became able to see the POP beam hitting the swiss cheese baffle in HAM2. It was too high and off toward left in the camera view. We temporarily placed the camera at 3 o'clock position at HAM3 spool. This allowed us for steering PR3 to get the POP beam coming out to ISCT1. Note that we could not see the spot with the GigE camera somehow.

We then placed an analog camera in the POP path on ISCT1. This is now blocking the POP beam opn the table, but serving as a reference. Also, touching ITMY, we got the Michelson fringing.

Re-alignment:

Since we touched PR3, we had to realign the downstream. We touched SR3 and SR2. We tried to center the beam on the left part of the SR2 baffle, but this resulted in DAC saturation in SR2 when centering the beam on SRM by steering SR2. So at the end, we gave up the centering of yaw of SR2 and brought it back to where it was. This released the DAC in SR2 as expected and we then could steer SR2 into SRM easily. We confirmed that the beam was hitting AS_A, _B and _C QPDs. The attached is the screenshot of the current alignment.

Since we are not super-confident with the SR3 alignment at this point. The HAM6 crews can feel free to revert the entire alignment, if they want to.

J. Kissel, K. Venkateswara

We did some very basic analysis of the data from the BRS_RY_OUT and the T240_X channels. The first attached plot shows the ASD of 5000 seconds of data from this afternoon. There was good coherence between the BRS and the T240X but there seemed to be a scale factor mismatch. The phase between the signals was very nearly zero. Since I believe BRS calibration is superior :P, I chose to apply a fudge factor of 0.62 to the T240X. To do the subtraction, I simply took the T240X velocity time-series data, differentiated once to convert to acceleration and divided by g. This was then subtracted from the BRS_RY_OUT time-series data, whose ASD is the light blue curve shown in the first plot labelled as 'simple subtraction'.

The second file shows an ASD plot of the raw T240X, the tilt-subtracted T240X and the T240 spec. in displacement units. Note that the weather was rather mild in the afternoon and the tilt noise can get much worse under high wind speeds.

12,185 process variables added
3,163 process variables removed
2,303 process variables are now unmonitored

Plot of pressure after 1 day on turbo pump, charge test is ongoing.

J. Kissel, K. Venkateswara, R. Schofield, S. Karki

Robert didn't believe that we can use our change in gravity gradient to damp the rung-up 8.8 [mHz] oscillations in the BRS, so we performed a demonstrative test in his presence. 

With Krishna himself as our test mass, he
(1) Waited for the balance to come to an equilibrium position,
(2) Moved in next to the North (+X) side of the sensor and squatted there. His approach created a bit of torque noise, but more importantly created a change in local gravity, changing the equilibrium position of the balance up because his squatted C.o.M. is slightly higher than the beam. 
(3) Stood up, increasing his center of mass much higher. This causes little-to-no tilt/torque and again changes the local gravity gradient shifting the DC equilibrium position of the oscillation to shift up. 
(4) Squatted back down, restoring his center of mass to the original location. Again there is a quick bit of torque noise as he squats, but one can see the DC equilibrium position has shifted back (roughly) to it's original location.
All of these changes in C.o.M. served to excite the 8.8 [mHz] mode, which is why you see the amplitude of motion increase at each change.

The first attachment is the time series of the tilt readout, and the second is pictures of the two positions.

Checked out both HAM2 and HAM3 optical levers today.  No major problems with either, only thing was the transmitter telescope pitch/yaw adjustments for both oplevs were not locked down so they both had significantly drifted (completely off the mirror, no return back on the QPD).  This was rectified; both oplevs were realigned and locked down.  Beam profiles and power measurements were done for both (will attach a comment tomorrow with this info, left it all in the LVEA...).  New calibrations were NOT attempted as this requires moving the ISIs; will need to find a window between commissioning work (maintenance Tuesday perhaps) and sit down with someone from SEI to do this.

08:15 LVEA is LASER SAFE 

08:30 Automated message about 200 West Area Emergency Drill - e-mail sent out LHO-All

08:44 Vacuum status is normal IFO wide. Corner station is pumping down and currently at 10 ^-6 torr.

09:04 Travis -out to LVEA to look for cable clamps for Jim

09:17 Gerardo -down to End-X to test power supply for ION pump

09:18 200 West Area Drill is terminated

09:20 Praxxair in for N₂ delivery

09:30 Visitor arrived on-site for tour

09:40 Cyrus-to End-X to check out FMCS "thing" ?

09:54 Dale -will be bringing in a tour group around 11:00

09:56 Koji - into LVEA for capton washer installation in HAM6

10:13 Cyrus - back from End-X

10:18 Jason -OpLev work @ HAM3. Also cable swap on SR3

10:30 Gerardo -back from End-X

10:37 Cyrus -Back out to End-X to swap parts

10:38 Praxxair out

11:02 Cyrus - returns! (cue music and credits)

11:15 Tour group in control room

13:27 Gerardo -to End-X to test ION pump power supplies

13:45 Cris - cleaning at X-End

14:40 Cris - back from End -X

15:30 LVEA IS LASER HAZARD

@ ~15:30 LVEA is LASER HAZARD

Vacuum pump (located in the mechanical room) that feeds some of the dust monitors is no longer working. Trying to locate old unit.

Filiberto Clara

K. Venkateswara, J. Kissel

Noticed BRS had been rung up with X-End activity (see LHO aLOG 13533).
- Gravity dance to damp the 8.8 [mHz] mode
- Changed very-low-frequency high-pass from 1 [mHz] to 0.5 [mHz], to improve signal fidelity for subtraction. 1 [mHz] was adding ~10 [deg] of phase to the signal at 10 [mHz] -- too much in the region we wish to use the BRS signal for GND T240.
- restarted code at ~11:45p PDT

Notes for future gravity dances:
- When Tilt signal is on the upper-half of its sign wave, one needs to stand on the North (+X) side, if lower-half on the south (-X) side.
- Transition, or start standing on a given side at the amplitude peak
- As the resonance gets damped, you need to stand on a given side for less and less time
- +/- 500 [ct] amplitude = need to stand on one side for a full half cycle (~30-50 seconds), +/-50 [ct] amplitude = only a few seconds at a time
- +/- 25 counts is good enough. 

Note on determining frequency for high-pass: 
- filter coefficient = (1 - (desired freq)/(sampling freq))
- Sampling frequency = 50 [Hz], desired frequency = 5e-4 [Hz] ==> filter coefficient = 0.99998;

SR3 Oplev laser dc S/N 194 DC regulator D1200461 added 

I physically realigned the MC1 and MC3 GigE cameras (h1cam11 and h1cam12 respectively) because they had been misaligned spontaneously. The attached are the snapshots of their views to show how they look like after the realignment.

Purge air is on while Jim works there.

Based on the matlab tf measurements taken after coil balancing on SRM SR2 and MC2, and in order to have a physical idea of what's happening, I calculated the DC coupling between longitudinal motion and test mass angular motion for the three stages of the three HSTS suspensions. The results are summarized in the attached spreadsheed, and the numbers in the table are from the transfer function measurements at 0.01Hz (7 averages using schroeder phase drive), and assuming the coherence was good. The transfer functions results are summarized in the second attachment.

To note from the results :
*Length to pitch coupling is roughly ~2rad/m and length to yaw is ~1rad/m.
*M2 length to M3 yaw coupling of SR2 is higher because of the broken actuator.
*M1 length to M3 yaw as well as M3 length to M3 yaw has a different phase than the other sus tested.

The plots can be generated by using the script living in trunk/HSTS/Common/Matlabtools/plothsts_matlabtfs_cross_levels.m
The matlab tf results can be found under /ligo/svncommon/SusSVN/sus/trunk/HSTS/{optic}/{level}/Data

K. Venkateswara

This morning I noticed that the BRS was rung up to large amplitudes (500 microrad), so I looked at the data from yesterday and noticed two main incidents/causes: Borja and Sheila were near the BRS at ~ 3:30 PM but that disturbance was small and did not drive it up the resonance much. The ASD and time series of the first disturbance is shown in the first attached file.

The second disturbance at ~5 PM was much bigger and really drove up the resonane of the bar from 50 nrad to 500 nrad as shown in the second file (the y-axis scale in the time series should be in nrad not rad). I'm not sure who this was yet. The gravity gradient from a person standing next to the balance is very large and can easily drive up (or down) the resonance amplitude to microrads. As the decay time is ~two days due to the high Q, it will take a long time for the bar to return to normal amplitudes. Furthermore, due to the non-linearities of the autocollimator, the harmonics of the fundamental become visible and destroy coherence with the seismometer as visible in the third file.

This is a known problem due to the open loop operation of the BRS and we hope to address it very soon with some simple feedback/damping loop. In the meantime, I would like to ask that people stay away from the BRS unless necessary. Gravity gradient torque falls off as distance^3, so even an extra  distance of 2-3 meters is sufficient to keep the influence small. Grvaity gradient torques are also filtered by the resonance of the balance, so if you move by it fast, that is generally okay.

When it does get rung up, it is kind of fun to drive it back down using your gravity :)

While the laser is shuttered this morning, I adjusted dark offsets for MC2 trans QPD, IM4 trans QPD (I changed the whitening gain on these yesterday to match the gain settings paul used for the calibration (alog 9716 ).  I also adjusted IMC trans and refl PD dark offsets.

The LVEA is now LASER SAFE

model restarts logged for Wed 20/Aug/2014
2014_08_20 15:09 h1broadcast0
2014_08_20 15:09 h1dc0
2014_08_20 15:09 h1fw0
2014_08_20 15:09 h1fw1
2014_08_20 15:09 h1nds0
2014_08_20 15:09 h1nds1
2014_08_20 15:10 h1dc0
2014_08_20 15:12 h1broadcast0
2014_08_20 15:12 h1fw0
2014_08_20 15:12 h1fw1
2014_08_20 15:12 h1nds0
2014_08_20 15:12 h1nds1

no unexpected restarts, DAQ reconfiguration.

Alexa Dan Fil Keita Koji

This afternoon we brought the second of Koji's three OMC children under control.

After working in the morning to understand the quadrant layout of the OMC QPDs, we were able to close simple diagonalized versions of the OMC QPD alignment loops to stabilize the beam in the chamber.  With Fil's help we enabled the high voltage to the PZT driver (in the process finding a cable that was plugged into the wrong slot on the AI chassis).  Before fiddling with the high voltage we checked that the HV readbacks were working as advertised.  We were able to drive the high-voltage PZT in a triangle wave across its entire range (0 -> 100V) and see flashes in the OMC.  We tried to improve the alignment by watching the flashes and searching for a clear 00 mode, but this turned out to be fruitless, probably because the beam is moving too much.

We proceeded to align the rest of the beam paths on the HAM6 table: OMC REFL QPDs, AS WFS, and the OMC REFL beam through the viewport.  For a while we were confused by a mirror on a too-short pedestal; Keita showed up at a lucky moment and fixed it.  The beam has been aligned onto all of the QPDs in the vacuum.

We should be able to lock the OMC tomorrow and study the alignment (and, possibly, take a first stab at the mode matching).  At the moment, the beam is moving a lot in pitch; this motion is due to something upstream of HAM6.  We suspect SR3 and the ISI table in HAM5, but it could be something else.  This motion really needs to be fixed before any robust OMC locking can happen, either by stabilizing the source or constructing a more robust OMC QPD servo.  While we flashed the OMC Koji was able to visualize the modes inside the cavity, and the 00 mode was there.

Before leaving the chamber we relieved the yaw and pitch bias on the OM tip-tilts and centered the OSEMs, and then clamped the tip-tilts to the table.  The TTs are in good shape.  One of the OM3 OSEM cables can potentially slip and block the beam to the AS WFS, we should find a way to clamp this cable in a safe place.

Tomorrow we need to install the kapton washers on the pico drivers.  We still need to align the OMC TRANS path, but we probably have to lock the OMC on a fairly strong 00 mode in order to see the beam.  In principle OMC TRANS can be aligned after the north door is installed.

Now that we have a beam we can do RF balancing of the AS WFS, if that's necessary.

We'd like to try to put the north door on HAM6 by the end of the day tomorrow.  Two other things need to happen before we can attach the door: cable dressing and table balancing by the SEI crew, and a check for ground loops.  (These steps may need some iteration if the ground loop situation is bad.)

For now the purge air has been turned off to give the mirrors a rest.

It appears that the end X FMCS EPICS readbacks went invalid at around 08/19/2014 23:35 UTC (from a trend of H0:FMC-EX_VEA_202A_DEGF). I checked the FMCS Windows computer and they appear to be down there as well. I'm not sure how to fix this, so I will email John.