Using the BSC repair arm, we reinstalled the ITMy lower QUAD (with wire hung ITMy optic). The arm is now back outside the chamber envelop and ready for removal from the door.  We still need to finish suspension and cabling before we are ready for anyone to look at it.  (But, we need to do work at BSC6 tomorrow too, so will have to interlace activities.)

After a bit of planning, a work permit was generated for the H1 BSC de-install. The tentative plan is to enter BSC3 through the east door and remove optics from BSC3-2-1 and then strip the guts from BSC3 so that we can chamber clean it. The work permit includes staging cleanrooms, etc. and door/dome removal.

Wipe down was completed and the dust barriers were removed. Second vacuum was completed. Tomorrow, we'll take care of close-out and return doors to the chamber. (I hope!)

V. Lhuillier, J. Garcia, J. Kissel

After confirming that all SUS in BSC6 were unlocked, functional, and damped, Vincent fired off an over night transfer function on BSC6 ISI. It has finished (but needless to say has not been processed).


All,

Measurements on LHO_ISI_BSC6:
Started at GPS:1018232359 - 04/11/12 19:19:04
and finished at GPS:1018266991 - 04/12/12 04:56:16

The seismic team

D. Barker, R. Bork, J. Garcia, J. Kissel

We have added two things to the QUAD_MASTER Model:
(1) Added two "TEST" filters which hook up spare ADC channels to Spare DAC channels (i.e. none are hooked up to any real electronics -- so no danger of positive feedback), and
(2) A DACKILL Part, to which the M0R0 watchdog is hooked up as the input flag.

The purpose of (1) was to have an independent way of confirming both the already-installed IOP DACKILL, and now the newly installed (2) usermodel DACKILL. For now, we've naively hooked up the M0R0 watchdog stage to it, so the our USER DACKILL merely performs the original intent of the watchdog and prevents all output of the model when the watchdog trips.

HOWEVER, this is too severe of a watchdog tripping, and currently (because we've yet to create an MEDM screen for it) is just a pain in the butt to reset. Eventually, we intend to hook this up to things more similar to the ISI's DACKILL, looking for "rogue" excitations such as coil driver monitor showing signal when "we haven't requested it," master switch being off, etc.

More details / development to come.


Details:
--------------
Since I haven't recompiled the a model recently, I provide a detailed log of what was done in order to actually install and ensure functionality of our changes to the model.

Made above mentioned changes to 
${userapps}/sus/common/models/QUAD_MASTER.mdl
the new test filters added two extra inputs and outputs to the QUAD library part.

THEREFORE made further changes to 
${userapps}/sus/h2/models/h2susetmy.mdl
connecting the TEST filters to ADC0_29 and ADC0_30, and DAC3_7 and DAC3_8. 
NOTE: This connection is unique to the ETMY top level model ... if we intend to keep these test filters in, we'll have to find unique spare channel locations for each chamber's QUAD.


Finally, with changes saved, we ran through the build process:
ssh h2build

cd /opt/rtcds/lho/h2/rtbuild-trunk/

make h2susetmy
(compiled successfully the first time -- we rule!)

make install-h2susetmy

ssh h2susb6

starth2susetmy
.........
Because we added two new filter banks to the model, this affects the .ini framebuilder file., so we restarted restarted framebuilder (the "starth2susetmy" step "automatically does" the DAQ RELOAD button mashing that is normally required when we changed the .ini file without restarting the model.)

telnet h2dc0 8087
shutdown

.........
Saw second light of DACs 1 2 (not 3?!) 5 red on both the H2SUSETMY and H2SUSBSC8 GDS_TP screens.
Learned that that's (another/the) way that you know the DACKILL is working ... it tells you that the DAC card is "no longer in use." (Yep. THAT's what the second bit means.)

SO:
reset ETMY M0R0 watchdogs (because they come up tripped, and that's currently what trips our new USER DACKILL)

reset DACKILL (because we don't have a screen yet, we had to do it by hand...)
    caget H2:SUS-ETMY_DACKILL_STATE
    0 (is BAD -- shows DACKILL is tripped)
    (saw zero)
    caput H2LSUS-ETMY_DACKILL_RESET 1 (triggers "the reset button")
    caget H2:SUS-ETMY_DACKILL_STATE
    (saw 1)

..........
Confirmed ability to drive by taking a quick low-resolution Longitudinal transfer function.

Mechanical brushing was completed using a total of three drills (1 non-starter, 1 short-timer, and 1 marathon-man). Hand detailing with the stainless steel toothbrushes was completed around the fins and under the support tubes.First vacuum was completed including the removal of bellows protection. Isopropanol was decanted in preparation for wipe-down. 

Attached are plots of dust counts > .5 microns.

5 horizontal GS13s and 4 vertical GS13s were received from LLO in shipment load # 3523. Huddle tests were performed.

Horizontal GS13s were initially set with the same orientation: as installed in the ISI. Two of them were then failing. Pods can be installed with 3 orientaions. Each orientation set up is distant of 120˚. We tried rotating the pods by increments of 120˚ to see if the test would be more successful then. GS13s were gently tilted back and forth after each rotation to make sure that the mass was not stuck. For some orientation the mass still felt stuck. The instrument's power spectrum would then reveal a failure of the instrument's response below 20Hz. 

The rotation test was performed two times: 04/10 and 04/10. The working set up found for both times correlated:

• Horizontal Pod# 37 - +240˚ CCW
• Horizontal Pod# 20 - Regular (as in ISI)
• Horizontal Pod #84 - Regular (as in ISI)
• Horizontal Pod #27 - +120˚ CCW 
• (No working orientation was found for Horizontal Pod #18)

However, when tried later this afternoon, this configuration would feature a failure of Pod #20, as reported by Corey.

The combination [leveling of the instruments in their pod + approximate level of the table used for test] could be an explanation for the need to rotate the instruments. Another explanation could be that loose flexures, as some were observed, would impact the symetry of their pull, causing the mass to get stuck in some positions and not in others.

As usual, Vertical GS13s appeared to be robust. Their spectra are all fine.

Test pictures and results are attached.

Oxide residues were found on vertical GS13s from shipment #3523. They appeared under the form of stains and small dust. Vertical GS13s, and surfaces in contact, were wiped with isopropanol before huddle testing.

Pictures are attached.

P. King, R. Abbott

ITMY H2 Scattered Light Photodiode Readout Electronics:

Put in 4 Melles Griot adjustable transimpedance amplifiers next to BSC8 on the floor under the cable tray (gain is presently set to 20nA full scale).  The installation started with a 25 pin D-sub cable on flange number F1, subflange 3, bottom D-sub.  The cable runs through the tray for a bit, then drops down to floor level in the cable tray leading toward the Y-end.  A 25 pin D-sub to (4) BNC connector breakout cable is used to fan out the D-sub to each of the transimpedance amplifiers.  The cathode of each photodiode is on the center conductor of the BNC connector, the anode is on the outer shield.

Four BNC cables run in the tray under the beam tube over to the H2 PEM chassis.  The BNC cables were reused out of a pile of old squeezer cables, so they have the prefix SQZ on their cable label.  Here's the breakdown:

SQZ:ADC4 - Connects the channel labeled 29 on the front of the PEM chassis to PD head 1
SQZ:ADC9 - Connects the channel labeled 30 on the front of the PEM chassis to PD head 2
SQZ:ADC15 - Connects the channel labeled 31 on the front of the PEM chassis to PD head 3
SQZ:ADC16 - Connects the channel labeled 32 on the front of the PEM chassis to PD head 4

The channel numbers on the front of the PEM chassis are 1 to 32, whereas the channel names are offset in a 0 to 31 format.  Next we need to view the channels in Data Viewer (and or a scope) for h2pemIO/LVEA, channels 28, 29, 30, 31 to see how noisy things are.

Removed and replaced electronics for the cold cathode PT343B.  Now, we wait.

J. Garcia, K. Kawabe, J. Kissel, T. Sadecki

We went in-chamber today to unlock the ETMY. It is now unlocked (and damping loops are functional). 

The Details:
- We ran into some trouble with new fiber protection plates interfering with ESD cables, as well as a few line stops around the test mass (Travis to provide a little more detail), but we've talked with Kurt / Besty / Travis since, and the discussion has started to improve it.
- We notice that both TMSY and ETMY had teflon tips still on most of their upper stage EQ stops. Note-to-self: these need to be removed before pump down
- In trying to run a few "is it rubbing?" TFs we discovered that their were some left over issues with the frame builder and some new .ini file modifications (See details from J. Garcia below).

We seem to have solved enough of the problems that the damping loops for both suspensions are functional and running.

Attached are a few "publicity photos" I got while Travis was unlocking H2 SUS ETMY in-chamber for the first time.

The QUAD_MASTER.mdl file located in the (local) SVN checkout under '~/opt/rtcds/lho/h2/userapps/trunk/sus/common/models/' was modified to include more channels from the user model to be stored to frame files.  There were several issues with compiling and installing the new individual models for 'h2susitmy' and 'h2susetmy' on the common frontEnd machine, 'h2susb6'.  The channel list changes were made in the QUAD_MASTER part, which is shared by all quad optics in their individual models.  

Channel List issues:
1.) The new channel list contained quotes ("") in its comments, which is used by simulink to parse the model's .mdl file to text.  The quotes ("") within the comments of the channel list prevented the correct parsing of the channel list.  The quotes and comments were removed completely from QUAD_MASTER to compile. NOTE: the quotes were in lines that were supposedly commented out by simulink, however simulink apparently disregards commented when parsing to text.

2.) The initial file had a few channels requesting a 128 b/s rate to the framebuilder. The data rate minimum allowed by the RCG is 256 b/s, so the few channels initially at 128 are now at 256 b/s.

3.) The TMS model 'h2sustmsy' was last recompiled and installed under RCG 2.4, whereas the latest 'h2susetmy' model was compiled using RCG 2.5.  The IOP model running on 'h2susb6' was compiled under RCG 2.5 as well.  The error was in the IOP machine,'h2susb6', attempting to run two models ('h2susetmy' and 'h2sustmsy') that were compiled under different RCG versions.

The TMS model was compiled and installed on 'h2susb6' under RCG 2.5, and, after a DAQ reboot, all previous errors on 'h2susb6' were cleared.  Damping loops on both TMSY and ETMY M0/R0 were closed and confirmed functional by late afternoon.

With the Staging Bldg Hot Yoga Studio at a balmy 77deg F (probably 25deg hotter inside our cleanroom/yoga suits), we practiced several SEI Hot Yoga Poses:

Yoga Pose#1:  HAM6 ISI Optics Table on Granite Table   (Corey, Eric, Jim W)

This table is now on the Granite Table and ready for lots of helicoils to be installed.  There was some damage on an edge of this table (scratch mark with traces of blue paint engraved in the scratches); this damaged occurred while the Optics Table was stored in the LVEA--it must have been rammed into during LVEA activities.

Yoga Pose#2:  GS13 Tests (Corey, Hugo)

Went through a suite of tests to determine optimal angular positions (if any) for Horizontal GS-13s.  For the four we looked at, we were able to find good positions for 3 of them; no matter what we tried for the 4th GS13, it always yielded "stuck-mass" spectra.  These GS13s are now stored on the shelves and Hugo will look at the Vertical GS13s. 

The Apollo Welders completed the welding of the EndX H1 HEPI fluid circulation system last week and pressured the system over the weekend.  The pressure held over the weekend so we deemed the system tight, actually more than 5 days.  A couple photos attached and a link to a resource space collection of more photos.

ResourceSpace link: https://ligoimages.mit.edu/?r=19113
If you go to my LHO_HEPI collection you'll see more

Attached are scans from Scott Lorimer's(Apollo) log book.  These graphically depict the plan view location of the elevation control available at the EndY and tabulates their value.  Nominally we would survey the BSC chamber (in this case BSC6) at the manufacturer's 90° marks on the B nozzles (BSC 60" door) (which we did) and then set the datum zero to the average of these eight elevations.  I elected to not do the latter as the average was less than 0.2mm approaching the noise of the measurements.  So the current end station elevation datum is zero at the South horizontal scribe of the East B nozzle.  Otherwise, use the elevation numbers from the table (in millimeters) to start your vertical survey.
Note, BM#101 is North of BSC10 and not seen on the plan view.

There was no TMS spectra posted to alog after it was transported to the test end, so here it is.

Current traces are in-chamber,  doors covered (yesterday) and references are under the test end (Mar/19/2012), both undamped and free swinging. Under the test end, ISI was locked down, but it was free last night.

The noise level of some DOF is much lower now than they used to, which might be due to the air flow under the test end.

These look different from in-lab measurement under the Bosch frame (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=1825). There's a whole bunch of peaks betweeb 1 and 2 Hz now, and also there used to be no 0.79-0.77 Hz peak under the Bosch frame. Usually I get suspicious about the touching/rubbing, but we looked and haven't found anything. OTOH, under the Bosch frame one of the suspension wire was resting on a washer on the table cloth, which was later fixed just before TMS was transported to the test end.

Frequencies of most of the peaks didn't change, but there are some that changed (e.g. from 0.79 Hz to 0.77 Hz, from 1.6 Hz to 1.5 Hz, and from 1.79 Hz to 1.75 Hz). The difference might be due to the ISI status (free VS locked down at the test end) but we don't know.

We'll check any interference again some time in the future, but at the moment we won't do anything and just damp it for ISI crews.

It seems that some of the in-chamber connectors on the vacuum feedthroughs don't have setscrews to keep them attached in position. So they're just plugged in. This is not limited to TMS.

Is this intentional? I cannot believe that we do NOT want to securely attach connectors.

Dan, Aidan and I went to EY to unlock TMSY. From earlier report by Cheryl I was worried if TMS is really close to touching, but it was fine. Maybe ISI unlocking did the trick, though we don't know.

Anyway, SUS team should feel free to go in the EY the first thing in the morning.

There is a minor problem, which is that TMS is undamped now because TMS DAC is disabled because ETMY is not plugged in. Don't ask me about this logic. We are supposed to be able to damp it once ETMY is up and running.

Attached are plots of dust counts > .5 microns. The dust monitor under the clean room over BSC8 (H0:PEM-LVEA_DST15_5) was not reliable enough to bother plotting. The dust monitor at location 7 in the LVEA was moved to location 15 in the morning. I have included a plot of H0:PEM-LVEA_DST7_MODE to show when.