8:38 am, David H. to CS VEA, Hartman table work.
8:53 am, Betsy to CS VEA, looking for parts.
9:00 am, Richard, Rai and Filiberto to Y-End VEA, ESD testing.
9:30 am, Keita and Daniel report a moth problem at X-End Station, no success on trapping the insects.
10:05 am, Cyrus and Adrian to Y-End VEA, upgrade CDS computers.
10:35 am, Bubba and crew CS VEA, remove HAM arm from HAM5 north entrance.
10:45 am, Betsy to CS VEA, West bay area looking for parts.
11:45 am, Cyrus and Adrian to Y-End VEA, install mice on CDS machines.
1:29 pm, Richard, Rai and Filiberto to Y-End VEA, ESD work.
2:47 pm, Received a call from power company, power glitch/outage on grid, reported to Richard M.
3:10 pm, Filiberto moving ESD test equipment from Y-End station to X-End station.
3:30 pm, Cyrus and Adrian to H1CER, upgrade CDS computer.
4:15 pm, Kiwamu to Y-End VEA, checking laser status, no light.

Did the same thing as X (3Hz injection to ESD each quadrant, with various offsets in DC and quadrants, measured Oplev response). And it didn't make sense (first attachment), nothing looked like a nice simple function of voltage difference.

That's until you notice that at least UL, UR and LR behave as if the bias voltage stayed the same for the entire measurement. In the second plot, I used the same data as the first one but assumed that the bias stayed at zero volt, and you see that UL, UR and LR looked quite nice. The only odd thing is LL.

So I assumed that LL was somehow cross-wired to the DC bias. I give LL -377, 0 or 377 volt, and repeated the same measurement (I used "DC" as a replacement for LL).

This time it makes much more sense (3rd plot). Comparing it with X ESD, assuming that the oplev sign convention is the same for X and Y (which should be the case), the conclusion is that:

1. LL is connected to the DC bias.
2. DC is connected to UR.
3. UL is connected to LR.
4. UR is connected to UL.
5. LR is connected to LL.

Or, if the oplev sign for P is the same but Y is the opposite of EX (which should not be the case)

1. LL is connected to the DC bias.
2. DC is UL.
3. UL is LL.
4. UR is UR.
5. LR is LR.

Anyway, the effective bias voltage etc. are:

Seems like the slopes are about the same as EX though DC is somewhat weaker.

Also, DC has a crazy offset which, if due to the charging, is equivalent of -842V (PIT) and -460V (YAW).

I manually measured the equivalent bias voltage of ESD caused by the charging for ETMX by looking at the oplev.

I changed the bias voltage (-377V, 0, 377V) and measured the transfer coefficients from the drive to the quadrant to the oplev at 3Hz.

In the case of UL and LL, I also put some offset in the quadrant output so I have a larger dc voltage difference between the bias and the quadrant.

As you can see, though it's not a perfect line as you can see in UL and LL, it looks very reasonable in that the absolute value of the slope of four quadrants are quite similar, plus PIT/YAW makes perfect sense.

The effective bias voltage obtained from PIT data and YAW data are different because it is dependent on where the charge is.

For each quadrant I fit the three data points that correspond to no offset in the quadrant itself and obtained these:

I found ETMY-ISI drive going up to huge numbers with the masterswitch off. Nothing was going out to the DAC since the masterswitch was off, but the Guardian should have turned the ISO loops off to prevent sending a big kick into the ISI when the master switch is turned back on. Jamie is going to provide a fix for this: The ISI will go into the "Offline" state, and turn back on from there, anytime its masterswitch is truned off.

As a side note, we should not turn the ISI off using the masterswitch while it is running. In this situation, the "Offline" state should have been requested from the ISI's Guardian menu.

Daniel and I restarted green WFS effort.

WFSA and WFSB were rephased using an injection into PDH CM board. Apparently somebody tried to compensate the signal differences across the quadrants when doing a similar injection as mine, and I followed that same path such that seg1 and seg3 are matched as well as seg2 and seg4.

Then I dithered PZTs at 2, 8, 11 and 13.5Hz to measure the sensing matrix, inverted the matrix, and put them in the input matrix, such that WFS_DOF3 becomes PZT1 and DOF4 PZT2. Note that both WFSs are much more sensitive to PZT2 than PZT1.

I didn't put any filter in DOF3/4 nor IP PITOFS and IP YAWOFS, but set the gain to some negative numbers.

In the input matrix of QPD alignment servo, I added a straight-through matrix to add the WFS signal.

I had a hard time working with state definition thing and maybe the guardian, so I still don't know if it works or not, but the intent is to do a high BW feedback to the PZT.

Cyrus, Adrian

We've changed the OS on the workstations at EY (eyws0, wyws1) from Mac OS to Linux, matching the current setup at EX (now that the bugs seem to be mostly worked out).

(John W., Gerardo M.)
The cold cathode was turned off in an attempt to extend its life.
Pressure before turning it off was 6.10x10^-05 torr.
The CC will be turned on and reading will be posted to keep track of the pressure.
However the CC will be off over the weekend.

Minutes taken by Corey G.

alog down
TCS:  have light on cameras, hartman work this morning & laser hazard in afternoon

HAM4
OFI:  installed & roughly located
Apollo:  request to remove HAM4 installation arm when convenient
Baffle installation remains
SEI:  balanced, may be unlocking HEPI soon

HAM5
sei awaiting final payload

HAM6
sled work in Optics Lab
will be Laser Hazard intermittently

ACB finished yesterday, will start CPB

Apollo:  HEPI plumbing

EY ESD testing (swinging etmy) this morning Rai/Richard/Filiberto

ISS PD Array cont. (Peter King)

model restarts logged for Wed 21/May/2014
2014_05_21 12:44 h1fw1

unexpected restart of h1fw1

Greg/David/Thomas

HWS 
- continued with alignment, position detectors were aligned using retro-reflected 532nm beam. 

TCSX
- had been running since Monday am, turned off for a couple of hours this afternoon to re-route some water lines to allow the FLIR camera, screen and enclosure to protect the camera to be positioned on table. 
- FLIR camera connected up using laptop and the camera side of the screen was imaged.
- Monitoring beam alignment was adjusted to centre the beam on this screen. Images taken and CO2 power onto this screen was slowly increased using rotation stage. Up to ~0.5W was projected onto this screen. Attached images show zero incident power (beam dumped but laser on), and ~500mW of incident power. 

I've again redlined D1001132 and added this to the DCC Record.  Again, balanced, floating(unlocked or off the 'stops') with C3 covers pulled back from OT for TFs.  HEPI remains locked.

9:45 Jason HAM6 picking up IAS gear  done 10:45
10 Corey in LVEA looking for IO stuff
10:15 DaveH to HWS HAM4 
10:15 JeffB to HAM5 
11:15 Travis to LVEA Test area
12:00JeffB out of LVEA, OFI installed
12:00 DaveH out of LVEA
12:45 LVEA transitioned to laser hazard
12:45 Karen to EY, back 14:30
13:15 MikeL to LVEA with small tour
13:15 DaveH to LVEA TCS tables
13:30 Travis to LVEA working on ACB
13:30 Mitch and Scott to LVEA looking for 3IFO parts
13:30 TVO Hugh to HAM4 and HAM5 to install oplev parts out at 16:00
13:30 JeffB and Andres to HAM6 to clean up out at 15:30
13:45 JustinB and DanH to LVEA and optics lab
14:45 TVo to LVEA TCS table

Just to compare what was posted at LLO yesterday https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=12702.
I ran 128k 3Hz sinewave to each quadrant with -125k bias on the DC and looked at the responses.  The good news is it actually responds.  The bad new it trying to make it respond to sensible signals like a pitch or a yaw does not yield much in a way a results.  I am sure Keita will have more to say.  But attached are our results of a 3Hz injection

Hugh, Thomas

The in-chamber optics are installed but not aligned yet, when the optical lever components on the outside of the chamber and the viewports are installed we will do the alignment portion. 

Dave and I fixed up the method by which the sitemap is opened today, fixing the problems we've been having with openning guardmedm guardian controls screens.  sitemap is now a script that should be in the path of all users (currently stored at /ligo/apps/linux-x86_64/utils/bin/sitemap).  It works from the command line, and menu bar launchers.  All other references to any other method of openning sitemap should be purged.

All sitemap calls should now also reuse ("-attach" to) the same MEDM session.  If a sitemap is already running, it should raise the already running session.

Andres R., Gerardo M., and Jeff B. 

   The OFI suspension was installed into HAM5. No problems were encountered during the installation.  

Measurements on lower stages (M2-M2 and M3-M3) of SRM succesfully completed yesterday night. The transfer functions are showing a good match with the model (plots pending).

Chris, Kiwamu, Lisa, Stefan

After the 45MHz 12.6dB boost this morning we recommissioned the interferometer:
- We realigned the whole interferometer.
- We added ND0.4 filter on REFLAIR_A to avoid saturation.
- We adjusted gains and phases to match REFLAIR_A_RF45, REFLAIR_B_RF27 and REFLAIR_B_RF135.

- First we tried approaching the fringe from the left side. We were hampered by weird demod phases in RF45, as well as the appearance of a resonance in transmission of the y-arm. This probably is the 20 mode of  the 45MHz.
- We then decided to approach from the right side of the fringe. There REFLAIR_A_RF45 had the same demod phase as PRMI only.
- We acquired 700 red Hz off resonance.
- We decided to use both its I and Q for PRCL and MICH, because they looked cleaner at low frequency.
- We transitioned at 700 red Hz to RF135.
- We needed the following settings:
   REFLAIR_A_RF45  147deg (same for PRMI, and with arms)
   MICH GAIN 1.2 (UGF 6Hz), PRCL GAIN 0.8 (UGF 25Hz)
- Next we started walking in. We needed to update the REFLAIR_B_RF135:
    73deg (PRMI),
    58deg (1kHz offset),
    51deg (and MICH GAIN from 1.2 to 1.0)(450Hz CARM offset)
    42deg (250Hz CARM offset)
    unlocked at 75Hz (up to 1 in ETMY transmission)
- Next attempt identical, but no unlock
    40deg (160Hz CARM offset)
    At 125Hz CARM offset we noticed that only the y-arm was building up, so we fine-tuned the DARM offset until the arms were symmetrical.
    37deg (60Hz CARM offset)
- Then we marched across the river.

Some observations:
 - We had ad least a factor of 10 buildup. We should get more, but we were still moving across the fringe rapidly.
 - We looked at REFLAIR_A_RF9 but it was puzzling: only a large offset in I.
 - We then tried a pure DARM fringe offset, but this made the 3f signals flaky.
 - The 3f signals were fine across the resonance.