We made two additional experiments with the unsuspended, isolated pilot (Corning ETM02) ITMY, in the west bay of the LVEA. (Moreno, Landry)

1) We applied FirstContact to the HR surface, let dry over 24h, measured no excess charge (no more than |3V| at 1" from HR surface, AR surface, and barrel), ripped the FirstContact off the HR face in ~20s *without* doing any TopGun ion gun blowing, and then measured the voltage 1" from the HR surface. We find the resultant charge negative, with a claimed voltage of ~-22kV, -22kV and -22kV at three points across the face of the optic.  Assessing the AR surface, we find a voltage 1" from the AR face of -12.1kV, -12.1kV and -11.3kV.  

2) We made another trial in which after FirstContacting, we removed the polymer film while TopGun blowing to neutralize the surface.  We followed the same basic procedures as outlined in alog 13104, with slightly different timings. The primary change in the experiment was the grounding of the optical table, and the addition of a grounded Al foil shield (see photo attached).  The addition of the shield and ground dramatically changed the behaviour seen in the prior experiment linked above: generally, individual measurements that took minutes to settle exponentially to some voltage now settled in seconds.  Furthermore, the apparent long time constants for which it seemed necessary to continue with the ion gun (~9min total) were not observed in this experiment. We took 2 minutes to pull the FirstContact, which included a coincident 2 minute TopGun blow, plus one additional minute of TopGun blowing, and measured +18 to +30V at several locations 1" from the surface of the HR side of the optic.  

We'll repeat experiment #2 one more time, with shorter intervals between electrometer measurements, to better understand the field sizes, signs, and time constants.

A new version of dataviewer has been built and installed for Ubuntu and OS X control room computers.  This version allows unsigned integer data to be viewed properly, fixes a bug where the mean value of integer data in minute trends was always 0 or close to it, and allows selection of short channel names from the channel menu.  WP 4837.

Following the recent replacement (generic maintenance) of PT120B, PT170B and PT180B Cold Cathode gauge sensor+electronics, there has been an apparent 25% discrepancy between the indicated pressures of the new PT170B and PT180B gauges -> Swapping the removable electronics between the two units has (surprisingly) resulted in both read backs being as expected in both absolute and relative pressure values 

As stated yesterday, I changed the ITMy oplev laser and saw no change in the sawtooth pattern in the oplev yaw.  I noticed that the curtains of the cleanroom that is still sitting over the Y manifold spool were resting on the oplev receiver pylon.  Today we moved that cleanroom and saw, once again, no change in the sawtooth pattern.  See the attached dataviewer screenshot, where the signal gets noisy is when we moved the cleanroom.  Will continue to investigate.

Changed location of ESD bias filter at ETMX and ETMY to before the 10kohm resistor instead of after.

no issues, goodness is good.

Despite having everything green and resets pressed on all the HEPI screens(watchdog, dackill, iopdackill) there is no output to the Actuators.  There are DK red lights on the CDS Overview.  We (Richard & I) can't figure out how to clear this.  He went away and return with "Restart the Model."

model restarts logged for Tue 09/Sep/2014
2014_09_09 09:11 h1iopsusquadtst
2014_09_09 09:11 h1susquadtst
2014_09_09 09:16 h1iopsusquadtst
2014_09_09 09:54 h1iopsusquadtst
2014_09_09 09:54 h1susquadtst
2014_09_09 10:34 h1iopoaf0
2014_09_09 10:34 h1oaf
2014_09_09 10:34 h1odcmaster
2014_09_09 10:34 h1pemcs
2014_09_09 10:34 h1tcscs
2014_09_09 10:46 h1dc0
2014_09_09 10:48 h1broadcast0
2014_09_09 10:48 h1fw0
2014_09_09 10:48 h1fw1
2014_09_09 10:48 h1nds0
2014_09_09 10:48 h1nds1
2014_09_09 10:54 h1isiham4
2014_09_09 10:54 h1isiham5
2014_09_09 11:05 h1lsc
2014_09_09 11:06 h1lsc
2014_09_09 11:07 h1dc0
2014_09_09 11:12 h1broadcast0
2014_09_09 11:12 h1dc0
2014_09_09 11:12 h1fw0
2014_09_09 11:12 h1fw1
2014_09_09 11:12 h1nds0
2014_09_09 11:12 h1nds1
2014_09_09 11:21 h1isiham4
2014_09_09 11:27 h1broadcast0
2014_09_09 11:27 h1dc0
2014_09_09 11:27 h1fw0
2014_09_09 11:27 h1fw1
2014_09_09 11:27 h1nds0
2014_09_09 11:27 h1nds1
2014_09_09 14:25 h1omc
2014_09_09 15:32 h1nds1
2014_09_09 15:50 h1nds1
2014_09_09 17:04 h1iopoaf0
2014_09_09 17:04 h1oaf
2014_09_09 17:04 h1odcmaster
2014_09_09 17:04 h1pemcs
2014_09_09 17:04 h1tcscs
2014_09_09 17:22 h1iopoaf0
2014_09_09 17:22 h1oaf
2014_09_09 17:22 h1odcmaster
2014_09_09 17:22 h1pemcs
2014_09_09 17:22 h1tcscs
2014_09_09 17:34 h1iopoaf0
2014_09_09 17:34 h1oaf
2014_09_09 17:34 h1odcmaster
2014_09_09 17:34 h1pemcs
2014_09_09 17:34 h1tcscs

maintenance day. Startup of h1susquadtst. Swap of DAC in h1oaf0, subsequent replacement of original DAC later. New ISI Ham4,5 code. Reversion of h1lsc to RCG2.8.3. New code for h1omc. Associated DAQ restarts. Unexpected failure of h1nds1.

(Jeff, Jamie, Sheila, Alexa, Lisa)

Tonight we used ITMX ISI with the guardian paused. We had damping on stage 2, and on stage 1 X, RX and RY. For stage 1 we used the level 3 controllers that are loaded and a gain of 2.

Our goal for the night was to lock PRMI on the carrier. However, we would lose lock when we aligned PRM after locking MICH on mid fringe. We must be missing some setting. We had found the FM2, FM3, FM4 were turned off (probably for locking on PRMI sideband) on LSC_POPAIR_A_LF. So maybe we are missing something else, but we just don't know what. Also the counts on LSC_POPAIR_A_LF_OUT have decreased to 1.8 from 3. To handle this, we adjusted the normalization matrix and triggering values, but this did not seem to work. The MICH mid-fringe OLTF was consistent with the previous measurements. We also slowed down the ramp for aligning PRM, but this did not help.

Jamie, Lisa

Jamie improved the tool he adapted from SEI to be able to plot multiple channels and rescale the axis all at the same time. It is now ready for public consumption.
The script which does the magic lives here:/opt/rtcds/userapps/release/sys/common/scripts/lockloss.

usage: lockloss plot [-h] [-w WINDOW] [-c FILE] [-o FILE] time

plot specific time

positional arguments:
  time                  GPS time to plot

optional arguments:
  -h, --help            show this help message and exit
  -w WINDOW, --window WINDOW
                        plot time window in seconds (default: '[-240, 5]')
  -c FILE, --chanfile FILE
                        file with list of channels to plot, 1 per line ('-'
                        for stdin)
  -o FILE, --outfile FILE
                        save plot to file

This is an example which uses a list of channels stored in my PRMI config file with some useful signals. I would be happy to attach this file to this entry, but apparently I can't.
In any case, it is just a list of channels...

lisa.barsotti@opsws3:~$ lockloss -c ~/lockloss/PRMI plot -w '[-200, 5]' 'tconvert Sep 9 10:34 UTC'

This is the lock loss that Kiwamu reported here , where the sideband build up is dominated by a 40 mHz oscillation in ITMX YAW.
The power fluctuations are kind of huge (75%), so the fact that the PRMI unlocked is not surprising, as Kiwamu was saying.

This tools will then talk to the Guardian and automatically provide a selectable list of lock loss GPSs.

The message of this entry is that, as long as NDS2 cooperates, this tools drastically improves the way we have been doing lock loss analysis in the last decade (and any analysis which requires zooming multiple channels, really).

AS Jason, Keita and I disscussed this morning, I left the BS oplev damping off for several hours today, from 9/9/14 17:00 UTC to 9/9/14 23:00

Sheila, Alexa, Lisa, Kiwamu

Today we went back to locking SRY as described in 13726, to try make sure we have some reasonable crossovers for the SRC actuation.

First we adjusted the phase for AS_45, to -71.9.  We also had to flip the sign, so we are now locking with a gain of -400 in SRCL. 

we are using a gain of 1 in SRM and SR2 ISC INF. 

After talking to Ryan we moved the 27 Hz notch to the SRM M2 lock filter, and disengaged the 27Hz notch in SRM ISCINF.  This keeps the DAC from saturating at the 27 Hz vertical mode, without causing a notch in the open loop gain.  

We have a ugf of about 30 Hz, measurements in the SRM path and the SRM M2 path are also attached.  It seems that we do not ring up the vertical mode in SR2 as easily as we ring it up in SRM. 

Causes outer "ability to drive" boarder to go white on overview screen.
H1:ISI-ITMY_ST1_WD_MON_STATE_INMON 
H1:ISI-ITMY_ST1_MASTER_SWITCHMON 
H1:ISI-ITMY_DACKILL_STATE         <-- This one shows red on middle click.
H1:IOP-SEI_B1_DACKILL_STATE

[This work was done last week, but I forgot to submit this log.]

I added NOMINAL state definitions for all SEI systems, including HPI, ISI stages, and HAM and BSC chamber managers.  All SEI guardian nodes were restarted to affect these changes.

NOMINAL state for HAM managers is "ISOLATED".

NOMINAL state for BSC managers is "FULLY_ISOLATED" (HPI and both ISIs isolated).

NOMINAL state for HPI is "ROBUST_ISOLATED", for both HAMs and BSCs.

NOMINAL state for ISI stages is "HIGH_ISOLATED".

Other than HAM 5 and 6, which are still being commissioned, everything except BS is set to be in the NOMINAL state, and is in the NOMINAL state.

We are currently operating the BS ISI with only stage 1 isolated, and stage2 left damped, corresponding to "ISOLATED_DAMPED" in the BS chamber manager (MICH locking has a tendency to trip the ISI stage 2 if isolated).  However, I decided to leave the NOMINAL settings to the default for ISI_BS_ST2 and SEI_BS, so that we're reminded to address this issue down the line.  Here's a crop from the GUARD_OVERVIEW, showing that the SEI_BS and ISI_BS_ST2 are not in their nominal states, as indicated by the far left OK indicators being orange:

We still need to add numeric indices for all the SEI states.  This will require a bit more work for SEI since the HPI and ISI states are generated based on the particular configuration.

J. Kissel, J. Rollins, S. Dwyer, A. Staley

While Sheila and Alexa began to lock PRMI on carrier, the HAM2 and HAM3 HEPI and ISIs tripped for an unknown reason. We'll leave this to people offline to figure out what happened. See attached actuator trip plots from the ISIs.