model restarts logged for Tue 23/Dec/2014
2014_12_23 10:29 h1iscex
2014_12_23 11:43 h1iscex
2014_12_23 11:44 h1iscey
2014_12_23 11:47 h1broadcast0
2014_12_23 11:47 h1dc0
2014_12_23 11:47 h1fw0
2014_12_23 11:47 h1fw1
2014_12_23 11:47 h1nds0
2014_12_23 11:47 h1nds1
2014_12_23 12:15 h1iopsusquadtst
2014_12_23 12:15 h1susquadtst
2014_12_23 14:39 h1iscex
2014_12_23 14:39 h1iscey
2014_12_23 14:44 h1broadcast0
2014_12_23 14:44 h1dc0
2014_12_23 14:44 h1fw0
2014_12_23 14:44 h1fw1
2014_12_23 14:44 h1nds0
2014_12_23 14:44 h1nds1

no unexpected restarts. Maintenance day builds of ISC EX,EY with corresponding DAQ restarts. Restart of susquadtst following DAQ problems when powering it down. Beckhoff restarts shown in attachment.

Conlog frequently changing channels report attached.

At John's suggestion, I checked the turbo bypass valve and found that it was still open (from rough pumping phase) -> Closed bypass valve -> OK

This is the first time that I have overlooked this in the "many" times that I have performed this procedure (there's a first time for everything!).  This proved (to me) to be a surprising explanation of the symptom since the bypass circuit is ~2' of 1.5" tubing (+ two 90s) connecting the turbo exhaust to the turbo inlet.  As such, I would have never guessed that a compression ration of ~500 could have been maintained with such a large conductance between exhaust-intake (who knew!) 

Also, isolated pump carts from BSC9 and BSC10 annulus volumes -> Both systems pumped only by ion pumps

~0635 - 0650 hrs. local -> In and Out of X-end VEA 

~0700 - 0710 hrs. local -> In and Out of Y-end VEA

J. Kissel

Just after the commissioning vanguard left for the evening (2014-12-24 03:57 UTC, Dec 23 2014 19:57:00 PST, 1103428636) the PMC / FSS went down, and it's been flashing and struggling to recover since. I attach a few relevant screen shots. Wish I could diagnose / fix...

Merry Christmas to all, and to all a good night!

J. Kissel

I've confirmed that the ESD on H1 SUS ETMY (turned on earlier today, see LHO aLOG 15809) is functional by driving a 4 [Hz], 30000 [ct_pk] sine wave into each quadrant using awggui, and measuring the response in the ETMY optical lever. There is clear amplitude and coherence in pitch and yaw when driving each quadrant.

Other less exciting notes, regarding the functionality of the whole ESD system:
- Remember that the front-end code is still in correctly ordered, but Richard McCarthy assures me that instead of wiring up what had made sense in analog, he has switched the inputs at the ESD driver such that the front end drives the right channels, i.e. the front end's DC bias, which drives the ESD driver's channel 1 is connected to pin 3, all the way to the ESD pattern in chamber as per Filiberto's aLOG (see LHO aLOG 15656), and the remaining quadrants are hooked up identically to how they're hooked up at ETMX and in the two LLO quads. Once Rich Abbott solidifies a drawing of what has been implemented at H1 EY, then the changes will be propogated elsewhere and the front end models will be fixed. Maybe, eventually. But the important statement, again, is that all 4 ETMs are now wired up in the same fashion, such that the front-end drives each quadrant in the same way. Until the analog monitors are functional and I get Rich's drawing, I don't want to add more confusion by attempting to make a channel order. Thank god, when it counts, we only ever use these things in longitudinal driving all four quadrants at once.
- The ESD analog monitor channels, e.g. H1:SUS-ETMY_L3_ESDAMON_LL_MON, are completely non-functional, they don't report change regardless of bias value or excitation on each quadrant.
- The ESD driver's digital monitor signals also don't report anything but ADC noise, *except* for the "MCU" channel, H1:SUS-ETMY_L3_ESDDMON_MCU_MON, which is a 1 [Hz], 3460 [ct_pkpk] sine wave.

DTT Templates for this measurement live here:
/ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMY/SAGL3/Data/
2014-12-23_H1SUSETMY_ESD_biasp9p5V_excLL.xml
2014-12-23_H1SUSETMY_ESD_biasp9p5V_excLR.xml
2014-12-23_H1SUSETMY_ESD_biasp9p5V_excUL.xml
2014-12-23_H1SUSETMY_ESD_biasp9p5V_excUR.xml

J. Kissel, R. McCarthy

At my request, after seeing that the EY BSC 10 vacuum pressure has dropped below 1e-5 [Torr] (see attached trend), Richard has turned on the H1 SUS ETMY ESD at ~2pm PST. I'm continuing to commission the chain, and will post functionality results shortly. 

Also -- 

I've found the ESD linearization force coefficient (H1:SUS-ETMX_L3_ESDOUTF_LIN_FORCE_COEFF) to be -180000 [ct]. I don't understand from where this number came, and I couldn't find any aLOGs explaining it. I've logged into to LLO, their coefficient is -512000 [ct]. There's no aLOG describing their number either, but I know from conversations with Joe Betz in early December 2014 that he installed this number when the LLO linearization was switched from before the EUL2ESD matrix to after. When before the EUL2ESD matrix the coefficient was -128000 = - 512000/4 so we was accounting for the factor of 0.25 in EUL2ESD matrix. I suspect that -128000 [ct] came from the following simple model of longitudinal force, F_{tot} on the optic as a result of the quadrant's signal voltage, V_{S} and the bias voltage V_{B}, (which we know is incomplete now -- see LLO aLOG 14853):
     F_{tot} = a ( V_{s} - V_{B} )^2
     F_{tot} = a ( V_{s}^2 - 2 V_{s} V_{B} + V_{B}^2)
     F_{lin} = 2 a V_{s} V_{B}
where F_{lin} is the linear term in the force model, and a< is the force coefficient that turns whatever units V_{S} and V_{B} are in ([ct^2] or [V_{DAC}^2] or [V_{ESD}^2]) into longitudinal force on the test mass in [N]. I *think* the quantity (2 a V_{B}) was mistakenly treated as simply (V_{B}) which has always been held at 128000 [ct] (or the equivalent of 390 [V] on the ESD bias pattern) and the scale factor (2 a) was ignored. Or something. But I don't know.

So I try to make sense of these numbers below.

Looking at what was intended (see T1400321) and what was eventually analytically shown (see T1400490), we want the quantity 
       F_{ctrl}
       -------
      2 k V_{B}^2
to be dimensionless, where F_{ctrl} is the force on the optic caused by the ESD. Note that comparing John / Matt / Den's notation against Brett / Joe / my notation, k = a. As written in T1400321, F_{ctrl} was assumed to have units of [N], and V_{B} to have units of [V_{esd}], such that k has units of [ N / (V_{esd}^2) ], and it's the number we all know from John's thesis, k = a = 4.2e-10 [N/V^2]. We now know the number is smaller than that because of the effects of (we think) charge (see, e.g. LHO aLOG 12220, and again LLO aLOG 14853).

In the way that the "force coefficient" has been implemented in the front end code -- as an epics variable that comes into the linearization blockas "Gain_Constant_In,"  (see attached) -- I think the number magically works out to be ... close. As implemented, the linearized quadrant's signal voltage is as shown in Eq. 13 of T1400490, except that the EPICs record, we'll call it G, is actually multiplied in
     V_{S} = V_{C} + V_{B}(1 - sqrt{ 2 [ (F_{ctrl} / V_{B}^2) * G  + 1 + (V_{C}/V_{B}) + (V_{C}/V_{B})^{2} * 1/4 ] )}
Note, that we currently have all of the effective charge voltages set to 0 [ct], so the equation just boils down to the expected
     V_{S} = V_{B}(1 - sqrt{ 2 [ (F_{ctrl} / V_{B}^2) * G  + 1] )}
which means that 
     G == 1 / (2 k) or k = 1 / (2 G)
and has fundamental dimensions of [V_{esd}^2 / N]. So let's take this "force coefficient," G = -512000 [ct], and turn into fundamental units:      
     G = 512000 [ct]             {{LLO}}
         * (20 / 2^18)     [V_{dac} / ct] 
         * 40              [V_{esd} / V_{dac}] 
         * 1 / (V_{B} * a) [(1 / V_{esd}) . (V_{esd}^{2} / N)]
     G = 9.5391e9 [V_{ESD}^2 / N]
   ==>
     k = 5.37e-11 [N/V_{ESD}^2]  {{LLO}}
where I've used V_{B} = 400 [V_{esd}] and the canonical a = 4.2e-10 [N/V_{esd}^2] originally from pg 7 of G0900956. That makes LLO's coefficient  assume the actuation strength is a factor of 8 lower from the canonical number. For the LHO number, 
     G = 180000 [ct]             {{LHO}}
         * (20 / 2^18)     [V_{dac} / ct] 
         * 40              [V_{esd} / V_{dac}] 
         * 1 / (V_{B} * a) [(1 / V_{esd}) . (V_{esd}^{2} / N)]
     G = 3.2697e9 [V_{ESD}^2 / N]
   ==>
     k = 1.53e-10 [N/V_{ESD}^2]  {{LHO}}
Which is within a factor of 3 lower, and if the ESD's as weak as we've measured it to be it may be dead on. So maybe whomever stuck in 180000 is much smarter than I.

For now I leave in 180000 [ct], which corresponds to a force coefficient of a = 1.53e-10 [N/V_{ESD}^2].

Throttling Turbo inlet valve confirms that gas load is coming from the chamber-side -> Connected LD and sprayed helium -> no response -> LD used is one that had been dedicated for view port testing in the labs and has older firmware that I am not familiar with -> can't find external cal-leak to confirm proper operation -> Did get a response however when O-ring joint (NW, KF) was sprayed at completion of testing -> Will leak test tomorrow (Wed) using "normal" equipment 

Summary: Recent CS seismic levels above 10 Hz are about twice iLIGO levels (probably because of HVAC flows), and a few times power-out levels. With power out, the CS has higher vertical motion and lower horizontal motion than the vault, suggesting that Love waves are scattered from the CS slab and reflected from a subsurface layer.  Thus the CS is likely to have different Newtonian noise levels than other stations.

During the power outage in August, I used battery power to obtain a Corner Station seismic spectrum with little self-inflicted noise. Figure 1, the X- and Y-axes, shows that the current level is, between 20 and 70 Hz, about twice the iLIGO level and about 4 times the power-out level. There is more self inflicted noise in the Y-direction than in the X-direction. This is consistent with the location of the broad-band sources, turbulent flows of air and mainly water, associated with the HVAC, roughly in the –Y direction from the seismometer.

Figure 2, the Z-axis, shows that, between 10 and 70 Hz, we are about a factor of 2 worse than iLIGO and a factor of more than 5 above the power-out level. The difference between recent and iLIGO spectra probably indicates that we haven’t yet completely returned HVAC air and water flows to iLIGO levels.

The Corner Station has always had more vertical and less horizontal seismic motion than other buildings (Figure 3). Figure 4 shows that the vertical/horizontal motion ratio at the corner station is considerably greater than one above 10 Hz, while the ratio is near one out away from buildings at the vault and at all other stations. Figure 4 also shows that this difference between locations is not associated with equipment in the LVEA but holds even when the power is out. With the power out, the CS horizontal motion in the 10 to 30 Hz band is slightly less than at the vault and the vertical slightly more (Figures 1 and 2). Assuming that the vault represents the building-free ambient background, it is as if the CS were converting horizontal into vertical motion.

These data are consistent with a hypothesis that the CS slab is large enough to scatter Love waves  (horizontally polarized surface waves), and that the scattered waves increase vertical motion by reflecting off of higher velocity layers tens of meters below the CS. Measured propagation velocities suggest that 15 Hz Love waves would have a wavelength of about 20 m. The outlying stations would mostly fit within circles of 12 m radius, while the corner station requires one with a 50m radius, consistent with a significant scattering difference between stations. If the broad peak at 15 Hz in the power-out trace of Figure 2 represents a resonance between the reflecting layer and the CS slab, than the reflecting layer would be about 15m below the surface. Love waves do not alter density distributions and so do not couple gravitationally. Thus conversion of Love waves into waves that couple, would increase Newtonian noise. This difference between corner and end stations may result in different requirements for an optimal Newtonian feed forward system.

I suspect that the ~250 Hz peak in the LLO DARM spectrum, and, I would guess, soon to appear in LHO’s DARM, is in part due to the piezo actuator/mount connection on the periscope (https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=14971). The last figure in the linked log is a photo of the mount on the LHO periscope. I set up an isolated version of the actuator/UA 200 to test my guess that the frequency is due to oscillation of the piezo actuator in the UA 200 mount. Figure 1 shows that a gentle tap on the actuator produces a large peak near 250 Hz. Figure 2 is a photo that shows the setup and, in the background, a picture of the actual setup on the LHO periscope. I eliminated several possible sources of the resonance, other than the mounting.  To test that it wasn’t the large optic with the piezo “flexure” acting as the spring, I epoxied an iLIGO version of the actuator with a large optic directly onto a plate. The lowest resonance was about 800 Hz. To check that it wasn’t the entire package oscillating on the connection to the table, I added weight to the mount (not the piezo actuator) and did not change the resonant frequency. I also attached the accelerometer directly to the mount. The peak was much larger, as expected.

There are two paths that I have been discussing with Rick and the Florida group. The first path is to design a new mount that holds the actuator at more than one point along its long axis and reduces moment of inertia. And the second path is to move the piezo actuator to the table and put a normal mirror in a UA 200 at the top of the periscope (since the periscope has a broad 150-300 Hz resonance, the piezo/mount resonance is amplified by being on the periscope). I think we should do both.

ISC end station upgrade RCG2.8.7:Rolf, Daniel, Jim, Dave

Rolf released the EXC code fix as RCG tag-2.8.7. The fix was tested yesterday on the DTS using Daniel's new Integrator Filter Module parts (IFM). Today I installed tag-2.8.7 on H1 and set the release/ pointers to refer to it. Daniel performed model cleanup and bug fixing of h1iscex and h1iscey during the morning, building against 2.8.7. We restarted these models several times today, with attendent DAQ restarts. After the final code change and restart, I repointed the release/ pointers back to RCG-2.8.5.

Daniel confirms the new RCG fixes the EXC and TP problems he was seeing with the IFM parts in the ISC end station models. This closes WP #4984

Power Down h1susquadtst: Jim, Dave

I took the h1susquadtst models out of the DAQ and we powered the front end down. Unfortunately this caused DAQ data errors for many front end systems for several minutes (susauxb123, lsc, asc, oaf in the corner station. all models in the mid and end stations). We tried a streamers restart on an end station sus model, which did not do anything. We then powered h1susquadtst back on and all the errors went away. I had forgotten to remove this system from the rtsystab file which may have caused the problem. After removing from both the DAQ and rtsystab, this time we issued a powerdown command and the DAQ problems were not repeated. To complete the power down of the LVEA test racks, all DC power supplies were powered off, as were the network switches. All power cords were removed from the FE computers.

EX Beckhoff h1ecatx1, Tuesday Freeze Up: Daniel, Dave

The EX Beckhoff system froze up at 13:50 PST. A repeat of its periodic Tuesday problems. Daniel restarted the system, but reported an unclean EPICS IOC startup (started too fast). Both conlog and the DAQ EDCU showed problems reconnecting to many h1ecatx1 channels. The problem was resolved after the EPICS gateway h1slow-h1fe was restarted, but even then it took about 10 minutes for conlog and EDCU to complete the reconnection in fits and starts.

Conlog reconfiguration: Dave

Following the ISC code changes, I reconfigured conlog. Later when conlog was not reconnecting to h1ecatx1, I added conlog's own epics channels to conlog to force a reconfiguration to hopefully permit a reconnection (this did not work, the epics gateway restart was the actual fix).

Partial and Modified-but-not-loaded Filter Module Files Loaded onto Front Ends: Jim, Dave

We performed the Tuesday reload of filter module files which had either been partially loaded or modified and not loaded over the course of the past week.

Modified files which were not loaded: ISIBS, SUSPRM, SUSPR3

Partially loaded files: SUSSR2, SUSSR3, SUSITMY, SUSBS, LSC, ASC, ASC-IMC, ISIHAM4, SUSETMX

SVN code with local SVN modifications: Dave

Attached is the list of FE user source code with outstanding local mods in SVN. Also listed, that for the guardian nodes source files.

LVEA: Laser Hazard
Observation Bit: Commissioning  

07:30 Karen – Cleaning in the LVEA
07:50 Cris – Cleaning in the LVEA
08:02 DGR delivering doors to VPW
08:50 Add 225ml water to diode chiller
09:30 Corey – Working in Squeezer Bay
09:35 Dave – Upgrade h1iscex & ey to RCG2.8.7 
09:35 Richard – Going to LVEA roof
10:28 Dave – Restart h1iscex
10:30 Praxair delivery of N2 to CP1
11:19 Kyle – Working on Instrument air in CS
11:42 Dave – Restart h1iscex
11:45 Dave – DAQ restart
12:01 Dave & Jim – Shutting down H2 Test Stand in LVEA
13:02 Richard – Turning on ESD at End-Y
13:34 Richard – Finished at End-Y
13:41 Elli – In LVEA working on IO2TR
14:00 Kyle – BSC9 on turbo pump
14:13 The PLCs at End-X stopped
14:35 Daniel – Restarted the End-X PLCs
14:37 Dave – Restart h1iscey and h1iscex
14:42 Dave – Restarted the DAQ
15:00 Kyle – Going to X-Beam manifold
15:49 Kyle – Going to End-X to check on pump down

Merry Christmas to all and to all a good night! 

X-end turbo also being backed by QDP80 -> Local scroll pump has same issue with its relay module as does the Y-end scroll, i.e. leads not landed on correct relay terminals or relay terminals not matching universal socket labeling etc. -> These two units have different relay components than the functioning YBM and XBM Turbo backing scrolls (why?)

This was running but valved-out for the recent HAM1/GV5/GV7 activities

Kyle, Bubba 
Switch contacts not really open and not really closed, i.e. ambiguous -> Resulted in switching failures past 24 hours or more

Attached is before and after ISI CPS & GS13 Spectra--No real change--Refs are with B STS and current traces are with the A STS.

See attached for the results.  The inline coupling is on the left and crossaxis is in the right plots.  The medms show the matrix elements.

This aLOG details the measurement.

Pretty good results here with ~10x improvement at the lowest frequencies.

Results from PSL weekly health report weeklies are posted below

The following elog is in support of Evan's upcoming elog on last nights TCS transient (turning off TCS)

Bottom line:

The contrast defect (CD) can be modeled as

CD = CD_0 + pi^2/8 * D^2*w^4/lambda^2 

where:
CD    : contrast defect
CD_0  : residual contrast defect, not due to ITM RoC mismatch
D     : Diopter change in (one) ITM, double pass, i.e. D=2*( 1/R_new - 1/R_old )
w     : beam spot radius on the ITM, nominally 53mm
lambda: wave length = 1.064e-6m 

Derivation: 

- incident beam:            |Psi> =  N exp(-r^2/w^2)
- ITMX reflection operator: exp(i*k*D*r^2/2)
- ITMY reflection operator: 1
- reflected field:          |r> = |Psi> * exp(i*k*D*r^2/4) *   cos(k*D*r^2/4)
- dark port field:          |t> = |Psi> * exp(i*k*D*r^2/4) * i sin(k*D*r^2/4)

- Power in dark port due to RoC mismatch:
    = k^2*D^2*w^4/32 = pi^2/8 * D^2*w^4/lambda^2 
  The bottom line formula for contrast defect follows from this.

Some other useful expressions:
- Power reflected from the Michelson:
    = 1 -  = 1 - pi^2/8 * D^2*w^4/lambda^2 
  Note that this power will be in a different mode, so the mode matching into the recycling cavity is expected to change.

And for reference, some Gaussian integrals:
   h_n := 
   h_n = n/4 w^2 h_(n-2)
   h_0 = 1
   h_2 = 1/2 w^2   
   h_4 = 1/2 w^4   
   h_6 = 3/4 w^6   
   h_8 = 3/2 w^8