SEI MEDM screens were all updated (HAM-ISI, BSC-ISI, HEPI) to account for the recent changes in the IOP Dackill channels names.

Displays are fully functional again for both HAM-ISI and HAM-HEPI. (before/after - notes)

BSC-ISI and BSC-HEPI need the IOP DACKILL parts to be updated so channel names match with chamber names, as It is currently the case on HAM chambers. DaveB has agreed to do those changes, and the related model restarts, next week so the BSC chamber IOP DACKILL channels are named as follow:
$(IFO):IOP-SEI_$(IOP)_SEI$(CHAMBER)_DACKILL_STATE, with $(CHAMBER) taking the following values: 'BS', 'ITMX', 'ITMY', 'ETMX', 'ETMY'

Work was performed under DaveB's WP #4672

In preparation for HAM 3 door removal on Monday, I have removed both the camera and illuminator cans from HAM 3 west door.  Gerardo was going to do a viewport inspection thereafter.  The mobility equipment is on a table next to the beamtube between HAM 2 and HAM 3.  Please try not to disturb this table as I have attempted to maintain the camera and illuminator orientation in them.  The table is labeled as such.

J. O'Dell, myself

With Joe's help, we "re-payloaded" the ITMx Quad with sleeve and vibration absorbers to bring it back to ~full weight for HEPI height adjustment.  The chamber has been sealed back up with the temporary aluminum door for cleanroom detachment. 

I've installed wireless APs in both mid stations for the use of the vacuum group and CDS when working with systems there.  They work the same as those in the other VEAs.

Measured the ITMx X, Y, Z position this morning after yesterday's SUS adjustments.  The errors are as follows:

• Longitudinal: -0.8 mm (South)
  • Tolerance: ±3.0 mm
• Lateral: -1.1 mm (East)
  • Tolerance: ±1.0 mm
• Vertical: +4.3 mm (high)
  • Tolerance: ±1.0 mm

I've finished upgrading the camera code on h1digivideo0,1, and 2 under WP 4682.  In addition to the code change, the startup scripts are now handled via Monit which means they can be controlled from the web interface with the link added to the overview MEDM.  The servers will now start all configured cameras at boot as well as the supporting IOC processes, so they are self-sufficient except for needing /ligo to read the camera INI files.  The only remaining work is to re-shuffle the camera assignments to balance them out and make room for new installs, which I'll do after coordinating with Filiberto hopefully sometime next week.

BSC3 HEPI needs to be moved to account for the ITMX height discrepancy
Jason will make a final measurement of the ITMX position first
SUS is missing payload which will need to be accounted for before the HEPI move

bolts have been broken on HAM3
a full cleaning has been done on HAM3, a partial cleaning has been done on HAM2
Travis will remove mobility experiment equipment from the HAM3 west door
plan to pull HAM2, HAM3 doors on Monday

hold putting doors on HAM6 until next week
Robert will be going into HAM6 again today

laser work finished on H1 PSL
frequency servo investigations to be done
planned work in the H2 PSL enclosure

Gerardo looking for washers to finish CPB assembly

Quad install ongoing in the staging building
Scotty cleaning storage can

model restarts logged for Thu 19/Jun/2014
2014_06_19 04:18 h1fw1
2014_06_19 04:26 h1fw1
2014_06_19 08:21 h1fw1
2014_06_19 10:20 h1fw1
2014_06_19 10:29 h1fw1
2014_06_19 11:57 h1fw1
2014_06_19 12:03 h1fw1
2014_06_19 12:15 h1fw1
2014_06_19 12:29 h1iopsusb123
2014_06_19 12:39 h1iopsusb123
2014_06_19 12:48 h1susitmy
2014_06_19 12:49 h1susitmy
2014_06_19 12:51 h1susbs
2014_06_19 12:51 h1susitmx
2014_06_19 12:54 h1iopseib3
2014_06_19 12:58 h1iopseib3
2014_06_19 12:59 h1hpiitmx
2014_06_19 12:59 h1isiitmx
2014_06_19 13:09 h1iopseib1
2014_06_19 13:11 h1hpiitmy
2014_06_19 13:11 h1isiitmy
2014_06_19 13:12 h1iopseib2
2014_06_19 13:14 h1hpibs
2014_06_19 13:14 h1isibs
2014_06_19 14:13 h1iopsusex
2014_06_19 14:17 h1susetmx
2014_06_19 14:19 h1sustmsx
2014_06_19 14:24 h1iopseiex
2014_06_19 15:24 h1hpietmx
2014_06_19 15:24 h1isietmx
2014_06_19 15:29 h1sustmsy

many unexpected restarts of h1fw1, which was fixed by rebooting the QFS server. SUS and SEI model restarts due to new IOP models on those frontends.

After the IOP watchdog upgrades, sus guardians need to be updated. They are all currently in an error state since asking for iop channels that do not exist anymore.

Transfer functions were ran during the day on the OMC in HAM6 in order to check for rubbing before closing the doors. The 6 dofs were tested and compared with the previous measurements chamber side (cf alog 8637). They all agreed perfectly so things haven't changed since then. Attached is the screenshot for one of the dof (yaw) in blue, compared with the previous measurement in black. Dtt files are saved under the svn as :

/ligo/svncommon/SusSVN/sus/trunk/OMCS/H1/OMC/SAGM1/Data/2014-19-06_1000_H1SUSOMC_WhiteNoise_$(DOF).xml
 

Follow up the investigation https://alog.ligo-la.caltech.edu/SEI/index.php?callRep=499
of the glitch present in the H1:ISI-ETMY before the WD trips pointing the ST1 actuator as the cause (Figure 1):

- The glitch spectrum shows that it has a frequency of 10 - 70 Hz, with a peak in 40 Hz. (Figure 2). 
- The L4Cs and GS13s are good sensors for frequencies above 1 Hz, then we may use them for our investigation.
- The ground motion is expected to be low frequency, so the glitch may comes from the ETMY chamber. 
- The transfer function between the sensors and the excitation should be approximately flat.
- For an excitation of the ISI stage 2 in the X direction, the transfer function (TF) and coherence for L4Cs in ST1, GS13s in ST2, and OSEMs in the reaction chain R0 are shown in Figure 3, 4 and 5 respectively. 

Comments:
- Even that the coherence is high, the TF shows a peak near 45 Hz for ST1 L4Cs and ST2 GS13s.

(Betsy, Travis, Joe O)

We spent all day today moving things around in an effort to verify that all 8 of the ITMx QUAD masses, the12 blade springs, and the 20 actuator/sensor pairs were free of mechanical intereference such that we could move on with height diagnostics.  Yesterday, the QUAD was left in a state where there was obvious course yaw to deal with.   Revisiting that today cause the usual QUAD ripple (ha!) effect where were ended up adjusting X, Y, Z, pitch, yaw, roll of many things since many are coupled mechanically.  As I've stated before, it's a painful iterative process to get a correctly pointed, yet mechanically free QUAD.

At the end of the day, we think we have the main chain pointing back down at the IAS station (on beam path-ish) with sneak peaks of healthy PITCH and VERTICAL DOFs.  SO, I deem this good enough for Jason to remeasure and repost X, Y, Z measurements in the morning.  From there, SEI, please adjust HEPI to fix the height error he posts.  Sorry.

I have nothing further to add to the history that Jason posted in an earlier alog regarding where we introduced the 3mm error we seemed to need for the pilot-ITMx but do not need now...

I'll be out for a 2 of the next business days, so my understanding of the events to take place in this chamber are:

- Jason measure X,Y,Z (Fri)

- SEI HEPI height accomodation - few days

-- Meanwhile, Travis "mic the ITMx TM-to-corner cube for Jason's new length assessment now that things have moved in the QUAD (Fri)

-- Meanwhile, Travis/Arnaud sneak peak TFs on R0 just so we know what to expect there for later next week (Fri, time permitting only)

The suspension HWWD ser. no. S1301701 has been installed in the DAQ test stand, and is currently cabled up and running.  It is available for testing.
Note: Initial values for RMS trip point and Time to Trip are 110.1 and 20.1 at power-up.

Jim and Dave.

We revisted the problem of not being able to control the HWWD unit when it is installed at EY, but the same unit works at other locations. We had tried the 4th DB-9 connector of the binary out chassis for both ETMY and TMSY. On the ETMY chassis all ports are used except the 4th, on the TMSY chassis only the first two ports are used. This afternoon we moved the binary out cable to the 3rd port of the TMSY chassis, and it works. We would like to connect the HWWD to the primary model (ETMY), so it would be good to verify the 4th port has a problem.

To perform this test, I modifed the SUS model h1sustmsy and compiled against RCG-branch2.8. The HWWD and SWWD systems are now ready for combined shake tests next week.

I installed the remaining SWWD systems in BSC 1,2,3, EX. This required new models for: h1iopsusb123, h1iopsusex, h1iopseib[1,2,3] and h1iopseiex. All were built against RCG-branch2.8. The SWWD MEDM was upgraded accordingly. All user models on these front ends were restarted to install the new IOP models.

8:15-8:45 Morning Meeting
9:00-9:36 Heading to End Y to get garbs – Karen
9:35- 12:00 Working on ITMx – Betsy, Travis, Joe
9:45-12:00  Heading to EndY to do some installations on Hartman tables – Greg
9:50-10:57 Contamination and Control work in LVEA – Jeff B.
10:35- HAM2/HAM3 cleaning – Christina, Karen, Cris
11:26- 14:04 Work on H1 PSL – Peter
12:04- Rebooting Frame Writer 1 (h1fw1) – Dave
13:24-13:45 Heading into the LVEA to unlock HEPI on ITMy – Jim
13:48- 14:07 Going into the Optics Lab – Jeff B.
14:30- Heading to EndY to remove IO cable from hardware Watchdog – Jim B/Dave
15:50-Going into the LVEA (Giving a tour) - Mike

Related to all of the shenanigans with ITMX, I unlocked ITMY HEPI to see if there were any big shifts after the ITM was re-installed. It has moved around, but not a surprising amount given the changes at the chamber, and similar to ITMX. I haven't looked at the level yet, but after the work at ITMX, I don't see any reason to think it's out of level, yet. Gaps on actuators and IPS's also still look reasonable. 

h1fw1 has been unstable today. At 12:05 I took the opportunity while h1fw1 was down to power cycle its NFS/QFS file server machine h1ldasgw1.

There is a short gap in the frame files from 12:05 to 12:17 PDT.

• Longitudinal: +0.2 mm (North)
  • Tolerance: ±3.0 mm
• Lateral: -0.9 mm (East)
  • Tolerance: ±1.0 mm
• Vertical: +2.8 mm (high)
  • Tolerance: ±1.0 mm

I looked back through my notes of the pilot ITMx cartridge alignment from way back in September 2013 and the in-chamber alignment from November 2013 to see what the history of the height adjustments are with this quad.  The ITMx height on the test stand is set with respect to the ISI table: we attach a calibrated height stick (with attached scale) to the ISI table and use that to set the total station 1742.0 mm below the ISI table; this is the desired distance the center of the ITMx should be from the ISI table.  We then aligned the ITMx in height to this location.  We started low by 1.6 mm, but adjusted to be high by 0.1 mm.  The cartridge was then craned into WBSC3.  I seem to remember Hugh setting the ISI table to its proper height prior to the alignment work (correct me if I'm wrong here Hugh).  I then took the first set of numbers and found the ITMx to be 3.6 mm low.  We still do not understand where this discrepancy between the cartridge alignment, Hugh's setting of the ISI table, and my 1st in-chamber look at ITMx comes from, but I should note that for the pilot ITMx we needed to raise HEPI by 3.6 mm, now for the production ITMx we need to lower HEPI by 2.8 mm; Betsy floated the idea that it is a possibility that the pilot suspension could have been long and the production suspension is correct, thereby causing the required HEPI adjustments.

At Betsy's suggestion I also looked back at ITMy to see if we could be walking into a similar situation with this optic.  This suspension goes all the way back to WBSC8 in December of 2011.  When this suspension originally left the test stand we were 1 mm low.  After the in-chamber fiber break the ITMy was suspended by a wire for the H2OAT.  In November of 2012 this suspension was moved to WBSC1 to be used for HIFO-Y and the most recent integration work.  The ITMy on the test stand before install into WBSC1 had a height error of 0.2 mm low.  Once installed in WBSC1, we began aligning in January 2013; the initial height error was high by 1.7 mm.  We used HEPI to adjust the ITMy height error to 0.0 mm.  This was the last time we looked at ITMy (~18 months).  Looking at the other BSC chamber optics (BS, ETMx, ETMy), they all had initial height errors of <= 1.0 mm, and with the exception of the BS they all started high (BS was initially low by 0.4 mm, so no problems there).  The pilot ITMx in WBSC3 had the largest initial height error we've seen here at LHO, and was 1 of 2 optics to have a negative initial in-chamber height error.

As a follow up to Betsy's log last night, I went out to ITMX this morning to release HEPI and look at actuator gaps. Payload is almost back to full, so I would expect if everything is healthy for HEPI to be pretty much centered. This is what I found, BUT... the vertical stops were all loose, meaning the platform had moved up some. I've also looked at IPS trends and they don't look horrible, reasonable shifts considering I locked with the loops on, a lot of payload came off then back on and we are still light some payload.So, a couple thoughts on what could have happened.

- Basically nothing. The error Jason found is all somehow in SUS. Seems unlikely.

- Some incredibly lucky/unlucky combination of horrible shifts. SUS removed a lot of payload, then pushed up on the platform a lot when they added back. I didn't get a really hard lock on HEPI because I was trying to preserve the aligned position, and it's really hard to reach all of the stops necessary. This means the platform could have moved up, moved the actuators in their mounts (if SUS pushed REALLY hard, seems unlikely) and somehow we have come back down just the right amount for HEPI to look more or less ok. I would expect that if we had come up enough to move the actuators 6mm (presumably when we removed payload or when SUS pushed on the platform with their arm), the platform would come back down and the HEPI actuators would be bottomed out. That's not what I found, so I don't know what's happening here.

Anyway, if Jason finds we are still 3 mm high, it means completely re-doing HEPI at that chamber. We should also re-check the level of the ISI at this point. Will probably also require re-doing some tests on HEPI, that we wouldn't otherwise do.