•	Moving ISCT EX table from LVEA to air lock at end x -> Apollo
•	The dust monitor (unit#3) that was in the "beer garden" has been moved to the East door side of the BSC3 cleanroom -> Richard 
•	Site fumigation -> Sprague
•	Installing cables into HAM 5 and 6 IO chassis -> Aaron
•	The front end computer was powered down to allow EE work on the IO Chassis of h1sush56 -> David 

Alog from yesterday. Did in-rack cabling for the STS-2 Seismometer Distribution Chassis for BSC1, BSC2 and BSC3. Each distribution chassis fans out to the HAM ISI chambers (HAM2-HAM6). The following schematics were used for reference: D0901301, D1000298, D1101576, and D1101584.

See attached for the physical location of each seismometer.

Filiberto Clara 

to permit EE work on the IO Chassis of h1sush56 the front end computer was powered down at 13:47 and back up at 14:26 (PDT) when the work was completed.

Clipping problems encountered in the PRC at LLO have led to the discovery that the PRC scraper baffle "Z Plates" were built with an aperture approximately 0.75" too small. The PR2 scraper baffle assembly installed in H1 will require removal and re-work. For more detail please see the following link to the LLO log.
https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=9200

For the record, Richard is moving the dust monitor that was in the "beer garden" to the East door side of the BSC3 cleanroom.  Data drops and high alarm levels will be seen this morning during the move.

[Mark Arnaud]

Results of ETMX M0 and R0 phase 3a (in chamber, in air) transfer functions from yesterday night have been processed and are plotted in the attached documents.

(1) Comparison between undamped M0 TF and model

(2) Comparison between undamped R0 TF and model

(3) Comparison between undamped M0 TF LHO phase 3a (in chamber), phase 2c, and LLO phase 2c

Main chain of ETMX is matching well the model cf (1), meaning it was freely suspended during the alignment (cf 8126). Only two modes of pitch are shifted down, which is a feature we already saw previously (cf (2) and alog 7415)

R0 measurements are not matching the model as well as M0, meaning something might be rubbing. Transverse and yaw degrees of freedom are very noisy. It makes sense for yaw, since the watchdog tripped when it was beeing driven, although it is not clear yet for transverse cf (2). It could be an issue in the actuation chain and I will take a closer look tomorrow.

In the process of adding subsystem links to the ODC channels I came across some inconsistencies in the medm macro files:

ISI:
there exist currently

/opt/rtcds/userapps/release/isi/common/medm/isibs_overview_macro.txt
/opt/rtcds/userapps/release/isi/common/medm/isietmx_overview_macro.txt
/opt/rtcds/userapps/release/isi/common/medm/isietmy_overview_macro.txt
/opt/rtcds/userapps/release/isi/common/medm/isiham2_overview_macro.txt
/opt/rtcds/userapps/release/isi/common/medm/isiham3_overview_macro.txt
/opt/rtcds/userapps/release/isi/common/medm/isiham4_overview_macro.txt
/opt/rtcds/userapps/release/isi/common/medm/isiham5_overview_macro.txt
/opt/rtcds/userapps/release/isi/common/medm/isiham6_overview_macro.txt
/opt/rtcds/userapps/release/isi/common/medm/isiitmx_overview_macro.txt
/opt/rtcds/userapps/release/isi/common/medm/isiitmy_overview_macro.txt

and

/opt/rtcds/userapps/release/isi/h1/medm/bscisi/isibs_overview_macro.txt
/opt/rtcds/userapps/release/isi/h1/medm/bscisi/isietmx_overview_macro.txt
/opt/rtcds/userapps/release/isi/h1/medm/bscisi/isiitmx_overview_macro.txt
/opt/rtcds/userapps/release/isi/h1/medm/bscisi/isiitmy_overview_macro.txt
/opt/rtcds/userapps/release/isi/h1/medm/bscisi/isitst_overview_macro.txt
/opt/rtcds/userapps/release/isi/h1/medm/hamisi/isiham2_overview_macro.txt
/opt/rtcds/userapps/release/isi/h1/medm/hamisi/isiham3_overview_macro.txt
/opt/rtcds/userapps/release/isi/h1/medm/hamisi/isiham4_overview_macro.txt
/opt/rtcds/userapps/release/isi/h1/medm/hamisi/isiham5_overview_macro.txt
/opt/rtcds/userapps/release/isi/h1/medm/hamisi/isiham6_overview_macro.txt
/opt/rtcds/userapps/release/isi/h1/medm/hepi/hepiham1_overview_macro.txt

and

/opt/rtcds/userapps/release/isi/l1/medm/bscisi/L1_isibs_overview_macro.txt
/opt/rtcds/userapps/release/isi/l1/medm/bscisi/L1_isietmx_overview_macro.txt
/opt/rtcds/userapps/release/isi/l1/medm/bscisi/L1_isietmy_overview_macro.txt
/opt/rtcds/userapps/release/isi/l1/medm/bscisi/L1_isiitmx_overview_macro.txt
/opt/rtcds/userapps/release/isi/l1/medm/bscisi/L1_isiitmy_overview_macro.txt
/opt/rtcds/userapps/release/isi/l1/medm/hamisi/L1_isiham2_overview_macro.txt
/opt/rtcds/userapps/release/isi/l1/medm/hamisi/L1_isiham3_overview_macro.txt
/opt/rtcds/userapps/release/isi/l1/medm/hamisi/L1_isiham4_overview_macro.txt
/opt/rtcds/userapps/release/isi/l1/medm/hamisi/L1_isiham5_overview_macro.txt
/opt/rtcds/userapps/release/isi/l1/medm/hamisi/L1_isiham6_overview_macro.txt


more that
1) h1 and l1 files are named differently and
2) some common files exist

SEI needs to sort out which ones we need to use



Also, for HPI, there exist:
/opt/rtcds/userapps/release/hpi/h1/medm/hepi/hepibs_overview_macro.txt
/opt/rtcds/userapps/release/hpi/h1/medm/hepi/hepiham1_overview_macro.txt
/opt/rtcds/userapps/release/hpi/h1/medm/hepi/hepiham2_overview_macro.txt
/opt/rtcds/userapps/release/hpi/h1/medm/hepi/hepiham3_overview_macro.txt
/opt/rtcds/userapps/release/hpi/h1/medm/hepi/hepiham4_overview_macro.txt
/opt/rtcds/userapps/release/hpi/h1/medm/hepi/hepiham5_overview_macro.txt
/opt/rtcds/userapps/release/hpi/h1/medm/hepi/hepiham6_overview_macro.txt
/opt/rtcds/userapps/release/hpi/h1/medm/hepi/hepiitmy_overview_macro.txt

and

/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpibs_overview_macro.txt
/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpietmx_overview_macro.txt
/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpietmy_overview_macro.txt
/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpiham1_overview_macro.txt
/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpiham2_overview_macro.txt
/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpiham3_overview_macro.txt
/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpiham4_overview_macro.txt
/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpiham5_overview_macro.txt
/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpiham6_overview_macro.txt
/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpiitmx_overview_macro.txt
/opt/rtcds/userapps/release/hpi/l1/medm/hepitemplate/L1_hpiitmy_overview_macro.txt


Note that
1) they have different name structures at the different sites
2) not all files exist for hanford
3) they are in different sub-directories




========================


I plead for standardization and sanity!

Today, during our contamination control discussions, Gerardo discovered that the X-beam tube manifold purge valve was still closed.  He opened it and the BSC3 soft cover showed sights of life billowing outward a bit.  So, it seems that since the vent ~10 days ago, we have only had the MC purge enabled which was not enough to supply positive pressure to all of the vented volume.  Darn.

To improve hampered HEPA flow at the BSC3 entrance (the walking plates almost completely occult the line-of-sight to the cleanroom ceiling HEPAs), I have set the draw fan previously used in chamber cleaning near the front of the chamber door through the soft wall curtains.  I have not turned it on because I am waiting for a particle counter to magically appear near the door to monitor the dust level (ehem, also ~10 days late).

ITMY now has two HEPI controllers installed (both of which work I think)

Control Level one is a positon sensor only ~5Hz UUG  in all DOF (VP and HP are AC coupled at some low frequency (<1mhz))

Control Level two, uses the second set of blend filters (lil bit iso) just the second button and has ~10Hz UUG (5Hz for VP and HP)

  It blends X,Y Z and rZ at about  0.5Hz  and rX and rY at about 0.8Hz

  I tried to design with minimum gain peaking every where (< a factor of two if you believe  linear control theory, which HEPI doesn't always)

  I characterized this controller in /ligo/svncommon/Seisvn/seismic/HEPI/H1/ITMY/Data/Spectra/Preformance_A.xml

There are three screen shots from this dtt attached, the Ref plots are with HEPI controls ON

The orange like color  and green are the ISI stage 1 T240 modal signals HEPI on/off

The pinkish  or grey and blue are the HEPI L4C signals on/off

red and pinkish are sts2 ground signals during the two tests

I don't really believe all of that isolation in the rotational directions, not sure why it is there .....

  **** the HEPI on script doesn't seem to be working so well hopefully this will get fixed soon ****

~ 09:00 - 11:00 Thomas and Gerardo working on baffle installation in BSC3
Dave restarted the models and IOP on H1SUSH34
Roofing and insulation removal continuing

Mitchell, Gerardo, Apollo (Scott, Randy, Tyler), Thomas

We got the suspension and the box into chamber and mounted onto stage-0.  The next steps are:

- Photodiode cabling
- Fine-tune alignment
- Check balance
- Set the eddy current dampening gap
- Wipe down
- Swing Back for first contact removal

• Y axis position: -199.93 mm
  • Target: -200.0 mm
  • Error: +0.07 mm
  • Tolerance: ±1.0 mm
• Z axis position: -79.97 mm
  • Target: -80.0 mm
  • Error: +0.03 mm
  • Tolerance: ±1.0 mm
• Yaw: 6 µrad CCW
  • Target: 0 µrad
  • Error: 6 µrad
  • Tolerance: ±10 µrad

Keita, Kiwamu, Sheila

We cleaned the last of the optics needed for HAM6, a 2 inch HR for 1064 with SN 0984.  There are some small marks that look like scratches on the AR side, a photo is attached.  Keita doesn't think this is a serious problem.  

Over the last few days I've been taking some passive noise spectra of the ISI-CPS on HAM6 to try and determine what the best grounding strategy is (Jeff made a nice cartoon of the options in T1300871).

Along the way I found out a few things

  1) The HAM 6 CPSs had two problems that canceled each other out

                 There as a master in each crate  (the box near the chamber that hold the CPS controllers)

                 and the cable which brings the sync signal from the power board was either bad or plugged in backwards (it isn't keyed)

                I tunred one of the masters into a slave and replaced the cable

  2)  All of the racks that I have tested have there chasis grounded, so placing them on a cable tray creates a ground and possible ground loop.

  3) Currently it is pretty likely that ALL of the CPS that are installed have grounds in the electroncs room rack AND at the chamber (Ground Loop Gaore)

  4) The resistance to ground from the power cable ground to the chamber is 0.6ohms

  5) the sync cable carries a ground from one rack to the next

 After fixing the problems I took spectra under three conditions

   Multiple grounds (electroncs room and chamber) these were bad

  Single ground in the electronics room, red and green lines in the attached png (clean room on/off are the differences)

  Single ground at the chamber, blue lines in the attached png

   Given that set of data i think that we should plan on converting to a single ground at the chamber.

   The attached pdf shows one spectra converted to m/rthz and the expected noise (we have measured something close to the expected noise on the bench for every unit in use)

  I don't really know what to say about this except yuck