Vincent finally made the HEPI and ISI behave, but I had a hard time realigning. TMS has a rather large offset in PIT which seems to be caused by HEPI incident.

Anyway, in the end I started over from scratch, centering on ITM using TMS and baffle diodes.

PD1 max (28500 counts) : TMSP=-92313, TMSY=26574

PD2 max (29300 counts): TMSP=-922420, TMSY=11355

PD4 max (29200 counts): TMSP=-54958, TMSY = 11817

I took the mid point of PD1 and PD4 and set TMS offset to (p,Y) = (-73636, 19196).

I used manual alignment followed by tdsdither to obtain this:

ETM: (P,Y)=(-3028.634, 5409.607)

ITM: (P,Y) = (5771.803, 761.433)

REFL_B_PWR went up to about 8100 counts, which is really good (remember, we inserted 10% pick off for WFS, which means that 8100 counts is equivalent of 9000 counts before the change).

However, WFS refuses to work. PIT just goes away even if I reduce the gain considerably. In an attempt to center WFS, one of the picos on the table might have dropped. I haven't looked at the table yet.

I'll leave it WFS-less for now.

Attached is the calibrated spectrum as of now (references are from Aug/25 (blue) and Aug/22 (green), respectively). Somehow 1/f-ish noise between 1 and 20Hz increased, though low frequency noise is good.

The file is here:  /ligo/home/controls/keita.kawabe/OAT_2012/length_example_20120905.xml

The differences between now and then are:

1. Sensor correction is on now.

2. VCO to HEPI relief is off now because Vincent wanted to leave it that way.

3. Alignment is different (HEPI didn't go back exactly to the original position and relatively large realignment of cavity and TMS was necessary).

4. WFS path is different now though WFS is off.

I haven't checked the refcav status except that it is locked.

Attached are plots of dust counts > .5 microns in particles per cubic foot. Also attached is a plot of the mode of dust monitor 9 in the LVEA (in the clean room over HAM1 and HAM2) to show when it was started. The first initial spikes may be from my testing it (rubbing gloves, frock over it).

[Michael Rodruck, Alberto]

We continued the work started yesterday to pickoff the PSL reference cavity transmitted beam. We installed a PCLX-386.3 CVI lens ( f~750mm) between the two steering mirrors that we had already placed yesterday. The lens is to mode-match the beam into the fiber.

Initially we aligned the fiber coupler by using the guide beam provided by an OzOptics fiber-coupled laser. Then we improved the alignment by monitoring the power transmitted thorugh the coupler's pigtail.

The power coupled into the fiber is now 3.0 mW, which is more than 50% of the 5.5mW coming from the refcav and also more than twice the power that we currently couple into the fiber in the optics lab.

We also installed a flange on the PSL table with fiber connectors so that we can easily plug-in the new long fiber to the optics lab that is going to be installed tomorrow.

	The broken magnets on H1-PRM have been replaced and the suspension has been realigned. The first transfer functions showed rubbing. We found the upper right M2 magnet rubbing on the flexi circuit in the AOSEM. We rechecked and adjusted as necessary all remaining OSEMs, and reran the transfer functions. They did not look good, but there were assembly activities underway in the staging building. I will rerun the transfer functions tonight when the building is quiet.    

[Alex, Cheryl, Deepak, Giacomo]

Yesterday, all ECDs have been set in place (position "2", i.e. 2 x 0.025" feeler gauges between magnet holder and bracket).

DC pitch of all optics has been set to 0 +- 0.5 mrad, except IM4 (set to pitch up by 4 +- 0.5 mrad).

All OSEMs have been centered, with the connectors (and the LED-PD line) in vertical, away from the optical axis. Although their relative position to the optic moved by some 50 um when we moved the suspensions in different positions on the table, clamped them and put the barrel on, all OSEMs can be set to read less than about 10 um by applying suitable offsets (basically showing that the "butterfly misalignment" is of this order). See data just after 17:45 local time on September 4.

We took TFs between about 6:00 and 7:30 pm yesterday, OSEMs' offset set to keep them centered and minimize non-linearities. Then left the suspensions undamped (but with offsets on) for the night. TFs and PSDs starting at 10:00 pm last night are attached.

Today I have spent most of the day trying to do a ringdown measurement on bounce, roll and transverse. I drove the "butterfly" mode at the frequencies previously measured for this mode, exploiting the parasitic coupling to excite them. I was able to excites all the modes, but I haven't had time to analyze the data yet. This are the relevant times for the excitations:

2012-09-05 12:28 Switching on "butterfly excitation" on IM1 and IM2. Amplitude = 10000 (per coil), frequency matching the measured one for bounce.

2012-09-05 12:50 Switching off excitation. Let it ringdown...

2012-09-05 13:57 Switching on "butterfly excitation" on IM3 and IM4. Amplitude = 10000 (per coil), frequency matching the measured one for bounce.

2012-09-05 13:19 Switching off excitation. Let it ringdown...

2012-09-05 13:32 Switching on "butterfly excitation" on IM1 and IM2. Amplitude = 10000 (per coil), frequency matching the measured one for roll.

2012-09-05 14:15 Switching off excitation. Let it ringdown...

2012-09-05 14:25 Switching on "butterfly excitation" on IM3 and IM4. Amplitude = 10000 (per coil), frequency matching the measured one for roll.

2012-09-05 14:47 Switching off excitation. Let it ringdown...

2012-09-05 14:55 Switching on "butterfly excitation" on IM1 and IM2. Amplitude = 10000 (per coil), frequency matching the measured one for trans.

2012-09-05 15:22 Switching off excitation. Let it ringdown...

2012-09-05 15:30 Switching on "butterfly excitation" on IM3 and IM4. Amplitude = 10000 (per coil), frequency matching the measured one for trans.

2012-09-05 15:50 Switching off excitation. Let it ringdown...

After the last measurement we removed the barrel and moved the HAUX in the middle of the table to make some space for HxTS testing.

Modifications to the old enclosure on the 'SMART TABLE UT2' in the LVEA laser lab area are complete (see picture 1). There were several components missing on this enclosure when I arrived that could not be located which I borrowed from the enclosure currently on the IOT1 table (bottom of the two stacked enclosures). These include angle brackets, 3 panels, and some panel bolts. 
This newly modified enclosure will serve as that for IOT1.

The new 3' x 5' table, legs, and enclosure to serve as IOT2 have been assembled and is resting outside of the LVEA laser lab area. I noted that the new enclosures do not include the cable tray system that is being installed on the modded enclosures. I used the cable tray system intended for LIGO India's IOT1 enclosure and modified it to fit in the IOT2 enclosure. 

I unpacked and stowed the Light Pipe assembly inside the IOT2 enclosure awaiting install.

Valved-out aux. cart for overnight -> Will valve-in and continue tomorrow.  I expect the ion pump to come on scale after a day or two of this.

Foton GUI quietly discarded (some of?) notch filter definitions and replaced them with a flat gain of 1.

This is easily reproduced by first opening e.g. /opt/rtcds/lho/h2/chans/filter_archive/h2iscey/H2ISCEY_120828_143926.txt and saving it to some other file, e.g. test.txt, and take a diff (attached).

Probably because of this bug, all WFS notches are gone from current H2ISCEY filter file.

This is extremely worrisome.

Noisy day, use of crane and forklift, lots.

• Apollo moved clean room over to BSC08.
• Removal of HAM01 West door, Hugh R. Corey G
• Keita K. visited Y-End station lab.

I have generated Fscans for many of the SUS, ISI, and PEM channels
listed here,

https://wiki.ligo.org/foswiki/bin/view/DetChar/OneArmTestLineInvestigations

Especially over the weekend I finished generating Fscans during
significant lock stretches ending on August 22, 25, 28, and 31.

You can find the SUS, ISI,and PEM Fscans respectively here:

https://ldas-jobs.ligo-wa.caltech.edu/~pulsar/fscan/H2_OneArm/H2_OneArm_SUS/fscanNavigation.html

https://ldas-jobs.ligo-wa.caltech.edu/~pulsar/fscan/H2_OneArm/H2_OneArm_ISI/fscanNavigation.html

https://ldas-jobs.ligo-wa.caltech.edu/~pulsar/fscan/H2_OneArm/H2_OneArm_PEM/fscanNavigation.html

Click on a date and then the channel name to get the Fscan plots and links to
the data files.

Note that the PEM Fscans also include the length sensing channel, e.g.,
H2:ALS-Y_ARM_LONG_IN1_DQ.

For those that mine the Fscan data, from the cluster at LHO look for the
data files respectively under,

/home/pulsar/public_html/fscan/H2_OneArm/H2_OneArm_SUS

/home/pulsar/public_html/fscan/H2_OneArm/H2_OneArm_ISI

/home/pulsar/public_html/fscan/H2_OneArm/H2_OneArm_PEM

Finally, the Fscan plots do not appear for some SUS channels, because
they were all zeros. Specifically, for Aug. 31, I find these channels
were all zeros:

H2:SUS-ETMY_L1_MASTER_OUT_LL_DQ
H2:SUS-ETMY_L1_MASTER_OUT_LR_DQ
H2:SUS-ETMY_L1_MASTER_OUT_UL_DQ
H2:SUS-ETMY_L1_MASTER_OUT_UR_DQ
H2:SUS-ETMY_L2_MASTER_OUT_LL_DQ
H2:SUS-ETMY_L2_MASTER_OUT_LR_DQ
H2:SUS-ETMY_L2_MASTER_OUT_UL_DQ
H2:SUS-ETMY_L2_MASTER_OUT_UR_DQ
H2:SUS-ETMY_L3_MASTER_OUT_LL_DQ
H2:SUS-ETMY_L3_MASTER_OUT_LR_DQ
H2:SUS-ETMY_L3_MASTER_OUT_UL_DQ
H2:SUS-ETMY_L3_MASTER_OUT_UR_DQ
H2:SUS-ITMY_L1_MASTER_OUT_LL_DQ
H2:SUS-ITMY_L1_MASTER_OUT_LR_DQ
H2:SUS-ITMY_L1_MASTER_OUT_UL_DQ
H2:SUS-ITMY_L1_MASTER_OUT_UR_DQ
H2:SUS-ITMY_L2_MASTER_OUT_LL_DQ
H2:SUS-ITMY_L2_MASTER_OUT_LR_DQ
H2:SUS-ITMY_L2_MASTER_OUT_UL_DQ
H2:SUS-ITMY_L2_MASTER_OUT_UR_DQ
H2:SUS-ITMY_L3_MASTER_OUT_LL_DQ
H2:SUS-ITMY_L3_MASTER_OUT_LR_DQ
H2:SUS-ITMY_L3_MASTER_OUT_UL_DQ
H2:SUS-ITMY_L3_MASTER_OUT_UR_DQ
 

(Bubba, Corey, Hugh)

Once we had access to the forklift & the South crane, the west door of HAM1 was removed.  Risers (vertical spacers) were placed on the Support Tubes, and then the Support Table was brought into the Chamber & lowered onto the Spacers.  3/8"-24 x 3" Ag-plated bolts were then used to secure the Spacers & Support Table on to the Support Tubes. 

We didn't have a torque wrench, but torqued the eastern row of bolts "wrench-tight" (should be confirmed later); the western row of bolts were just hand tightened.  The lifting hardware is still on the Support Table (along with tooling).

Next up, we can begin craning the rest of our iLIGO Isolation Stack hardware over to HAM1 and continue the build-up.

After three different rigging configurations, Bubba and crew were able to pick the short-sided cleanroom out of the south bay. This move took until shortly after 1 pm to accomplish. The crew spent the rest of the afternoon helping Hugh with the door removal at HAM1.

As of now, Foton filter text files for H2SUS ETMY & ITMY are now under SVN control in the "cds_user_apps" repository.  Previously, the text files were written to the "/chans/" directory locally:
'/opt/rtcds/lho/h2/chans/'.

This directory now contains soft-link names "H2SUSITMY.txt" & "H2SUSETMY.txt" which point to the actual SVN-controlled Foton files located:
'/opt/rtcds/userapps/release/sus/h2/filterfiles/'

with the same filenames, "H2SUSITMY.txt" & "H2SUSETMY.txt".  

Edits to these files should be written to the SVN directory (and committed) and NOT to the "/chans/" directory.  Doing so will break the soft-link pointer.

The dust monitor labeled 'B' was installed under the clean room between HAM1 and HAM2 on the west side. It is set at location 9 in the LVEA.

Modifications to the QUAD L1 (UIM) and L2 (PUM) stage CoilOutF filter banks were made via Foton to reflect the latest State Machine Diagrams updated last week.

The changes were saved to the filter text files, and filter coefficients were loaded via the "*_GDS_TP" medm.

The Foton filter text files were committed locally to the "cds_user_apps" Repository checked out under:
'/opt/rtcds/userapps/release/sus/h2/filterfiles/H2SUS*TMY.txt'

After noticing difficulties with untripping the QUAD watchdogs, I realized that a more sophisticated process is required to restore the QUAD status after a watchdog trip now that there are gigantic P and Y offsets on the TOP stage. Bare with me, it's complicated and convoluted because we didn't imagine this scenario while installing the infrastructure, but it's now on the "to-do" list to get it changed / more straight forward in the future.

For now, the process is as follows:

(1) Turn off the master switch.
(2) Untrip any relevant watchdogs.
(3) Change the gain in the P2P and Y2Y DriveAlign matrix filter banks to 0.00 (you can do this from the screen, or since you (currently) need a terminal open for the next step anyways, you can caput / ezcawrite it too). For example, if you're doing ITMY, that's 

]$ caput H2:SUS-ITMY_M0_DRIVEALIGN_P2P_GAIN 0
]$ caput H2:SUS-ITMY_M0_DRIVEALIGN_Y2Y_GAIN 0

(4) Change the ramp time in the P2P and Y2Y DriveAlign matrix filter banks to 10 sec. (The link to the "full" screen is currently broken, so you'll have to do a "caput" or "ezcawrite" or whichever). For example, if you're doing ITMY, that's 

]$ caput H2:SUS-ITMY_M0_DRIVEALIGN_P2P_TRAMP 10
]$ caput H2:SUS-ITMY_M0_DRIVEALIGN_Y2Y_TRAMP 10

(5) Turn ON the P and Y offsets to the desired value (if they're not on already); turn ON the damping loops (if they're not on already)
(6) Turn ON the MASTER SWITCH
(7) Change the gain of the P2P and Y2Y DriveAlign matrix filter banks back to one. Now that there's a ramp time in the signal chain, it'll slowly ramp up the offsets (and the P and Y damping loops), so the watchdogs won't trip.


--------------------------

The items on the "to do list" in order of difficultly/level of hackiness (from easiest / hackiest to most difficult / do-the-right-thingiest)
(1) Fix the DriveAlign Matrix sub-screen such that
    (a) The "FULL" button works, and it opens the full filter bank (may just require an userapps svn up...)
    (b)  Add the TRAMP epics read/write to every element of the the upper level DriveAlign screen-
(2) Update the auto-damping script to include the above sophistication
(3) Offload what offsets you can to ISI and/or HEPI
(4) Make a model change such that the P and Y alignment offsets can be ramped (e.g. make the DCDRIVECAL gain a full filter bank, or add a ramp to the MASTER SWITCH, or something)
(5) Ask CDS to make the cdsEpicsIn block generate a TRAMP channel as well as a value channel on compile.

Garcia has volunteered to take on items (1) and (2) for now.