During the red beam lock, the 2 HEPIs and ISIs (BSC1 and BSC6) were supposedly in the state given by alog https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=7235. By the time, the HEPI at BSC1 was locked. Some information were extracted from the 15-minute lock. ISIs provide great isolation above 100mHz but the motion increase below 100mHz is not negligible and can become problematic to lock the cavity. The results present the ISI’s contribution in the arm’s length variation.

The arm was kept locked using the red beam.  The green beam is used as a witness sensor.
 

1- State of the ISIs
The attached spectra (H1_BSC_ISI_ST2_GS13_Y_20130726.jpg) show the motion of stage 2 in the Y-direction of the 2 BSC-ISIs (ITMY and ETMY) during the lock.
On ITMY (red curve):
- It is not sure if the sensor correction was engaged properly (no amplification at low frequency and no and important motion at 700mHz)
- The resonance of the HEPI pier is clearly visible at 11.5Hz

On ETMY (Blue curve)
- Above 2 Hz, the motion is much larger than on June 14^th - Reference in black (same configuration?)
 

2- ASD of the arm’s length seen by the green beam
The ASD of the green beam is presented in attachment (H1_GB_Cavity_Length_Red_Lock_20130726.jpg).
The large motion seen around 40mHz is created by the ISI (mainly ETMY cf Coherence). The aggressive filters used for the sensor correction strongly amplify the ISI motion around 50mHz. It’s a tradeoff between amplification below 100mHz and a “0 degree phase” above 100mHz.

3-Coherence from the ISI drives to the cavity length
Once the HEPI and the ISIs are controlled (ground excited only), I used the control drive (Isolation filters output, damping filters output negligible) to evaluate the coherence from the drive to the length of the arm. Coherence in the bandwidth of interest (0-200mHz) are presented in the video at: https://svn.ligo.caltech.edu/svn/seismic/BSC-ISI/H1/Common/Misc/Video/H1_ISI_Coherence_Cross_Coupling_20130725.avi, channels are:
- 1 to 6: ETMY stage 1 drive in the direction X, Y, Rz, Z, Rx, Ry
- 7 to 12: ETMY stage 2 drive in the direction X, Y, Rz, Z, Rx, Ry
- 13 to 18: ITMY stage 1 drive in the direction X, Y, Rz, Z, Rx, Ry
- 19 to 24: ITMY stage 2 drive in the direction X, Y, Rz, Z, Rx, Ry
- 25: Y-arm length

NB: Index 1,1 is at the bottom left (The diagonnal is going up). The matrix is symmetric.

From 40mHz to 60mHz where the motion is maximal, the coherence matrix shows:
- the 2 ISIs were maybe in a different state (block matrix 1:12,1:12 very different from 13:24,13:24). Was the sensor correction engaged properly on ITMY? It is difficult to evaluate at posteriori. The sensor correction might be also less effective on ITMY since the STS-2 installed in the beer garden is relatively far from the chamber (in comparison with ETMY). Is there a reaction from the HEPI (locked in for ITMY and unlocked for ETMY)?

- ETMY
    -The coherence is important from stage 1 Y drive to length, stage 1 Ry drive to length and stage 2 Y drive to length.
   - The cross coupling drives are important
   - There is an important Z to Rz cross coupling (bad positioning of the horizontal CPS)

- ITMY
   - There is some coherence from stage 1 Y drive to length, stage 1 Ry drive to length and stage 2 Y drive to length. The coherence from the drives to the length is globally lower than ETMY.
   - The cross coupling drives are moderate
   - There is an important Z to Rz cross coupling (bad positioning of the horizontal CPS)

Some measurements are currently running to evaluate the tilt (X->RY and Y->Rx). The translation to tilt coupling will be used to correct the position sensor signals. This correction is used to take care of the CPS misalignment.

We can also notice a good coherence between the two ISIs on stage 1 in the Y  and Z direction and stage 2 in the Z direction.

4- Coherence between the STS-2s and the arm
The coherence between the STS-2 and the arm is presented in the video https://svn.ligo.caltech.edu/svn/seismic/BSC-ISI/H1/Common/Misc/Video/H1_STS2_Coherence_Cross_Coupling_20130725.avi Channels are:
- 1:3: ETMY STS-2 X,Y,Z
- 4:6: ETMY STS-2 X,Y,Z
- 7: Y-Arm

The coherence at 60mHz is shown in attachment H1_STS2_Coherence_Cross_Coupling_20130725.jpg. Around 60mHz, the coherence between the corner station and the EY is important in the Y and Z directions. The coupling beween the ground Y direction is important. The ground motion is amplified by the sensor correction of the ISI then visible in the cavity.
 

5- Contribution of the drives in the arm's length
I am currently trying to evaluate what is the contribution of each drives in the arm.

At 10:45 last night (local) the DAC outputs of h1seih23 went to zero (and latched there) and the WD error bit was set on the IOP STATE_WORD. We worked with Rolf to diagnose the problem. For this error to have occurred there must have been a DAC FIFO error. He looked at the /proc/h1iopseih23/status file and it is showing no current FIFO errors. He has not seen a DAC FIFO error come and go before. With no futher online diagnostics needed, I restarted all the models and handed the system back to Hugo for HAM2 commissioning at 10:54 this morning.

A trend of the IOP STATE_WORD shows the WD bit being set at 10:45 Wed evening, which was latched on until this morning's restart. At two occasions overnight the DAC bit was also briefly set for less than a minute each time.

Rolf is looking into the code to see if additional diagnostics can be applied in future releases of the RCG.

Kyle, Gerardo 

Today, after John had notified Rai of our intent, we applied a few drops of Vacseal (SPI Supplies, Space Environment Laboratories, original formula 0502-AB) to the top of the previously identified leaking 1.33 CFF on GV6 (North gate annulus port).  The leak seams to be fixed now.  

I stopped h1fw0  to allow Dan to grow the SATABOY disk system controlled by h1ldasgw0. He merged the H1 and H2 SATABOYS into one disk system, doubling H1's capacity.

here are the times between which no frames were being writen by h1fw0

EX -----------------------
- ETMX alignment - Jason in AM
- TMS - Keita
- Betsy - at ETMX late AM and after lunch

EY -----------------------
- electronics - Filiberto

Corner ----------------------
- HEPI - Hugo and Hugh
--- Hugo - any electronics work on HAM2/3? - unable to drive due to unknown issue with IOP watchdog - see alog from Dave/Rolf

- H1SEIH23 IOP STATE WORD - actual real problem related to Hugo's 
--- Dave and Rolf looking into it - MEDM colors wrong (green when channel is really red) - see Dave's alog

- Travis - at ITMX

- DUST LAB1 and LVEA16 calibration failure

MX -------------------
CP6 filled - alarmed, but is OK now

Travis, Jason, Betsy

Over the last 4 days, we have worked to tune all 12 DOFs (6 each lowest mass on 2 chains) to within the IAS tolerances.  As usual, since all DOFs crosstalk, we took many roundabouts, but finally think we have acheived it.  Jason will append final pointing/position numbers.  TFs taken tonight will exhonorate this "final" pointing.  After TMS joins us on the table (still a few days out) and finishes their IAS alignment, we will finish payloading the QUAD.

Note, the alignment process takes many days because after each adjustment, many mechanical brackets and structural items need to be realigned such that the BOSEMs are in range and we can turn the damping on in order to make another IAS measurement of pointing.  As well, we have to maintain the floating OSEM/magnet pairing alignments on the lower stages which cause the chain to go out of alignment due to their own weight.  Then, IAS makes a measurement, we make the pointing adjustment in the chain, readjust the floating OSEM/magnet pairs (often at the cost of some of the point adjustment we just made), readjust many mechanical brackets, reenable damping everywhere, repeat IAS alignment, cycle around again.

(Alexa, Kiwamu, Stefan)

Attached is a graph of the noise budget we have been developing for the ALS HIFO-Y control model. A detailed documentation of the model and results will be avaliable shortly.

The following transfer functions are being measured overnight:

HAM2: Tilt decoupling frequency measurement
HAM3: Tilt decoupling frequency measurement
HAM6: Local to Local transfer functions for Initial In-Chamber testing 

EY Oplev pier disassembled (Thomas)

HEPI fluid work at EX (Hugh)

Craning Clean Room "skeleton" in preparation for move to EY (Apollo)

As-Built drawing check of racks at EX & EY (Dave, Jim)

TMS Assy work at EX (Andres, Cheryl, Jeff, Keita)

A couple of big tours of kids (with Dale)

[Kiwamu with a help from Christina@AEI remotely]

 Today I made some efforts to bring the ISS back on by following an instruction by Christina and made it sort of running --- the loop can be closed by the autolocker but the diffraction power seems bit too high and also the gain seems too low. Certainly the ISS needs further investigations.

• Reference signal
  • Initially I tried to set it to be 1/5 of the DC signal of PDA which was 8.5 V.
  • -1.7 V at the reference signal didn't work -- it unlocked the ISS loop because of a too big signal at OSCILLATION_MON_LP.
  • I empirically ended up with a reference of -1.62 V which seems giving us a stable lock.
  • However this gave me a big diffracted power of about 16 % and I guess this needs to be about 10 % according to the strip chart in the ISS medm screen.
• GAIN
  • Initially this was set at 7 dB.
  • I increased the gain by 6 dB but it seems that a higher gain induces an unknown oscillation at about 100 kHz. This was clearly visible at the outer loop PD output in an oscilloscope.
  • Toggling the noise eater didn't change the situation.
  • So the gain was set back to 7 dB.

Yesterday, after suffering severe brain damage via knocking the massive mechanical test stand numerous times with my head, I managed to connect the balance of the suspension wires between all stages of the ITMx QUAD while mounted to the ISI.  The QUAD is ready for coarse alignment which will take many days before assembling the OSEM control brackets and lacing cables.  Deepak has been helping us with this work, including getting the cable brackets mounted for upcoming testing.

The optical lever for ETMY that was used in the OAT and HIFO-Y has been de-installed and dis-assembled in preparation for the cartridge transfer from BSC6 to BSC10.  The leaner pylon will be placed in storage and an opposite-handed leaner will be used for the H1 optical lever configuration, but the transmitter pylon is transferable so it will stay at the EY until we re-install the H1 optical lever.

Late entry for Tues 6th Maintenance.

The Vacuum Controls VME system in the corner station mechanical room (h0vemr) was booted against the new Linux based vxworks boot server as a first test. The plan is to migrate all Vacuum VME sysems from the legacy Sun Solaris boot servers to the new server, at which point the Sun servers can be decommissioned. This will reduce the power and heat loading of the MSR, and remove reliance on an old RAID unit which is showing errors.

[Stefan, Jamie, Kiwamu]

 After a couple of small tweaks, the IMC came back to the point where it routinely locks.

Since there will be a couple of scheduled measurements tonight for HAM2/HAM3 HEPIs/ISIs/SUSs, we disabled the autolocker so as not to disturb the measurements and also not to drive the FSS crazily.

• Small Tweaks:
  • H1:SUS-MC2_M3_LOCK_L_GAIN was decreased from -600 to -300.
    • Since the LOCK filters had been changed to Livingston ones recently, the gain wasn't too high to have a cross over frequency of about 20 Hz.
    • Currenlty FM3 and FM9 are used for acquiring its lock. Once it grabs a fringe FM2, which is a boost, needs to be turned on.
  • H1:SUS-MC2_M2_LOCK_L_GAIN was set to be 0.2
    • This was somehow found to be zero.
    • Currently only FM4 is used.
    • During the acquisition GAIN is set to be zero and needs to be ramped up to 0.2 once it is in lock.
  • We checked the I and Q signals of the IMC length signal at the floor and made sure it hadn't changed.
    • It seems the same as that we had before (alog 7181) on the oscilloscope.
    • Therefore the WFS must be also the same as before.
  • We enabled MC1/2/3_M1/2/3_LOCK_P/Y_OUTPUT such that the WFSs can act on the top mass of the MC suspensions.
    • They were off for some reason and hence the WFSs wasn't properly working.
    • The WFS loops seem working fine.
  • We haven't do a characterization of the IMC lock loop after these little tweaks.
    • At some point the cross over frequencies need to be revisited.

TMS tele/table was released from the support bridge, stabilizer bars were detached, all on-table cables were installed, and then the entire structure was put on a scale using Genie lift with a TMS lift tooling.

It was measured 79.5kg. Nominally it should be 82 so we'll have to add some masses.

Then we wanted to balance the entire structure on a balance bridge tooling, we had the bridge itself but it turns out that we don't have a special bolt and a pin that provide pivot point for balancing, it seems like all units are still at LLO. We're stuck, so no mating to the SUS today.

Wrote an email to Matt Heinze, if he finds them we'll be back to business.

Attached are plots of dust counts requested from 4 PM August 5 to 4 PM August 6.

CP5 filled
Constantly high dust counts in all three OSB optics labs
Jim B. updated the control room CDS workstation GDS tools
09:06 Ace Portable Toilets on site
10:16 spike in dust counts at end Y, possibly coincident with Hugh R. flushing HEPI air lines
Hugh R. reported he could not control medm screens from end Y, had me update HEPI pump control settings from control room
10:21 - 10:30 Cyrus R. reconfiguring and rebooting the mechanical room vacuum VME crate, MR INST AIR went invalid for a short period
10:34 Paradise water delivery
11:13 Hugo P. updating HAM ISI master model
11:49 Hugo P. restarting HAM ISI models, DAQ restarted

J. Kissel, H. Paris, A. Pele, B. Shapiro

After spending all afternoon getting all the chambers up into their best (local) performance, I've used Stefan's instructions to lock the Y ARM on Red. So easy -- even I could do it! Thanks to all of those who've written scripts to automate the ALS and IMC :-). Interestingly, and I forgot to ask about it, but there's no need to run any down script when the lock is lost. One just runs the two scripts again (assuming your Beam Splitter alignment remains good).

OK, I wrote the aLOG too soon. There have been several lock stretches, and the ISI-BS has tripped. I detailed time line is written below, for as long as I stayed here.

Here's the configuration of the SEI/SUS during these stretched:

Cavity Lock: 
Chamber    HEPI                                   ISI                               SUS
HAM1       Locked                                 n/a                               n/a
HAM2       Floating, Alignment Offsets Only       Level 2 Isolated                  MC1, MC3, PRM damped Level 1.5; PR3 damped Level 1.0
HAM3       Floating, Alignment Offsets Only       Level 2 Isolated (eLIGO Blends)   MC2, PR2 damped Level 1.5 
BS         Level 2 Isolated (Position Locked)     Level 3 Isolated*                 BS damped Level 2.0
ITMY       Locked                                 Level 3 Isolated                  ITMY damped Level 2.1
ETMY       Level 2 Isolated (Position Locked)     Level 3 Isolated                  ETMY damped Level 2.1, TMSY damped Level 2.0

* I noticed ISI-BS had tripped around 2:53 UTC, but it may have been down for some time. I didn't bother bringing it back up, 'cause I didn't want to blow the cavity lock. Or another three hours.

All Optical Levers are well centered.

All BSC-ISIs have been brought up to the configuration outlined in LHO aLOG 7226, but just for posterity, this means:
Level 3 Isolation Filters
Blends at ST1 "T250mHz" and ST2 "250mHz"
GND to ST1 STS2 Sensor Correction is ON (The corner station ISIs are both using the beer-garden STS2)
ST1 to ST2 T240 Sensor Correction is ON
ST0 to ST1 HEPI L4C Feed-Forward is ON (with "FF01_2" filters)
The Input Gains for the L4Cs and GS13s are OFF (I *think* this means they're in low -gain mode). They're ON for the T240s.

----------
Time Line (all times UTC, Jul 25 2013)
2:27 Locked on Red
2:46 Lost Red Lock
2:47 Regained Red Lock
    2:50 Glitch in CARM_IN1!
    2:53 Noticed ISI-BS had tripped. All other ISIs are still fully operational
    2:57 Glitch in CARM_IN1!
3:00 Lost Red Lock
3:06 Regained Red Lock
    3:11:23 Glitch in CARM_IN1! 
    3:24:47 Glitch in CARM_IN1!
3:27 We begin to ignore the IFO and go home, be cause there's enough data in the can to get a 0.01 [Hz] measurement in the past (assuming those glitches don't spoil the spectra)... but may the lock last through the night!