Attached are plots of dust counts > .5 microns in particles per cubic foot. Also attached is a plot of the mode of the dust monitor at end X (H0:PEM-EX_DST1_MODE). This shows approximately when the values read for that dust monitor went invalid.

Finalised the name changes in the h2iscey model, and commited the model to svn. The following filter module name changes are made

1. _CM_PDH -> _REFL
2. _CM_PHASE -> _FIBR
3. _REFL_PWR_MON -> _REFL_B_PWR
4. _IR_PWR_MON -> _LASER_IR_PWR
5. _GR_PWR_MON -> _LASER_GR_PWR
6. _BB_PWR_MON -> _FIBR_A_PWR
7. _PDH_DC -> _REFL_A_PWR

The model compiled and was installed.

Update MEDM Screens

I modified the following adl files

isc/h2/medm/OAT.adl

This was done with sed string replacement:

sed -i -e 's/_CM_PDH/_REFL/' -e 's/_CM_PHASE/_FIBR/' -e 's/_REFL_PWR_MON/_REFL_B_PWR/' -e 's/_IR_PWR_MON/_LASER_IR_PWR/' -e 's/_GR_PWR_MON/_LASER_GR_PWR/' -e 's/_BB_PWR_MON/_FIBR_A_PWR/' -e 's/_PDH_DC/_REFL_A_PWR/' OAT.adl

I then hand edited the 'column buttons' to reflect the filter names.

Update filter files

I modified the following file

/opt/rtcds/lho/h2/chans/H2ISCEY.txt

first I made a copy, cp H2ISCEY.txt H2ISCEY.txt.20120814bak, then did the sed thing again,

sed -i -e 's/_CM_PDH/_REFL/' -e 's/_CM_PHASE/_FIBR/' -e 's/_REFL_PWR_MON/_REFL_B_PWR/' -e 's/_IR_PWR_MON/_LASER_IR_PWR/' -e 's/_GR_PWR_MON/_LASER_GR_PWR/' -e 's/_BB_PWR_MON/_FIBR_A_PWR/' -e 's/_PDH_DC/_REFL_A_PWR/' H2ISCEY.txt

Restore EPICS values

Used a snap file from 5am this morning and did a sed thing, and burt restored the system.

cp /ligo/cds/lho/h2/burt/2012/08/13/05:00/h2isceyepics.snap /ligo/home/bram.slagmolen/work/h2isceyepics_20120814_05am.snap

sed -i -e 's/_CM_PDH/_REFL/' -e 's/_CM_PHASE/_FIBR/' -e 's/_REFL_PWR_MON/_REFL_B_PWR/' -e 's/_IR_PWR_MON/_LASER_IR_PWR/' -e 's/_GR_PWR_MON/_LASER_GR_PWR/' -e 's/_BB_PWR_MON/_FIBR_A_PWR/' -e 's/_PDH_DC/_REFL_A_PWR/' h2isceyepics_20120814_05am.snap

burtwb -f h2isceyepics_20120814_05am.snap

Analyses channels

To monitor if the arm cavity is locked the channel name has changed (for the last time!!), the new channel is,

H2:ALS-Y_REFL_B_PWR_OUT - it has a 100 Hz low-pass filter.

Values between 4000 and 9000 represents a locked cavity, with a higher value better alignments. The units are counts, and are arbitrary as we apply an offset to the input to make it zero when the cavity is off resonance, and then we have a gain of -1. So, when we bring the cavity on resonance the output goes up.

The cavity lenght error point is still,

H2:ALS-Y_ARM_LONG_IN1 - and is in units of [nm].

All fixed now:
1. This morning we noticed that the slow voltage monitors indicated a failure. This was tracked to the +24V in EY being only at +22V.
2. Looking at the alarmed OK readbacks of the common mode boards, we noticed that the error flag indicated all was fine. This was due to a missing call to the error handler.
3. The DC power readbacks now have offset adjustment, transimpedance gain and optical response settings. However, due to a programming error, the save/restore of these settings was not working.
4. The RF power monitors of the demod and PFD boards always indicated relatively high LO readings. We tracked this to an error in the equation which is used to translate volts into dBm. 
5. While looking at the LO input to the ALS demod board we noticed that the RF level was marginal at ~7dBm. The additional loss is due to the delay line phase shifter feeding the LO. However, there was a 2dB attenuator attached to the input of the delay line. Removing it gave us a nominal 9-10dBm.
6. Last Thursday we noticed that we don't have a timing system readback from the 24MHz RF source in EY. The first problem was a fiber module with the wrong model number in the fanout. 
7. The second problem was that the RF source never synchronized to GPS. After trying everything we finally reprogrammed the FPGA PROM which resolved the issue. Not sure how this unit passed testing, but this almost certainly affects our cavity length measurement which needs to be repeated.

Jeff and myself: reverted h1susmc2 and h1suspr2 models back to early last week before the latest L1 models were tried.

The h1sush34 IOP WATCHDOG was disabled. This means that the DACKILL on h1sush34 cannot be triggered by bad MC2 or PR2 OSEM signals. This was interfering with commissioning of these optics while MC2 is in chamber and PR2 is chamber side. I will keep the workpermit for this variance open until the WATCHDOG is restored.

I tried to take the L1 latest l1susim model and convert it to H1. When I tried to run it spectacular things happened:

• all H1 front end data was marked as bad
• restarting daq streaming caused DAQ to crash
• all models using Dolphin stopped running (my bad, new IM uses Dolphin)

The new l1susim required a C-code file ATAN.c which I brought up from LLO.

I ended up reverting to my original h1susim model (itself a L1 copy done in June) and restarted all SUS and SEI models to clear the errors. I'll work with David Feldbaum on the new model at a time when losing PR2, MC2 and PSL data is not so disruptive.

MarkD EdP ScottL JimW HughR

No real issues to report on this now our third (fifth or sixth if you count eLIGO + extract) ISI installation.  We did use the crane to help roll the A-Frames w/I-Beams attached into the chamber.  The balancing measurements & moves paid off as we cleared HEPI by a comfortable 1/2".  All the tooling/fixtures are removed.
We likely won't do much more with this installation except to plug cables into feedthrus and dress said cables.  We will not payload table which means the Lockers remain unlocked but the suspended stage is clamped in position with the Shipping Braces.  The Shipping Braces prevent the installation of 4 of the 15 bolts so the ISI is not completely bolted to the Support Tubes.  This will be done when Installation decides this needs to be completed.

A few photo attached for your pleasure.

H2 Maintenance:

Jamie, Bram and myself installed a new h2iscey model (changed internal filter names in ALS_END). This required a H2 DAQ restart.

I added the second TCS L0 ADC on the CDS OVERVIEW MEDM screen.

HAM5ISI Installation

The main activity of the day was the installation of the HAM5-ISI.  Hugh & crew started rolling this assembly into HAM5 at 10:30 & they were mainly done before lunch.  They were completely done by 2pm-ish.

Other Activities

• All BSC8/BSC6 SEI Watchdogs tripped last night due to Russian earthquake
• Fire Dept on-site
• Dave addressed watchdog issue with the HAM3 optics (this was to allow Betsy to run measurements remotely)
• TCS CO2 Laser powered up in East Bay
• EX Dust Monitor went INVALID (notified Patrick)
• Thomas re-aligned the EY Optical Lever "x 2"           (FYI, a lizard now calls EY VEA home)
• HAM2 ISI positioning work (Hugh, Jim)

For the afternoon, Vincent requested quiet time so he could run SEI measurements.

Maitenance:

• CP8 filled
• Unifirst & King Soft Water on-site

The awgtpman program has been updated and the awgtpman process has been restarted for all running models on h1.  The new awgtpman will output much less information in the log file it generates, hopefully retaining the information of use.  Log files had been growing absurdly large, prompting the change.

The awgtpman program has been updated and the awgtpman process has been restarted for all running models on h2.  The new awgtpman will output much less information in the log file it generates, hopefully retaining the information of use.  Log files had been growing absurdly large, prompting the change.

Making another go at it now that Dave has bipassed the IOP watchdogs on h1sus34 (see Dave's work permit).  I've reenabled the damping on PR2.

With high pressure in the area and a few fires in the area (Red Mountain nearby, and a huge one near Cle Elum, WA), wanted to check for particle levels on the site. 

In the attached 48-hr trend, it shows that we had elevated dust levels observed mainly in the End Stations, with EY showing a huge explosion (almost 300K particles!).  The high dust levels mainly occurred from 8pm-2am.

Last night, the ISIs HEPIs and SUSs at BSC6 and BSC8 tripped at the same moment. An earthquake seems to be the cause.

- Earthquake_Ground_Z_20120814.fig
- Earthquake_ETMY_20120814.fig
- Earthquake_ITMY_20120814.fig

The aLog has had a minor update.  You will notice links between the LLO & LHO logbooks at the top of the page.  Also there is a new 'links' tab which will be used for interesting links (including the RSS feed).  The L-mails have been enhanced to include the log entries for those who prefer to follow things via email.

Last night I closed the damping loops on MC3 at 1028936901 MatLab GPS time for taking power spectra.

The ramp up/down function (launched from Commands) can be used to engage/disengage isolation filters on HEPI.

From LLO, I have enabled the damping and launched the first TF measurement on PR2 (chamberside, with glass).

Mark Barton and Jeff Bartlett

Further to the PR2 flag repair on Friday ( https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=3813 ), we went in this morning and retracted and removed the repair jig. The magnet-standoff assembly stayed in place and looked good, so we set all OSEMs to half-light ready for testing.

Thomas tried to add a python script (with extension .py) to his LHO aLOG 3758, but was thwarted and needed to change the extension to .txt in order upload it. Please add this to the acceptable files.