Nutsinee's Saturday report of an alog no longer being viewable and needing to be reposted reminds me that anyone can subscribe to "L-mail" and get an email everytime an entry is created and edited (for both main entries and comments). If an entry goes missing, you can easily reconstruct the entry from raw HTML via your email application.

I have been investigating the spike in the computed value of kappa_tst shown here in the summary pages:
https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20161122/cal/time_varying_factors/
A closer look reveals a seeming correlation between the DARM line coherence and the values of kappa_tst (see the attached plot). Currently, kappa_tst computed values are gated with PCALY_LINE1 and SUS_LINE1, the only lines used to compute kappa_tst.

Things to note in the plot:
1) kappa_tst diverges from the expected range about a minute after the DARM line coherence uncertainty skyrockets, just the amount of time it takes to corrupt the 128 running median.
2) kappa_tst as computed by CALCS also diverges when the DARM coherence goes bad.
3) Ungated kappa_pu behaves similarly to kappa_tst, but since it is gated with the DARM coherence, the GDS output is not corrupted.

After John Worden noticed multiple gauges were flatlined, we discovered that pulling the fuse to depower PT180 gauge for bake-out inadvertently flatlined LX beckhoff vacuum system this past weekend, including CP2 PID loop. CP2 LLCV locked at 60% open (1.7x its nonimal value) due to integrator high limit. Strange that the % full dipped from ~92% to 91.7% (Kyle noted a step change in PT120 (cold cathode gauge) after pulling PT180 fuse). Bubba noticed significant ice build up on exhaust line this morning. Now we know why. There was significant LN2 consumption as a result of overfilling for four days. Dewar level fell from 49% to 32%. The exhaust pressure was also not reading actual values. Thanksfully we opened all CP exhaust bypass valves as new nominal state last week to prevent overpressurization!

There was no indication of faults from the vacuum overview MEDM screen. PT180 appeared to be powered with a reasonable pressure value. The LVEA subscreen, however, did show a fault for PT180. I filed FRS 6772 to have faults moved to front overview page. We will work with Patrick to create an alarm handler for future events where perhaps a fuse blows on its own.

PT180 was manually disabled in beckhoff this morning which caused the other components to read as-is, showing PT180 reading red and zero and CP2 and LX gauges to reflect their faults. Richard will write an instruction manual so we can do this in the future for planned events.

Kyle pulled the fuse for the LX PT180 Inficon BPG402 gauge on Nov. 22 (alog 31814). For reasons not entirely clear to me, this put all of the input channels for LX into an invalid state with their values flatlined. In Beckhoff this error was was only indicated by the WcState for each channel.

To fix this, in the TwinCAT software on h0vaclx, I right clicked on 'Pressure Gauge PT180 (BPG 402)', clicked on 'Disable', then went to the 'TwinCAT' menu and ran 'Activate Configuration'. When it asked whether to restart in run mode I said yes. This ended up crashing the EPICS IOC, which I restarted. I burtrestored the IOC to 6:00 AM on Nov. 22 (local time).

For each readback channel there is a channel with the same name that ends in _ERROR. These channels reported this condition, however they are not on any of the overview MEDM screens or in any alarm handler. This should be changed.

So currently, the PT180 pressure gauge is powered off and disabled in Beckhoff. The other LX channels should be valid again.

Following up on the DetChar report of ETMx oplev laser glitching causing problems, I confirmed (using the DetChar summary pages) that the laser was indeed showing signs of glitching.  I also noticed the ETMy laser was also showing signs of glitching.  I increased the power for both lasers to hopefully get them into a thermal state they are happy with.  I used the Current Monitor (outputs a voltage to monitor the current delivered to the laser diode) port on the back of each laser as a guide.  The changes were:

• ETMx
  • Current Monitor Before: 0.814 V
  • Current Monitor After: 0.830 V
• ETMy
  • Current Monitor Before: 0.861 V
  • Current Monitor After: 0.880 V

Seeing as I had to open the cooler for both lasers they will both need 4-6 hours to return to thermal equilibrium.  At that point a determination can be made as to whether or not this helped at all.  The attached 3 hour trend of the oplev SUM for both optical levers gives hope; after the power increase the SUM signal is quieter for both oplevs.  I will leave WP 6348 open for now as more adjustment may be necessary to fix the glitching.

I have turned of the "silent lines" (suspension actuator lines canceled by Pcal lines) at ~18:45 Nov 28 2016 UTC. All values for the line frequencies, amplitudes, and phases have been zeroed. These changes have been accepted in the observe and safe SDF files for both SUSETMY and CALEY.

Had doubted what I had been told last week by an INFICON service tech. that our gauge could only tolerate 80C bake when the external electronics were removed.  I was able to confirm this in INFICON's published Operating Manual BAYARD-ALPERT PIRANI GAUGE tina46e1-a (2010-03) which also specifies this 80C limit even when the external electronics are removed (why?)-> I don't see anything in the materials exposed to vacuum list that would explain this low temperature limitation so I sent them an email requesting that they confirm.

J. Kissel, E. Goetz

The roaming PCALX calibration line was turned off for hardware injections over the weekend (LHO aLOG 31861). It looks like we have enough data at 5001.3 Hz (started at LHO aLOG 31738), so I'm restarting the line at the low frequency end (1001.3 Hz) and re-running through the lower half of the schedule in order to gather data at 30 [W] instead of the inconsistent 25 & 50 [W]. I include the old completed schedule for reference as well, just in case we don't get enough data before the run starts.


Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 28 2016 17:20:44 UTC
1501.3       35k                      02:00                   39322.0           
2001.3       35k                      02:00                   39322.0           
2501.3       35k                      05:00                   39322.0           
3001.3       35k                      05:00                   39322.0           
3501.3       35k                      05:00                   39322.0           
4001.3       40k                      10:00                   39322.0           
4301.3       40k                      10:00                   39322.0                
4501.3       40k                      10:00                   39322.0           
4801.3       40k                      10:00                   39222.0           
5001.3       40k                      10:00                   39222.0           


Frequency    Planned Amplitude        Planned Duration      Actual Amplitude    Start Time                 Stop Time                    Achieved Duration
(Hz)         (ct)                     (hh:mm)                   (ct)               (UTC)                    (UTC)                         (hh:mm)
---------------------------------------------------------------------------------------------------------------------------------------------------------
1001.3       35k                      02:00                   39322.0           Nov 11 2016 21:37:50 UTC    Nov 12 2016 03:28:21 UTC      ~several hours @ 25 W
1501.3       35k                      02:00                   39322.0           Oct 24 2016 15:26:57 UTC    Oct 31 2016 15:44:29 UTC      ~week @ 25 W
2001.3       35k                      02:00                   39322.0           Oct 17 2016 21:22:03 UTC    Oct 24 2016 15:26:57 UTC      several days (at both 50W and 25 W)
2501.3       35k                      05:00                   39322.0           Oct 12 2016 03:20:41 UTC    Oct 17 2016 21:22:03 UTC      days     @ 50 W
3001.3       35k                      05:00                   39322.0           Oct 06 2016 18:39:26 UTC    Oct 12 2016 03:20:41 UTC      days     @ 50 W
3501.3       35k                      05:00                   39322.0           Jul 06 2016 18:56:13 UTC    Oct 06 2016 18:39:26 UTC      months   @ 50 W
4001.3       40k                      10:00                   39322.0           Nov 12 2016 03:28:21 UTC    Nov 16 2016 22:17:29 UTC      days     @ 30 W (see LHO aLOG 31546 for caveats)
4301.3       40k                      10:00                   39322.0           Nov 16 2016 22:17:29 UTC    Nov 18 2016 17:08:49 UTC      days     @ 30 W          
4501.3       40k                      10:00                   39322.0           Nov 18 2016 17:08:49 UTC    Nov 20 2016 16:54:32 UTC      days     @ 30 W (see LHO aLOG 31610 for caveats)   
4801.3       40k                      10:00                   39222.0           Nov 20 2016 16:54:32 UTC    Nov 22 2016 23:56:06 UTC      days     @ 30 W
5001.3       40k                      10:00                   39222.0           Nov 22 2016 23:56:06 UTC    Nov 28 2016 17:20:44 UTC      days     @ 30 W (line was OFF and ON for Hardware INJ)

The IFO has been locked in low noise for ~7 hours now.  However, from 15:58-16:33 11/28/16 UTC (7:58-8:33am PT just this morning) the flow signal dropped down from 3 to 1.5 and then recovered back up to 3.  The lasers kept on chugging through this.  This caused an alarm to the operator who notified me - upon inspection, I see that chiller is still reading 4.0 flow at the chiller.  So all seems ok right now again...

REMINDER: O2 officially starts this Wed.

SEI: BRSx needs to be looked at opportunistically

SUS: nothing

CDS: PEM work @ mids

CDS software: Matlab license update Tues., DAQ work Tues.

PSL: PZT mount work today

OpLev: EX OpLev glitching

VAC: PT180 work ongoing

FAC: nothing

PEM: injection ongoing

LVEA walkthrough scheduled for tomorrow after maintenance activities complete.

TITLE: 11/28 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 70.5897Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    Wind: 32mph Gusts, 23mph 5min avg
    Primary useism: 0.10 μm/s
    Secondary useism: 0.73 μm/s
QUICK SUMMARY:  Locked for the past 6+ hours.  Robert is still here, so we'll see how long that lasts.

State of H1: locked in NLN on POP WFS

• all activity in alog 31892
• since going back to Observe the rage has improved and then turned around

State of H1: NLN, running al2

Outgoing Ops: TJ

Activities:

• a lock that broke in Increase Power
• small tweak to alignment of PR3 and PRM
• damped bounce and violins in DC Readout
• went from Noise Tunings to NLN manually
• running a2l since noise in DARM is higher at 20Hz...
• however, useism is steadily marching upwardand all stations are about 0.5um/s
• 10:05UTC, a2l done
• 10:06UTC, range is 74Mpc, went to Observe
• 10:10UTC, noticed ASAIR and REFL beam diverters were not closed, out of Observe
• closed ASAIR and REFL beam diverters
• 10:11UTC, back in Observe

I've scheduled 5 more burst injections. They're spaced 70 minutes apart. The first one begins at 8:10 UTC (12:10 PT). Here are the updates to the schedule file:

For some reason a +50 degree filter was turned on in the ETMY top mass damping on October 12th, it was not good and we got no real top mass damping. Nutsinee and I just turned it off, so the settings are now the same as for ETMX.  This fixed the problem