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.  

Insulation removal started in earnest on Tuesday of this week. The vendor is using a soft sided 54 foot trailer to load waste insulation into. Once a day they fill the trailer and take it to the city dump where they have stationed another forklift to help push the insulation off of the trailer.

They are making very good progress - starting at the LVEA they have progressed to the third double door which is ~2400 feet down the arm or ~800 feet per day.

Photos show the work in progress and the end result - a clean beam tube enclosure.

A few pictures of the recent state of our roofing project. The first two photos show the XEND station roof from the backside. The metal trim is in process. This is the first of the trim work.

The other 3 pictures show today's state of the LVEA roof. I expect the membrane on this level to be complete early next week.

I ran the following:

caput HVE-EY:Y1_423BTORR.HIHI 4.77e-08
caput HVE-MY:Y5_246BTORR.HIHI 5.11e-08
caput HVE-MY:Y1_243BTORR.HIHI 3.81e-08
caput HVE-LY:Y4_124BTORR.HIHI 8.47e-08
caput HVE-EX:X1_523BTORR.HIHI 4.08e-08
caput HVE-MX:X5_346BTORR.HIHI 1.48e-08
caput HVE-MX:X1_343BTORR.HIHI 2.12e-08
caput HVE-LX:X4_144BTORR.HIHI 2.69e-08
caput HVE-EY:Y1_423BTORR.HHSV MAJOR
caput HVE-MY:Y5_246BTORR.HHSV MAJOR
caput HVE-MY:Y1_243BTORR.HHSV MAJOR
caput HVE-LY:Y4_124BTORR.HHSV MAJOR
caput HVE-EX:X1_523BTORR.HHSV MAJOR
caput HVE-MX:X5_346BTORR.HHSV MAJOR
caput HVE-MX:X1_343BTORR.HHSV MAJOR
caput HVE-LX:X4_144BTORR.HHSV MAJOR

I looked at the ITMx ACB position for any gross positional errors with respect to the ITMx. Athough the ISI and ITM are on stops the indication from the total station is the ACB will not interfere with the fine alignment of the ITMx. The ITMx rough position looking from the spool is good as far as the optic cap centering goes. I predict that we will need little elevation or lateral adjustment.
We won't know about longitudinal position or pitch and yaw until the ISI and SUS are leveled, TFs are done and the optic is suspended.

I intended to change the channel's alarm level, but accidentally set the value of the channel itself.

HVE-EY:Y1_423BTORR got briefly changed from 4.77394e-09 to 4.77e-08.

A plot of the change is attached.

h1sush34 developed a timing error at 09:45 PDT. I activated the IOP DACKILL and restarted all the models (MC2, PR2, SR2 and IOP), which cleared the problem. The IOP Watchdogs in turn tripped h1seih23 (h1seih45 was already tripped). 

The cause of the timing error is currently unknown. I'm leaving all systems tripped.

From late Wednesday afternoon - After issues were encountered running a Matlab script I looked at the tripleteststand.  Checked the system time and the model time, found them to be as close as can be expected.  Noted that the NDS process was not running, and couldn't be kept running when started.  Killed the daqd process, started the nds process, then restarted the daqd process.  

Checked the ability to get data from _DQ and testpoint channels using dataviewer, all appeared OK.  Jeff Bartlett confirmed that the Matlab script could be run successfully this morning.

I created a new group called BeamTube_Pressure in the vacuum alarm handler configuration file and added the following channels to it:

HVE-LX:X4_144BTORR
HVE-MX:X1_343BTORR
HVE-MX:X5_346BTORR
HVE-EX:X1_523BTORR
HVE-LY:Y4_124BTORR
HVE-MY:Y1_243BTORR
HVE-MY:Y5_246BTORR
HVE-EY:Y1_423BTORR

I committed the changes to subversion.

Jeff B and Andres R

  We have taken and plotted the damped and undamped transfer functions and power spectra for H1-OMC. The results look positive for exiting Phase 1b testing. The plots are attached below.   
   

Started M0 and R0 undamped ETMX transfer functions

Betsy, Travis

This afternoon, we connected the 5 ETMx SUS cables and the ringheater cable to the inside of the feedthru flange.  We then had issues with signal faults.  We investigated and found the out-of vac cables not plugged in well at the outside of the feedthru.  Apon fixing, all looked well with the signals.  The suspension is still not fully suspended although we pulled out all of the extra teflon stopping brackets and prepped it for full unlock after SEI is done float/balance, after IAS is done figuring out where to put us.

I used thenano scan to measure a beam profile on IOT2L.  near the periscope, the vertical waist diameter is 4411um.  The horizontal beam isnot gaussian, the waist diameter fit is 4007um.  (screen shot is first image attached to this report) This was taken 3 and 1/2" from the bottom periscope mirror, the periscope height is 23 and 1/2 ", and the top periscope mirror is approx 2'8 and1/2" from the viewport.  This data is saved as IOT2L1 on the nanoscan computer.  

I moved the scan head back to  14"  behind the botttom periscope mirror, and measured 4405 um diameter vertical , the horizontal beam still is non gaussian, but the diameter is 4070 um.  (screen shot is second image attached)

This data is now transfered to http://www.ligo-wa.caltech.edu/~sheila.dwyer/NanoScanData/IO/