Roof work is progressing well.

The first 3 photos show a mid station ready for sheet metal trim installation. All four out buildings are at this stage.

Other photos show the upper level of the LVEA about 1/2 covered with membrane and the lower part (OSB) staged with materials.

cdsfs1 locked up again Wed morning, with the same symptoms it has had in the past when the RAID controller hangs.  I reviewed the logs, but they did not provide any additional clues (other than what we know from previous cases).  I've verified that we are running the current tools versions for the card in the OS.

I've upgraded the firmware to the latest release, 4.10.00.027, as the installed version was rather old.  We will see if this improves things; it may be that we picked up an upstream kernel driver update when upgrading the OS that required the firmware to be upgraded, and we've missed this fact.  That may explain why cdsfs1 has historically been 'more unreliable', because we've updated the OS on cdsfs1 much earlier, and more often.  But this is largely speculation.  We will just have to wait to see if this improves things.

The GV7 annulus has been vented in preparation for spool removal. PT134(beam tube side of valve) held steady at 3e-9 torr while venting.

For future reference I took a spectrum of the 5 HSTS (MC1 MC2 MC3 PR2 PRM) from monday morning before the corner station was vented.

The isolation and damping on HAM2 and HAM3 ISIs were ON, and feedforward was OFF. The suspensions damping loops were closed. The chambers were under vacuum.

The attached pdf shows a comparison between the 5 HSTS, for every "mass" levels (M1 M2 and M3) and every degree of freedom.

Few things to notice on the plot :

- The performances are really consistent from one chamber to an other

- Signal is really close to sensor noise, especially at the bottom mass

- There is an interesting feature between ~0.1Hz and ~1Hz seen for longitudinal transverse and vertical dofs. This is something I would need to double check, but I'm pretty sure it is transmitted ground motion.

(Kiwamu, Stefan)

Triggered by Anamaria (https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=8984) 
we looked into whether we see the same excess noise when the demodulators are driven by 135MHz.

Short answer: yes - it seems to be a characteristic intrinsic to the demod board design.

Long answer:

1) We switched the LO of the 135MHz and 27MHz. The noise stayed with the 135MHz (i.e. both demod boxes act identical).
2) We verified the demodulation gain on the 135MHz board: 6.0mVpkk of RF into the PD input produced 33mVpkk at the monitoring point. That's 14.8dB gain, or a factor of 5.5.
3) The digital gain after this is x2 (single to differential on the demod board) x 10^(45/20) (whitening gain) x 2^16cts/V = 583kcts/V. We measured about 560kcts/V. We put its inverse - 1.8e-6V/ct - as calibration factor into the input filter modules.
4) Plot 1 shows the terminated demod noise, referred to the demod mon point, for the 135MHz and the 27MHz demodulators. To compare to Anamaria's numbers, divide by 5.5 to refer to the demod input.
5) Plot 2 shows the same thing, but taken in analog at the demod monitoring point. The noise agrees. We also verified that there are no outrageous high frequency signals - the largest signal is not surprisingly at 135MHz, with -63dBm at the monitoring point. There is also a 410MHz signal with -73dBm.
6) We also verified that the LO signals look clean - there were no competing peaks. We also took a hi-res spectrum around the carrier - at 100Hz offset from the carrier we have 95dBc/Hz for the 135MHz (-99dBc/Hz for the 27MHz), plots 3-6.

In summary , we cant find anything wrong with the LO signal or the sensing chain - the problem is most likely intrinsic to the design.

- 8:40 Fred escorting visitors out on LVEA (laser safe)
- Praxair inspecting cryo-tubes
- Rick and ¿Peter K.? inside H2 PSL since early morning
- Apollo working at BSC3
- "Roofers" after yesterday's shower, works continue
- 11:30 EX clean toilet
- Micheal L. escorting an "IEEE interviewer" (if I understand correctly)
- 12:00 Cheryl in OSB Optics Lab
- 12:40 Dave reconfigured h1nds0 (read only science framed) so Hugo can perform some tests. (check entry 8064)
- Nchole W., Scott S., and Thomas V. going into BSC2 through BSC3 and do "baffle's" work
 

Nice day, wasn't it?

pablo

The dome and east door of the BSC 3 chamber was removed and walking plates were placed on the work platform. These have not been installed because we have not located the C channel pieces that bolt to the walking plates so the C 3 cover can be secured to the walking plates. We also installed the permanent flooring in BSC 3 chamber. We installed the soft roof that was on the BSC 3 clean room onto the clean room over the cryo pump spool. The SEI soft roof "sock" is on the clean room over BSC 3.

HughR, HugoP, 

Here is the current status of the aLIGO SEI work at Hanford. Everything in red is a change from last status. Everything in green is available.

WP#4183 

To test the data content of the science frame (requested by Hugo) I have reconfigured h1nds0 to read only the science frames for the duration of this test. h1nds1 (which is the default NDS) is unchanged and continues to serve the full commissioning frames. When this test is completed I will revert h1nds0 back to commissioning frames.

(Sheila, Alexa)

532nm power:

@ laser = 52mW

@ M11 = 32.5mW

We inserted a dichroic mirror after M11 in the green path and found the transmitted 532nm light to be 32.1mW and the reflected 1064nm light to be .54mW

I've created a large OSEM overview medm screen, accessible from the sitemap under the CDS tag. It shows all the OSEMS which are currently in the DAQ system.

It can only be displayed on a high resolution iMAC screen (e.g. control room workstations).

(Sheila, Alexa)

See D1201448 for reference. 

We inserted ALS-L1 (ROC=75mm), which we had temporarily removed. Then, with the Mode Master (silicon detector), we spent the day mode matching the telescope along the green path (ALS-L6 and ALS-L7), which were placed for the OAT configuration and not the nominal configuration.

First, we examined the beam profile with the table in the OAT configuration and the mode master 28.5inches from ALS-M11. Image 'OneArmTextEndX' portrays the result. We subsequently removed ALS-L6 (ROC=-100mm) from the path and took another beam profile with the mode master in the same position. Image 'OneArmNoLens' portrays the resullt. We used this data to determine the seed waist of the beam. This seed waist matched that of the optical layout. We proceeded to create an "a la mode" matlab script to determine the proper positions of L6 and L7 with the target waist size of 2.2mm at 184.6inch from M11. Note: the target wasit size was determined via T1200200; the location was determined by measuring the distance from the TransMon secondary mirror to the chamber viewport (TransMon layout (D0902163, D1201457) and assuming the TransMon chamber was 2ft from the ALS table. We determined that L7 was 7inch from M10 and that L6 was 37inch from L7. This gave us a 99% overlap.

In this nominal configuration, we placed the mode master 660mm from M11 (we wanted to better stablize the MM). We noticed that the MM kept giving different results. Images 'ISCEXMM660mm2M11...' are snaptshots of four runs of the beam profile with everything in the exact same position. We were a bit unsure why the MM kept giving such different results. The waist size seemed close enough to 2.2mm; however, the location was drasitically off. We concluded for the day in this puzzled state...(more work tomorrow)

I have also attached the matlab script.

The dust monitor software has been moved to met_one_227b_comp_ctrl-1.0.0 for device support and dust_met_one_227b_comp_ctrl-1.0.0 for the IOCs. The targets in /ligo/lho/h0/target were backed up to /ligo/lho/h0/target_archive and updated. The sitemap has been updated to link to modified medm screens.

The primary change is that the software now controls the timing and puts the dust monitor into 'standby mode' between samples. The sample time and hold time durations can be set from EPICS. I also added code to attempt to reconnect on TCP/IP disconnects.

The IOCs are running in 'screen' on a new virtual machine that Cyrus created, h0epics.

I updated the H0EDCU_DUST.ini file to remove the MODE, TEMP and RELHUM channels and add ACTSAMPLETIME, HOLDTIMEMON, SAMPLETIMEMON, STATE and ISENABLED channels. Dave has rebooted the DAQ and these changes are now in place.

Each dust monitor location is now enabled/disabled by toggling the on/off switch on the medm screens.

I tried to update the alarm configuration file to use the ISENABLED channels to mask the dust monitors that are not running, but could not seem to get this to work.

The wiki pages have been updated.

This should complete WP 4172.

Jim did the hard work and I did the brain thing.  We could only get our level rod to just past half way to the west side from the East door and Jim was really stretching.
We found the vertical level runout from the East side to the center portion of the table to be about 0.047" or about 2.4mm over the whole table.  May have been good enough (per comm RAbbott) but you're talking about SEI & HCR here.  We weren't about to be satisfied.  The elevation was about 1/64" low and that is close enough.  So to level the table we moved one stack of 20kg 2x2" (diagonally NW to SE) to get our calibration.  We then move 10kg 24" ultimately to put us very level.  I redlined a pdf and added this to the DCC, D1200524, to show the as-built of the masses.

Final position: -200.45mm Gz level to +-0.1mm over the span of the Optical Table per D1200524.  Attached is my log book page for this survey.  The numbers there are in local elevations.  At HAM1 subtract the 14.1mm vertical offset to get to the Gz: -186.35-14.1 = -200.45mm

PeterK and RickS
We intended to make weekly PSL performance assessment measurements this morning, but we found that the FSS had not locked since about 4 PM yesterday afternoon.

After 6 hours of so of investigating, we found that there was a mouse in the RF distribution rack (one that likes Swiss chocolate!).

It seems that the 80 MHz RF distribution is being reconfigured.  After restoring the RF drive to the VCO and FSS AOM, the FSS locked right up, the ISS locked, and the system appears on cursory inspection to be operating as expected.

Both HAM2 and HAM3 chambers are now fully controlled (HEPI+ISI). 

Those chambers feature:
- Standardized ISI damping loops (defined in: SeiSVN/seismic/HAM-ISI/H1//Scripts/Control_Scripts/Version_2/Step_4_Damping_Filters_H1_ISI_.m)
- Standardized ISI blend filters (SeiSVN/seismic/HAM-ISI/Complementary_Filters_HAM_ISI/HAM-ISI_Generic_Comp_Filters.mat)
- Hybrid aLigo/eLigo blend filters are available (SeiSVN/seismic/HAM-ISI/Common/Blend_filters/Filters_HAM_ISI_Blend_Hybrid_24_Jul_2013.mat)
- All 3 levels of ISI isolation loops (UGF=10Hz, 25Hz, 35Hz - LHO aLog # 5355). Performance is mostly limited by the blend filters. Level 2 controllers give similar amount of isolation as Level 3. Level 2 controllers are prefferred for now - ISI Perfomance can be found in LHO aLog #7414

- HEPI position blend filters (IPS signals are multiplied by 1, L4C signals are multiplied by 0)
- HEPI position loops. UUG = 2 Hz. Should be set to 5Hz soon. HEPI position loops performance plots, and controllers, can be found in LHO aLog #8037.

Trun on Process:

Prepare:

1. Use the command button to shut down any kind of control on both HEPI and ISI.
2. Make sure the border of the ISI screen is green. If not, check the Watchdogs (model, Dackill, IOP dackill, SUS) and the master switch.

Damp ISI:

1. Use the command button to turn on the damping loops on the HAM-ISI.

Turn on HEPI:

1. Make sure that the following are in the correct state for HEPI: Watchdogs (model, Dackill, IOP dackill, SUS, ISI) and the master switch.
2. Open the IPS screen. Be careful there are 2 of them. One for the vertical sensors, and one for the horizontal sensors. 
3. In this screen, make sure that the alignment offsets are loaded and engaged. We want them to be set at the opposite of the locked hepi IPS redouts referrenced in LHO aLog# 7180
4. Open the DC bias screen and make sure that everything is disengaged - it should be.
5. Repeat (4) for the Sensor Correction screns, the ISC mon, the feedforward (FF) and the Twist.
6. Make sure that offsets are disengaged ont he OUTF screens. Be careful there are 2 of them as well. 
7. Push both gain sliders to 1.
8. Engage the Blend filters named "Pos"
9. Make sure signals come out of those filters. If not, refer to LHO aLog #7299, and follow Sebastian's instructions
10. Check the IPS 2CART matrices. For now, they should look like that. If not, use SeiSVN/seismic/HEPI/Common/MEDM_Functions_HEPI/Populate_Matrices_HEPI.m to fill them out. Do not use Populate_MEDM_Screen_HEPI.m instead, as it will reset a lot of the things you just worked on.
11. Use the "Isolate <Chamber> Lvl1" button of the HEPI command screen, to engage the position loops

Engage the isolation loops, on the ISI

1. Open the Sensor correction block and make sure that everything is disengaged.
2. Open the blend filters block. Make sure that filters named "01_28" are selected. These are the generic blend filters mentioned above.
3. Open the command screen of the ISI ou are working on
4. Wait for the readouts to stabilize
5. Use the "Reset CPS offset button" to reset the CPS biases. 
6. Press the "Store Target offsets" button. This will store the current position so the ISI can be steered back there once the isolation loops are engaged
7. Use "Turn on Lv. 2 isolation loops for ...." button, and wait for the isolation loops to get engaged.

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.

** LVEA has been laser safe throughout the day
** Praxair delivered to CP8 this morning.  The CP8 value on the HOVE overview screen remained near 104 through the lunch hour and now sits at 101.
** Roofers have worked all day on the LVEA roof except for a period this afternoon when the storm was active.
** See John's entry about water leaks in the LVEA this afternoon because of the storm.
** Alexa and Sheila have worked in the HAM6 bay through the day.
** Betsy entered the chamber at EX late this morning.  The ETMX speedometer needles on SUS_OSEM_OVERVIEW are now active.
** The cartridge is bagged on the LVEA test stand.
** Lots of dust alarms through the day at a number of locations.  In most cases the alarms correlated with human activity in the affected areas.  We saw alarms this afternoon from the beer garden dust monitor (5) near 30,000 and it wasn't clear from the cameras if there was activity near BSC3 that was the cause.  Patrick is checking the area to see if there might be a water leak nearby.
** The EX dust monitor went white this afternoon.  Filiberto was in the VEA; he tightened the cable on the rack side and the monitor turned back on. 
** Rick has been working on the ref cav this afternoon

Dan saw the same problems on h1ldasgw0 as he saw on h1ldasgw1 a few weeks ago. He upgraded solaris and rebooted to fix the QFS file system. h1fw0 got into a stuck state, unable to unmount or remount the NFS file system, I had to reboot it using the front panel reset button (it got stuck rebooting too). Unfortunately I accidentally restarted the DAQ in the process.

The data gap on h1fw0 is:

Oct  8 13:44

Oct  8 15:17

h1fw1 was running the entire time, except for the DAQ restart.