I added two stages of whitening to the IMC REFL DC readback, so we are no longer ADC noise limited anywhere.

I also added a ct2mW filter based on the old calibration described here.

Attached is the last 2 months of relative humidity data from the desiccant cabinets in the VPW.  Apparently the DB4 RH logger quit recording data sometime last month, so it is not attached.  I'm looking into a replacement logger.  If it's any consolation, when I've spot checked the RH reader periodically over the last month it has always been under 1%.

Peter K., Jeff B.   

   Today there have been elevated dust counts in the PSL laser room and in the Anti-Room. Trends over the past few weeks show several spikes of high counts in both rooms.

   The alarm level settings for the Anit-Room (DM 102) are set for clean 1000 (Minor alarm 700 counts, Major alarm 1000 counts). The PSL enclosure is set for Minor alarm at 140 counts and major alarms at 200 counts. 

   We are still looking into the cause of these spikes. 

P.S. Ops - Please let me know if you are getting dust monitor alarms and what the wind is doing at the time of the alarms.    

I changed to  WINDY_NO_BRSX for PCal work at EX. I forgot to switch it off at EY for earlier work that was done but it appears to be ok down there.

J. Kissel, E. Hall

Worried that the 1083.7 Hz calibration line on PCAL EY -- the "standard candle" for the > 1kHz roaming calibration line on PCAL EX -- is being swamped by new non-stationary noise around 1.1 kHz, I took a closer look. I've compared the DARM ASD (0.01 Hz BW, 10 avgs) and coherence between PCALY RX PD and DARM at several different times:
     2016-01-30 22:22:27 UTC -- Canonical O1 Reference Time, with no such new noise (Shown in YELLOW)
     2016-10-31 07:00:00 UTC -- Beginning of last night's quiet, long lock stretch (Shown in PURPLE)
     2016-10-31 10:00:00 UTC -- In the middle of the same long lock stretch, when the range degraded a little bit (Shown in BLUE)
     2016-10-21 17:30:00 UTC -- Toward the end of the ghoulish lock stretch with high microseism, high-wind, and an 5.4 [mag] earthquake. (Shown in NAVY)

One can see that, regardless of the non-stationary noise, we can still get ample coherence between PCAL and DARM with 10 averages and a 100 [sec] FFT. Recall, this 1083 Hz line is *not* used in any of the calculations for time-dependent DARM loop parameters, so we're free to use any bandwidth and integration time we wish to get the best coherence / SNR/ uncertainty. As such, we'll just leave the line where it is.

*phew*!

Evan G., Dave B., Chris B., Thomas S.

After completely restarting the INJ_TRANS Guardian node, this finally fixed the transient injection problem as reported in LHO aLOG 31030. The interferometer was not locked, so no point in trying to recover the signal in a low-latancy analysis. This is the entry in the schedule file:
1161980000 INJECT_CBC_ACTIVE 0 1.0 /ligo/home/evan.goetz/lscrepos/Inspiral/H1/coherentbbh7_1126259455_H1.out

I observed the signal in H1:CAL-PINJX_HARDWARE_OUT, H1:CAL-PCALX_RX_PD_VOLTS_OUT, and H1:CAL-PCALX_OFS_AOM_DRIVE_MON_IN2.

• I was asked to keep the IFO down due to high wind conditions. 
• Travis and the PCal team did some work at EY
• Sheila plugged in a power monitor for the ESD in the corner

On the attached snap of the Terramon window, the second event is a largesh EQ in Middle East.  The EQ distance to H1 is 1000km shorter than the distance to L1 but the computed site velocity is 1/2 at H1 versus L1.  Is this one of those cases where the waves arrive first from opposite directions and so the crust encountered is different for the travelling surface waves?  Interesting info I'm sure everyone wants to know.  I see a similar descrepency for the G1 and V1 velocities but those waves are certainly travelling on the same direction.  Maybe it is just the local site geology being taken into account?  HunterG?  Thanks-H

Last Friday (28 Oct.) and now today (31 Oct.), I unfortunately run across this error when trying to make a hardware injection test:
2016-10-31T17:47:43.17850 INJ_TRANS JUMP: AWG_STREAM_OPEN_PREINJECT->INJECT_CBC_ACTIVE
2016-10-31T17:47:43.17898 INJ_TRANS calculating path: INJECT_CBC_ACTIVE->INJECT_SUCCESS
2016-10-31T17:47:43.17943 INJ_TRANS new target: RAMP_GAIN_TO_0
2016-10-31T17:47:43.18017 INJ_TRANS executing state: INJECT_CBC_ACTIVE (101)
2016-10-31T17:47:43.18292 INJ_TRANS [INJECT_CBC_ACTIVE.enter]
2016-10-31T17:47:43.18413 INJ_TRANS [INJECT_CBC_ACTIVE.main] USERMSG 0: INJECTION ACTIVE: 1161971300.000000
2016-10-31T17:47:43.18625
2016-10-31T17:47:43.18632  *** Break *** write on a pipe with no one to read it
2016-10-31T17:47:43.18639 awgSetChannel: awg_clnt[124][0] = NULL
2016-10-31T17:47:43.18646 Error code from awgSetChannel: -5
2016-10-31T17:47:43.22723 INJ_TRANS [INJECT_CBC_ACTIVE.main]   File "/opt/rtcds/userapps/release/cal/common/guardian/INJ_TRANS.py", line 549, in main
2016-10-31T17:47:43.22726     self.hwinj.stream.send(self.hwinj.data)
2016-10-31T17:47:43.22727
2016-10-31T17:47:43.22770 INJ_TRANS [INJECT_CBC_ACTIVE.main]   File "/ligo/apps/linux-x86_64/gds-2.17.9/lib/python2.7/site-packages/awg.py", line 621, in send
2016-10-31T17:47:43.22772
2016-10-31T17:47:43.22772     self.append(data, scale=scale)
2016-10-31T17:47:43.22773 INJ_TRANS [INJECT_CBC_ACTIVE.main]   File "/ligo/apps/linux-x86_64/gds-2.17.9/lib/python2.7/site-packages/awg.py", line 599, in append
2016-10-31T17:47:43.22774
2016-10-31T17:47:43.22774     self.open()
2016-10-31T17:47:43.22775     + ": " + awgbase.SIStrErrorMsg(ret))
2016-10-31T17:47:43.22775 INJ_TRANS [INJECT_CBC_ACTIVE.main]   File "/ligo/apps/linux-x86_64/gds-2.17.9/lib/python2.7/site-packages/awg.py", line 584, in open
2016-10-31T17:47:43.22776
2016-10-31T17:47:43.22777 INJ_TRANS [INJECT_CBC_ACTIVE.main]  can't open stream to H1:CAL-PINJX_TRANSIENT_EXC: Error setting up an awg slot for the channel
2016-10-31T17:47:43.24578 INJ_TRANS JUMP target: FAILURE_DURING_ACTIVE_INJECT
2016-10-31T17:47:43.24605 INJ_TRANS [INJECT_CBC_ACTIVE.exit]
2016-10-31T17:47:43.32248 INJ_TRANS JUMP: INJECT_CBC_ACTIVE->FAILURE_DURING_ACTIVE_INJECT
2016-10-31T17:47:43.32252 INJ_TRANS calculating path: FAILURE_DURING_ACTIVE_INJECT->INJECT_SUCCESS
2016-10-31T17:47:43.32253 INJ_TRANS executing state: FAILURE_DURING_ACTIVE_INJECT (300)
2016-10-31T17:47:43.32253 INJ_TRANS new target: WAIT_FOR_NEXT_INJECT
2016-10-31T17:47:43.32254 INJ_TRANS [FAILURE_DURING_ACTIVE_INJECT.enter]
2016-10-31T17:47:43.32780 INJ_TRANS [FAILURE_DURING_ACTIVE_INJECT.main] ezca: H1:CAL-PINJX_TRANSIENT_GAIN => 0.0
2016-10-31T17:47:45.47968 INJ_TRANS [FAILURE_DURING_ACTIVE_INJECT.main] ezca: H1:CAL-PINJX_TINJ_OUTCOME => -4
2016-10-31T17:47:45.48415 INJ_TRANS [FAILURE_DURING_ACTIVE_INJECT.main] ezca: H1:CAL-PINJX_TINJ_ENDED => 1161971282.48
2016-10-31T17:47:45.52790 INJ_TRANS [FAILURE_DURING_ACTIVE_INJECT.run] USERMSG 0: ERROR


Chris Biwer suggested a simple test that I think worked:
>>> import awg
>>> import numpy
>>> stream = awg.ArbitraryStream('H1:CAL-PINJX_TRANSIENT_EXC', 16384, 1161970100) 
>>> timeseries_data = numpy.zeros(10)
>>> stream.send(timeseries_data)
Warning, couldn't open log file
Aborting Logging because SIStrLog call failed -4
Warning, couldn't open log file


Chris B. and Dave Barker have been notified of this issue.

J. Kissel

Admiring the work of the SEI and ASC teams, we've just lost lock on a really impressive lock stretch in which we had ~40 mph winds, ~70th percentile microseism, and a 5.4 Mag earhtquake in the horn of Africa and survived. It would be most excellent it DetChar can compare amplitudes of ISC control signals, check out the beam rotation sensor tilt levels, the ISI platform sensor amplitudes, take a look at optical lever pitch and yaw compared with ASC signals etc.
    Start: Oct 31 2016 16:15:05  UTC
    End:               17:37-ish UTC

To recover our alignment after the PSL work that happened last week, IM3 was moved pretty significantly (alog 30910).  For the last week or so, it has been regularly running extremely close to the edge of the actuation range for LL and UR.  The MasterOut channels are around 126,000 counts, but the front end model outputs are above 130,000.  It would be great if someone from DetChar could have a look and make sure that we're not causing ourselves trouble by operating so close to the DAC edge here.  Note that the VoltMon channels for these two OSEMs are totally railed, so they will not be useful for looking at - I don't know if those are a regular part of the detchar scripts. 

• SEI -  running fine. EQ mitigation is satisfactory. Wind mitigation is ongoing.
• SUS - nothing to report
• CDS electronics - running ok. there are a few WP items to finish regardgin BIO readbacks and 24V runs in corner.
• CDS SW - HWS work is ongoing
• PSL - Peter is looking to measure water flow into the laser heads using a clamp on meter that is being brought in by a vendor. He hopes that the vendor will leave the device for a period of time.
• VAC - nothing or today
• FAC - the exit gate is malfunctioning and stuck in the UP position
• Work Permits

This will reduce unnecessary HEPI slow system movement.  This movement could be causing creek and maybe slow albiet minor alignment changes.

When both the ISI and HEPI Isolation loops are closed, the first step is to measure the free hanging position so the loop starts with zero DC shift.  Once the loop is fully engaged, the "Target Reference Location" is ramped into the loop to put the alignment of the platform to a repeatable place.  This restoration of position happens for all HEPIs and the HAM ISIs.  The BSC ISIs do not restore a Target position; no evidence to show now, but we don't see large shifts or wanderings of the BSC ISI positions.

Okay, for the HEPIs, the Vertical and Horizontal Pringle modes are overconstrained dofs of the HEPI platforms--8 actuators with 6 degrees of freedom.  As such these isolation loops are not DC coupled as are all the other dofs X Y Z RX RY  & RZ.  As such though, the restoration of a Target position into the AC coupled loop puts a large step into the loop and drives.  Attached are 30 day trends showing four ITMX HEPI trips.  The large step up on the horizontal Actuator drives are the restoration of the old target position of 900nm (upper right trace.)  This HP measurement is literally a distortion of the platform, some taken up by the soft Actuator connection and some by actual stress in the platform.  I would be most worried about yaw alignment shifts but there are none evident in the optical levers.  Given the length of this trend plot though, most of the optical lever data here may be in-loop.  There is probably some ASC output I could trend for that.

The bottom line is that since these are AC coupled loops and over some time, the offsets are AC'd out of the loop, why put them in in the first place.  Start the loop in the free hanging location like all loops and let this AC loop slowly go where it will.  We don't expect them to go much of anywhere.  Just avoid the potential problems no matter how minor.

I propose all HEPI Pringle loops be removed from the Target location restoration list (Guardian chamber edits.)  This has been discussed in the weekly SEI subsystem call and principals agree.

J. Kissel for S. Karki

I've moved the roaming high frequency calibration line driven by PCAL X from 1501.3 to 1001.3 Hz at Oct 31 2016 15:44:29 UTC (1161963886, 08:44:29 PDT). Note, O2 reference measurements for PCALX will be taken tomorrow, we should be sure to scale any results to those measurements.

Here's the status: 
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           Oct 31 2016 15:44:29 UTC
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
4301.3       40k                      10:00       
4501.3       40k                      10:00
4801.3       40k                      10:00  
5001.3       40k                      10:00

• Gusts have actually been in excess of 40mph at times.
• hand aligned PR3 a bit after DRMI ASC engaged

TITLE: 10/31 Owl Shift: 07:00-15:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Ed
SHIFT SUMMARY:
Locked for most of the shift. 4753Hz line was slowly ringing up so I reconfigured the damping filter. Range were up and down likely due to wind. Lockloss seems to coincide with ~40 mph wind gust. PI mode18 rang up once, flipped the phase sign and never saw it again. Verbal alarm complains about TCSY chiller flow towards the end of shift but this is bogus. As Kiwamu requested I also increased CO2 power thoughout the shift, 90 minutes at a time.

LOG

08:33 Increased CO2X from 0.2W to 0.3W, CO2Y from 0W to 0.1 W

9:18 Got an unknown external call

10:04 CO2X 0.3-->0.4W, CO2Y 0.1-->0.2W

11:35 CO2X 0.4-->0.5W, CO2Y 0.2-->0.3W

13:06 Co2X 0.5-->0.6W, CO2Y 0.3-->0.4W

13:40 Intent bit dropped for a second due to Guardian code load

14:11 Lockloss. SRC1 suddenly ran away. Coincide with ~40mph wind gust but this happened before earlier in the shift without breaking the lock.

Got a verbal alarm complaining about TCSY chiller flow so I went out to check the chiller on the mezzanine. At the TCSY chiller itself reported flow rate to be ~4Gpm. I also went out and check the mechanical flow meter in the LVEA and it appeared to be reporting >3Gpm. I don't know why the flow channel (H1:TCS-ITMY_CO2_FLOWRATE) is reporting something bogus.

The mode is made of two lines, 4735.05 Hz and 4735.09 Hz. Not sure why I didn't see this before. I increased the BP to be 1 Hz wide so the phase change between the two lines are not too far apart. Now damping at -60 deg phase, 0.02 gain.

J. Kissel

With hints of improvement last night from Sheila (see LHO aLOG 30947) on reducing the most egregious ~41 Hz peak in DARM (which is known to be the HSTS roll modes, a.k.a R3), I launched a campaign of adding similar ~1 Hz wide notches to all HSTS suspensions' local damping loops (M1_DAMP) at both the highest roll mode and highest vertical modes (a.k.a V3 at ~27.5 Hz).

The filter designs are
V3 notch: FM8 "SB27.5" ellip("BandStop",4,1,60,27.05,28.05)gain(1.12202)   [Input -- Always On; Output -- Ramp; Ramp Time -- 2 sec]
R3 notch: FM9 "SB40.9" ellip("BandStop",4,1,60,40.4,41.3)gain(1.12202)     [Input -- Always On; Output -- Ramp; Ramp Time -- 2 sec]
where I've made sure that the lowest and highest frequency V3 modes (coincidentally both IMC mirrors: MC1 @ 27.38 Hz, MC2 @ 27.74 Hz) faLL within the stop band of the notch (and I've confirmed that this is true with Sheila's R3 notch design as well). Further, the V3 notch causes a phase loss of only 2.2 [deg] at 10 Hz, so it will not impact any of the damping loop's phase margins. To confirm, I've spot checked SR2's local damping open loop gain tfs just to be sure. Indeed all DOFs are still quite stable (and quite poorly tuned, as expected).

During the campaign I found that PRM, MC1, and MC3's "ellip50" standard low-pass filters were not engaged, so I engaged them.

I've greened up all ODC status lights, and then accepted all of the changes in the SDF system -- V3 filters ON, R3 filters ON, ellip50 filters ON, and Correct Damp State.

While haven't had an uber-long lock stretch since I've turned on all of these notches, I was at least able to grab 5 averages of a 5 [mHz] BW ASD and compare against the long data set from last night. The notches appear to have done their job -- a large fraction of the modes have been squashed and don't show up in DARM anymore. Success! 

The SR2 damping loop open loop gain TF templates have been committed here:
/ligo/svncommon/SusSVN/sus/trunk/HSTS/H1/SR2/SAGM1/Data/
2016-10-28_2223_H1SUSSR2_M1_openloop_L_WhiteNoise.xml
2016-10-28_2223_H1SUSSR2_M1_openloop_P_WhiteNoise.xml
2016-10-28_2223_H1SUSSR2_M1_openloop_R_WhiteNoise.xml
2016-10-28_2223_H1SUSSR2_M1_openloop_T_WhiteNoise.xml
2016-10-28_2223_H1SUSSR2_M1_openloop_V_WhiteNoise.xml
2016-10-28_2223_H1SUSSR2_M1_openloop_Y_WhiteNoise.xml