I've continued to analyze stochmon's results (found here) for coherence between the h(t) channels of L1 and H1. One interesting line is at 74 Hz, at which I get coherences at both H1 and L1 from corner station accelerometers. You can find the full results for the coherence here and here, but I've attached some relevant summary slides. Any idea where this is coming from?

TITLE:  12/18 OWL Shift:  08:00-16:00UTC (00:00-08:00PST), all times posted in UTC     

STATE of H1:   Observing at ~75 Mpc.

Incoming Operator:  Jim

Support:   Jim, Jenne

Quick Summary:

The range has been ratty since 8 hours ago. Omicron shows band of glitches around 20 Hz and between 100-200 Hz. I don't see any significance changes in environment from 8 hours ago. I dig through the summary page breifly and found SR3 oplev spectogram looking very nasty started 8 hours ago, but the spectrum doesn't show any misbehave osems. So the cause of these glitches is still unknown.

Shift Activities:

• 11:34 Noticed ETMY timing error. Cleared it while still in Observing.

DMT Omega looks glitchy between 100-200Hz. Useism have reached 90th percentile. Low wind (<5mph). A 5.6M earthquake at North of Ascension Island is coming through. LLO is already down. Hope we ride this one......

TITLE:  12/17 OWL Shift:  08:00-16:00UTC (00:00-08:00PDT), all times posted in UTC     

STATE of H1: Observing

Incoming Operator:  Jim

Support: 

Quick Summary:

Very quiet night. Nothing to complain.

Shift Activities:

TITLE:  12/17 EVE Shift:  00:00-08:00UTC (16:00-00:00PDT), all times posted in UTC     

STATE of H1:   Observing for last 8+hrs with range of ~75Mpc 

Incoming Operator:  Nutsinee

Support:  None needed

Quick Summary:

A nice quiet shift.  useism holding steady at 0.4um/s for the last 24hrs.  The winds seem to be calming down.  And the snow is still on the ground.  Range has been a little ratty-looking 70-80Mpc.

Shift Activities:

• ETMy Saturations:  1:34, 7:27
• 6:16 PSL Crystal Chiller topped off
• 7:44 - 7:48 Acted as Buddy to Fyffe as he went to address PSL power meter (?)

Evan G, Jeff K

Summary:
We finally processed the data Jeff collected (aLOG 21325) to investigate the mysterious zero near 100 Hz. Unfortunately, while we began to further understand the calibration measurements, we also uncovered new issues needing investigation.

Solved:

1. We can verify the DC transconductance of the UIM BOSEMS is ~590 uA/V, and not off by a factor of 2 (see 21127 and 21142), and is an issue with the fast I MON
2. There is some "zero-like device" (see details below) that is at ~100 Hz

New mysteries:

1. The frequency dependence of the "zero-like device" appears to be f^{3/4}... WHUT?!
2. The state 3 and state 4 zero-pole might not be fit that well but we are not sure if it is real, but it looks smallish
3. The CAL model uses incorrect zero-pole pair in the UIM stage, and not using any of the fitted low-pass filter values

Details:

Taking Jeff's measurements of the driver electronics (plotted magnitude only called rawXX.pdf attached) and dividing by the fitted values for the low-pass filters from aLOG 21283, we can see the remaining effect of the BOSEM in the circuit (see XX.pdf attached). We plot the magnitude and phase of each state. Left hand plots are over the full range of 1 Hz to 10 kHz, while right hand plots are zooms from 1 Hz to 200 Hz.

Fortunately, from these measurements, we can confirm that the DC transconductance is: UL = 578 uA/V, LL = 589 uA/V, UR = 582 uA/V, LR = 600 uA/V. Earlier measurements (see 21127 and 21142) had found that this was off by a factor of 2, but we do find the expected value. However, when trying to understand the "zero-like device" we found that the frequency dependence at higher frequency goes like f^{3/4}! Now we are confused.

Looking closely at the low frequency region, and in the zoom (right hand plots) we see that the fitted zero-pole pair doesn't quite take out the low-pass filters for state 3 and state 4 (last two low-pass stages). This could be because of the buffers in the driver electronics, but we are not sure if this is really the cause.

We also started looking at the parameters file for the CAL model and found that the UIM parameters have the wrong zero-pole pair and, in addition, are not using the fitted low-pass filter values. This needs to be rectified.

The script that plots these results is in:

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Scripts/Electronics/analyze_uimdriver_wBOSEM_20150908.m

J. Kissel

As a part / start of the review process for the calibration pipeline, it has been requested that -- along with a long-term view of the PCAL to GDS-CALIB_STRAIN ratios (as shown in LHO aLOG 24285) -- we take snap-shots of the entire C01 GDS-CALIB_STRAIN spectrum at a smattering of times, and take the ASD ratios as has been done for the official strain sensitivity plots (see e.g. G1501223). I've done so over the early part of the run, between Sep 11 and Oct 22 2015, every 5 days or so, 
Sep 11 2015 20:30:43 UTC
Sep 18 2015 04:50:43 UTC
Sep 25 2015 07:23:43 UTC
Oct 01 2015 01:30:43 UTC
Oct 05 2015 05:31:43 UTC
Oct 11 2015 18:57:43 UTC
Oct 17 2015 07:41:43 UTC
Oct 22 2015 03:12:43 UTC
(recall that we get 420 [sec] of data for each ASD -- see T1500365).  Attached are the zooms of the ASDs of both GDS-CALIB_STRAIN and PCAL displacement around the three PCAL frequencies (
C01_H1_O1_Sensitivity_displacement_asd_pcalzoom.pdf) and the ratio of these ASDs (C01_H1_O1_Sensitivity_displacement_asd_pcalzoomratio.pdf) for these 8 data sets. I figured this was plot overload, so I leave all nine plots that come with each official strain simply committed to the CalSVN here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/H1/Results/DARMASDs/
where the collection of plots are dated accordingly (e.g.  2015-10-22_C01_H1_O1_Sensitivity.pdf). 

The message: for these spot-checks, the ratio between GDS C01 calibrated displacement and PCAL calibrated displacement is within the expected 10%, and all but the earliest data point data point is better than 5%. Very good -- great job CAL team!

-------
These plots were made with a generalization of the official strain producing script that now lives in
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O1/Common/Scripts/produceofficialstrainasds_O1_C01.m

Per the Shift Check Sheet (for Thursday's task), I went and checked on the Crystal & Diode Chillers for the PSL.  The Crystal Chiller was not at maximum, so I added 125mL (basically to get the water's meniscus close to the "MAX" level).  NOTE:  according to the notepad, this was filled on 12/16 with 125mL also.

Diode Chiller was fine (no red error light).

H1 has been locked for 5.5+ hrs with a range between 70-80Mpc (only one ETMy saturation).

All running well here.  I was not able to log into the ops workstation (operator0) at the beginning of the shift, but Jim B was able to remedy that.

Snowed earlier in the shift, and we have about 0.75" of snow on the ground currently.  Winds are at about 6mph & useism is at 0.4um/s

The omicron scans of the top ten Hanford BBH/BNS triggers on December 16th show a notable recurring wave-like glitch. The glitches are present in the following scans:

https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/GW/1134302174/
https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/GW/1134294300/
https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/GW/1134291513/
https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BNS/GW/1134295111/

Inspection of the auxiliary channels revealed that these signals seem to stem from one channel: H1:ASC-Y_TR_B_PIT_OUT_DQ.The scans for this channel are visible here:

https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/1134302174/#H1:ASC-Y_TR_B_PIT_OUT_DQ
https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/1134294300/#H1:ASC-Y_TR_B_PIT_OUT_DQ
https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BBH/1134291513/#H1:ASC-Y_TR_B_PIT_OUT_DQ
https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/BNS/1134295111/#H1:ASC-Y_TR_B_PIT_OUT_DQ

The rest of the scans from December 16th can be accessed from the chart here:

https://ldas-jobs.ligo-wa.caltech.edu/~jacob.broida/Dec16/Results.html

TITLE:  12/17 Day Shift:  16:00-24:00UTC 

STATE of H1: Observing, only just

Support: Yes

Quick Summary: Quiet shift until an earthquake knocked us out of lock

Shift Activities:

17:45 Mitch to Optics Lab

19:00 Jodi to Mid-y and EndX, back 19:45

It was a relatively quiet shift. We were locked at about 75 Mpc until about 15 minutes ago when a 6.4 earthquake in Mexico hit us.  .03-.1 hz ground motion is about 5 microns. Otherwise, wind is moderate, microseism was about .5 microns. Now we play the waiting game.

I've taken some measurements indicating the EX sensor correction in Z is causing problems for the ISI. I've ramped it off,   watching the IFO for issues and will be taking some measurements. This may result in a change of configuration for the ISI, eventually.

J. Kissel, K. Izumi, J. Betzwieser

Since we've last taken the full actuation characterization measurement suite (see LHO aLOG 20940, T1500383), we've revised a few bits of the measurement methodology such that we might have more successful measurements. I recall them here to help us remember what we plan to do.

The major differences are as follows:
(1) Order of measurements (LLO innovation). In order to try to make the suite as robust against environmental or other reasons for lock-loss, Joe has suggested that we take the full IFO portions of the suite *first* while the IFO is stable and fully operational. These "final results" are really the only measurements that *need* to be in the same lock stretch, such that we can make sure that the optical gain of the FULL IFO is the same. Only after all 6 of those sweeps are complete, *then* we intentionally break the IFO and begin the ALS DIFF and Free-swinging Michelson measurements with lesser configurations of the IFO. The full outline of the measurements is attached as a picture.

(2) Merging of Free-swinging Michelson and ALS DIFF, IFO propogation measurements (LLO innovation). To-date, LHO has propagated the Free-Swinging Michelson absolute calibration from ITMX L2 stage to ETMX using the traditional single arm locked on red. However, during his last attempt, Joe had used ALS DIFF to propagate the the absolute calibration because (a) ALS DIFF is a more sensitive measurement and (b) we need to lock ALS DIFF anyways in our path propogate the ALS DIFF absolute calibration.

(3) Using the "super actuator" ALS DIFF transfer function (LHO innovation). This was mentioned in LHO's last attempt (see 20940). The idea being to reduce the number of seeps by one, by taking advantage of a little loop math:
From a simple diagram of the loop, one can show that  
   L3 LOCK IN2       1
   ----------- = ----------
   L3 LOCK EXC   1 + G_DIFF
which is true with any excitation at any point around the loop, just like is done "normally" done with a DARM IN2 / DARM EXC TF. Further, 
DIFF_PLL_CTRL       1
------------- = ----------  x  ETMX  x  DIFF
L3 LOCK EXC     1 + G_DIFF
one can immediately see that the absolute calibration of the super-actuator ETMX falls out of ratio of these two transfer functions, assuming you have the absolute calibration of DIFF such that you can divide it out (i.e. the [Hz/ct] and z:p = 40:1.6 Hz pair of the VCO, i.e. measurements (3) and (4), which we do, a priori). What's great, is that since you're using the same excitation, as long as you store both of these channels in the template, you can directly measure and export the transfer function ratio that you really want,
   DIFF_PLL_CTRL
   ------------- = ETMX x DIFF
    L3 LOCK IN2
and thus you've reduced two measurments into one.

BNS range is taking a small dip of ~5 Mpc. Probably due to an increasing traffic. Otherwise everything looks good. Wind speed < 10mph. Useism hanging out at 50th percentile. Ground motion in EQ band is trending downward. Couple of ETMY saturation since shift started.

Summary:

There were 11 scheduled hardware injections:
1134345924 1 1.0 coherentbbh10_1128678894_
1134348928 1 1.0 coherentbbh11_1128678894_
1134353728 1 1.0 coherentbbh15_1128678894_
1134354928 1 1.0 coherentbbh16_1128678894_
1134356128 1 1.0 coherentbbh17_1128678894_
1134357328 1 1.0 coherentbbh18_1128678894_
1134359800 1 1.0 coherentbbh11_1128678894_
1134361000 1 1.0 coherentbbh12_1128678894_
1134362200 1 1.0 coherentbbh13_1128678894_
1134363400 1 1.0 coherentbbh14_1128678894_
1134364600 1 1.0 coherentbbh19_1128678894_

The first column is the start time of the injection. The second column is an integer that specifies that it was a CBC injection. The third column is the scale factor. And the fourth column is the beginning prefix of the parameter/waveform files.

The waveform files can be found here: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/Inspiral/H1/ and https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/Inspiral/L1/

The parameter files can be found here: https://daqsvn.ligo-la.caltech.edu/svn/injection/hwinj/Details/Inspiral/

Two of these happened in L1 only because H1 lost lock. Those two are:
1134348928 1 1.0 coherentbbh11_1128678894_
1134357328 1 1.0 coherentbbh18_1128678894_

Segments:
The segment database reports 9 injections for the H1:ODC-INJECTION_CBC:2 flag:
1134345929,1134345931
1134353734,1134353735
1134354934,1134354935
1134356134,1134356135
1134359806,1134359807
1134361005,1134361007
1134362206,1134362207
1134363405,1134363407
1134364606,1134364607

And 11 for L1:ODC-INJECTION_CBC:2 flag:
1134345929,1134345931
1134348934,1134348935
1134353734,1134353735
1134354934,1134354935
1134356134,1134356135
1134357333,1134357335
1134359806,1134359807
1134361005,1134361007
1134362206,1134362207
1134363405,1134363407
1134364606,1134364607