The dewar level for CP7 is relatively low and the LLCV % open is nearly maxed out -> The vapor head pressure is 20 < pressure < 25 psi which should be more than adequate -> Delivery isn't for 6 more days -> At this rate we will have to do something or CP7 will have to be filled manually 

IP3 lost 1 of 2 channels shortly after replacing IP1 controller -> Both of these two units are the original (circa 1997) Varian MultiVac models of which we only have one or two left now on the site -> The failure is "Over Temperature" which is the typical failure mode -> I am unsure what is left for spares but will replace this unit as I am able

~1330 hrs. local -> Installed Gamma LPC unit (No CDS signal interface to this Make/model yet.  Indicated CDS values are bogus until otherwise specified)  

Kyle, Gerardo 

Dumped unpumped gate annulus volume into pump cart -> Decoupled cart from GV20 -> Opened GV20

h1seih23 filled its internal connection tracking table yesterday and had to be rebooted. Here is the current list of conntrack counts for all front ends as of 12:14PDT (the table fills at 65,536)

h1psl0 5,382
h1seih16 4,310
h1seih23 4,329
h1seih45 5,332
h1seib1 3,293
h1seib2 3,296
h1seib3 3,296
h1sush2a 5,400
h1sush2b 2,275
h1sush34 4,355
h1sush56 4,350
h1susb123 4,372
h1susauxh2  2,266
h1susauxh34 2,263
h1susauxh56 2,261
h1susauxb123 2,266
h1oaf0 6,400
h1lsc0 4,345
h1asc0 5,378
h1pemmx 2,231
h1pemmy 2,241
h1susauxey 2,267
h1susey 3,326
h1seiey 3,292
h1iscey 5,368
h1susauxex 2,266
h1susex 3,323
h1seiex 3,296
h1iscex 5,366
 

Since Fil has just put the Xend ALS fiber in a [something], I tweaked the polarization such that H1:ALS-X_FIBR_LOCK_FIBER_POLARIZATIONPERCENT is at 9% (it started at 22%).   

Also, yesterday Daniel and I tweaked up the Yend ALS fiber polarization.

Rebooted the h1seih23 computer because network connectivity had failed due to the nf_conntrack table full error.

Vac

• EY looks good, solely on the Getter Pumps
• EX will be switched over to the Getters today and then opened after lunch
• May leave some turbos on fro RGA work (1~2 days)

Comm

• SRY Initial Alignment is get better

SEI

• Hugh moved Seismon B to EX
• Moved Seismon A to biergarden
• Running CS Sensor Correction from Seismon C
• Jim to take BSC measurements this morning (10~15min)
• Next Tues trun off HEPI platforms for accumulator maintenance

SUS

• Leo taking daily 3pt/mass charge measurements
• ESD High Voltage off at EX yesterday and EY was railed negative (See Jeff's alog)
• TMS damping chain lost some gain from the vent, not sure why

CDS

• EX ALS fiber will be rephased
• PEM cabling
• Jim B. rebooting SEIH23 thismorning

Fac

• Beam tube cleaning on Y arm near the end
• X arm joint sealing ongoing
• EX piping work
• OpLev grouting will not take place till after O1

No safety meeting today.

Summary of CDS maintenance model and DAQ restarts. Upgraded DAQ to RCG2.9.4. SEI new models. Upgraded Mid Station PEM to RGG2.9.4. DAQ restart to support upgrades.

* = unexpected restart

model restarts logged for Tue 07/Jul/2015
2015_07_07 00:30 h1fw1*
2015_07_07 09:49 h1nds0
2015_07_07 10:37 h1hpiham1
2015_07_07 10:42 h1hpiham2
2015_07_07 10:42 h1isiham2
2015_07_07 10:48 h1hpiham3
2015_07_07 10:48 h1isiham3
2015_07_07 10:56 h1hpiham4
2015_07_07 10:57 h1isiham4
2015_07_07 11:08 h1hpiham5
2015_07_07 11:08 h1isiham5
2015_07_07 11:13 h1isiham6
2015_07_07 11:15 h1hpiham6
2015_07_07 11:25 h1hpiitmy
2015_07_07 11:27 h1hpibs
2015_07_07 11:27 h1isiitmy
2015_07_07 11:29 h1isibs
2015_07_07 11:33 h1hpiitmx
2015_07_07 11:33 h1isiitmx
2015_07_07 11:38 h1hpietmx
2015_07_07 11:39 h1isietmx
2015_07_07 11:43 h1hpietmy
2015_07_07 11:43 h1isietmy
2015_07_07 11:52 h1broadcast0
2015_07_07 11:52 h1dc0
2015_07_07 11:52 h1fw0
2015_07_07 11:52 h1fw1
2015_07_07 11:52 h1nds0
2015_07_07 11:52 h1nds1
2015_07_07 12:11 h1fw0*
2015_07_07 12:31 h1fw0*
2015_07_07 13:06 h1ioppemmy
2015_07_07 13:06 h1pemmy
2015_07_07 13:07 h1ioppemmy
2015_07_07 13:08 h1ioppemmy
2015_07_07 13:09 h1ioppemmy
2015_07_07 13:10 h1ioppemmy
2015_07_07 13:11 h1ioppemmy
2015_07_07 13:12 h1pemmy
2015_07_07 15:54 h1ioppemmx
2015_07_07 15:54 h1pemmx

[Stefan, Jenne]

Since the Yarm gate valves were opened this afternoon (but the Xarm is still closed), we aligned the Yarm to the green beam, and then aligned the input IR pointing to the Yarm.  (We assumed that the BS pointing was fine from yesterday.)  

* We used the ITMY baffle PDs to set the TMS pointing for the green input, then used the green WFS to align the Yarm.  We touched PR3 a bit to keep the green transmission at the corner on its camera.  

* We used PR2 and IM4 to align the IR beam to the arm.

* We then aligned PRX, followed by SRY.  

After that, we started on the SRY work that I've already reported on.

[Stefan, Jenne]

We were informed that the SRY lock acquisition step of initial alignment was flaky, and could get into a state of ringing up the SR optics.  

The solution was two-fold:
(1) We increase the input power to 10W to improve the SNR on ASAIR_A_RF45_Q.  (After the ASC offload step, the power is returned to the original 2W).
(2) We utilize the front end fast triggering, for both the output and the FM4 integrator.  

For item (1), we did a little bit of finagling in the guardian script to ensure that the value of H1:PSL-POWER_SCALE_OFFSET matches H1:IMC-PWR_IN_OUTMON.  This is required so that we don't lose lock (due to de-triggering) when we are changing the power levels.  Since we're using H1:LSC-ASAIR_LF_NORM_OUT for triggering in item 2, if the value in H1:PSL-POWER_SCALE_OFFSET (which does the "norm" in H1:LSC-ASAIR_LF_NORM) does not match reality (as approximated by H1:IMC-PWR_IN_OUTMON), the loop will often de-trigger even if it shouldn't have, which is why we need those values to match.

For item (2), we changed the SET_SRY guardian to leave the SRCL input always on, and use H1:LSC-ASAIR_LF_NORM for triggering.  We found that values of 50 cts up, and 30 cnts down were good thresholds.  Since only the output of the LSC filters are triggered, this means that we cannot leave the FM4 integrator on unless the loop is engaged.   We use the filter module triggering (which was already triggering FM1, a +6dB gain) to also trigger the FM4 integrator.  Since the integrator's oomph is needed to acquire the lock, we use a "delay" in the filter module of 0 seconds (it used to be 0.2 seconds).  

Nic, Evan

Summary

The frequency noise in CARM is limited in part by the dark noise of REFLAIR9I between 30 Hz and 1 kHz.

Details

First, an explanation of the plot traces:

1. The first trace gives the out-of-loop CARM noise in full lock as sensed by REFL9I, taken on 2015-06-14 06:16:10.
2. The second trace is the dark noise of REFL9I, taken a few days later when the IMC was down.
3. The third trace shows the dark noise of the in-loop sensor (REFLAIR9I), taken today (out of lock, REFL shutter closed). Notes on this:
   • We had to temporarily increase the whitening gain by 30 dB in order to overcome the ADC noise.
   • We have also scaled this noise by a constant factor in order to give the equivalent amount of noise that would be seen on the out-of-loop sensor. [The total scale factor is 10^(-30/20) / 0.0525 ≈ 0.60­, where 0.0525 ct/ct was the previously measured conversion factor from REFL9I to REFLAIR9I in full lock on 2015-06-14.]
   • The detailed shape of the CARM loop is not taken into account (see explanation below about our assumptions for CARM). So above a few kilohertz, where the CARM gain is only a factor of a few, this in-loop dark noise is probably not impressed very strongly onto the OOL sensor.

In the case that the CARM loop is sensing-noise limited, the dark noise (and the in-lock shot noise) of REFLAIR9I should appear on REFL9I. The CARM ugf is about 15 to 20 kHz, and is >30 dB below 1 kHz. Additionally, the white(ish) noise in REFL9I from 30 Hz to 1 kHz strongly suggests that we are seeing some kind of sensing noise. So we believe that the sensing noise from REFLAIR9I is indeed being impressed onto the CARM loop, and is the dominant contributor to the OOL noise between 30 Hz and 1 kHz.

We would like to additionally measure the shot noise as seen in REFLAIR9I (with no lock), to see how large it is relative to the REFLAIR9I dark noise. Either way, it is probably advantageous to switch control of CARM to REFL9I.

around 15:37PDT I noticed my CDS overview MEDM was not connecting to the models running on h1seih23. The control room TV MEDM screen was not showing this problem, but new MEDM connections were not being established. I was also unable to ping or ssh onto h1seih23.

h1seih23's console is reporting many errors (several per second) of the type:

nf_conntrack: table full, dropping packet.

and sometimes

net_ratelimit: 66 callbacks suppressed

a quick goggle search shows that the internal IP connection table has reached its limit.

Over time new MEDM connections are actually being established. Guardian is not reporting any issues with its connections.

So we are thinking that new channel access connections are flakey, but established ones (like guardian) will continue to work. The IFO team would like to delay a restart of h1seih23 until tomorrow unless it becomes a major issue to IFO locking.

J. Kissel, L. Prokhorov, T. Shaffer

Another episode in the saga of the High Voltage ESD Drivers. Though we've not been able to identify why, the high-voltage for both end station's ESD High Voltage Drivers were found OFF. We've queried the usual suspects, and those who were around, and no one has any idea why they might have been *turned* off, so we suspect that they had tripped off from all of the vacuum and electronics work at the end-stations today (the best aLOGs for which are the sparse ops log, LHO aLOG 19462, and VE logs 19472, and 19471).

The ETMY Driver remains railed negative. We've tried all of the possible button mashing and cable plugging and unplugging we've either done before or heard has been tried before, with no success. We request the assistance of the CDS team in the morning.

---------

As you know, we're still in the odd state that the ETMY high-voltage driver is controlled by the new(ish) low-voltage driver, and the ETMX high-voltage driver is controlled via a temporary Beckhoff setup. Therefore, the start-up procedure for both is different.

ETMX
- Flip ON the high-voltage supplies' power switch in the racks near the entrance of the building (you'll hear a ~few second loud continuous beep, wait for the initialization procedure to complete)
- Hit black "V SET" button, followed by entering in 430 V (i.e. hit 4, 3, 0, then enter)
- Hit black "I SET" button, followed by entering in 80 mA (i.e. hit 8, 0, then enter)
- Hit red "OUTPUT ON/OFF" button
You should see the volts go to ~430 V, and the current go to ~3 mA

Now, head out to the driver in the XVEA. You should see both the 430 V and the (low voltage, I don't remember what it is 12 or 15 or something) lights on the front panel showing bright green. You can either turn on the driver manually by hitting the red "start" button, or using the temporary remote system. You'll know the driver is ON when the light above that button goes from OFF to bright RED.
To use the temporary remote system, via a terminal on a work station, toggle one of the remote switches:
caput H1:ISC-EXTRA_X_BO_4 0
caput H1:ISC-EXTRA_X_BO_4 1
then turn on the second,
caput H1:ISC-EXTRA_X_BO_3 1
Once you see all of the lights on on the front panel of the high voltage driver, make sure to confirm that you see a change in the readbacks when turning ON and OFF requested signals (i.e. turn the BIAS "DC" ON and OFF, and turn an OFFSET in each of the quadrants UL, LL, UR, and LR ON and OFF).

ETMY
(This is the same as ETMX)
- Flip ON the high-voltage supplies' power switch in the racks near the entrance of the building (you'll hear a ~few second loud continuous beep, wait for the initialization procedure to complete)
- Hit black "V SET" button, followed by entering in 430 V (i.e. hit 4, 3, 0, then enter)
- Hit black "I SET" button, followed by entering in 80 mA (i.e. hit 8, 0, then enter)
- Hit red "OUTPUT ON/OFF" button
You should see the volts go to ~430 V, and the current go to ~3 mA

(This is different than ETMX)
- Head out to the YVEA (so you can see the front panel of the ESD driver, because these first few steps rarely work), and open the BIO screen of the ETMY SUS.
- Hit the big beige RESET button on the bottom right corner. This *may* toggle the High Voltage Driver on and off, and you *may* regain functionality but likely not.
- Several times now, the driver has been found to be "railed negative" in which he primary symptom is that the readbacks for every channel show about -15700 [ct], and the channels are unresponsive to change in requested drive signal.
Here's what has been tried in the past (ranging from "that's probably it" to "there's no reason hat would have worked anyways, but we're grasping at straws"), and so what I've tried this evening:
- Manually turning ON and OFF the driver with the START button on the front, with the REMOTE RESET cable and INPUT cable still plugged in.
- Unplugging the REMOTE RESET cable and manually turning ON and OFF the driver with the START button (INPUT cable still plugged in)
- Plugging the REMOTE RESET cable back in, and trying both to remotely and manually turn ON and OFF the driver
- Unplugging REMOTE RESET and INPUT cables, manually turning ON and OFF the driver
- Toggling all of the low-voltage driver binary I/O switches (i.e. the HI/LO VOLTAGE and HI VOLT DISCONNECT switches)
None of which were successful this time around.

Elli, Nutsinee

Today we moved theITMY HWS periscope to fix the return beam clipping issue (it was clipped at the lens between the two periscope mirros). I lost the green beam during the alignment (ITMY misaligned) so I left it there for now. The return beam seems to be clipping at the edge of the first iris (the green came right through the center though). *Should* be a quick fix next time (don't I always hope that?).