[Kiwamu, Sheila, Stefan, Paul]

Today we tried to get the Faraday isolation ratio measurement using the method Chris Mueller described in his LLO alog 8608, but were unsuccessful so far. 

First we had to restore the IMC and several other optics to their previous state after the power outage. We tried looking for the return beam with the viewer cards, but we didn't find any beams that were not present when the mode cleaner was unlocked (as the true PRM reflection beam would be). We expect this is mainly due to misalignment of the return beam from PRM with respect to the IMC, such that little of the return beam actually makes it back through the IMC, instead being reflected from MC3. At LLO when making this measurement this alignment state was already know well since the central IFO alignment can be used as a reference there.

We tried scanning the PRM alignment, but to no avail. We checked at what PRM alignment offsets the REFL beam on ISCT1 becomes clipped, because this gives a good indication of the alignment parameter space for PRM which we need to search within: if the FI rejected beam is not making it back through the Faraday correctly, then the beam we're looking for is certainly is not making it back through the IMC. The beam became clipped within ~±500 urad of our inital alignment values in pitch and yaw. As a rough comparison, IMC transmitted power can be expected to halve for a MC2 pitch misalignment of 60urad, so it looks like we still have some alignment parameter space to search before we would even expect to see the return beam

The other issue we were dealing with was the back reflection from the second mode matching lens, which was close to parallel (~1 deg) with the forward propagating beam. We aligned a PDA55 to this beam as reflected from the second pick off beam-splitter in the path, since it serves as a reasonable reference for the sought after PRM return beam. In order to help us locate the PRM return beam, as well as for the reason that it had to be done at some time anyway, we decided to rotate this lens (see Cheryl's post from yesterday). We were able to do this, apparently without causing too much change in the alignment into the IMC since the IMC transmitted power recovered to its previous value (~1240 counts on MC2 trans) with the WFS loops engaged. The back reflected beam from the second mode matching lens is now easily separated from the forward beam, and has been dumped on a razor blade dump. We estimated the power in this beam to be around 1mW in the absence of the pick off beamsplitters and with the power through the EOM at 1W.

J. Kissel, H. Paris, A. Pele, S. Ballmer, C. Wipf

Yet again today we battled with the HEPI and ISI systems in the ITMY (BSC1) chamber trying to get them back after the weekend's power outage. HEPI is up and running again, but I don't think at the same alignment. The ISI cannot make the final transitions to awesome without its watchdog tripping. Details below. 

I'm leaving the entire ITMY (BSC1) and BS (BSC2) chambers OFF for the evening so DetCharians can follow up on a study of the 10 [Hz] HEPI pier amplification *AHEM* Laura Nuttall *AHEM*. 
Ground STS2 Channels          ITMY HEPI L4C Channels              BS HEPI L4C Channels
H1:ISI-GND_STS_HAM2_X_DQ      H1:HPI-ITMY_BLND_L4C_X_IN1_DQ       H1:HPI-ITMY_BLND_L4C_X_IN1_DQ
H1:ISI-GND_STS_HAM2_Y_DQ      H1:HPI-ITMY_BLND_L4C_Y_IN1_DQ       H1:HPI-ITMY_BLND_L4C_Y_IN1_DQ
H1:ISI-GND_STS_HAM2_Z_DQ      H1:HPI-ITMY_BLND_L4C_Z_IN1_DQ       H1:HPI-ITMY_BLND_L4C_Z_IN1_DQ
H1:ISI-GND_STS_HAM5_X_DQ      H1:HPI-ITMY_BLND_L4C_RX_IN1_DQ      H1:HPI-ITMY_BLND_L4C_RX_IN1_DQ
H1:ISI-GND_STS_HAM5_Y_DQ      H1:HPI-ITMY_BLND_L4C_RY_IN1_DQ      H1:HPI-ITMY_BLND_L4C_RY_IN1_DQ
H1:ISI-GND_STS_HAM5_Z_DQ      H1:HPI-ITMY_BLND_L4C_RZ_IN1_DQ      H1:HPI-ITMY_BLND_L4C_RZ_IN1_DQ
H1:ISI-GND_STS_ITMY_X_DQ      H1:HPI-ITMY_BLND_L4C_HP_IN1_DQ      H1:HPI-ITMY_BLND_L4C_HP_IN1_DQ
H1:ISI-GND_STS_ITMY_Y_DQ      H1:HPI-ITMY_BLND_L4C_VP_IN1_DQ      H1:HPI-ITMY_BLND_L4C_VP_IN1_DQ
H1:ISI-GND_STS_ITMY_Z_DQ 
which I've confirmed are in the frames. Chris is going to do a few more things with the IFO, but things should be off by 00:00 PDT, 07:00 UTC Oct 1 2013, 1064646016.

--------
HPI-ITMY

The goal here was to get HPI to the same alignment we had during HIFO-Y (see LHO aLOG 6566). However, the biases had been reported in the Colocated basis and we want to progress forward, sticking these biases in the Cartesian basis in calibrated units. After a few unsuccessful attempts, we finally

- Turned the position isolation loops OFF
- Turned the input to the IPSINF banks OFF
- Inserted the desired input readings as offsets in the IPSINF bank
- Read off the corresponding values at the input to the blend filter bank (letting the front end do the appropriate basis conversion and calibration for us [thanks Stefan!])
- Turned the IPSINF offsets OFF
- Turned the input to the IPSINF banks ON
- Turned the 100 [mHz] UGF "position" lock isolation loops ON (watching as the inputs meander off to some weird location)
- Installed the desired Cartesian values and a 10 sec ramp into the DCBIAS bank, turned them ON.


For the first few minutes, the plan worked like a charm; inputs to the IPSINF moved to exactly where we wanted them. However, after those few minutes and currently, the location has drifted to some other location, mostly in horizontal DOFs. Other commissioners were not as successful at restoring light this far into the interferometer, so we never got the chance to test whether this alignment is good enough. Out of frustration, we'll leave it as is.

Here're the final results:
Colocated Channel             Value [ct]  |  Cartesian Channel               Value [nm or nrad]    CART Bias Channel              [nm or nrad]    
H1:HPI-ITMY_IPSINF_H1_INMON    -873.2     |  H1:HPI-ITMY_BLND_IPS_X_INMON    -7156.64              H1:HPI-ITMY_DCBIAS_X_OFFSET  = 7156
H1:HPI-ITMY_IPSINF_H2_INMON    -822.083   |  H1:HPI-ITMY_BLND_IPS_Y_INMON    -33425.1              H1:HPI-ITMY_DCBIAS_Y_OFFSET  = 33425
H1:HPI-ITMY_IPSINF_H3_INMON   -2786.58    |  H1:HPI-ITMY_BLND_IPS_RZ_INMON   -4374.85              H1:HPI-ITMY_DCBIAS_RZ_OFFSET = 4374
H1:HPI-ITMY_IPSINF_H4_INMON   -3773.34    |  H1:HPI-ITMY_BLND_IPS_HP_INMON   -1073200              H1:HPI-ITMY_DCBIAS_HP_OFFSET = 1073200
H1:HPI-ITMY_IPSINF_V1_INMON   -6121.07    |  H1:HPI-ITMY_BLND_IPS_Z_INMON    -71553.4              H1:HPI-ITMY_DCBIAS_Z_OFFSET  = 71553
H1:HPI-ITMY_IPSINF_V2_INMON   -1038.65    |  H1:HPI-ITMY_BLND_IPS_RX_INMON   -46597.7              H1:HPI-ITMY_DCBIAS_RX_OFFSET = 46597
H1:HPI-ITMY_IPSINF_V3_INMON    2772.24    |  H1:HPI-ITMY_BLND_IPS_RY_INMON   +72672.               H1:HPI-ITMY_DCBIAS_RY_OFFSET = -72672
H1:HPI-ITMY_IPSINF_V4_INMON   -2990.78    |  H1:HPI-ITMY_BLND_IPS_VP_INMON   +75188.8              H1:HPI-ITMY_DCBIAS_VP_OFFSET = -75188 

      
-------
ISI-ITMY

The goal was to get the ISI in as best-performing state in order to use the GS13s (our best sensors of the isolation system at this point) to measure whether the 6.18 [Hz] feature had been reduced as much as had been shown by Arnaud in LHO aLOG 7919. As Hugo had stated earlier (see LHO aLOG 7915), he and Arnaud got things most of the way up, but not nearly as good as Vincent's work during the original discovery (see 7747) because the configuration Vincent outlines has just enough typos to be confusing.

So, I tried my hand at it, having had a few more conversations with Vincent about the configuration but to no avail. My attempts failed at various points along the way, but most often because the watchdog would trip on the actuators as I'd tried to switch in the T240s to the ST1 blend filters. I'm too tired to dig in deeper, but we'll try again tomorrow.

Here's what I found broken / frustrating / interesting along the way:
- The ISI-ITMY model must not have been restored to a good time (or not at all). The damping loops were OFF entirely (inputs, outputs, gains, and filters). I restored them by hitting the "damp ITMY" command script.
- The damping loop status lights are red when functioning nominally. The "correct state" is set to 0x6000034, when the current state is 0x1401 and the loops are running as designed. This should be an easy fix.
- ctrlDown of the isolation loops is now a part of the front end, so one no longer needs to remember hit the command button before restarting the isolation process.
- The ST0 to ST1 feed forward is not a part of the ctrlDown or isolate command scripts. One has to manually remember to SLOWLY ramp them off (or on).
- The Sensor correction is not part of the ctrlDown or isolate command scripts. One has to manually remember to SLOWLY ramp them off (or on).
- The Sensor Correction overview screen is grouped by degree of freedom instead of by instrument source -- and otherwise it looks identical. These should be at least *colored* differently. It's tough to tell whether I'm turning on the ST0 L4C sensor correction (which I shouldn't) or the GND STS2 sensor correction (which I should).
- The TRAMP for the MATCH banks on the Sensor Correction overview screen is missing. I had to dive into the MATCH banks internal screen to get to the TRAMP.
- The full filter bank sub-screens for anything on the Sensor Correction overview screen are not obviously accessible. You can do it by just clicking around blindly and landing on a hidden link, but there's no obvious button like there are for most other sub-screens.
- The FULL command script for "isolate ITMY lvl3" froze several times in the middle of ramping up ST2. I didn't diagnose why, but it fails in the middle of ramping up the ST2 RX and RY loops. I had to run ctrlDown and run each of the Stages (and at one point each of the degrees of freedom) separately.
- The "isolate ITMY lvl3" script turns on the "Boost_2" filters.

Here're some good philosophical discussions that came up:
[Kissel with himself]
- "There's a 'switch all' screen on the blend filter screen for each stage. Vincent at one point [a month ago now] had set it up that -- even though not all of the blends were the same for each DOF -- the Y DOF's filter characteristics defined the name of all the DOF's filter names for that level of button. This way, the user knew 'I get the best performance if I hit the "T40mHz_NO.44' button on the switch all' screen." This is opposed to having to know the best blend for each of the 6 DOFs and in which order to switch them in. 
I prefer the "one-button switches in all the right blends." Much better for configuration control.

[Ballmer with Kissel]
- Instead of writing in Perl, Python, or folding it into the Guardian structure, we should now have the ability (thanks to the cdsCtrlFilt2) to move the entire isolation loop turn on dance into the front end as a c-code state machine. This, if coded correctly
(1) shouldn't take more than a month off offsite development, 
(2) removes all reliance on the EPICs network and interaction with scripts,
(3) makes the user/guardian interface a more straightforward state-machine, and
(4) removes flexibility to mess things up.
I think we should do it.

HugoP, JimW

After finishing up floating and balancing the ISI this morning (Stage 2 was floated on Friday, Stage 1 required minimal adjusting this morning), we started testing the ISI in the afternoon. First we built and installed a recently updated BSC model, then populated the MEDM, then used a somewhat shady epics variable short cut (exclusive to the ISI test stand) to de-activate the SUS watchdog (the quad is on stops, so the watchdog is not doing anything right now, anyway). After all that, we were able to start driving, first the actuator static local basis test to verify the actuators behaving properly, and now an overnight transfer function. Should finish by the morning meeting.

With Patrick and Filiberto's help, the EX Beckhoff system is now running.  The Twincat System Manager sees all EX components, and keepalive signals are propagating down the fiber link from the corner to EX and vice versa.  Here's the documentation we followed to get the fiber links working: http://infosys.beckhoff.com/english.php?content=../content/1040/el6692/html/bt_el6692_functionality.htm

MEDM screens went live after we started Maggie's EPICS server, using the command C:\SlowControls\EPICS\Utilities\Bin\start_h1x1.bat

Cabling out to the electronics in the VEA still has to be set up and tested.

[Hugo Jeff Arnaud]

Now that one of the satellite box of ITMY (see 7780) has been changed, and following Jeff's and Vincent's investigation on the 6.18Hz noise injected from sus to sei (see 7720 7709 and 7609 for details), a spectra of GS13 on stage 2 of ISI has been taken (using Vincent's scripts), as well as a spectra of the left and right osems before and after changing the sat amp, with the ISI isolated level 3, and the suspension with all the damping loops closed. The pdf attached are described below :

(1) Light blue is GS13 from Sept 10th before the sat amp was changed, and the 6.18Hz peak is present. Dark blue from Sept 30th, and we don't see the peak anymore. Pink and Violet are showing ground motion.

(2) Dashed curves are left and right osems from September 10th before the sat amp was changed, the 6.18Hz peak is present. Plain blue and red are from September 27th, after the sat amp was changer, the peak is a lot reduced.

From those plots, it looks that changing the satellite box reduced the peak by a large amount.

We would need to get the ISI to the requirements, as shown on dark blue of first pdf, and do the same measurement, in order to conclude that it entirely fixed the problem.

Joe Gleason, Pablo Daveloza, Keita Kawabe

We attempted to balance the RM2 Tip Tilt optic by shifting the wire clamp mounting block in the optic holder but were unable to do so at the limit of its range.

We elected to install the optic in a new suspension assembly from the set for HAM6. The new assembly also required a large change to the wire clamp positions but we were successful in getting it balanced. We performed the remaining setup on the assembly and bagged/stored the assembly in the temporary clean room outside HAM2.

SEI -- JimW MitchellR & Hugh
We figured we could tolerate a few errant pounds for this initial floating.  All the pre-install weight is on and while the ISI likely won't balance at the moment, it should be really close for the HEPI payload.
So BSC9 ETMx HEPI is unlocked and we leveled the Optical Table pretty well (ISI is still locked).  So I believe SUS and TMS can shed their extra loads now.  We may want to keep the glass locked until the ISI is unlocked and balanced.  Also, some initial IAS work can possibly go forward now.

Shift started out with a windy morning and the Control Room in a post-power outage glitch state.  Here are today's activities:

• Recover from Power Outage.  Back to normal around 11:15am (Jim & Dave)
• Sheila restored PSL from the Outage
• LVEA transitioned to Laser SAFE to install/swap HAM1 Feedthrus (went back to HAZARD in afternoon)
• Cabling/fiber work at EX (Filiberto/Cyrus)
• Arm Cavity Baffle work continues (Thomas)
• SEI crew working on the BSC9 ISI (Jim & Hugh?)
• Ken drilling on pedestals on Y-Beam Manifold for cable trays
• Patrick did work with PSL & Dust monitors
• HAM6 cabling/grounding work (Elec crew)

I ended up power cycling the PSL environmental chassis and rebooting h1ecatc1. I was testing code for the rotation stage and had put things in a bad state. It should be recovered.

Restarted IOP models for the triple test stand and the bsc test stand in the staging building after power failure.  Made sure that DAQ was running on each.

ITMY-ISI controls were turned back ON for the 6.18Hz peak investigation.

Stage 1-2:

- Level 3 Isolation Loops
- T750mHz blend on RX, RY and RZ  (750mHz blend that includes the T240s)
- T100mHz_NO.44 on X, Y and Z         (100mHz blend including Trilliums, with notch)

Stage 0-1 feedforward is ON.

After Dave restarted the front ends, hepi itmy matrix values were empty. I restored them as they were friday morning, turned the master switch and all the loops off, and saved a new safe snapshot from that config.

A soft link from /opt/rtcds/lho/h1/target/h1hpiitmy/h1hpiitmyepics/burt/safe.snap -> /opt/rtcds/userapps/release/hpi/h1/burtfiles/h1hpiitmy_safe.snap has been created

h1hpiitmy_safe.snap has been commited to the svn

sw-msr-h1fe decided to reboot itself today at 10:45AM, the cause is unknown but most likely related to the power problems earlier in the morning.  When I went looking for syslogs for possible clues, I realized that none of the Netgear switches had remote sysloging enabled, so I took the time to make that configuration change on all the switches, as well as the Fujitsu DAQ broadcast switch.  The installed Cisco switches and APs already had syslog logging enabled.  There is no guarantee that having syslog messages will give any indication of what caused a problem (in this case reboot), but it provides more information than none at all...

Due to a pair of power failures, the DAQ test stand needed to be restarted.  All front end computers were rebooted.  The x1ldasgw computer was locked up and was rebooted.  The DAQ computers which mount the SATAboy disk array were also rebooted once the x1ldasgw was operational in order to get the file system mounted and the daqd processes running.  Finished about 11:45 PDT.

(David Barker, Cyrus Reed, James Batch)

LHO experienced a 2 second power fail at 00:40:43 PDT and a power glitch at 06:06 PDT which caused front end reboots.  Also affected were both CDS file servers.

The main file server entered a read-only state, while the backup file server locked up and was unresponsive.  Both file servers were restored by 08:30 PDT.

All front-end computers were powered off, as several were not logically attached to their I/O chassis.  On power up, the following computers still could not find the I/O chassis:

h1seib1
h1seih45
h1sush2b
h1susquadtst
h1susex
h1susexaux

In each case, turning the power switch on the front of the I/O chassis from on to off to on caused the I/O chassis to power up.  The computers were then power cycled to get the I/O chassis reattached.

At this point, there were IPC problems in which channels could not be received from the following computers:

h1lsc0
h1asc0
h1seih23
h1seih16
h1seib2

In order to correct this problem, the Dolphin switches in the MSR needed to be power cycled, which in turn required all computers in the MSR that were attached to the Dolphin network to be power cycled.  Once this was accomplished, and a few models manually restarted, all appears to be well.  The system is back in operation as of 11:30 PDT.

after the power glitch the PSL had to be restarted.  Justin and I followed the procedure to start it in low power mode, we reset the kepco HV supply to 200mA, as Christina wrote in her alog instead of the 400mA in the procedure.  We also reset the LRA, even though we were starting it in low power mode I wasn't sure if the beckhoff computer had lost power or not.  

The only hitch was that we couldn't open the external shutter, the situation was similar to  last time , 
H1:PSL-MIS_FLOW_OK was 0, although H1:PSL-MIS_FLOW_INMON was within the limits.  We tried the reset button on the medm screen, which didn't do anything, and we tried caput which also didn't change the value.  Jim and Dave managed to open it, they will write a log about what they did.  

The PMC is now locked, but the medm screen reports -30W transmitted power.  H1:PSL-PWR_PMC_TRANS_GAIN is now -0.024, while it was 1 before the power glitch.  

The ISS is not staying locked, which was also the case before the power glitch.  

[JoeG, Keita and Kiwamu]

We continued working on the HAM1 installation this afternoon.  All the optics except for the detectors are now on the table including the newly installed QPD sled. We removed the counter weights although didn't check the table level yet.

Besides, there are two (unhonourable) highlights to mention from today's HAM1 incursion.

1. The mirror of a tip-tilt (RM1) was found to be backward. So we flipped it to the right direction in situ.
2. The other tip-tilt (RM2) started showing a too big pitching

A big pitching in a tip-tilt (RM2):

After the removal of the counter weights we went through the alignment process again in the in-vac detector path. The alignment needed a slight touch mainly in pitch. Then we found that RM2, which is a tip-tilt , showed a large pitching so that the reflected beam went too low. Joe tried to correct it by screwing the bottom 8-32 screw further in. This screw is designed such that as we screw it in, the center of its mass changes the pitching of the whole holder (so as to lower reflected beam). We wanted screw it in further but however the screw was too long and in fact it was already touching the back cage. Keita brought a shorter screw which is 8-32 x 1" and we tried this. However sadly it still hit the back cage because of too large pitching. Joe translated the upper blades to the front to separate the back cage and holder further apart, but this didn't fix the issue. Note the mirror holder was picthing in the same direction even without the screw.

According to our inspection, the clamping point of the wire on the left wire clamp (when looking from the front) on the mirror holder is too close to the back side. Probably about 1 mm off from the center toward the back side. The other side looked also close to the back side but not as big as the left side. At the moment we think this gives such pitching in the mirror holder. Pictures of the clamping point for both left and right sides are attached below. You can see how they are clamped through a rectangular window of the side cage. We have no idea of if it has been like this or when and why this happened. Adjusting the clamping point is certainly beyond what we can do in the chamber because it probably involves with all the alignment and adjustment process. Therefore we removed the tip-tilt our of the chamber. It is now in the clean booth nearby HAM1.

Plan :

 Next week we will bring another tip-tilt which was assembled for HAM6 and swap the bad one with it. Hopefully we can smoothly place the tip-tilt and move on to some measurements for checking the mode matching.