Trends are the last 20 days  due to trends not being taken last week.

WeeklyXtal - Nothing unusual. Amp powers following humidity. Normal power dergading in Osc diode power. Blown readback on Osc DB3 current.

WeeklyLaser - normal. Incursions Monday.

WeeklyEnv - normal

WeeklyChiller - normal except for a trip on Tuesday morning.

Around 8:30 AM local. Cameras glitched again.

State of H1: relocking, at ENGAGE_SOFT_LOOPS

Activities:

• 9 hour lock that started in the previous shift
• as the lock degreded, I went out of Observe to tweak alignment to preserve the lock
• 15:33UTC, lockloss, plot attached

• 13:46UTC, H1 out of Observe
• adjusted TMSX and TMSY
• 14:01UTC, running a2l
• 14:06UTC, a2l is done
• 14:06UTC, H1 back in Observe

Could someone on site check the coherence of DARM around 1080 Hz with the usual jitter witneses? We're not able to do it offsite because the best witness channels are stored with a Nyquist of 1024 Hz. What we need is the coherence from 1000 to 1200 Hz with things like IMC WFS (especially the sum, I think). The DBB would be nice if available, but I think it's usually shuttered.

There's indirect evidence from hVeto that this is jitter, so if there is a good witness channel we'll want to increase the sampling rate in case we get an SN or BNS that has power in this band.

• 09:15:03UTC, H1 was taken out of Observe by the channel H1:CAL-PINJX_TRANSIENT_GAIN, when it was set from 0 to 1 (screenshot attached)
• Since Adam's injections were scheduled for 09:20UTC, I'm assuming this change was as a result of his code setting up his injection
• I changed the channel to not monitored
• 09:16:26UTC, H1 back in Observe

I made a few measurements tonight, and we did a little bit more work to be able to go to observe. 

Measurements:

First, I tried to look at why our yaw ASC loops move at 1.88 Hz, I tried to modify the MICH Y loop a few times which broke the lock but Jim relocked right away.  

Then I did a repeat of noise injections for jitter with the new PZT mount, and did repeats of MICH/PRCL/SRCL/ASC injections.  Since MICH Y was about 10 times larger in DARM than pit, (it was at about the level of CHARD in DARM) I adjusted MICH Y2L by hand using a 21 Hz line.  By chaning the gain from 2.54 to 1, the coupling of the line to DARM was reduced by a bit more than a factor of 10, and the MICH yaw noise is now a factor of 10 delow darm at 20Hz.  

Lastly, I quickly checked if I could change the noise by adjusting the bias on ETMX.  A few weeks ago I had changed the bias to -400V, which reduced the 60Hz line by a factor of 2, but the line has gotten larger over the last few weeks.  However, it is still true that the best bias is -400V.  We still see no difference in the broad level of noise when changing this bias. 

Going to observe:

I've added round(,3) to the SOFT input matrix elements that needed it, and to MCL_GAIN in ANALOG_CARM

DIAG main complained about IM2 y being out the nominal range, this is because of the move we made after the IMC PZT work (31951).  I changed the nominal value from -209 to -325 for DAMP Y IN1

A few minutes after Cheryl went to observe, we were kicked out of observe again because of fiber polarization, both an SDF difference becuase of the PLL autolocker and because of a warning in DIAG main.  This is something that shouldn't kick us out of observation mode because it doesn't matter at all.  We should change DAIG_MAIN to only make this test when we are acquiring lock, and perhaps not monitor some channels in SDF observes. We decided the easiest solution for tonight was to fix the fiber polarization, so Cheryl did that. 

Lastly, Cheryl suggested that we orgainze the gaurdian state for ISC_LOCK so that states which are not normally used are above NOMINAL_LOW NOISE, I've renumbered the states but not yet loaded the guardian because I think that would knock us out of observation mode and we want to let the hardware injections happen. 

REDUCE_RF9 modulation depth guardian problem:

It seems like the reduce RF9 modulation depth state somehow skips restting some gains (screenshot shows the problem).  (noted before in alog 31558).  This could be serious, and could be why we have occasionally lost lock in this state.  I've attached a the log, this is disconcerting because the guardian log reports that it set the gains, but it seems not to have happened.  For the two PDs which did not get set, it also looks like the round step is skipped. 

We accepted the wrong values (neither of these PDs is in use in lock) in SDF so that Adam could make a hardware injection, but these are the wrong values and should be different next time we lock. The next time the IFO locks, the operator should accept the correct values

I've scheduled a CBC injection to begin at 9:20 UTC (1:20 PT).

Here is the change to the schedule file:

1164532817 H1L1 INJECT_CBC_ACTIVE 1 1.0 Inspiral/{ifo}/imri_hwinj_snr24_1163501538_{ifo}_filtered.txt

I'll be scheduling more shortly.

TITLE: 11/30 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 72.6285Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 5mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.50 μm/s
SUMMARY:

• Sheila was here when I arrived, done with her activities
• LLO returned to lock, and went to Observe
• Sheila accepted two vaules in SDF
• I put H1 in Observe
• minutes later the fiber polarization on Y arm ALS was above it's acceptable range, and kicked H1 out of Observe
• Y arm polarization was at 20, until I opened the door on the rack, and it shot up to 74
• I gently used a twist tie to loosly secure the fibers away from the door
• I reset the polarization for both arms and both read 1% wrong polarization when I was done
• I gave Adam Mullavey access so he can run hardware injections
• currently he's logged in and there's was briefly an error on the INJ_TRAN guardian, cleared up now

TITLE: 11/30 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: NLN, Sheila was making some measurements
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: Locking was pretty easy tonight
LOG:
Corey had it locked when I came in.

Kiwamu did a measurement at DC Readout.

Jenne and crew cleaned up some SDF hickups, ODCMASTER OBSERVATION bit was preventing us from going to Observe.

Sheila had some measurements in NLN that broke lock a couple times.

J. Kissel

I've injected a broad-band PCAL EY excitation into the IFO and measured its response in CAL-DELTAL EXTERNAL to confirm that systematic errors are small. I've followed it immediately with a set of reference-measurement sensing function swept sines of PCAL2DARM and DARMOLG TFs that have been tuned to improve the low frequency (> 30 Hz) information. 

Attached are the results. I also attach the results for a never published measurement that was taken on Nov 21 2016 20:13:36 UTC.

One can see that
- The systematic error between 10-200 Hz (where the coherence is reasonable enough to make a statement) is frequency dependent, but less that 5% and 2 [deg]. 
- The swept sine version of the same measurement agrees with the frequency dependence, but confirms that the discrepancy flattens out in magnitude, sticking to around -5%
- Here're the fit results for physical parameters of the sensing function:
                                 [Units]  value(95% c.i.)      
Meas Date                 2016            Nov 21              Nov 30
IFO Input Power                  [W]      29.5                29.9
SRC1 Loop Status                          ON                  ON

Optical Gain              x 1e6  [ct/m]   1.150 (0.003)       1.124 (0.003)
DARM/RSE Cav. Pole Freq.         [Hz]     348.7 (6.0)         347.5 (5.8)
Detuned SRC Optical Spring Freq. [Hz]     7.09 (0.2)          7.40  (0.2)
Optical Spring Q-Factor (1/Q)    []       0.0413 (0.02)       0.0581 (0.02)
Residual Time Delay              [us]     1.87  (4.9)         0.84 (4.7)
 
aLOG                                      LHO 31994


- There is statistically significant evidence for what I'll call "DC flattening" in the sensing function, that we see for the first time with these two measurements because we've tuned the transfer function to have high precision there. This is interesting because our current simplified model of the sensing function (described in detail in LHO aLOG 31665, for example) does *not* include the influence of the test mass's finite stiffness at low frequency. The parametrization we currently use is based on the 2001 Buonanno and Chen Paper (via Evan Hall's thesis work and Kiwamu & Craig's similar derivation), but none of these incorporate a test mass with real dynamics and finite stiffness. The only study I've seen that does do this -- and shows evidence for the response flattening below a certain frequency -- was some work done by Adam Mullavey very early on, in which he used an Optickle simulation with (I believe) the full QUAD dynamical model included -- see pg 5 of G1400064. There are two impacts of this effect on the physical parameter estimation:
    (1) It distracts the lower-frequency fit of the optical spring frequency and Q slightly -- which means that there is systematic error, (albeit small for this level of detuning) in the sensing function as high as 30 Hz.
    (2) There is a few tens of percent discrepancy in the 5-10 Hz region. However, Adam's study hints that -- although the detuned spring frequency increase with power (as we have seen) the restoration-to-flatness frequency does not. I think this makes sense physically -- the finite stiffness of the suspension (at least in the longitudinal direction) should not change with power (of course the angular plant does -- see e.g. LHO aLOG 25368)

Other Notes:
- (I only re-discovered this today -- thanks Shivaraj!) that these templates come pre-calibrated. 
The swept-sine calibration is an imported text file that calibrates the DELTAL EXT / PCALY RX transfer function (i.e. not the individual channels) from preER10,
     /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Scripts/ControlRoomCalib/pcal2darm_calib.txt
written by Kiwamu, with the script 
     /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER10/H1/Scripts/ControlRoomCalib/H1_pcal2darm_correction.m
and originally mentioned in . 
The broad-band calibration is an imported text file that calibrates DELTAL EXT from the PreER9 model,
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER9/H1/Scripts/ControlRoomCalib/DARM_FOM_calibration_new_20160512.dat
written again by Kiwamu, with the script 
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/PreER9/H1/Scripts/ControlRoomCalibH1DARM_FOM_correction.m

These scripts, regrettably, have a few FIXMEs and are not using the latest DARM model. We should update these script, regenerate the ASCII dump of calibration, and recalibrate this data to confirm that the systematic errors are still small (and in fact they may get smaller, who knows). 

- All data is exported from these templates always use the raw channel's value so any matlab analysis done in the past is unaffected by the above imported DTT calibrations.

- The time of the broadband injection was about 40 [sec] between Nov 30 2016 02:53:00 to 02:53:40 UTC (enough to get 25 avgs at 0.1 Hz BW, or 10 sec FFT with 75% overlap). This will be used to make the same comparison of PCAL to GDS-CALIB_STRAIN, especially now that it is correcting from time-dependent systematic errors (see LHO aLOG 31926).

Measurement templates: 
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/
    PCAL/2016-11-30_H1_PCAL2DARMTF_BB_5to1000Hz.xml
    PCAL/2016-11-30_H1_PCAL2DARMTF_4to1200Hz_fasttemplate.xml
    DARMOLGTFs/2016-11-30_H1_DARM_OLGTF_4to1200Hz_fasttemplate.xml


DARM model / Sensing Function Fit constructed from:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/
H1/Scripts/PCAL/fitDataToC_20161116.m (rev3908)

Common/params/IFOindepParams.conf (rev3829)
H1/params/H1params.conf (rev3855)
H1/params/2016-11-12/H1params_2016-11-12.conf (rev3855)

[Sheila, Jenne, JeffK]

While clearing SDF differences, we caught the same filter-not-on situation that Ansel and Young-Min helped find in alog 31524.  We looked around in the guardian, and Sheila found why they didn't get set, and has fixed the problem.  SDF saves the day!

The problem is that the filters were only being set in the DRMI_Lock_Wait state, so if we gave up on catching the DRMI and went for PRMI, then had a successful transition from PRMI to DRMI without a vertex lockloss, we would never go back to that state, so the filters would never get set.  Sheila has moved the setting of those filters later in the guardian to the offload state that we go through no matter which way we acquire the lock, so this shouldn't be a problem again.

[Jenne, JimW, JeffK, Sheila, EvanG, Jamie]

We were ready to try hitting the Intent bit, since SDF looked clear, but kept failing.  We were auto-popped out of Observation.  With Jamie on the phone, we realized that the ODCMASTER SDF file was looking at the Observatory intent bit.  When the Observe.snap file was captured, the intent bit was not set, so when we set the intent bit, SDF saw a difference, and popped us out of Observe.  Eeek! 

We have not-monitored the observatory intent bit.  After doing this, we were able to actually set the bit, and stick in Observe. 

Talking with Jamie, it's perhaps not clear that the ODCMASTER model should be under SDF control, but at least we have something that works for now.

Betsy, Keita, Daniel

As part of the LVEA sweep, prior to the start of O2, this morning, we spent over an hour doing a cleanup of misc cables and test equipment in the LVEA and electronics room.  There were quite a few cables dangling from various racks, here's the full list of what we cleaned up and where:

I also threw the main breaker to the OFF position on both of the free standing unused transformer units in the LVEA - one I completely unplugged because I thought I could still hear it humming.

No monitors computers appear to be on except the 2 VE BECKHOFF ones that must remain on (in their stand alone racks on the floor).

We'll ask the early morning crew to sweep for Phones, Access readers, lights, and WIFI first thing in the morning.