Here is work from Wed....

Vertical Adjustment of Shims

Tues night, we found the tips of the Springs to be higher than the base of the Springs.  So, the 0.126" Shims under the Lockers were swapped out for thinner Shims.   This brought the tip/base Spring difference to around our tolerance of 0.015".  The ISI was then balanced.

Current Locker Shims:

• A:  0.122"
• B:  0.122"
• C:  0.120"
• D:  0.120"

Horizontal Adjustment of Shims

With the dial indicators, we were able to monitor float/locked positions of ISI.  Horizontally, we saw an overall counterclockwise twist (saw dial indicator changes on the order of 0.007-0.018".  So, we went about re-positioning the Locker Bases. 

(I'm noting procedure here mainly for my own records)The ISI was unlocked, the Dial Indicators (DI) were zeroed.  Then at ONE Locker, we loosened the Base bolts & Locked the locker.  Due to friction/sticking between the Locker Base and the Stage0 floor, you will probably see some Stage1 motion.  If you do, just tap on the Locker Base to free up your Base & to keep your DI at zero.  Once the Locker is locked, and the DI says zero, one can start tightening the Locker Base to Stage0.  Unlock the Locker (rezero DI if needed), and re-Lock, and confirm the change in state is within 1-2 thousandsths.  Repeat for remaining three Lockers.  After we did this, when we re-locked the system it did so without binding up the 4th Locker---a good thing.

For the most part we are mostly done with this ISI, EXCEPT, it was noticed the installed-Actuators aren't "aligned".  When they were removed off the ISI, they first had their Set-Up Bars installed to "lock" their alignment.  Either they weren't aligned before, or they Set Up Bars weren't installed correctly, and we've lost their alignment.  Each Actuator will need to be pulled off, re-aligned on a work bench, and then reinstalled.

Steady progress is being made towards cartridge insertion at BSC8, likely late this week Thu/Fri.  Items underway include:

-The cleanroom at BSC8 was swapped out for the shorter, modified variant.  We had neglected to account for a known interference, that of the gate valve stem (and box works mounted there), when lowering the cleanroom to fly the cartridge and center over BSC8.  The shorter extent (as aligned along the Y beam axis) allows for the cleanroom to be lowered without interfering with the gatevalve.  Small modifications to the work platform/railing were made to limit interference there as well.

-At the y-manifold/cryo pump area, the H1/H2 optical lever piers and table, and TCS laser were removed, and plumbing under the beamtube modified (TCS chiller lines removed, purge air modified) for clear access.  De-installation here allowed for the arrival of cleanroom, cleaning of the area, and eventual spool extraction.  The driver is the vacuuming of the y-manifold, part of the in-chamber cleaning effort, intended to limit a particulate source near the recently brushed and cleaned BSC8.  Vacuuming is to take place prior to cartridge insertion.

-At the cartridge test stand #2, SEI software transfer functions completed and the ISI was locked up, and final power spectra obtained.  Both suspensions remain unlocked.  In an effort to pulse and vet the ESD cabling, we removed an iLIGO feedthru from HAM8 with the appropriate connector type; this failed as described in R. Abbott's earlier alog, and will require an in situ retrofit of the ESD cabling (a limited run from the feedthru to a connection point affixed to the ISI)

Attached are plots of the 7 tap test locations on the FMY performed yesterday afternoon. Data was exported from the PULSE software to a text file and imported into Matlab. For this measurement, a metal tip on the B&K hammer was used as opposed to the rubber tip used in previous measurements.  A new template ("Simple Hammer Display 3.pls") in the PULSE software was used according to T1000697-v2.

The plots each have the 3 DoFs from the accelerometer used and are plotted according to location.  The FMY M1 Damping Loops were closed and the ISI floating.  The plots show the response trending upwards from ~100Hz and higher as in previous results.  However, previous measurements saw this upward trend in magnitude beginning from ~10Hz.  Here, the trend is a decrease in magnitude from the lowest frequencies to ~100Hz.  

For these measurements, the accelerometer was placed on the back side of the FMY (i.e. the side facing opposite the ITMY) due to accessibility. A description of the locations on the FMY are as follows:

location1 - back side of fmy beam tube side just above the accelerometer
location2 - side of M2 hitting away from beam tube
location3 - M2 cross brace downwards
location4 - M1 cross brace downwards - straight cross brace
location5 - top side from beam tube going away - above M1
location6 - straight cross brace on M2 on clean room side
location7 - cross brace on M2 clean room side

Data was also taken for the ITMY QUAD structure, however, there was a data corruption issue encountered in data from 5 of the 7 locations.  Measurements on the ITMY QUAD will be re-taken with time permitting before cartridge install.

The spool piece by GV5 was pulled to allow access to the section of the arm cavity leading toward BSC8. Once the spool section was out and the Arm Cavity Baffle removed, Cheryl V., Mark L., and I went into the cavity to conduct an assessment of particulate content and document what we found. (As you may recall, this expedition was first contemplated during ICC at BSC8 because of the quantity of "detritus" that we found at the drop-off between the chamber nozzle and the larger diameter Arm Cavity.) Our objectives were to assess both the quality and quantity of "detritus", determine whether there appeared to be a gradient in the location of "detritus", get good quality close-ups of items in-situ, and to collect samples of various items. We accomplished all of our goals and the preliminary results are listed below:
1. The quality of "detritus"-Seems to be very similar to what we've found during in-chamber cleaning (pieces of glove, thread, "fluffy" fibers, metal fragments including what looks to be Al foil, "goopies" of various kinds, and a very fine patina of metal "dust")
2. The quantity of "detritus"-Again, very similar to what has been found in chambers (Cheryl will attach some pix to this post when she gets a chance.)
3. There does not appear to be a gradient in the quantity of "stuff". We thought we might see more "detritus" close to the BSC or gate valve but that does not seem to be the case. The "crap" seems to be quite evenly spread from gate valve to BSC...
4. Cheryl got some great pix including the fine metal dust falling from the top of the tube and the gate valve on the north(?)side of BSC8 showing its amazing quantity of "detritus"
5. We were able to collect several samples for Robert S. and others to look at.

Performed a test of the ESD cabling associated with the BSC8 cartridge.  A time domain reflectometer was used to verify the integrity of the coaxial cable from the vacuum side connector down the suspension chain leading finally to the reaction mass ESD actuator.  Discovered that 3 out of the 5 coaxial paths were bad.  Cause traced to a failure of the solder joints used to attach the coaxial cable to the PEEK custom connector.  The joints were baked at 200 degrees C in the vacuum bake process.  The solder used has a melting temperature of 184 degrees C, which resulted in a complete failure of these connections.  Even the two that tested good rapidly failed when tension was applied to the connections.

After a conversation with John Worden and Mike Landry, we elected to leave the majority of the cabling intact and to re-terminate the coaxial cables in a new connector after the cartridge is installed.  The 5 coaxial cables will be drawn through the aperture of the conflat feedthrough and a new connector will be installed in situ.

All of the five cables appear intact and correct aside from the failure of the vacuum side conflat mate.

The communication to the dust monitors in the LVEA was lost twice today, once when the power to the Comtrol serial to Ethernet switch was lost, and once later when the software froze for an unknown reason. These times can be seen in the mode of dust monitor 11 (H0:PEM-LVEA_DST11_MODE) when it stops changing in the attached plots for today.

Attached are plots of dust counts > .5 microns during today and yesterday.

There are now two dust monitors running at end Y, both of them in the clean room for the test mass. The channel names for the particle counts > .5 microns are H0:PEM-EY_DST1_5 and H0:PEM-EY_DST2_5.

In order to investigate whether the Length modes coupling into H2 SUS ITMY M0 Top2Top Yaw transfer functions are real or noise, I've taken a high resolution (2 mHz) measurement of the same transfer function (same amplitude, BSC-ISI unlocked but undamped, ITMY M0 damping OFF, ITMY R0 damping ON).

I attach three plots for discussion. 
(1) A full-frequency-range plot measurement itself, 
(2) A zoom in on the resonance that we've been concerned with, and
(3) A plot of what cross-coupling we expect from the model (i.e. zip, nadda, zilch).

Note that neither of the first two plots are calibrated properly, but the relative amplitude should be accurate

One can see from the full-range plot that not only is the lowest Longitudinal mode present (at 0.43 Hz), but the second L mode (at 0.98 Hz) also creeps in. Regrettably, I'm now convinced that this (these) resonances are actually a measurement of physical motion, not just unlucky in coherent noise.

Now, is it a show stopper? No (yet).

A useful tip from the good Dr. Lantz: physically cross-coupled modes typically show up as pole-zero pairs, as opposed to what we see here -- just a sharp pole.

Other pertinent information: the excitation for this drive is a continuous, broad-band, white noise excitation across the measurement band, for the duration of the measurement. You'll note in the second plot attached (upper right panel), that the coherence (i.e. the measure of the *linear* coupling) between the Y drive and this particular L resonance is ~0.25, which is roughly consistent with what we know to be noise in the rest of the band. 

However, the lower right panel shows the OSEM basis response of F2 and F3 to Y (in PHASE); the sensors that compose this DOFs Euler basis signal. Here, (though it's tough to see with the black cursor overlayed -- sorry) the sensors are identically in phase, implying real longitudinal motion.

Why don't I think this is a show stopper (yet)? We have found from experience that moving around these suspensions, after locking and unlocking, that these sharp cross couplings come and go. Case and point -- we don't have a smoking gun of what might have happened between the 2011-11-19, 2011-11-29, and 2011-12-02 measurements that might have caused such a gradual increase in coupling, except for *better* aligning the chains. Further, I expect that the coupling will be significantly reduced once we take a similar measurement with damping loops ON (we'll be sure to confirm this of course) -- which is the default "plant" upon which we'll apply ISC control loops (if there are any at this stage). 

But most importantly, let's just see what we get after we install the cartridge. We'll have to lock and unlock the suspension, and will have to do another round of BOSEM centering (in and out, not necessarily laterally). We may get lucky and the coupling may be reduced, or we could get unlucky and have much worse coupling. Further, we have yet to use what's in our digital back-pocket: diagonalizing the drive using sensors. This may help as well. From what I've seen of the remaining degrees of freedom, I'm confident that the suspension's mechanical system is behaving well.

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

Data for this measurement can be found here:
{SusSVN}/sus/trunk/QUAD/H2/ITMY/SAGM0/Data/20111207_1700_H2SUSITMY_M0_Mono_Y_0p002to50Hz_TF.xml

   The EE shop found no gross problems with the staging building satellite box (see aLOG #1845), which was showing a noise spike at 55Hz on channel 1 and generally elevated noise levels on channel 3. Dave did find a couple of questionable solder joints, so he gave the box a going over and re-soldered connections as necessary. This removed all noise issues with this satellite box. A second satellite box was also showing some noise around 55Hz on channel 2. Dave in the EE shop re-soldered the connections in this satellite box, which also removed the noise. Both boxes are back in the test stand and functioning normally

- Removal of section of Y-Arm beam tube in LVEA for IAS alignment

- Preparing for BSC8 ITMY,FMY cartridge installation

- Cleaning ongoing throughout LVEA West Bay

- Videography ongoing in LVEA

- SUS fiber welding at EY (EY now has restricted access)

- FMCS network repairs ongoing

- iLIGO H1 DAQ shut down (except for h1adcusus, h1adcupem, h1adcuex, h1adcuey)

- Dust levels high (red zone) throughout day in vertex and west bay area of LVEA due to vacuum and cleaning activity

(Corey, Eric, Greg, Jim, Mitch)

We have disassembled HAMISI#1 (which has an Optical Table S/N #004), and have been putting it back together for the last couple of weeks (HAMISI#3 is on the other Test Stand and is being tested by Hugo).  We are now at a point where we can start taking inventory of various parts for the assembly.  [Except for GS13's, we don't have GS-13's for this assembly]

Unfortunately, we failed to note some s/n's until after they were installed and they are in a state where getting their s/n's is just not possible (this is especially the case for the Flexures).  I looked at the original Pre-Integration document for HAMISI#1 when it was made back in June '10, but I wasn't able to find Flexure information there either.

With that, here is inventory information thus far:

Spring S/N's

Forgot to check S/N's for the Springs before the Optics Table was installed, but were able to see their numbers with the use of an inspection mirror.

• Corner 1:  22
• Corner 2:  12
• Corner 3:  5

Flexure S/N's

These Flexures were not assembled consistently convenient, in that 2of3 Flexures were installed upside-down (meaning, scribed s/n's are on the bottom of the Flexures and are now not very visible).  Tried using a mirror and flashlight to view the Flexures from under Stage1, but the Flexures are fairly high up, and the scribe marks are also hard to read.  With that, we can only say we have "best guesses" at s/n's for Corner 1 & 3.

• Corner 1:  50? (best guess)
• Corner 2:  13
• Corner 3:  25? (best guess)

Actuator S/N's:

There were no issues with installing the Actuators.  They are all torqued down to Stage1, and are not connected to Stage0.

Corner 1:

• Horiz:  48
• Vert:  52

Corner 2:

• Horiz:  60
• Vert:  61

Corner 3:

• Horiz:  62
• Vert:  65

Sensor Head S/N's:

I'm a little confused at the inventory of the Sensors.  Looking at the document above, it looks like the order of the Sensors was V1,H1,V2,H2,V3,H3.  But we've apparently had a model change and have an order similar to the BSC:  H1,V1,H2,V2,H3,V3 (HAMISI#3 is already set like this).  However when I looked at the Sensor Assys, I saw that the Sensors were mounted in this order:  V1,H1,H2,V2,H3,V3 (!)

Not sure where this mix-up occurred, but I went ahead and swapped the Corner1 CPS's in their mounts so that we now have the correct order of:  H1,V1,H2,V2,H3,V3.  I did not make any change to the Boards in the rack, and the CPS's all match their Board.

Only able to install the horizontal CPS's.  The Target/dowel pin & the Target Mount is a tight connection, and it was found that some of these were very tight and needed alcohol to lubricate them.  This is not desirable for the Vertical CPS's because there's potential for alcohol to drip down on to the Target Face, and cause a "stain".  So, we decided to hold off installing these Sensors, and ream out the Target Mounts.

On the topic of marred Target Faces, we have found that most of our Target Faces are far from pristine.  There are noticeable marks from use of teflon to measure gaps, and just various marks from handling.  One of the Target Faces had some deep divets on it, and we decided to pull this Target Face out of use.  Hope marks on other Target Faces aren't detrimental to future operation.

At any rate, here is the inventory for CPS:

Corner 1:

• Horiz:  11979
• Vert:  11991

Corner 2:

• Horiz:  11986
• Vert:  12017

Corner 3:

• Horiz:  12033
• Vert:  12038

GS13's S/N's:

Not available since we have no GS13's.

Current State:

We have also installed payload on this ISI, and it has been floated.  We are now in the process of shimming the Lockers. 

I've re-arranged the TOP input and output orders in the 
${RTCDSROOT}/userapps/release/sus/x1/models/x1susquad.mdl
to obey the new convention, as per the latest version of the schematic, D080273. Any future QUADs attached to this test stand should have its TOP stages (M0 and R0) cabled up according to T1100327.

I've also modified the foton file (to include compensation filters for L1 and L2, that disappeared during the re-build process), which lives in
${RTCDSROOT}/chans/X1SUSQUAD.txt
but has now been copied to
${RTCDSROOT}/userapps/release/sus/x1/filterfiles/X1SUSQUAD.txt

Further, I've modified the framebuilder's .ini file, such that all OSEMINF_*_OUT_DQ channels are stored in the frames (and removed/"un-stored" some unnecessary DAMP_*_OUT_DQs). This file lives in
${RTCDSROOT}/chans/daq/X1SUSQUAD.ini
but has now been copied to
${RTCDSROOT}/userapps/release/sus/x1/daqfiles/X1SUSQUAD.ini

All three files, the .mdl, .txt, and .ini, are commited to the userapps SVN as of rev 1554.

I've confirmed that all sensor channels are functional, the frame builder is green, and data can be taken via DTT in real time and the past. Whether the channel rearrangement was successful, is yet to be determined by actually plugging in OSEMs (but I'm 90% sure it worked).

Details:

- logged into bisbee / bscteststand2, and made sure the running version of the model had been committed to the svn (it had).
- svn up'd my local copy.
- Modified simulink model according to D080273, committed as a part of repo version 1552.
- svn up'd bisbee's copy
- logged into bscteststand2, used "cdsCode" alias to cd to proper build directory
- "make x1susquad" -- wait patiently for all the useful stuff, then all the garbage to pass by
- "make install-x1susquad" -- make sure I see at *least* two active channels -- but there was only two. Somehow the make process blew away whatever 
- The most recent .ini file with more than two channels? X1SUSQUAD_111128_104742.ini. Go figure. 
- cp /opt/rtcds/tst/x1/chans/daq/archive/X1SUSQUAD_111128_104742.ini /opt/rtcds/tst/x1/chans/daq/X1SUSQUAD.ini
- run inicheck on X1SUSQUAD.ini, seems to be OK, 72 active channels
- Restart framebuilder:
	- controls@suswork1:/opt/rtcds/tst/x1/chans/daq/$ telnet bscteststand2 8087
          Trying 10.11.0.26...
          Connected to bscteststand2.
          Escape character is '^]'.
          daqd> shutdown
          OK
          Connection closed by foreign host.
          controls@suswork1:/opt/rtcds/tst/x1/chans/daq/$
- Check frame builder status after restart,
$ caget X1:DAQ-DC0_X1SUSQUAD_STATUS
X1:DAQ-DC0_X1SUSQUAD_STATUS 8192
 (This is 0x2000) 
- Hit DAQ Reload on GDS_TP screen, then restarted frame builder, worked this time
$ caget X1:DAQ-DC0_X1SUSQUAD_STATUS
X1:DAQ-DC0_X1SUSQUAD_STATUS 0
 (This is 0x0, and green)
- restarted newly installed fronted process, by logging into bscteststand2, and running
controls@bscteststand2 ~ $ startx1susquad
(Did this while watching GDS_TP screen, and hit the BURT button as soon as it became visible in order to trigger daqd, etc.)
- Found warning of "modified IIR file" on GDS_TP screen. Looked around, didn't see anything abnormal. Reloaded anyways. Found that L1 and L2 stages OSEMINFs were now missing.
- Added filters via copy and paste in foton, and reloaded coefficients.
- cp ${RTCDSROOT}/chans/X1SUSUQUAD.txt ${RTCDSROOT}/userapps/release/sus/x1/filterfiles/
  committed to SVN under rev 1553.
- Checked that OSEMINF_*_OUT_DQ channels were stored in frames via DTT. L1 and L2 stages were not stored, so modified .ini file to store L1_OSEMINF_*_OUT_DQs. Hit DAQ reload on GDS_TP, and restarted frame builder.
- cp ${RTCDSROOT}/chans/daq/X1SUSUQUAD.ini ${RTCDSROOT}/userapps/release/sus/x1/daqfiles/
  committed to SVN under rev 1554.
- Confirmed that all OSEMINF_*_OUT_DQs can be measured real time, using 
/ligo/svncommon/SusSVN/sus/trunk/electronicstesting/AOSEM/noise/2011-12-06-01/AOSEM_Batch_Data.xml
- Confirmed that all OSEMINF_*_OUT_DQs can be measured in the past (10 minutes), using 
/ligo/svncommon/SusSVN/sus/trunk/electronicstesting/AOSEM/noise/2011-12-06-01/AOSEM_Batch_Data.xml

Good to go!
  

The problems with h2fw0 are more than it crashing every few hours. Some times it also glitches its framed data written to disk with a 16Hz square wave. Since this effect seems random on restart, the problem appears and disappears as h2fw0 restarts itself.

The problem is not seen in the secondary frame writer h2fw1 (whose data is served by h2nds1). Therefore for now we should only use h2nds1 to get archived frame data (h2nds1 is now the default NDS for dtt).

h2fw0's problem is only with data written to frames, any real-time testpoints or DQ channels obtained from h2nds0 do not show this noise.

We will investigate the problem further today.

Dave and Jim

PeterK, JanP, MichaelR, RickS

Yesterday, we made some final parameter measurements for the H1 PSL, inspected the pump fiber surfaces, then shut down and began dismantling the H1 PSL.

As of last evening, the pump fibers have been pulled back to the H1 Laser Diode Room, the electronics racks have been partially gutted, and we are beginning to remove components from the table.

Right now we are focusing on the components that we will reuse for the H1 aLIGO PSL.

We expect this process to continue into next week, partly because we want to spend as much time as possible working with JanP on the H2 PSL this week, which is his last before heading back to Germany on Friday.

We will post the measurement and inspection results shortly.

This afternoon the ETMy PUM glass mass was loaded into the Lower Structure marked in the fiber welding cleanroom at EY. The ETMy optic is at the end station and will be loaded tomorrow morning. Setting the mass positions relative to each other and the structure, and setup of the fiber equipment will likely continue through Wed, with welding hopefully starting sometime Thursday.

J. Garcia, J. Kissel

Today while trying to troubleshoot the FMY Damping Loops, a strange high-frequency noise was evident in the time-series signals via a dataviewer session.  A spectra of the H2:SUS-FMY_OSEMINF_*_OUT_DQ channels reveals a strange 75Hz peak in only the F1, F2, and F3 channels.  The added mystery is the fact that these channels share a physical cable with the *FMY_OSEMINF_SD_OUT channel.  We assume this is purely electronic noise arising from one of the boxes in the racks and not due to physical motion. This may also explain the added jitter in the OSEM input signals indicated by the dial indicators on the medms.  Attached is a power spectra of the *FMY_M1_OSEMINF_*_OUT_DQ and *ITMY_M0_OSEMINF_*_OUT_DQ channels with the 75Hz peak not apparent in the ITMY channels.  Investigations to ensue.

This peak is also not evident in the *ITMY_L1_OSEMINF_*, *ITMY_L2_OSEMINF_*, or *ITMY_R0_OSEMINF_*_OUT_DQ channels.  Plots for L1, L2, and R0 attached in the second pdf.

During noise testing, in the Staging Building, of the AOSEMs I found a noise spike on channel 1 and generally elevated noise levels on channel 3 on one of the satellite boxes (for M0F1-M0SD S/N 32007-14). I have removed the box to have it checked. 

B. Bland
Reports from Garcia and Vincent from last night are that the FMy BOSEMs look unhealthy.  In fact, one of the satellite boxes is without power.  So, Richard is looking into why this is "broken". 

Yesterday evening the laser was shut down due to a lid violation error. During the attempt to install the rf-summation box inside the 35W front-end box, we had made a mistake in the activation of the lid-overwrite, which is required to safely open the FE box. As we did not completely understood what happened we decided to leave the laser in the off state overnight.
Today the laser was restarted and run the full day without any problems. The currents of the HPL diode boxes were adjusted to the following values:
DB1: 50.5A
DB2: 49.1A
DB3: 48.9A
DB4: 49.2A

We installed and tested the water flow sensors for the water cooled power meters. All three flow sensors were set to switch at 1.5 l/min. If the flow is too low , the shutter of the high power lasers is automatically closed. With this system in place we can now operate the PMC overnight.

We continued to work on the beam path from the PMC pickoff port to the reference cavity. With the PMC transmitting 142W at the IO interface we get 387mW in the FSS beam path (measured directly infront of the FSS-AOM). The AOM is aligned to a double path efficiency of 59% such that 225mW are measured directly after the PBS downstream of the double passed AOM. (VCO_MOD_LEVEL 32000 in FSS MEDM screen, all power levels measure with an OPHIR 10A-V2-SH power head). A WinCam scan of the single path pattern is attached. The modematching was adjusted to give a 75% dip in the reflected light while scanning over the TEM00 mode of the cavity. The transmitted peak of the largest higher order mode has about 10% of the peak heigth of the TEM00.