This afternoon Andres and I removed the H1-Pr3 and H1-PRM HAM suspensions from their storage containers and placed them on the chamber-side optics table in the LVEA. No problems were encountered during the move.  

I needed a little hardware for the dial indicators for BSC1 and I had to rob from BSC6.  The two western DI trees are no longer engaged but the East side has three axis monitoring still on both corners.  And of course there are still the HEPI IPS.
Before disconnecting the west side, I recorded the indicators and comparing to my last recordings, they are still reading valid.  I see a coherent rotation of about 0.1mrad clockwise wrt the readings I logged on 30 Aug.  The vertical readings are unchanged.

For new shells started after 12:03 PST, the default nds server has been changed to h1nds0.

Installation of last Custom Wedged Viewport VP2 to IO Septum (between HAM 1 & 2) completed with Apollo.
Wedged VP orientation was with the thick part of wedge (scribe mark on flange) to 3:00 O,clock position so deflection is horizontal in nature.
HAM1 can now be isolated as needed.

The IR beam was successfully aligned from the PSL to HAM2, through the IO periscope, off 2 steering mirrors, and through MC1 to HAM3.  In HAM3, we discovered that MC2 has FC, which precludes bouncing a beam back to HAM2.  We aligned the beam to MC2, explored some options for continuing to work, and then called it for tonight.

Attached are plots of dust counts > .3 microns and > .5 microns in particles per cubic foot from approximately 6 PM Nov. 14 to 6 PM Nov. 15. Also attached are plots of the modes to show when they were running/acquiring data.

The sensor may be failing in the dust monitor in the optics lab (H0:PEM-LAB_DST1). The calibrate failure alarm is being raised momentarily (status of 1 in attached plot).

Dust monitor 4 in the LVEA may have been turned off after the cartridge install. It was in the clean room over the test stand farthest from the Y manifold.

I continued the build of the SUS frontend for ITMY (h1susb123). Richard resolved the SFP timing issue this morning and the IOP model has been running all day. I built the h1susitmy model by copying the H2 model this afternoon but then found that the H1.ipc IPC file has exceeded the 64 Dolphin channels limit. It exceeded it some time ago when EY was copied over to H1. So I have put a halt on ITMY development until we can get this resolved. I have taken out the ITMY IPC channels from H1.ipc and stopped the h1susb123 models for now.

Noted that the computer time was about 4 minutes fast, investigated, found ntp had not been installed on h1dmt0.  Installed the ntp package, configured, set the date, and started the ntp client.

Michael R. and James B. fixed one of the cameras in the H1 PSL enclosure.
James B. moved the H1ECATC1 computer to a different rack in the MSR. I shutdown and started it, including the TwinCAT PLCs and EPICS IOCs.
The ITMY cartridge was moved from the test stand to BSC1.
Michael R. transitioned the LVEA to laser hazard to allow PSL light into HAM1, HAM2 and HAM3 for the first attempt to flash the MC.
SKi and a visitor worked on the FMCS system.
Joe G. worked on the IOT1 table.
Keita and Kiwamu worked on deinstalling a PZT controller at end Y.

Dale documented so I'm sure he will have some video/photos available soon.
So real issues other than a waiver on a torque wrench use.
Flying weight was 9440lbs less the 440lbs of the Tri-Lifter for an even 9000lbs Cartridge.  There was no Keel or Stage1 Vibration Absorber mass which totals 600lbs plus 60kg.  We'll be adding that to the Assembly next.
Thanks to JimW MitchellR Zac & Scott, Randy Bubba & Jody too.

John took the attached RGA scan of the Y-end station today using the iLIGO RGA (not Rai's hydrocarbon RGA)

I've laid out most of the components on IOT1 table including partially setting up the periscopes. The components for the MC REFL path are in roughly the correct position. The components for the MC TRANS path will need to be adjusted for the final periscope location. I looked into using the round periscope that is currently sitting in the MC REFL path and determined that it may be necessary to make some modifications to the design in order to adapt it for use with 2" optics. I've set up the triangular MC TRANS periscope for use with the new 2"optics. 
I cleaned everything that was installed on the table and left the HEPI fan running.

The table currently requires the following items.

1) 4" Holes cut in end panels for venting
2) 45 degree mounts purchased for lower periscope mirrors to mount to table
3) Adaptation of round periscope for 2" optics?

ChrisM, HugoP,

Locked HAM3-ISI so Chris could do alignment work this afternoon. I showed Chris how to unlock so he can do it once he is done.

After some spectacular detective work by Anamaria back in September, she had identified a bug in 
${SusSVN}/sus/trunk/Common/MatlabTools/TripleModel_Production/generate_Triple_Model_production.m
(the function used to generate all models of triple suspension [HSTS, HLTS, BSFM] dynamics, both damped and undamped) in which the connection matrix -- used to close the damping loops around the undamped state space model -- had double-counted the index of the input and output ports, effectively closing the damping loops around the M2 (Middle) stage instead of the M1 (Top) stage. This, as she said: "[...] made some of the [transfer functions] look believable [namely, the diagonal TFs], while some of the cross-couplings were obviously wrong (when compared to the undamped case). This [...] also explain[ed] why we needed a strange gain fudge factor to make the Qs [match measured data]."
As of the entry in September, Anamaria had fixed this bug [though added some other hard-coded stuff, which makes the script only valid for HSTSs for the time being].

Since I wrote these functions, I have always had similar problems with predicting reality on the QUADs. Because the Triple function was a copy, paste, and reduction of the similar function for the QUADs,
${SusSVN}/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/generate_QUAD_Model_production.m
written by the same jerk (i.e. me), I suspected this same subtle bug was present. 

Today, I looked, and *BUHZINGA*, the same bug.

As of this entry, and SusSVN rev 3738, I have fixed this bug in the QUAD function. Please update the following corner of your local SusSVN repo:
${SusSVN}/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/
(Note that you'll receive some other updates as well, but no other changes are substantial.)

I'll now work on comparing it with measured data, but I assume it will work out nicely.

Other notes:
- This does not affect any previous *undamped* modeling results, this bug only manifested itself on *damped* model predictions.
- Attached is comparison of select transfer functions between various stages produced by the buggy model ("OLD," solid lines) and fixed model ("NEW," dashed lines). One can see, as Anamaria had described, that most diagonal degrees of freedom (highlighted with thicker lines) are not terribly different [just some subtle changes in Q of the given resonances], but the cross-coupled transfer functions (thinner lines) are significantly different. OK, maybe the plots are too busy to actually see, but take my word for it.
- The default damping filters used by the model are identical to those used for the H2OAT, but the gains are not well-matched. So, although this gives a *better* prediction of the damped QUAD dynamics it does not yet exactly reflect reality. More updates to come after comparing with measured data.

Uninstalled one of two Mad City Labs PZT controllers and the PZT connected to it on the EY ALS table.

The driver is a fanless Nano-Drive (not Nano-Drive 85 with a fan) which is at the bottom of the overhead rack. The PZT is the one with 1" mirror close to the Faraday. These are sent back to the manufacturer.

Before pulling the PZT out, we restored HEPI, ISI, EY and TMS suspension so that everything is at roughly the right angle, injected the green beam, enabled the QPD centering servo so the beam hits the center of green QPDs, confirmed that the beam retroreflected by EY was coming back to the table, held the output of the PZT output and turned the servo off, and marked the beam path using irises. This will allow us later to reinstall the PZT without losing the input pointing.

For future reference, here is the cable numbers on the front panel:

X (PIT) cables:

WBSC6-RF28-1: Input X

RF29-1: Sensor X

RF29-2: HV/10 X

Y (YAW) cables:

RF28-2: Input Y 

RF29-3: Sensor Y

RF29-4: HV/10 Y

X and Y DB9 cables are connected to the X and Y feed through on the ALS table.

The mirror was dirty (some pictures to be attached later). Most of them went away with a gentle wiping, but some big ones persisted. Also, we couldn't find any obvious way to remove mirrors. It seems as if it was glued, so we're sending it back to the manufacturer with the mirror.

I installed modified IOP models for the three LVEA test stand front ends: h1iopsusquadtst, h1iopsusbstst and h1iopseitst. I completed the H2 to H1 renaming and added user switches to enable and disable the watchdogs via EPICS records. The WD MEDM screen was changed to include the WD control buttons.

We started up the H1 BSC1,2,3 SUS frontend for the first time (h1susb123). I created an IOP model with SUS Watchdog for the ITMY and BS top OSEMS.

Attached are plots of dust counts > .3 microns and > .5 microns in particles per cubic foot from approximately 7 PM Nov. 13 to 7 PM Nov. 14. Also attached are plots of the modes to show when they were running/acquiring data.

[Paul, Giacomo]

After moving the HAUX on the HAM table, we observed an overall reduction in OSEMs open light values (OLV), with relative changes spanning from a few % increase to up to almost 30% decrease (see entry 4603). This triggered the need for some debigging, that is summarized here.

First of all, we discovered that there was an error in the out of vacuum connections: as a results, different electronics channels were reading different OSEMs, making the measurement not directly comparable with the ones taken chamber-side (channels and OSEMs have all different "gains", so when you change the pairing...).

Once proper connections were restored we took a series of OLV measurements in which each OSEM of a single HAUX was read by each of the same HAUX's electronic channels. Nothing magic in this particular combination, just a way of having an "OSEM vs channels" matrix to use for some statistics. We obtained a matrix like the following for each suspension:

As we wanted to calculate a sort of "gain" for each OSEM, independent from the channel it was connected to, we proceeded as follows:

- took the OLV reading of UL_OSEM with UL_CH, and divided it by the average OLV read by UL_CH on all 4 OSEMs (same row)

- repeated the above calculation using UL_OSEM and LL_CH, UR_CH and LR_CH

- averaged these 4 values (same columns) to obtain the "gain" for the UL_OSEM

We repeated the exact procedure for all 4 OSEMs of a single suspension.

We then calculated a "gain" for each channel as well, using the exact same procedere but swapping rows with columns. The following table reports the OSEMs and channels "gains" calculated this way (the full set of data is available in the attached pdf):

From this table, the channels seems to have very consistent "gains" (to within a few percent). The OSEMs show somehow more variability, as probably expected. particularly "bad" is the spread in the IM1 OSEMs...

As of now, the OLVs are as follows (with the "Aug-12" column reporting the values read in august during chamber-side testing):

Overall, there is a reduction in the 5-10% range, maybe due to increase resisitance in the new cables (as observed by Jeff in entry 4541); I don't have the data for the previous and current lenght and/or resistance of the cables, so I cannot confirm this.

In addition, IM1_UR and IM3_LR both show a reduction significantly bigger than the others (and the lowest absolute OLV values); also, for some reason they were reading even lower values (by about 10-15%) during the OLV matrix measurements than reported in the above table. A closer look at the recorded data (see attached png) shows that the change happened "during" the OLV matrix measurements: they were both reading about 20k before the OLV matrix measurement (also taken as the first value for the diagonal elements in that measurement); after being disconnected and reconnected several times, they were put back in their original positions and the readings increased to about 22k. The reason for this is unclear and may require further investigation.