• H1 locked at NLN/Observing
• All BSC are set to BLEND_250_SC_A
• EQ bands up around .07um/s. uSei is 1+um/s and holding steady for the last 6 hours or so.
• Winds are around 15-20mph gusting to 30+ at times
• LVEA dust monitors 6&10 and both PSL dust monitors have been sending alarms

• Trying Sei configurations stated in WP#6369
• 00:35UTC Since both IFOs were out of lock and µseism is at or above 1µm/s, Corey and I placed a phone call to Jim inquiring about trying the new sei configuration to see if it made any improvements as monitored in the Tidal StripTool. All BSC configs were switched from BLEND_250_SC_B to BLEND_250_SC_A. Tidal seemed to improve slightly as can be seen to the right hand side of the attached tidal image (the noisy bit in the middle can be ignored as it was irrelevant to the situation). These changes were made around the DRMI_LOCKED Guardian stage of locking. After some requisite BS aligning, the locked progressed to SWITCH_TO_QPDS and broke there. This is not an uncommon place for a lock to fail in my experience. Subsequent attempts at locking would end at FIND_IR with the guardian message "x-arm alignment bad not searching". 

01:06UTC I reverted back to the original sei configuration for BSCs and locking attempts continue.

01:34UTC multiple locklosses at FIND_IR. Reverting back to new configs just to see if I can get past this stage.

01:50UTC New sei configs got me into DRMI land. MICH alignment looks pretty terrible. Trending witness sensors not revealing much. Going to try some alignment with INITIAL_ALIGNMENT guardian. Not going to do the arms if I can help it.

02:00UTC INITIAL_ALIGNMENT/INPUT_ALIGN not working. After trying to adjust the gain higher to get a lock I decided to trend(TimeMachine)IM4. I found it to be about 100urads out in pit. This seems to have corrected the issue. Perhaps this less-than-optimal pointing has been the sore spot in my locking efforts? Also had to put SR2 back to center before aligning SRC.

04:00UTC H1 Locked, Observing Range is ~72Mpc. Lock stretch so far: 01:08 coincidental with L1.

02:51UTC - NLN 75.3Mpc

Keita is working on some ALS diffs that were knocking the intent bit loose. I firmed up some channels to be unmonitored for some BS gain settings with the assistance of Jim W ( by telephone) so that I could set the intent bit.

TITLE: 12/02 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 73.9893Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:

Locked for a good chunk of the shift, but useism & wind grew pretty noisy in the afternoon....to a point where locking was going to be tough.

LOG:

• Elevated Dust Levels in Southbay & inside PSL Room from OWL shift & continued throughout the day.
• 16:36:  Xmid Cleaning
• 20:16 Out of Observing
  • A2L Run & testing of new A2L interface (JimW & Jenne)
  • High-freq Cal Line change (Evan)
• 20:28 OBSERVING
  • 20:51 Lockloss!
  • ASC ERROR Pitch increased, Wind gusted up to 16mph, useism is hovering around 0.7um/s
• Alfredo & Elizabeth at MidY
• 21:44 OBSERVING
  • BS & PRM were way off, so during locking tweaked BS alot in MICH Fringes, & PRM with unlocked PRMI (under Sheila's watchful eye).  Then PRMI finally locked!
  • 22:56 "TCSY chiller flow is low" alarm.  Looked at trend, notified Jason, and he went to Chiller.  He thinks it's a Chiller issue & swapping this out is on their Maintenance To Do list.
  • 23:13 GRB Alarm
  • 23:21 Knocked out of Commissioning by SDF Diff from EX Beckhoff computer. (not clear what channels caused it yet).
  • 23:56 Lockloss (due to high useism & winds).

At 23:13 we received a "Gamma Ray Burst" Alarm.

Following L1500117:

• Step 1:  Checked to see if this is a TEST  
  • What does this mean?  Do Tests have the "INJ" flags?  Are there any other types of flags for Tests?
  • On GraceDB, there was a little confusion.  We could see a (1) GRB Report (EM_COINC) from Swift, but (2) around the same time, there were also some INJ EM_COINC's from CWB (!).  The GRB's event time was over 2min after the EM_COINC's.  
  • So was NOT a TEST
• Step 2:  Stand Down Time from 23:13 - 0:13utc
• Step 3:  Finally talked with LLO.  They did not know about the GRB, so they went to go check. Heard them say they DID NOT receive audible alarm, but had "text notification".

THEN:

AT 23:21 We were bumped out of OBSERVING!!  (Sheila noticed it, we didn't hear it for some reason during all the hub bub of figuring out the deluge of GraceDB reports.)  It wasn't obvious why we were bumped out of OBSERVING.  But since we tend to get bumped out due to SDF Diffs/changes, JimW looked at the DIAG_SDF node's log.  On here he noticed we were getting DIFFS for the SDF NODE:  sysecatx1plc2

Unfortunately, when the diffs appeared they only happened for a few seconds (knocked us out of OBSERVING), and then go away.  So it was hard to see what channels were in question.  It happened several times, and managed to catch a glance at the channels in question.  Words we saw in the channel were:  ALS, Fiber, polarization.  Since they deal with the ALS, we can probably safely say we can NOT_MONITOR these channels (but we should get a blessing from Keita).  Or if we are in a fix in the middle of the night, and you are able to figure out who these elusive channels are, be sure to note the channels, NOT_MONITOR them for the night and then alog what you did.

Epilogue:

We ended up losing lock at 23:56--it's really noisy seismically with useism & wind.

4:20pm local

Took 22 min. to overfill CP3 by raising LLCV to 50% open from control room. I raised nominal value from 16% to 17% for weekend.

O2 days 1,2:

model restarts logged for Thu 01/Dec/2016 No restarts reported

h1guardian was restarted at 08:50PDT, its RAM was increased from 12GB to 48GB.

model restarts logged for Wed 30/Nov/2016 No restarts reported

ER10:

model restarts logged for Tue 29/Nov/2016 No restarts reported

Lock# 8
Times are in: GPS (UTC)
Start time: 1164672438.0  (Dec 2 00:07:01 UTC)
  Itbit Engage: [0, 1164672969.0, 1164673578.0, 1164674812.0, 1164700372.0, 1164745711.0]
  Itbit Disengage: [0, 1164673508.0, 1164674325.0, 1164700288.0, 1164745010.0, 1164747085.0]
End time: 1164747085.0  (Dec 2 20:51:02 UTC)
Total length: 74647.0 , 20hr 44min 7sec
Total Science: 72774.0 , 20hr 12min 54sec


Lock# 9
Times are in: GPS (UTC)
Start time: 1164750245.0  (Dec 2 21:43:48 UTC)
  Itbit Engage: [0, 1164750308.0, 1164756280.0, 1164756461.0, 1164757097.0]
  Itbit Disengage: [0, 1164756100.0, 1164756401.0, 1164756773.0, 1164758206.0]
End time: 1164758206.0  (Dec 2 23:56:26 UTC)
Total length: 7961.0 , 2hr 12min 41sec
Total Science: 7334.0 , 2hr 2min 14sec



End of Day Summary
Current Status: Unlocked
Total Day Locked: 22hr 56min 48sec [95.6%] (82608/86400)
Total Day Science: 22hr 15min 8sec [92.7%] (80108/86400)

This is the first trial of a daily post by the Day shift operator of a summary of the locks for the UTC day. This information is created by (userapps)/sys/h1/scripts/VerbalAlarms/Lock_Logging.py which runs in the background of the VerbalAlarms program. The Lock# was started at the begining of O2 and is used only as a reference, it is only used in the control room. The idea behind these daily posts is that it will give the CR something to reference. The lock clock that is displayed in the CR will soon show the current Lock# to match these.

Any question, please let me know. Hopefully its helpful!

Corey alerted us to a low TCSY chiller flow - as alarmed on the side ops station.  Jason inspected at the chiller and found the usual nominal ~4 GPM, all good there.  A trend shows the flow sensor (which causes the alam and is out on the floor on a pipe under ~BSC2) has dropped, similar to what it has been doing (alog 31900). However this time seems to be taking longer to recover.  The value dropped from ~3.1 to 2.6 and is now bouncing around more than it had at the 3.1 value.  In the last 50 minutes it seems to be on a slight rise, but not out of the woods.  We spoke with Alastair just now to find out how low this can go before something else happens such as triggering the laser off.  He is going to look up to see if there is any hard coded trip set points somewhere.  However, in the 90 day trend attached Jason and I note (puprle ellipses) that there have been quite a few times that this flow sensor has dipped briefly below 2 and even 1 and the laser has been uneffected.  SO, we're hoping the flow sensor rides out long enough for us to schedule a Tues maint period to swap in the spare flow sensor. 

Ops - if the TCSY laser does anything funny this weekend AND the flow drops well below 3 and is staying there, call us.

Jenne, Jim W, Dave:

In order to run the a2l_min_LHO.py script from an MEDM shell launcher, I had to explicitly define full paths for all files used. Jenne created a testWrite.py which I used to test this out.

The MEDM command block in the A2L_screen.adl file (callable from SITEMAP via the SUS pulldown) is

        command[0] {
                label="A2L Script"
                name="xterm"
                args="-hold -e 'cd /opt/rtcds/userapps/trunk/isc/common/scripts/decoup; /usr/bin/python /opt/rtcds/userapps/trunk/isc/common/scripts/decoup/a2l_min_LHO.py'"
        }
 

As requested by Jeff and the calibration review committee, I've done a number of checks related to tracking the behavior of PCAL lines in the online-calibrated strain. (Most of these checks accord with the "official" strain curve plots contained in https://dcc.ligo.org/DocDB/0121/G1501223/003/2015-10-01_H1_O1_Sensitivity.pdf) I report on these review checks below.

I started by choosing a recent lock stretch at LHO that includes segments in which the H1:DMT-CALIBRATED flag is both active and inactive (so that we can visualize the effect of both gated and ungated kappas on strain, with the expected behavior that gstlal_compute_strain defaults each kappa factor to its last computed median if ${IFO}:DMT-CALIBRATED is inactive). There is a 4-hour period from 8:00 to 12:00 UTC on 30 November 2016 that fits the bill (see https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20161130/). I re-calibrated this stretch of data in --partial-calibration mode without kappas applied, and stored the output to

LHO: /home/aurban/O2/calibration/data/H1/

All data were computed with 32 second FFT length and 120 second stride. The following plots are attached:

• Timeseries of the ASD residuals of CAL-PCALY_RX_PD_OUT_DQ to GDS-CALIB_STRAIN (the online data with kappas applied) and TEST-CALIB_STRAIN (my recalibrated data without kappas), as computed at the PCAL lines (36.7, 331.9, and 1083.7 Hz).
• Overlayed median spectra of these three channels, zoomed in at each PCAL line.
• Overlayed ASD ratios zoomed in at each PCAL line.
• Full, overlayed median spectra of PCAL and the strian channels.
• A timeseries of the computed BNS range with and without kappas, compared against the behavior of each kappa (except the coupled cavity pole frequency, which is not applied online).

The script used to generate these plots, and a LAL-formatted cache pointing to re-calibrated data from the same time period but without any kappa factors applied, is checked into the calibration SVN at https://svn.ligo.caltech.edu/svn/aligocalibration/trunk/Runs/PreER10/H1/Scripts/TDkappas/. A similar analysis on a stretch of Livingston data is forthcoming.

• useism is well above the 90percentile.  (we had a 20+hr lock end...most likely due to this?)
• Back up to OBSERVING, but can clearly see useism effects:
  • See it on the Tidal Strip Tool
  • SEI BLRMS is above 90percentile
  • Glitches of PRC Gain & POP18 look glitchy/noisy on PRMI striptool
  • Range is just above 70Mpc
  • Continue to run in the standard WINDY ISI_CONFIG

Additional CBC injections are scheduled:

1164747030 H1L1 INJECT_CBC_ACTIVE 1 1.0 Inspiral/{ifo}/bbhspin_hwinj_snr24_1163501502_{ifo}_filtered.txt
1164751230 H1L1 INJECT_CBC_ACTIVE 1 1.0 Inspiral/{ifo}/bbh_hwinj_snr24_1163501502_{ifo}_filtered.txt
1164755430 H1L1 INJECT_CBC_ACTIVE 1 0.5 Inspiral/{ifo}/imri_hwinj_snr24_1163501530_{ifo}_filtered.txt
1164759630 H1L1 INJECT_CBC_ACTIVE 1 0.5 Inspiral/{ifo}/imri_hwinj_snr24_1163501538_{ifo}_filtered.txt