To answer Jeff's question about the wind, I looked at the ten hour lock, and the three hour lock starting about 23:30 UTC (ignoring the stochastic injection). I wrote a custom script to make the plots, since I couldn't get sensemon range from NDS. I've done a 3-minute median filter on the wind and range minute trends to smooth them out a bit.

The first plot shows the wind and range for the first lock. Around 12:30 UTC, the spectrogram (second plot) shows a big increase in the noise, and there's a corresponding decrease in the range. I think this is unrelated to the wind, and will be investigated elsewhere, so I've cut this lock off about 320 minutes in (third plot). The fourth plot is the scatter of the wind versus the range. A simple fit gives a value of 8.4 Mpc at zero with an 0.03 Mpc decrease per MPH of wind. The fifth and sixth plots are this repeated for the other lock, starting after the stochastic injection ends. The fit is 9.0 Mpc at zero with an 0.01 Mpc decrease per Mpc of wind.

I've attched the script I used. It needs a cache file for data of type H-SenseMonitor_CAL_H1_M called snsw.lcf. There's some values hard-coded, but it should be obvious what to change.

16:24 Jim left the interferometer locked. Intent bit switched to Undisturbed.

19:48 Lock loss. PSL tripped ("Epics Alarm" went red). The guardian didn't switch off the undistrubed intent bit. I switched it off few minutes later.

20:40 PSL recovered (Thank you Peter K!) but IMC wasn't. I waited at least 5 minutes but it doesn't seem to lock itself. I trended and adjusted the MC1, MC2, and MC3 pitch back to where it was before it lost lock.

21:22 IMC locked. Redid initial alignment for the first time today.

22:18 Locked at LOWNOISE_ESD_ETMY (~11Mpc)

22:28 Intent bit switched to Undisturbed

22:50 Undistrubed intent bit turned off. Attempted to damp the violine modes.

22:55 Intent bit switched to Undistrubed. Jeff Kissel suggested I leave the violin modes alone.

23:01 Lock loss. PSL tripped AGAIN ("Interlock OK" went red).

23:09 PSL recovered

23:47 I realigned IMC again. It seems to me that IMC optics read off the bad alingment from somewhere and didn't go back to where it was when the ifo was locked. I was able to bring the IMC reflected light down to 52 counts (It was 53 during the previous lock). The alignment is saved. AS Air flashing at none 0,0 mode. Redid the initial alignment (didn't take too long. The ALS was already good).

           ALIGN_IFO stays on MICH_DARK_LOCKED for a very long time even though AS AIR was ~0. I moved on to SRC ALIGN before the panel was green.

00:17 Lock loss at ANALOG_CARM. IMC locked itself this time.

00:34 Locking again at LOWNOISE_ESD_ETMY (~10 Mpc). Intent bit switched to Undisturbed. Leaving the interferometer at this state. Wind slowly picking up speed.

A few notes before I leave the chair:

- As Jeff K. has requested, it would be nice if a Detcharian out there could plot the BNS inspiral range vs. wind speed during lock segments. I'm unable to do ligo-proxy-init from the control room computer and don't know of other way to get the BNS range data.

- Guardian does not switch off the Undisturbed intent bit when lock lost.

- IMC lock does not recover on its own after both PSL trips, but recovered just fine after a lock loss that doesn't cause by a PSL trips.

- We have a total lock time of ~20 hours during this 40-hour mini run (started Friday 8AM, ended Sunday at midnight - locking 50% of the time). 

I guess that is it for the Mini run. Enjoy the data!

Since the initial alignment hasn't been done since last night. I'm redoing the initial alignment. Wind speed looks good so hopefully I can get it back up again soon.

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, E. Daw

In this current lock stretch, I've begun Ed's Stochastic Injection (LHO aLOG 18161) starting at 23:29 UTC. Scared of breaking the lock, I've started with multiplying the whole injection by a scale factor of 0.1. Out of habit, this has gone through the H1:CAL-INJ_TRANSIENT bank instead of the H1:CAL-INJ_CW bank, but signals arising from both banks should result in identical DARM CTRL [ct]. It should last ~10 minutes. The observation intent bit is on.

J. Kissel,

Early signs from yesterday's measurement: The DARM coupled cavity pole is now up at 355 [Hz], much closer to the designed/ideal/predicted LLO value of 389 [Hz] (LLO aLOG 15923). Hopefully it stays consistent with today's measurement (or is higher!). Also -- since I'm getting great coherence out to several [kHz], I can expose and refine the precision the ESD driver pole frequency (nominally at 2 [kHz]; T1000220, specifically, pg. 6 of 'ESD_PA95_circuit_diags_comp_overlays_1_of_6.pdf'; preliminary results are pointing to that it's actually 2.2 [kHz]). 

I'll post full analysis of both measurements compared against all prior measurements in a bit, but this DARM OLG TF I just took lives here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER7/H1/Measurements/DARMOLGTFs/2015-05-02_H1_DARM_OLGTF_LHOaLOG18181.xml
For this measurement, I 
- decreased the frequency range to *actually* 5 to 5000 [Hz] (because getting down to yesterday's 3 [Hz] took too long). The measurement now takes 25 minutes.
- decreased the drive envelope's amplitude above 1 [kHz] by 2, to make sure (a) I don'tneed to turn of the ETMY L3 stage digital limiters, and (b) I'm sure it's not me ringing up the violin modes
- increased the drive envelope's amplitude below 10 [Hz] by 2, in attempts to get better coherence in the 5 to 15 [Hz] region. It didn't work, will try to drive harder there next time.

Relevant loop gain information also attached.

Jeff wants to take a DARM OLG measurement, so I've turned off the intent bit. Service will resume when he's done.

From looking at a few of the loudest Omega scans in the recent lock, i.e. scan 1 and scan 2, I noticed that ASAIR_A_RF45_Q is glitching in a similar way. There's about a one minute period of excess glitching in DARM (first plot). A coherence spectrogram of ASAIR_A_RF45_Q with DARM shows high coherence in the right frequency band, 20 to 500 Hz, only during this time (second plot). There's only excess noise in this AS45Q channel during this time (third plot). There's no excess coherence of MICH, PRCL, or SRCL with DARM during this time (fourth through sixth plots).

I'm not quite sure what this indicates - maybe an excess of junk light, or intensity fluctuations onto the OMC? There's no indication that the coupling to DARM is changing, since the AS45Q channel itself starts glitching at the same time DARM does. We got some loud CBC injections at the start of the lock, so we can hopefully use those to check whether this channel is safe.

J. Kissel, J. Warner, D. Barker

HAM6 Software / IOP Watchdog, which is triggered on the TOP OSEMs of the OMC SUS, tripped at 
May 02 2015 18:15:50 UTC or 1114625766
shutting down the entire HAM6 SEI system, HEPI and ISI. As soon as the SEI system was shut off, the BLRMS of the OSEMs that were upset went down.

The offending OMCS OSEMs were T3 and LF, which are sensing unrelated DOFs.

@DetChar what happened here?

J. Kissel, J. Warner

We're trying to recover the IFO after the epic 10.5 [hr] lock stretch, but we're having trouble getting past the DC READOUT transition. I attach the last four lock losses,  
2015-05-02 16:36:53.342000  ISC_LOCK  LOWNOISE_ESD_ETMY -> LOCKLOSS
2015-05-02 16:56:35.161000  ISC_LOCK  DC_READOUT -> LOCKLOSS
2015-05-02 17:10:12.335000  ISC_LOCK  DC_READOUT_TRANSITION -> LOCKLOSS
2015-05-02 17:36:44.730000  ISC_LOCK  DC_READOUT_TRANSITION -> LOCKLOSS
in which all but the first (which is the end of the 10.5 [hr] stretch) show a ring up of some 8 [Hz] oscillation. In the DARM ASD this appears as a sharp non-stationarity at 6-8 [Hz] with harmonics at 12 and 18 that show up as soon as the OMC starts to look for the carrier. Is this back scattter? Is this the DARM offset being incorrect? I don't know... we'll keep lookin'; any help is appreciated.

Not Nutsinee, this is Jim. Didn't see I was still logged in as her.