Checking in to report that CP3 and CP4 have been stable since the sensing line blockage removal. CP3's fill signal is noisier since recent Dewar fill. Its cycle time was set to 1,000 seconds, where as the others are 10,000 s, so I changed CP3 to match the others. I also lowered its LLCV 'output lower limit' from 15% to 13% open because it bottomed out during the Dewar fill at 15% open.

• change in urad over 700 days
• start of O1 to June 2017
• all starting values adjusted so that start = 0

• change in urad over 700 days
• start of O1 to June 2017
• all starting values adjusted so that start = 0

FAMIS 4734

The script to plot the optical lever trends is returning an error:

patrick.thomas@zotws1:/opt/rtcds/userapps/release/sys/h1/scripts$ python oplev_trends.py
Traceback (most recent call last):
  File "oplev_trends.py", line 29, in 
    buffers= conn.fetch(start,stop,channels_pit)
RuntimeError: Requested data were not found.

When importing either cdsutils or gpstime into python we were getting the warning message:

>>> import gpstime
/ligo/apps/linux-x86_64/gpstime/lib/python2.7/site-packages/gpstime-0.1.2-py2.7.egg/gpstime/__init__.py:150: RuntimeWarning: Leap second data is expired.
Run 'update_leapdata()' to download the latest bulletin from the IETF
  RuntimeWarning, stacklevel=1)
 

The local leap second data files had expired 28th June 2017. The updated file from IETF has a new expiration 28th Dec 2017 (and no leap second to be applied at the end of the year).

The packaged debian machines (just one on H1 at the moment) load a new local copy of the file into the user's home directory when the expiration is detected. For all the non-packaged machines (most of them) I have updated the leap-seconds.txt file in the /ligo/apps/[linux-x86_64, debian8] areas.

Drifting but not out of the range that's acceptable.

TITLE: 06/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 54Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 3mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

• 15:30 - Karen driving to the VPW
• 16:52 - out of Observe for a2l - ETMX yaw took a bit of time to find a good gain
• 17:13 - a2l is done, funning passive to see results
• 17:17 - H1 back to Observe
• before and after a2l spectra attached

TITLE: 06/30 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: A mysterious lock loss and some trouble getting back up. An initial alignment helped, but it still lost lock at NOMINAL_LOW_NOISE after a min, but then came back up with no issues after that.
LOG:

• 07:58 Lock loss
• 09:15 Observing for seconds before it lost lock
• 09:47 Observing

No obvious cause.

TITLE: 06/30 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 68Mpc
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY: 2 hour lock after recovering from an earthquake.

TITLE: 06/30 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 69Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:  Some trouble after the EQ lockloss, but all seems to be well now.  Lock is ~2 hours old.
LOG:

6:34 Accidentally went out of Observe for less than 1 minute

I ran A2L again which seemed to clear a bunch of SDF diffs in ASC (maybe it didn't complete the previous time I ran it), but not all of them.  I accepted the remaining diffs (sorry, no screenshot).  DARM spectrum looks normal again and we are at ~70 MPc.