J. Kissel, K. Izumi

Kiwamu is making sure the online calibration filtering (currently in the "OAF" model, will eventually be in the "CAL" model) is reasonably up-to-date. In doing so, we discovered that the two ETMs have different damping loop filters installed and ON. Most filter modules are as expected, according to the original, low noise, Level 2.1 quad design (see LGO aLOG 6760). However, in FM3 of the L and Y banks of both ETMX and ETMY, there are filters called "resg1" and "+12dB" respectively. They are ON only in ETMX.

After a little digging down memory lane, we recalled that in attempts to get ALS DIFF up and running last time (see e.g. LHO aLOG 15025), before we lost the arms, we had copied over LLO's damping filters' differences at the time -- described in detail in LHO aLOG 14959. However, as indicated in LHO aLOG 15037, having the filters constantly ON never got captured in any sort of configuration control, because ALS and LSC control was bouncing between using ETMX and ETMY depending on the functional-state and state-of-confusion for each test mass.

We have now turned both FM3's of L and Y filter banks ON, and changed the DAMP_STATE_?_GOOD state to match the current state with those ON. We have not yet captured a new safe.snap in this configuration, but we'll do so ASAP.

A note -- the ITMs do NOT have these "bonus" LLO filters installed, so FM3 is therefore OFF.

Replaced bad projector lamp on left side projector in control room.  

NOTE: The lamp socket internal to the projector has badly overheated and the plastic mount that holds the socket pins has lost it's integrity. If you smell smoke in the control room, this projector should be powered off.  This seems to be a common problem with these projectors.

For the Schnupp asymmetry measurement, one of the patch panel connectors on ISC R1 (by the PSL) is now wired to another patch panel connector on ISC R3 (by HAM6). The wiring is as follows:

• Existing patch cable: ISC R1 #11-4 → ISC C4 #2-4
• New 1 m cable: ISC C4 #2-4 → ISC C4 #5-6
• Existing patch cable: ISC C4 #5-6 → ISC R3 #15-6.

Initially, all these ports were labeled as "spare" and most of them were terminated.

The connector on ISC R1 will be driven by an rf signal from an IOT2R PD. The connector on ISC R3 will go into a spectrum analyzer.

DAQ was restarted to sync up with temporary h1iscey model change which was applied in the last hour.

We only restored PIT of HEPI2 (H1:HPI-HAM2_IPS_RY_SETPOINT_NOW) yesterday, but there was a change in ROLL (RX) on the order of 10 urad that was not restored, which might affect the input pointing.

Also, there was a jump in ROLL in HEPI3, again on the order of 10 urad, which would affect POP and ALS beam position on ISCT1 as well as POP sled in HAM3.

These DOFs were brought back to pre-maintenance levels.

I don't know/remember why, but it seems that a new set of angle setpoints is made for HEPI such that the system starts new with free-hanging position after each restart. Seems like this free hanging position changes over time.

Since any change in HEPI angle (RX, RY and RZ) on HAM2 and HAM3 would affect many things related to the alignment, most notably pointing references like IM4 transmission QPD and POP sled, it's a good idea to keep the set points unchanged over multiple restarts.

I noticed the autoburt VM was behind in patches, so I updated it and rebooted in between snapshot runs.  There should be no gaps in the autoburt coverage, though the next run may take longer as the embedded gateway re-caches the PV names.

Replaced the ISI Coil Drivers D0902744 for HAM3. This is a temporary swap to help with troubleshooting the 0.6Hz seen in HAM3.

Electronics removed:
S1103321 U24-U25
S1103358 U23-U22

Electronics Installed:
S1103316 U24-U25
S1103301 U23-U22

model restarts logged for Mon 12/Jan/2015
2015_01_12 08:59 h1nds0
2015_01_12 10:49 h1hpietmx
2015_01_12 10:49 h1iopseiex
2015_01_12 10:49 h1isietmx
2015_01_12 13:41 h1fw0

two unexpected restarts. ADC replacement of h1seiex in preparation for RCG2.9 upgrade.

model restart for Tue 13/Jan/2015

in attached file. RCG2.9 upgrade required all systems to be restarted. Several later unexpected DAQ restarts of frame writers.

Now that ETMX is back to vacuum, I measured a trend of the effective test mass charge voltage over 3.5 hours. The sensor was the oplev, since there is no cavity. I was told by Jeff K, who was told by Richard (or was it Kyle?) that the ion pump is valved out. The pressure was about 1.5e-6 torr, pumping with the turbo for about 2 days since the last vent.

The first pdf shows the charge seen the pitch and yaw oplev signals from excitation in each ESD quadrant. The second pdf shows the deviation from the average of each quadrant - oplev siignal pair, e.g. pitch from UL exc, etc. The largest deviation is -12 V. Most of the data is within +-10 V.

The charge measuring script is

/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Scripts/ESD_UL_LL_UR_LR_charge_07-H1.py

The charge analysis script is

/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Scripts/ESD_UL_LL_UR_LR_analysis07_H1.m

The charge trend script is

/ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/Scripts/Long_Trend_H1.m

Jim, Dave: WP5003

This morning we upgraded H1 FE and DAQ to RCG2.9. First the DAQ was upgraded and restarted. Then FE startup scripts were changed, model startup scripts changed.

Then a "make installWorld" was ran to install the models which were compiled yesterday. The H1.ipc file generated yesterday was re-installed.

We tested a reboot-restart first on a non dolphin FE (h1susauxh2) and then on a Dolphin FE (h1seib1).

We then restarted all frontends in the MSR by power cycling the computers, and end station frontends by rebooting the computers. We ended up having to powercycle h1iscex because it got stuck in reboot. In the MSR when we were restart testing, h1susb123 got stuck on reboot and needed a power cycle which Dolphin crashed the other MSR machines.

We got to a stable system with DAQ and FE reboots proceding correctly. We had 6 front end IOP models with large IRIG-B excursions into the 1000-2000 counts. The h1oaf0 IOP took 4 hours to return to normal IRIG-B range. One IOP went below zero (999998) which caused IPC errors on models receiving its channels. This fixed itself in about 10 minutes.

We noticed a single ADC error on the h1ioplsc0, which was cleared with a DIAG_RESET.

We noticed the DAQ frame size is smaller now. For science frames 670MB to 610MB (10% reduction) and commissioning frames 1.2GB to 1.0GB (20% reduction). We suspect new common models are the reason for this.

I linked Jamie's SDF_OVERVIEW MEDM screen to the SITEMAP under the GRD section. We are configuring the IOP, PEM and PSL systems.

This closes WP5003

Some of the ODC channels now appear to have string values with unrecognized characters. For example:

caget H1:PSL-ODC_FSS_BIT21
H1:PSL-ODC_FSS_BIT21           FSS Not Resonant (Loop 300370216d377177

I regenerated the channel list, searched it for channels with ODC in the name, added these to the exclude list, and regenerated the channel list again.

(To know the whole story about the Z-RZ coupling, see DCC document #E1400432.)

I turned ON the substraction on ETMY-ISI ST1 with good results. If you look at the first attachement:

- Red curve -> nominal configuration (RZ loop OFF)

- Blue curve -> RZ loop ON. As expected, we amplified the RZ motion around 0.1Hz by turning the loop ON. The loop provides some isolation above 0.5Hz. Z doesn't change.

- Brown curve -> RZ loop ON + Substraction ON. We can see an improvement by almost a factor of 10 in the RZ spectrum around 0.1Hz. The substraction seems to work just fine.

As Ryan suggested, we also wanted to see if we can obtain similar results without the substraction. We do have Z sensor correction on HEPI, so we might be able to relax the actuation on Z (meaning higher blend) and still have reasonable performance in vertical. By relaxing Z, the couping with RZ should be reduce. Unfortunately, the Z motion seems to big for our need if we swich to higher blend  (see second attachement).

Last attachement shows different substraction configurations:

- Red curve: Substraction ON with a 90mHz blend on Z and Z sensor correction on HEPI

- Blue curve: Substraction ON with a 45mHz blend on Z and Z sensor correction on HEPI

- Brown curve: Substraction ON with a 90mHz blend on Z and Z sensor correction on ISI

Viewing those results, it seems that switching to a lower blend on Z might be a good idea.
For further analysis, we need to look at more sensors and the optical lever. We might want to look at the other chambers as well.

J. Kissel, S. Dwyer, D. Sigg, E. Hall, N. Mavalvala

After performing all of the usual alignment position checks (SUS, SEI, MC TRANs QPD, IM4 TRANS QPD), after the RCG 2.9 upgrade (see LHO aLOG 16040) we've confirmed that the IMC REFL path has jumped down in pitch again as it has done several times in the past after major computer reboots or SEI/SUS events (see Integration Issue 854, LHO aLOGs 10335, 11481, and 15650). 

We didn't preserve camera views prior to the reboot, and I didn't get the chance to capture an UNLOCKED camera view in which the REFL path was similarly low, but I attach the misaligned views after the RCG, then SEI and SUS recovery before realigning the path, and the realigned views after Evan, Sheila, and Nergis have realigned the whole path. We've also confirmed that the MC WS are running happily now as well.

Note that the IMC REFL L RFPD and trigger PD are on different image planes and lens focal points than the MC WFSA and MC WFSB and MC REFL GIGE Camera (see D0902284), so it's to be expected that they're differently affected by a misalignment of the MC REFL path. In other words, the IMC LSC path is much less sensitive to misalignments than the IMC ASC path (which contains the MC REFL GIGE Camera View).

Finally, for future reference, I attach a screenshot of all of the relevant camera views and screens I can for the IMCASC and surrounding sensors, with 2015-01-13_H1IMC_Status_ScreensandCamera.png