It seems that the ETMX oplev calibration has been off by a factor of 2.3 with the oplev values smaller than that expected from the alignment biases. I have corrected the calibration of yaw, but not pitch yet. I will do the calibration of pitch tomorrow.

The attached is a plot of the oplev signal in yaw as a function of the alighnment bias before the correction. According to a least square fitting, the oplev was underestimating the angle by a factor of 1/0.436 ~ 2.3. I corrected this by multipling the same factor to the oplev pitch gain so that the gain is now 81.2 /0.436 = 186.2 urad/cnts.

7 - 8 Cris & Karen in LVEA (note on desk)
07:49 Turned the state bit from undisturbed to commissioning
09:23 Elli and Kiwamu to ISCT1 to add photodiode to table
10:05 Ed to H2 building
11:06 Bubba going into LSB LDAS computer room to look at fire extinguisher system
13:50 Keita to end Y to check IR QPD amplifiers
14:24 Keita back
14:42 Kyle to mid Y
16:06 Evan and Elli to ISCT1 to check on photodiode
16:10 Kyle back
16:12 Evan and Elli back

Summary of the PSL trips from 2015-5-1 to 2015-5-3 during the LHO mini run.  Every instance of the PSL tripping was due to the same interlock, H1:PSL-IL_DCHILFLOW, tripping with no apparent loss in coolant flow for the diode chiller, H1:PSL-OSC_DCHILFLOW.  The first three trips on 2015-5-3 were during the long interlock trip that Nutsinee reported in alog 18187.  Data for the other PSL trips over the last 10 days have been reported in alogs 18083 and 18134.  All times UTC.

Using 0100pdt on Saturday morning as an okay time to check the ~middle of the 10 hour lock stretch during the run.  No large coherence with DARM_CTRL for any of the three controlling pressures for the HEPI Pump Controller Servos.  Everything is below ~0.6 and most all just look like noise.

Attached are power spectra of the sum signals of the 4 IR QPDs that are on the ETM Trans Mon tables (in-vac). Each Trans Mon has 2 QPDs (labeled A & B). Also included in the plot is a spectrum of QPD_B from the L1 Y-arm. As discussed in LLO log entry (hmm, LLO log is down), the L1 Y-arm QPDs show broad noise peaks at 30 Hz, 60 Hz, 90 Hz; these peaks show up in DARM and are believed to be caused by scattered light at the end station (the L1 X-arm QPDs do not show these noise peaks).

The good news is that the H1 TransMon QPDs do not show anything like the scattered light noise peaks seen in the L1 Y-arm, and in general the H1 QPD spectra are lower than the L1 spectra (all channels are normalized to unity for a single arm lock). The RMS of the X-arm transmitted power fluctuations is about 30/10,000 = 0.3%; about 1% pk-pk.

The bad news is that there is something wrong with QPD_A on the Y-arm. It shows an elevated 1/f noise above a few Hertz. This is presumably related to the QPD 'clipping' problem reported by Keita in entry 18204. Looks like some electronics problem to me. On the other hand, the X-arm QPD_A is anomolous in another way: its average value is about 30% lower than the others (see table below).

For reference, the average values of the QPD NSUM channels were:

Laser Status: 
SysStat is good
Front End power is 31.4W (should be around 30 W)
FRONTEND WATCH is RED
HPO WATCH is RED

PMC:
It has been locked 0 day, 23 hr 54 minutes (should be days/weeks)
Reflected power is 2.0 Watts and PowerSum = 24.3 Watts.
(Reflected Power should be <= 10% of PowerSum)

FSS:
It has been locked for 5 h and 4 min (should be days/weeks)
TPD[V] = ~1.1V (should be 1.3 - 1.6)

ISS:
The diffracted power is around 8.5% (should be around 7%)
Last saturation event was 22 h and 57 minutes ago (should be days/weeks)

Attached are the series of plots: ASDs, Coherences, and TFs; for and between the three LVEA SEI STS2 instruments.

Last week I moved the STS2-B (ITMY) to concrete (References for it are the old unit on vinyl under the igloo.)

The current traces attached are from this morning at 0130pdt.  I had a problem with the calibration and units before, but getting that straight hasn't made answers to all the questions clear.

The three Z ASD are right on top of one another to below 20mHz.  The Y DOF ASDs are similar but they diverge below 40mHz.  For the X DOF, the HAM2 instrument seems the outlier diverting from the other ASDs as high as 90mHz whereas ITMY and HAM5 are hand in hand until 20mHz.

The Coherences look very good on Z, other DOFs are here and there.  Maybe as expect too, the Z TFs look great, and the other DOFs are 'it depends.'

I think we can say that the removed STS2 should go in for overhaul and the HAM2 machine should be huddle tested with one of the others.

Apparently I haven't aloged it last week, but oplevs recive the IR scatter from the arm. It's not a big deal, I'm writing this just for the record.

Attached shows one 7W lock when ETMY OPLEV was not working (no light). As soon as IR resonates in the arm, ETMY oplev segments jump up  and the SUM goes to 560 counts (left and middle row). If the oplev laser was alive, this 560 counts would have been added on top of about 30k counts. Fortunately this is mostly common for all four segments, and the effect on the angle readout, when the oplev laser is alive, would have been about  0.03% of the full range, or about 0.03 urad.

The same thing happens to ETMX (right bottom) except that the oplev laser was alive and that the scatter increased the oplev SUM by only 360 counts.

For ITMs the SUM due to the arm scattering seems to be abount an order of magnitude smaller than ETMs, but the oplev power itself is also smaller (3000 to 4000 counts).

(Update: See Peter's alog.)

I looked at the lock stretch from last night and the IR QPDs on TMSY still show the sign of clipping though the saturation was fixed.

On the left column you have X QPD SUM(B)/SUM(A) data (top), which is basically just a solid flat line after the IR resonates in the arm over a large change in the IR alignment.

The top right plot for Y QPD SUM ratio has the same scale as the top left, it goes up and down in low power lock and then steps up when the power was increased. Even during the 10W lock, the ratio was not as stable as X.

It's not like Y beam is particularly moving larger than X.

J. Kissel

Now that the mini-run is complete, I've reverted the "nominal" ISC_LOCK guardian state back to LSC_FF (I'd changed it to the mini-run state of "LOWNOISE_ESD_ETMY" on Friday, see LHO aLOG 18145). I've reloaded the guardian code change, and confirmed that the "nominal" box is now surrounding the LSC_FF state; see attached.

SEI
nothing planned

SUS
nothing planned

CDS
continue preparations for chassis swap
possible RCG upgrade on Tuesday

FAC
starting repair of wall around patio area
wet paint all around building
expecting delivery from Sunbelt

PSL
trips appear to all be related to flow sensor

VAC
preparation for vent of end stations in June
need to run pump cart at Y end for 24 hours to bakeout RGA, possibly Tuesday

This morning AOM diffracted power was up to ~ 13% with a refsignal setting of -2.00 . I've adjusted the Diff power to ~ 8.5% -> refsignal = -2.05

J. Kissel

Having processed the last two DARM open loop gains -- the first measurements out to 5 [kHz], and the first measurements after we've tuned up the ASC loops to give us a consistent recycling gain of 35-40 -- I can now make the following statements:
- The DARM Coupled Cavity Pole (CCP) frequency is now consistently much closer to the "as designed" value. The measurements are consistent with a model of the DARM loop using a CCP of 355 [Hz].
- The ETMY ESD's driver pole frequency is 2.2 [kHz], not the colloquially thrown about 2 [kHz].
- I've added the violin modes to the model of the QUAD suspension, and they have no appreciable effect, but I'll leave them in for completeness.

On what these measurements and changes to the model mean for the uncertainty (precision and accuracy):
- The modeled unknown time delay remains at 0 +/- 5 [us].
- The frequency dependent uncertainty in the calibration model remains at +/- 2.5% in magnitude and 1 [deg], but I've data to back up that this extends out to the entire required* frequency band 10 and 2000 [Hz]. See attachment 2015-05-02_FittedCCP_H1DARMOLGTF.pdf (* OK, what *used* to be the requirement. The requirements are now extended albiet inflated out to 5 [kHz]; see T1300950)
- Over these last two measurements, the scale factor used to match the model against measurement has only varied by 3%. Indeed, if you cluster the eight measurements, grouping by CCP, then the standard deviations of the three, three, and two measurements are 7%, 41%, and 3%. However, the total standard deviation of all measurements is 22%, and the latter two measurements are only 1 day apart. From the data I have, I'm still not confident in decreasing the scale-factor uncertainty below 22%; perhaps PCAL can make a better statement on this (but I fear the current Mini-Run noise is too high for the low-frequency PCAL line). See 
2015-05-02_upto5kHzOnly_FittedCCP_H1DARMOLGTF.pdf
- The current calibration installed in the CAL-CS model is incorrect, both in frequency dependence and scale factor. 
    - Frequency dependence: The CAL-CS filters assume a DARM CCP of 389 [Hz] in the sensing path, and an ESD Driver Pole (ESDP) of 2.2 [kHz] in the actuation path. For the latest lock stretches, that inflates the uncertainty of CAL-DELTAL_EXTERNAL_DQ with a known, systematic error of 
      current / correct = ( 1 / (current CCP / correct CCP) + (current ESDP / correct ESDP) ) / (properly normalized)
                        = ( 1/zpk(-2*pi*389,-2*pi*355,355/389) + zpk(-2*pi*2e3,-2*pi*2.2e3,2.2e3/2e3) ) / 2
      which translates to as much as a 7% magnitude error at 1 [kHz], and 1.8 [deg] swing in phase surrounding 1 [kHz].
      This is demonstrated in 2015-05-02_H1CAL-CS_Systematic.pdf,
      This is also reflected in the statistical uncertainty estimate. All comparisons are shown if a 389 Hz CCP and 2 kHz ESDP were used in 2015-05-02_389HzCCP_2p0kHzESDPole_H1DARMOLGTF.pdf.
    - Scale Factor: this depends on whether we want to use 22% or 3% for our scale factor uncertainty. If 22%, then the last two lock stretches still fall within the 1.1e6 +/ 22% [ct/m]. But, if the scale factor is 1.2725e6 (the mean of the last two scale factors), then that indeed falls outside of 1.1e6 +/-3%
    - We *still* have not implemented any compensation for the analog or digital, AA or AI filters. 
- The GDS/DMT produced calibration is off just as much as the CAL-CS produced calibration, because GDS/DMT calibration is using the same filters.

------------------
All parameter files have been committed (with updated ESD driver poles, and fitted DARM coupled cavity poles) here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Scripts/
H1DARMparams_1109994128.m
H1DARMparams_1111998876.m
H1DARMparams_1112399129.m
H1DARMparams_1112933759.m
H1DARMparams_1112942996.m
H1DARMparams_1113119652.m
H1DARMparams_1114541595.m
H1DARMparams_1114634170.m

Which are processed by the DARM model function here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Scripts/H1DARMmodel_preER7.m

And then compared with the script here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Scripts/CompareDARMOLGTFs.m

J. Kissel, N. Kijbunchoo

We've tried several more times to reacquire lock after the damping the rung up violin modes (LHO aLOG 18153), a slow but steady increase in wind up to the current 30-35 [mph] (see 1st attachment), the PSL tripping (LHO aLOG 18159), a mysterious guardian failure (LHO aLOG 18162), and now a rigorous trip of the ETMX seismic isolation because of what I think is my user error. We've run out of steam, and I don't think there's a point in continuing to battle the IFO under these terribly windy conditions. We'll start again tomorrow morning.

Some details from the few lock acquisition attempts after the Guardian failure:
Attempt 1: Just let the guardian try and do it's thing. Lost lock at the start of TRANSITION_TO_QPDs (but didn't realize it)
Attempt 2: Noticed the recycling gain (as measured by ASAIR) was low, lost lock again
Because I'd heard Kiwamu talking about low recycling gain vs. high recycling gain causing a sign flip in the ASC loops, I suspected the low recycling gain was the problem. So I had Nusinee play with the alignment of PR3, and the ITMs to try and get the ASAIR  signal back up into the 600s (where is was in the 500s). She found that PR3 YAW was most effective (and the recycling gain has stayed in the 600s since she touched it up) -- we still lost lock on the TRANSITION TO QPDS.
Attempt 3: After relocking, the recycling gain came up awesomely with out having to touch anything. Still lost lock at the same point.
Attempt 4: This time, requested DRMI_LOCKED, such that we could go manually through each of the steps leading up to SWITCH_TO_QPDs. We got as far as the step right before -- REDUCE_CARM_OFFSET -- which completed. I was *just* about to hit go on the TRANSISTION_TO_QPDS when we lost lock.
Then Nutsinee noticed that the ETMX SEI isolation system had tripped. After chasing down a bunch of WD trip and lock loss tools, we found the lock loss in the following order:
HEPI 03:54:12 UTC (Actuators)
IFO  03:54:13 UTC 
ISI  03:54:19 UTC (ST1 Actuators)
TMSX 03:54:24 UTC
Now, because I was messing around with the ISC_LOCK guardian in manual, I have a feeling it was me somehow sending a huge Tidal impulse to HEPI that took down the chamber but I can't be sure. Looking at the plot of the lock loss, it's certainly a huge impulsive spike that kicks the chamber, not like some slow shove from the wind or as if the Tidal was huge (again because of wind) and it suddenly hit the edge of the range.

Anyways, I don't think there's something systematically wrong with HEPI that we need to freak out about, this was one lock loss of MANY over the past day, and my gut feeling tells me that the problem right now is that the TRANSITION_TO_QPDs fails while it's servoing the ALS-C_DIFF_PLL_CTRL_OFFSET and even during the REDUCE_CARM_OFFSET, because there's too much uncontrolled arm angular motion (from wind) for the CARM reduction to happen. According to the guardian logs, this servo seems to stress and eventually break the IMC lock, but I'm not sure if it's a cause or effect.

We're gunna try to lock one more time, because getting to DRMI_LOCKED is incredibly robust, even in these high winds. BUT, we're not gunna log the result if negative and just go home. 

I have created a 10 minute injection file simulating a stochastic source at omega_GW=1 at 100Hz, and placed it on the cds system in:
/ligo/home/edward.daw/research/hardware_injections/2015_05_01/inj10mins.txt
The file was created as follows:
on the h1hwinj1 machine,
cd /ligo/home/edward.dad/research/hardware_injections/dependencies/sources/virgo/NAPNEW/SCRIPTS/IsotropicSbGenerator
python IsotropicSbGenerator.py --init IsotropicSbGenerator2.ini
This code generates a single 600 second frame which I subsequently moved to /ligo/home/edward.daw/research/hardware_injections/2015_05_01/SB_HI_L1-1114555770-600.gwf.
To convert the frame to an ascii file, I tried running a local matlab, but I couldn't get a license. I therefore shipped the frame to my laptop, and used matlab interactively:
>> [data,tsamp]=frgetvect('SB_HI_L1-1114555770-600.gwf','H1:strain',1114555770,600);
>> outfile=fopen('inj10mins.txt','w');
>> fprintf(outfile,'%g',data);
>> fclose(outfile);
...and finally I used gsisftp to move the resulting text file back to the cds machine at the above location.
The above matlab code could easily be used to scale the data by a factor, as it seems you have done with previous injections, if the existing scale proves inappropriate for the injection. Please inject this 10 minute duration signal once the machine is stable and you are ready for more injection tests.
Thanks. 
Ed