Late last week after we aligned the entire SR chain with the PSL beam, re rediscovered that we had left the ITMx clamped.  So this morning, I entered through HAM 4 (since we have blocked off the door to BSC3 for laser safety reasons) and unclamped the ITMx.  Hopefully the realignment now will remove some of the bias we had to put on the BS to shoot to the center of SR3.

After adding a peek tab and waiting a while this AM, I attempted to pull the little 1" sheet of FC from the SRM-HR (surrogate optic) surface.  THe peek tab pulled off, removing a perfect square window behind it where the peek tab had been.  SO, I filled in the hole in the sheet with more FC and reattached the peek tab in another location around the pericmeter of the sheet.  After ~45 mins the peek tab pulled the entire sheet off (with N2 blow).  On to re-alignment of the SRs.

So the crew could climb into the plenum, HAM4 HEPI was put on its mechanical stops.

Translational dofs shifted from controlled position less than 60um.  Rx tilted -4urads, Ry tilted 2urads, & Rz rotated 3urads; hopefully that is close enough.

What I was able to hear from meeting:

• SRM alignment check this morning? (pull first contact (Betsy),  laser hazard (Justin), & check)
• Lower SR3 OSEM adjustments this afternoon when Laser SAFE (Jeff/Andres)
• Status:  SEI HAM4 & 5 balanced, & locked
• SR2 (calum/kate) start cleaning while locked?
• ITMy--coarse alignment, address 2mm misalignment? 
• BSC3--trying to close, wait for clean by Calum/Kate cleaning
• BS--parts (wire protection baffle) in C&B/avail Fri for installation?
• EX Status:  vent slated today (door off tomorrow), no first contacting required of ETMx,need ISI locked, need laser hazard (but can transition when needed). 
• EX:  TMS first part of week, may want to correct TMS pitch (which has been corrected by using HEPI up to now)
• EX:  PCAL starting midweek.  need new SOP for their laser
• EY--bakeout of deionizer (out Fri), drill holes for it? 
• EY--pulling cables for beam centering wfs
• EX pulling cable for dust moniters (require code change)
• RCG upgrade for Channel Monitoring (Jamie), parisitic checks, possibly use/test with ETMy
• Viewport surveys:  HAM4,5, BSC3
• Detchar Meeting Mon-Wed this week
• Film crew here this morn
• Jordan & Paul new students from UofO arrived

The power watchdog for the frontend laser was (re)started this morning.

On a side note, the water level in the crystal chiller was about half way between maximum and minimum.  I added 200 millilitres to bring the level up to maximum.

no restarts reported.

no restarts reported.

Worth noting - we had a strong EQ yesterday (an M6.5 off the coast of Japan) arriving at ~19:40 UTC (Friday July 11).  

Of the two SEI chambers actively isolating that day: 

• ETMX, which was fully isolated (both stages at level 3), saw both stages trip simultaneously (independantly) on the actuators at the time of the quake (ST1, ST2) 
• ETMY, isolated at level 1 (see alog 12706), rode the EQ out and did NOT trip 

A trend of the ground BLRMS for the day of July 11 is attached (made with ligoDVweb because BLRMS trends not accessible via nds recently -  units in nm/s not counts). 

Just one example, but could be worth exploring. 

J. Kissel, J. McIver

After some fussing around with ISI command scripts vs. Watchdog vs. Guardian vs. my remote ssh/MEDM connection (see details below), we've changed the ISI from the guardian uncontrolled state of Isolated on Level 1 (see LHO aLOG 12706) to the guardian controlled state of ISOLATED DAMPED which is
- HEPI controlled with level 1 isolation filters, blended with "pos" position sensor only blends.
- ISI_ST1 control with level 3 isolation filters, blended with "TBetter" on all DOFs but RZ, which is on "TCrappy" (the current standard configuration)
- ISI_ST2 damped only.

The guardian finished the transistion to this state at
Jul 12 2014 20:43:29 UTC

Details
-------
We started this adventure trying to get the ISI-ETMY into both states controlled with *level 2* isolation on both stages, a state which guardian is incapable of creating. As such, I tried doing so using the command scripts. After running ctrlDown to clear out the level 1 isolation, I hit isolate lvl2. Unfortunately, because the SEI group's attention has been focused on guardian, the command scripts have gotten less attention: isolating level 2 consistently trips the watchdog. 

The trip is on the ST1 actuators (see example attached), and happens the instant when ST2 RX RY isolation filters begin their ramp, just after the blend filter switching -- yes, the command scripts (as opposed to the current guardian configuration) DOES still change the blend filters, switching them to "Start" filters. I suspect that its a case of forked processes not being synchronized and that the command scripts are still messing around with alignment biases. ST1 is fully isolated in Start filters (i.e. NOT using the T240s), ST2 alignment biases have just been ramped to some value, creating a large error signal in the isolation loops, the ST2 blend switching is not finished, and when the tilt isolation loops turn on with such a large error signal (even with a gain of 0.1 and the good spline ramping), it rocks ST1 enough that the actuators saturate. We're still tripping on a single sample of actuator saturation?

I tried this three times between Jul 12 2014 19:51:52 UTC and Jul 12 2014 20:08:20 UTC. After which, I gave up, and when on to the guardian controllable state of ISOLATED_DAMPED (as described above). This proved to be a pain for two reasons:
(1) After having been able to open many ISI screens over the double ssh -X connection, I went to the guardian overview screen to change the mode of the SEI_ETMY guardian and its subordinates back to MANAGED. But, for some unknown reason, by the time I got to the subordinates,  I could no longer open guard, and then subsequently any, medm screens. So, I tried from the command line, and that also failed:

jeffrey.kissel@opsws4:~$ guardmedm HPI_ETMY
medm -x -attach -noMsg -dg +0+0 -displayFont -misc-fixed-medium-r-normal--8-60-100-100-c-50-iso8859-1 -macro IFO=H1,SYSTEM=HPI_ETMY,MODULE_PATH=/opt/rtcds/userapps/release/isi/common/guardian/HPI_ETMY.py /ligo/apps/linux-x86_64/guardian-1021/lib/python2.7/site-packages/guardian/GUARD.adl

Could not open Display
jeffrey.kissel@opsws4:~$


I must have just stressed out the ssh connection too much, because only opening an entirely new ssh session remedied the problem. I was able to reproduce this problem, while writing this aLOG --> connection is open for a while, guardian screens cannot open but others can, then no screens can open.

Also of note, the command-line method of what I wanted to do from the MEDM screen, 
jeffrey.kissel@opsws4:~$ guardctrl mode MANAGED HPI_ETMY
doesn't do anything either.  

(2) Once I was able to use MEDM screens again, I switched the subordinates to managed. Soon after doing so, the ISI subordinates claim problems with "filters not in expected state. see log" which said "ISO filters needing to be cleared," even though all isolation filters, inputs and outputs were off, with the gain set to zero. In this state, the manager cannot change anyone's state to clear the problem. To solve the problem, I used the command screen to run ctrldown again. This cleared the warning message, and then I was able to request the manager to go ISOLATED_DAMPED. Note, that I had to manually switch the blend filters back to the above mention configuration before requesting ISOLATED_DAMPED, since the command scripts change them and guardian does not.
 

model restarts logged for Fri 11/Jul/2014
2014_07_11 11:09 h1fw0
2014_07_11 11:31 h1fw0

No unexpected restarts. Restarts of h1fw0 after repair work to h1ldasgw0.

9:06- 10:24 Heading into the LVEA to fix rubbing on SR3 – Jeff B.
9:10- 10:00 Moving Laser barriers around in the LVEA – Justin
9:16-12:00 Heading to the LVEA to align PR2 – Kiwamu/Jeff K
9:20- Heading to work in the optics lab – Nathan
9:37- 10:30 Checking the PSL power (LVEA) – Kiwamu
10:01- 12:00 Going to EndY to work on H1 ISC table – Sheila/Daniel
9:40-- Working on Turbo/QDP80 pumps at End X – Gerardo/Kyle
10:38- 12:00 Back to the LVEA to work on Contamination & Controls – Jeff B
10:46-10:57 Heading into the LVEA by ITMY to check on Seismometers – Hugh
10:48- Searching for cables in the LVEA - Corey 
11:52- 12:12 Covering Viewports in LVEA – Gerardo
12:00 – Motorized Rotation Staged have been de-energized and key put away – Jeff K
12:45 - Transitioning the LVEA south and east bay to laser HAZARD – Justin
13:00 -15:00 Working on HAM5 – Betsy/Travis
13:12- 15:27 Heading to the LVEA to continue on the ITMY alignment setup – Jason/Dugh
14:01- 15:16 Going back to the LVEA to work on Contamination and Control – Jeff B.
15: 18 Transitioning LVEA to Laser Safe- Justin

(Travis, Betsy, Kissel)

After getting the handoff beam from the input HAMs, we double checked that the beam was centered on the ITMx.  We then traced the beam and found it miscentered on the SR3 HR baffle (in front of SR3).  Using the BS bias, we were able to roughly center the beam on SR3 - using ITMx bias didn't seem to drive the beam very much.  We needed to use half of the BS YAW bias, however.  Once centered, we looked at SR2 and found the beam within 1-2" centered on the optic (with 0 bias on SR3).  We then used a bit of SR3 bias to roughly center on SR2.  Heading over to SRM, we again found the beam within 1-2" from the center of the optic and centered it using some SR2 bias.  We then verified that the beam (although blocked by a layer of First Contact on SRM-HR) sprayed through the OFI and out to HAM6.  We suspect the OFI alignment "won't take much."

Notes:

We paused to recheck the ISI locking of HAM5 when we observed that the beam wobbled when we rested on the table.  It seemed pretty locked, but the beam didn't seem to wiggle as much after we squeeked the lockers a bit more.

We increased the damping gains on the SR3 in order to help with the wobbling beam.

We started the realignment of the SR3 lower stage OSEMs.

Next up for HAM4:

Install TCS Temp Sensor Cable

SEI ISI Testing

FC Clean SR2

Chamber Closeout

Next up for HAM5:

Align all lower stage OSEMs on SR3 - a nasty task and will take a few hours, including checks of healthy SUS along the way

Pull FC on SRM (minor task)

OFI Alignment

OFI Res Testing

Install TCS Temp Sensor Cable

SEI ISI Testing

FC Clean SR3

Chamber Closeout

Finished alignment equipment setup and took a first look at the alignment of ITMy this afternoon.  Current alignment errors are below (due to the size of their errors, pitch and yaw are very rough estimates only accurate to approximately ±500 µrad).

• X axis (lateral):  -2.2 mm (south)
  • Tolerance: ±1.0 mm
• Y axis (longitudinal): 0.0 mm
  • Tolerance: ±3.0 mm
• Z axis (vertical): +0.7 mm (high)
  • Tolerance: ±1.0 mm
• Pitch: ~2 mrad up
  • ±50 µrad
• Yaw: ~2 mrad CCW
  • Tolerance: ±50 µrad

Thomas Vo, Arnaud Pele, Greg Grabeel

Aligned the ITMx CO2 laser in-vacuum mirrors this morning. Using the alignment laser from the CO2 table Thomas and I aligned through the irises onto the periscope mirrors. Once I was inside the chamber we found that while the laser entered the first viewport glass fairly well centered it is fairly low on the second, inner viewport glass. Because of the low path through the inner viewport glass, the alignment laser ran a bit high onto SM1 (BSC3 steering mirror). However, SM1 was able to center the beam path nicely onto SM2 (BSC2 steering mirror). Arnaud and I had to fight SM2 for quite awhile to get well aligned onto the ITMx test mass. SM2 requires brute force instead of finesse in its adjustment but it was eventually cudgeled into place.

Thomas was able to manually drive the upper-periscope mirror adjustments to test for clipping issues. Everything looked good with the beam path we only encountered path issues when the alignment laser was driven off the test mass horizontally, the alignment laser would clip off the upper edges of SM1. It doesn't appear that this will be an issue in any sort of normal operation though. 

This will enable the cartesian values to be calibrated.  Can't imagine why these filters shouldn't be engaged.  While the ISI still needs damping and isolation filter development, the cal filter is generic, and other work is started here and the cal filter is one of the first things installed.  I've turned them on now so the cartesian values are valid, I guess I need to do the safe.snap too.  Safe.snap made.

JessM pointed out to us that the H1:ISI-BS_ST1_GNDSTSINF_B_[X,Y,Z]_INMON signals were flat in the BLRMSs, since 5 June.  McCarthy suggested that the PEM crew may have disturbed the unit and stuck it on the rail.  A few pushes on the zero button at the local satellite box got the signals in range again.  X & Z still have some larger DC component so maybe the level of the instrument has been shifted.