To measure the Spring Profile one must use a plunge micrometer and then measure the distance from the top of the Optics Table down to the Spring.  For each Spring there are two access points/thru-holes for the micrometer:  at the Spring Tip & at the Spring Base (I forgot to measure the Spring Base measurement when I did this last Wed, so I re-did the measurement this morning)

HAM3 Spring Profiles

Spring 1 (where tip location warrants corner location, in other words Spring1 is mounted on Spring Post which has Corner 3 Actuator & CPS, but Tip is in Corner1 zone)
base:  0.388"
tip:  0.375"

Spring 2
base:  0.399"
tip:  0.381"

Spring 3
base:  0.390"
tip:  0.378"

These measurements were made with our clean plunge micrometer.  It was fitted with a 2" extension.  Measurements are +/- 0.0005" (this is the slop of the locked Lockers).  I also made Tip measurements where I avoided the Spring Hatches---just stayed on the Optics Table.

On July 31st Unit #6 was placed into a storage container. Aug. 1st a purge was started at 10:30am. Ambient air was 8.2 tdºC at 24.7ºC. Boil-off LN2 was run at 20lpm until about Aug. 3rd 2:00pm.

I tried to dry out the bag the wand was in and get a baseline for the purge gas, but after approximately 15 minutes of purging just the ameristat bag and the dewpoint wand was reading -34.4tdºC and 25.5ºC. I must have been picking up a fair bit of moisture from the line and bag.

Interestingly Unit 6 in the storage container dropped in dew point much faster than HAM6 in a shipping container. Maybe there is a significant difference between the shipping and storage containers. Do the inflow and outflow locations for the purge make a difference? Less surface area in a storage container?

Found that the daqd process had quit on h2nds0.  Last error message in the log file:

Invalid broadcast received; seq=3177250 tp_seq=3177267 gps=1028180001 tp_gps=1028180002 gps_n=62500000 tp_gps_n=187500000

Restarted daqd process.

If a user is in the middle of uploading files (or even just getting started), and he forgets to select a file for uploading and subsequently hits "UPLOAD FILE" with nothing selected, it takes the user to a blank white screen. Thankfully, nothing is lost, and one can just hit his browser's back button, but the log should throw a warning / error when this situation arises. A pop-up that gray's out the log, saying "You've not selected anything to attach, please browse for a file" with an "OK" acknowledge button would suffice. Or if that's too sophisticated for the infrastructure of the log, this user error should at least take you to another page with the same warning, and a link back to the upload page and/or the add report page. 

One of the nice features of commercial search engines is that surrounding a phrase with double quotes forces the search to use the whole phrase as an exact string, i.e. "Optical Lever" returns only results that contain the whole phrase, not every entry with either "optical" or "lever." Is it possible to do this with our aLOGs?

In my bouncing between aLOGs, I've found that the colors for different Sections + Tasks are not symmetric between them. Any chance we could? (I'd specifically notices that the LogBook Admin Sections are RED in the LHO aLOG, and SEA GREEN in the LLO aLOG).

When writing a comment to an aLOG, the user has the option to change the title (as opposed to the default "Comment to [insert original subject here]"), or change the Section / Task. However, after submitting the entry, these additions / edits are not reflected on the resulting comment. Interestingly enough, the information is stored, however, because when one clicks to edit the comment, the changes and new title are still there.

See, for example, LHO aLOG 3727, LHO aLOG 3550, or LLO aLOG 4156.

The attached are the Euler and OSEM-basis spectra for the H1 PR2 M1-stage OSEMs. Each plot contains traces when M1 Damping was on and off from the nights of 08-01-2012 and 08-02-2012.   

With phone help from Bram, I reset  SUS, ISI and HPI,  which had tripped in the middle of the night, and relocked the arm. Low power though.

Attached are plots of dust counts > .5 microns in particles per cubic foot.

I have placed a dust monitor in the clean room at end X. It is set to location 1.

Reset the watchs dogs for ITM SUS, ISI and HEPI (needed to zero the ITM dc alignemtents).

I did a quick dither alignment of the TM to the laser beam.

I engaged the ISI isolation on both ITM and ETM (I think they don't have the boost on), and enabled the offload to the ETM HEPI.

attached are a spectrum and a striptool.

All is running smoothly.

In the H2 FMY suspension the USER DACKILL has white screens. I am not even sure if the damping feedback is going out to the suspension or not.

I would not be able to reset this if it had tripped. Would be nice if this can be fixed.

Removed the 90/10 beam splitter in front of the RF LSC diode, and replaced it with a 50/50 beam splitter. Adjusted the gain to set the UGF to ~300 kHz. I tried to insert a ND filter to see if the 2.74 Hz peak disappears, but don't have a conclusive result yet.

Progress on the leak testing of the Vertex has been hampered due to the prevalence of "very" loose bolts on 80% of the flanges on the GNB provided MC spools.  After finding that 12 of the first 15 flanges tested were leaking badly I ceased spraying any additional helium and, instead, torqued the bolts on the flanges which were leaking.  This was very time consuming and was not "on the schedule" but did manage to demonstrate that the majority of leaking flanges could be made leak tight by doing this. 

I will propose that all of the GNB joints (leaking and not yet leaking) be torqued on Monday (Apollo help?) before continuing on with the helium leak testing. 

Aug. 3 OPS:

Start of the day: 
ISI tripped on ETMY - HEPI tripped on ITMY - Vincent looking into it, Bram emailed

Work going on:
craning arm to install on HAM3
Filiberto to EY to pull network cable
Karen to LVEA to clean
Patrick working in the NYN room
Patrick to EX to install dust monitor
Eric to HAM2 to install hardware on actuators
Kyle to EY - retrieving equipment from VEA
Alex to EY - inventory in TMS lab
Michael R. to EY TMS lab to verify tagged out lasers
Doug to HAM3 optics table to measure some threaded hole diameters
Karen and Chris to EY to clean
HAM3 has an ARM attached to it

J. Kissel, T. Vo

After finally getting the optical levers aligned while the optics were aligned in a good state for the cavity, I've taken a spectra of both H2 SUS ITMY and H2 SUS ETMY in the quiet time mentioned in the isolationist data miner's dream. 

There're lots of fun features, differences, and similarities between the two test mass spectra, that will be good to noodle over. This will be excellent material to try to reproduce via models!


If anyone wants to gather future data, this calibrated template lives here:
/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Data/2012-07-27_H2OAT_Oplev_ASDs.xml

Jeff K. , Thomas V.

Below are the calibration parameters for the H2 ITMY Optical Lever:
        Slope          Y-intercept
Pitch [ 580.41229822  -11.51774017]
Yaw  [ 689.70532274  -13.3345144 ]


And here are the calibration parameters for the H2 ETMY Optical Lever:
         Slope           Y-intercept 
Pitch [ 1666.80728788   -33.14694715]
Yaw  [ 1727.67131855     23.41350328]

Both sets of calibrations were attained via the same process of moving the QPD along a translation stage and measuring the output signal.  All four sets of slopes are in units of radian*meters.