TMS is hung

Today we installed the fall protection wire and temporary vertical protection bars for the TMS isc table, and removed the Genie, while the cube is still on EQ stops. It went fine.

Originally the temporary protection bars weren't required at this stage, however the new initial alignment procedure the TMS and the intial alignment people have been working on requires that a large target is mounted on the input aperture of the telescope plate. Since this totally changes the balance of the TMS/tele, we needed temporary EQ stops on the vertical protection bars.

Photo 1:  It was difficult to attach our preferred cable into the bottom QPD bracket on the transmon table. (This is for the green QPDs, we think.) We removed the unconnected pins but this didn't help; in the end we switched the cables and things worked ok. (We preferred to use the cable with more slack for the lower connection, but c'est la guerre.) 

Now, the cable arrangement is (photos 2-5): 

Top QPD connector (red QPDs): S1104109
Bottom QPD connector (green QPDs): S1104468

Top ETM-side connector (picomotors): S1104116 
Bottom ETM-side connector (IR beam diverter): S1104114 

These numbers don't matter much in the long run, other than we will take care to plug the other end of the cables into the proper ISC connector on the bracket on the ISI table. (And then check that the ISC cables are connected to the dummy feed-through in the proper way...et cetera, et cetera.) 

Other attached photos: the transmon table is now hanging on its own. Note that since the telescope mirrors are silvered, if you look down the axis of the telescope you can see reflections all the way up to the periscope mirrors. Also, if you look down the green path from the in-air side, you can faintly see a QPD at the other end!

Ops Shift Summary

Replacement of FMCS UNC at mid Y.

BSC 6, gaps under the root of small blades

Jim, Hugo

Issue: 
LLO have a BSC-ISI that is under-loaded by 400lbs. They noticed that its small blades where lifted from their clamp-plates. They measured this gap by inserting shims at the blade/clamp-plate junction. A 1.5 mils-thick shim could be inserted by approximately 18/64” in the whole length of that junction.

Test:
We did the same test here at LHO on BSC6, which is reasonably loaded, in order to help LLO diagnose. The access was limited. Only two blades were tested. They could only be tested along 2” of the junction’s length.

Result:
Observations are the same for both of the blades that were tested. A 1 mil-thick shim could be inserted by approximately 28/64”, and a 2 mils thick shim could be inserted by approximately 19/64”.

Conclusion: 
The gaps measured on LHO-BSC6 are similar to the ones measured on the unit studied at LLO. Hence, the space measured between the blades and their clamp-plates doesn’t seem to be a justification for a BSC-ISI to be under-loaded. 

Suggestion:
Further discussion revealed that our bolts were lubricated before torqueing. Lubrication allows reaching a higher level of compression before tripping the torque wrench. It also revealed that our bolts were torqued to a higher torque value. 

MSR and control room upgrades

H1 front end racks were installed into the MSR and populated with computers. The first two of the H2 racks were installed and have front ends installed except those currently running the H2OAT.

Cleaned up H2SUSITMY.txt filter file

I remotely logged in from LLO and modified the H2SUSITMY.txt file located in /opt/rtcds/lho/h2/chans/ directory, which contains the ITMY suspension control filters.

I removed 4 AntiAcqL1 filters which shouldn't have been there and which may have been installed awhile back incorrectly (possibly by the prepare.m script I've since modified, possibly by someone by hand).

Testing with the current suspension prepare.m script in /ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools does not generate this filter, so future use to prepare filters for other QUAD optics should not have this problem.

I copied the new H2SUSITMY.txt to /opt/rtcds/lho/h2/userapps/release/sus/h2/filterfiles and checked it into the svn.

H2 SUS FMY -- Pre-Pumpdown TFs: Rubbing Badness

I've take new, pre-pump-down H2SUSFMY data, and have identified that the suspended elements are inhibited by some sort of rubbing. Of course, it's too late fix anything now -- at least for the foreseeable future, and we don't need H2 SUS FMY for the single arm. But, it's sad.

See attached comparison between
H2SUSFMY (111114) -- Phase 2C approved Measurement: pre-cartridge install, metal mass
H2SUSFMY (2012-01-09) -- Un-posted Phase 3A measurement: post-cartridge install, taken to be "final," but before final setting of EQ stops (see below). Taken to be measurement that approved the SUS.
H2SUSFMY (2012-02-15) -- Today's measurement, just before pump-down of BSC8.

We initially approved this suspension, post cartridge install with measurements on Jan 9th (no original aLOG posted, but shown in the attached plots).

We neglected to confirm that the dynamics were OK after EQ stops and BOSEMs were set to the "final" values for both BSC8 Suspensions on Feb 01, assuming that moving the EQ stops closer (but obviously attempting not to touch the suspended elements) would not effect the dynamics.

Note, I'm so confident it's EQ stop rubbing, because we had recently decreed (see M1100256) that we need to get the stops 0.75mm +/- 0.25mm away from the suspended masses. The technique for determining this distance is 

(1) Run in all stops until "just touching" the mass
(2) Given the knowledge of the stop's bolt thread, turn out the bolt the number of turns necessary to create a 0.75mm gap. E.g. a 1/4-20 screw (typical EQ stop size) has 20 threads per inch, or 0.05 inches / thread, or 1.27mm / thread. In practice one can get ~1/4-1/2 turn accuracy, or +/- ~0.0.31mm at best.

However, there are several factors further against you while setting these stops: 
- "just touching" the mass, because running stops in is typically done sequentially is difficult to get: one can believe that running the first stop into "just touching" would move the suspended mass by ~0.5mm or more. 
- For a good fraction of the EQ stops, the point of contact is invisible rendering the check of the gap, one they're believed to be backed off at best difficult (say by using a mirror system), or at worst impossible.

Perhaps we need to revisit this decision/requirement again...

HAM ISI Rebuild & Tested #2 in the Can

No production GS-13s on this unit but it does have good parts.  No issues getting it in the Storage Container.

See Jim worry it down into position.

Anyone know why the images aren't working?

TMS tele/ISC-table moved to the test end

We attached the tele/table to the cube under the test end, though the tele/table is still supported by Genie.

Tomorrow we'll fully suspend it.

Roughed YBM with QDP80 for ~7 hours today-will resume in the morning

Kyle, iGerardo

ETMy Test Stand Alignment Progress

D. Cook, J. Oberling, T. Sadecki

• ETMy Pitch: ~662 µrad down
  • Desired pitch of 639 µrad down with a ±100 µrad spec
• ETMy Yaw: ~64 µrad CW
  • Desired yaw of 0 µrad with a ±100 µrad spec

For the ERM we aligned the pitch until the reflection from the ERM was overlapping the reflection from the AR surface of the ETMy.  With this combination together I am unable to get an accurate measurement of the pitch and yaw because the two reflections sway independently, creating an irregularly shaped "blob" on the laser autocollimator (LAC) which is not representative of the pitch and yaw of either surface.  The ERM spec is ±1.47 mrad of differential pitch and yaw between the AR surface of the ETMy and the front surface of the ERM.  With the two reflections overlapping we are well within this spec.  The ETMy and ERM are now aligned and we (IAS) are waiting word from TMS to begin aligning the TMS assembly.

TMS Qube-to-Cartridge Installation (Betsy, Cheryl, Keita, Dan, Craig, David)

The Qube-to-Cartridge Installation was successfull and went pretty much as planned. We were nearly able to get the qube into position using the genie/5-axis table combination, but were a little shy of the back (+Y) leg of the cookie cutter (we used the far cookie cutter option relative to the Quad). Weighing options, we decided to apply the pusher tools to finally adjust the position to the cookie cutter. We then installed all (except one) dog clamps as per D0900419. The small dog clamp which partially wedges between the ISI Table and stage 0 will be attempted tomorrow as we need a short socket and overall 'low-profile' tool set-up for it. We just lacked the short socket.

Now we hope that our position and bearing are just right relative to the ETM. By eye it looks good.
 

plots of dust counts

Attached are plots of dust counts > .5 microns.

ETMy status

For today's TMS activity under the cartridge test stand, I clamped the PenRe (the mass most vulnerable to bumping, yet also the most robust), plut the face shields on the ERM and ETMy, then bagged the suspension.  The main chain is theoretically* hanging free (* the clamping of the PenRe could have pushed a reaction mass into a main mass).  This is how the suspension will remain until further notice, due to TMS installation.

H2SUSFMY ini file restored, data concentrator restarted

At the request of Jeff Kissel, the H2SUSFMY.ini file was replaced with an older one, archive/H2SUSFMY_120211_095125.ini.  A DAQ Reload was performed and the dc0 restarted.  The H2SUSFMY.ini file had been generated with two channels active during the RCG 2.1.4 update.

All H2 SUS restored and confirmed functional

After the timing failure, and subsequent reboot of all H2 frontends, I had to go in and BURT restore all the suspensions. I started off using the previous versions of the _safe.snap files found in
${userapps}/sus/h2/burtfiles/
but as previously reported, they show a red "not ok!" when restored, presumably because they were generated when the DAQ system was at RCG 2.3.1. But again, it seems to restore the EPICs values just fine.

I glanced over H2 SUS ITMY, H2 SUS ETMY, and H2 SUS FMY, made sure all there damping loops were functional, with their BIOS and watchdogs set appropriately (for their given model status -- ITMY is at a newer version of this stuff) and have re-created the follow snapshots, which should be used (for now, until we upgrade ETMY and FMY, and merge the branch-2.4 and trunk of the userapps repo)

H2 SUS ITMY (Now at RCG 2.4) -- /opt/rtcds/userapps/branch-2.4/sus/h2/burtfiles/h2susitmy_safe.snap
H2 SUS FMY -- /opt/rtcds/userapps/release/sus/h2/burtfiles/fmy/h2susfmy_safe.snap
H2 SUS ETMY -- /opt/rtcds/userapps/release/sus/h2/burtfiles/etmy/h2susetmy_safe.snap


I've left all suspensions in this safe state.

All H2 Frontends Restarted

After the timing failure that Jim alludes to below (I don't know the details of the failure, hopefully those on site have an aLOG pending), all H2 aLIGO front ends were rebooted.