Apollo drilling at end Y for BSC test stand. Moved vacuum outside to mitigate high dust counts.
Mount lock and key on site
Fire department truck on site
FMCS reverse osmosis alarm
end Y transitioned to laser hazard
Filiberto replaced a seismic capacitive position sensor at BSC6.
Richard rebooted the front end systems at end Y
Kyle to connect a turbo pump/pump cart to a closed 8" gate valve on the HAM3 east door.

TMSY damping has been tested (before changing anything...), and works fine, see the attached spectra : 2013-04-30_Damped_vs_Undamped.pdf.

If the TMSY seemed to move a lot compared to the ETMY, it might have been due to an electronic issue. After Richard power recycled susb6 IO chassis and front end at the end station, the intriguing peak at around 1900Hz that was probably causing our suspicion suddenly disappeared. See the pink spectra on 2013-04-30_ETMY_vs_TMSY_NoiseCheck.pdf representing OSEM input signals of TMSY, before rebooting chassis vs blue spectra, after rebooting. This peak was also present for the ETMY but much lower in amplitude. See brown before reboot and red after (eg : last page of pdf). The spectra also shows that the low frequency noise floor is lower after the reboot...

more investigation to come...

I posted an updated version of the TMTS first article model to the SVN and wiki:

^/trunk/Common/MatlabTools/DoubleModel_Production/tmtsopt_firstarticle.m (r4580)
^/trunk/Common/MathematicaModels/DualLite2DBLateral/20130501TMTS_FirstArticle
https://awiki.ligo-wa.caltech.edu/aLIGO/Suspensions/OpsManual/TMTS/Models/20130501TMTS_FirstArticle

It has all as-built numbers from the Matlab tmtsopt_firstarticle.m r4547 (Mathematica 20130426TMTS_FirstArticle) by Szymon of last Friday, plus a tweak of +4.3 mm to d1 to better match the fundamental R (=Matlab/Mathematica pitch) mode. This was tried because it is clear from the mode shape plot (see wiki page) that that mode is almost pure R (pitch) motion of the top mass, and experience with other suspensions shows that d's associated with blades can often differ from nominal and produce a large effect on pitch frequencies. Although a sag of the blade tip by 4.3 mm is reasonably plausible, this is not directly confirmed and an alternative possibility is that the pitch mode has been driven up by stiffness of the cabling.

The only remaining mode frequency discrepancy of any note is that the highest R (pitch) frequency is predicted at 4.27789 Hz but observed at 3.875 Hz, a 10% difference. 

John W. and I took more measurements on the main crane rails, will continue tomorrow with additional measurements. All holes were drilled for test stand at End X and started assembly of pedestals. Scott and Randy took some measuerments on BSC 10 support tubes, and moved some HEPI fluid to End X for Hugh.

HughR, GregG, MitchR, JimW

After much shuffling, shifting, stacking and pushing, Hanford's last H1 BSC-ISI went into it's storage container this afternoon. It will get purged tomorrow, and likely be moved to EX sometime in June. Just five more to go.

Even though I went into task manager and closed everything that had anything to do with twincat, it acts as though there is already a PLC open when I try to run the install scripts and gives a message that the PLC has crashed.   

Even after a reboot, the behavior is the same.  

At 09:11 PDT restarted EPICS gateway between slow controls network and CDS (control room) network at request of slow controls group.

Chris and I rebooted h1ecaty1 sometime between 6 and 7 pm.  

~30 hrs of pump time total to rough-out this volume!  Ouch!   

I had to shut down all the opcIoc shells anyway, and Daniel suggests that a reboot might help with some of the odd behavior today.

I measured the transmission of the fiber at end Y:
coming out of fiber 35 uW
1.5uW towards trans PD
19uW in the wrong polarization
8 uW towards beamsplitter

It looks like we need to use the polarization adjuster box to fix this.  I will put a calibrtion of the PDs into the PLC.  

 

- praxair
- bottled water
- sprague

- reboots to dust monitors - some red alarms - all cleared
- work in EX and EY caused some dust
- EY IOP State Word went red a few times
- PSL env. monitoring went white a few times
- no reboots that were run by me - except a reboot of the DAQ around 4PM by VIncent
- I discovered that HAM2 and HAM3 had offsets for ISI change yesterday - not me, not Vincent
- I put HAM2 and HAM3 optics at their correct slider values and have them damped for alignment check - I have no tests running
- lots of work at EY and EX

Alignment in-air of IO up to PRC:

- MC1	
P	335um	 628 counts
Y	-795um	-2131 counts

- MC2	
P	505um	 946 counts
Y	250um	 670 counts

- MC3	
P	177um	 331 counts
Y	-894um	-2396 counts

- IM1	
P		 2330 counts
Y		-170 counts

- IM2	
P		-1880 counts
Y		-300 counts

- IM3	
P		 2850 counts
Y		 300 counts

- IM4	
P		-2100 counts
Y		-950 counts

- PRM - aligned	
P	-830um	-1556 counts
Y	-50um	-134 counts

- PRM - parked	
P	-330um	-618 counts
Y	-6100um	-16351 counts

- PR2 - best guess	
P	1400um	2625 counts
Y	900um	2412 counts

Attached are plots of dust counts requested from 5 PM April 28 to 5 PM April 29.

The dust monitor at location 4 in the LVEA keeps stopping due to an unknown loss of power.

[Dave Arnaud]
Following Stuart's update of medm screens at LLO, the previous aLogs, and the recent update of medm macro character limit (from 256 to 2048), Dave and I edited the changes on the SITEMAP for all suspensions* at LHO.

• the /opt/rtcds/userapps/release/sus/common/medm repertory has been svn updated in order to get the text files where the new arguments are defined, eg susetmy_overview_macro.txt
• SITEMAP.adl in /opt/rtcds/userapps/release/cds/h1/medm arguments has been edited
  • the Arguments column now calls the newly created argument text file the following way :
    %(read $(USERAPPS)/sus/common/medm/susetmy_overview_macro.txt),USERAPPS=$(USERAPPS),SITE=LHO,site=lho,IFO=H1,ifo=h1
  • the Display File column calls the overview screen the following way :
    $(USERAPPS)/sus/common/medm/quad/SUS_CUST_QUAD_OVERVIEW.adl

*except for ITMX/ETMX/TMSX/BSTST and HAUX

• An additional susquadtst_macro.txt in /opt/rtcds/userapps/release/sus/common/medm has been created, and updated to the svn

I started the rework of the IOT2L layout today.  Changes were made after LLO had some experience with their table.  With the new layout, I found that our REFL PD and the new position for the WFS1 pico motor were incompatible, so I move the WFS1 pico motor toward it's pick-off be 3", and moved WFS1 by 3" to achieve the same path length as on the new layout of 290mm.  Pictures of REFL PD, WFS1 and WFS2 attached.  Also attached is a list of components and their status for the REFL path - i.e. which components are currently not on the table.

• Apollo crew busy at EX
• Greg working on HEPI at EY
• IOT2L Rolled into place & Cheryl worked on it
• The pumping down of the Vertex continues slowly (at 2Torr now)
• Misc work out in LVEA
• Arnaud running excitations on the H1 BS this afternoon (~315-415pm)
• RO Critical/MAJOR alarm this afternoon (Ski investigating)
• Few Dust Alarms throughout the day at the End Stations and LAB areas, but they were all of the short-lived variety

BSC2, IY adapter, HAM1, HAM2 and HAM3 have all viewports necessary for the full IFO.

BSC1 is good for HIFO but one viewport for CO2 laser should be installed in the future.

For video and illuminator viewports, no inspection was made except to confirm that something was installed.

For viewports that receive 1064nm and/or 532nm beam, we made a visual inspection to see the color of the surface, and all seemed to have some AR. No attempt was made to tell 1064/532 combo AR from so-called "high quality" optic (iLIGO 1064nm viewports?).

Thomas looked at oplev viewports and confirmed that they are the correct ones.

Following is a list of what is installed and what is not. Viewport numbers are based on https://dcc.ligo.org/T1000746.

BSC1 (IY): Illumination (G3), IY alternative video (G2), IY CP video (G11).

CO2 laser viewport (C0G5) is going to have to be installed in the future, but not this time.

BSC2 (BS): Oplev IN/OUT (G2), Video BS (G8), Illuminator (G9)

IY adapter A-1: Oplev IY OUT (VP1), IY Video (VP2), Oplev IY IN (VP4).

FTIMY-related viewports (VP3, 5B, 6) are not installed as we don't have H2.

HAM1: Video (A2F1) and Illuminator (A2F4) on the east door. IR PSL (A1F5), ALS green (A1F4) and POP/REFL (A1F3) on the west door.

HAM2: Faraday input video (A2F1), General video(A2F2), "IO trans mon & PRC MM mon beam" (A2F3), "IO trans mon & PRC MM mon beam" (A2F4), PRM video (A2F5) on the east door.

General video (A1F2), Illuminator (A1F1), MC1 Video (A1F3), MC REFL (A1F4), SM1 TRANS (A1F5) on the west door.

MC3 video (D7), Faraday output, SM1 and SM2 video (C1) and REFL parking (D8) on top.

It doesn't make sense that both A2F4 (left on the east door) and A2F3 (middle) are specified to use 1064/532nm combo viewport for the same purpose. There are two beams coming through SM2 (IM4) but both of them come out of A2F3.

A2F4 is valuable as a video viewport, so we can proceed with this configuration, but somebody needs to confirm my suspicion that VP800 is good enough for A2F3,  and then T1000746 should be updated.

HAM3: PR2 video (A2F3) on the east door. Illuminator (A1F3), MC2 Trans (A1F4) and MC2 Video (A1F5) on the west door.

WAMCA1 attachment by HAM2: PR2 Video (VP3), Oplev HAM3 in/out (VP7, not VP5 as specified by T1000746), Video MC2 (VP9).

WAMCB1 attachment by HAM3: MC3 video (VP3), Oplev HAM2 IN/OUT (VP5), Oplev PR3 IN (VP7), PRM Video (VP9), MC1 Video (VP10), Oplev PR3 out (VP11), PR3 Video (VP12).

Beamsplitter transfer functions have been running over the weekend in order to fix any issues during the day if needed.

The attached pdfs show :

1. Comparison between last TF damping on and model
2. Comparison between last TF damping off and model
3. Comparison between LHO damping on/off and LLO phase 3a (feb 2013) TFs
4. Zoomed version of 3.

Vertical degree of freedom is noisier than expected between 1.5 and 3Hz (3rd page of each pdf).