- Kapton washers to prevent picomotor sticking were installed on the HAM6 picos in the morning.
- Cable grounding were checked with Dan after Jim's cable rerouting in the evening. (Entry below)
The last ISC task before puting the north door is alignment of the OMC leakage trans beam on the northwest viewport (emulator).
With 2W PSL input, corresponding to 3~4mW on the OMC, I expect 20uW transmitted when the OMC is locked and well aligned.
It is probably tough to find.
We might just barely be able to see this beam with a CCD + zoom lens. Otherwise, we need to rely on increasing the input power to 10W.
Dan, Koji
After Jim finished working on the seismic platform, we checked the HAM6 electronics for ground loops. We re-discovered the grounding of the beam diverter shields in the vacuum, and found another short on the shield for the ASC-AS_C QPD. The beam diverter grounds appear to be due to the cable connector on the diverters themselves, and I think I recall that we essentially resigned ourselves to living with them. Koji fiddled with the cables and the connectors for the AS_C QPD and the ground loop went away; all of the ISC and tip-tilt connections to HAM6 are free of grounding issues. (We did not check the OMC SUS cabling, should do this tomorrow.)
Once we finished with the ground loops we checked the dither for the OMC PZT was functional. We set the dither frequency at 3.3kHz and toyed with the amplitude while trying to understand the LV readback on the OMC control screen. The numbers didn't make much sense to us (we need to understand what's going on in the PZT driver board), but we verified that there was a signal coming out of the driver board and going into the vacuum. Tomorrow we will try to lock the OMC.
When we looked at the low-voltage PZT drive with an SR785 we immediately noticed an 8Hz comb in the spectrum, which has been observed previously at LLO. The comb is mostly at high frequency and seems to depend on the amplitude of the drive, but it's loud and messy and it's on the DAC input to the PZT driver board. The attached plot is an amplitude spectrum of the signal from the AI chassis on the input to the driver; note the units are in amplitude, not amplitude spectral density, because we were trying to understand the calibration of the digital controls. The amplitude of the dither in the plot may be much higher or much lower than what we ultimately use to control the OMC; at LLO they use 0.3V but we don't yet understand the calibration of our input signal. An oscilloscope trace of the signal leaving the PZT driver and going into the vacuum looks very noisy, with many periodic sharp glitches of ~1microsecond duration that are presumably the source of the comb in the frequency domain. (Note: the comb is also visible in the LV readback of the PZT drive, using DTT.)
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.
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.
K. Venkateswara For the skeptical, here's a rough order of magnitude calculation of the deflection: The angular stiffness of the flexures = kappa = I*(w_0)^2 = 0.59*(2*pi*8.8e-3)^2 = 1.8e-3 N m. The torque on the balance due to me standing a distance of ~2 m is Tau = (G * M1 * M2/R^2) * Lever arm * sin(angle) ~ 6.7e-11 * 2 * 70/2^2 * 0.4 * sin(arctan(0.5/2)) which gives torque Tau ~ 2.3e-10 N m The angular deflection is simply Tau/kappa ~ 0.1 microrad (=100 counts), which is roughly what we saw.
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 N2 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.
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.
J. Kissel, J. Worden John called and suggested we reboot the FMCS machine in the back of the control room. After 20 minutes of windows updates, I was able to log back in, but the status of the X-end did not change. We're both unsure if there's any program to be restarted, but John thinks not. The in-vacuum components (SEI / SUS), nor to the ground instruments (T240 / BRS / PEM) and other PEM instruments show no sign of bad news, and the vacuum pressure looks reasonable, so we assume this is just a failure of the readback system. John will look into the problem when he's back in on Friday.
This is a known issue with the network hubs that are used in the mechanical room to connect the FMCS controller to the network (along with a couple other systems); they are flaky after power outages, and just in general. In this case, I changed out the hardware since it's been flaky over the past few days and the usual power on/power off thing didn't clear it up today. The long term fix is to pull more cable so that these things can be directly connected to a real switch. P.S. Only the vacuum system shares any common infrastructure with FMCS - the operation (or non-operation) of any 'fast' front end EPICS system is not a useful indicator for problems limited to either of these (vacuum/FMCS).