DQ Shifter: Beverly

LHO: Fellows: Young-Min, Evan

Full results may be found here.

• The duty cycle was rather low (8.4% on Monday, 55.2% on Tuesday, 39.5% on Wednesday for a combined duty cycle of 34.4% ). Ongoing snow and ice made it dangerous for staff to drive so operators were absent for several shifts. In addition, two strong earthquakes ended locks on 10 Jan.
• The 1080 Hz glitches first appeared in the second lock on 11 Oct 2016 and were present ever since.  It was discovered on 6 Jan 2017 (PST) that these glitches were caused by a problem with the OMC length control ( 33037). On 9 Jan 2017, the IFO was brought to low noise (but not to observing) to test some proposed changes. It turned out that the dither line amplitudes had been lowered on 11 Oct 2016 when the 1080 Hz glitch problem began. At that time, the OMC length servo gain was not raised to compensate for the amplitude changes. Today they ran with the servo gain set to 24 (to give the nominal 6Hz ugf) and the lowered dither line amplitude from 19:21 UTC to 19:51 UTC Jan 9th (see 33104). The glitches disappeared during this experiment. A second lock of the day, in observing mode, showed reappeared glitches because the changes during the experiment were reverted due to the ongoing configuration lock and concern that other channels might be adversely affected. 
• A later investigation was made showing that channels found by hVeto to be associated with these glitches were either unaffected by the experimental configuration or had their glitching reduced by it. (See attached PDF.) However, concerns arose about increased noise from 10-25 Hz in DARM during the experiment although there was no evidence for correlations between DARM and OMC-LSC. See alogs (33175, 33176, 33177).
• The BNS range during this shift was only about 60 Mpc (with periods of lower range during episodes of snow plowing). Evan reports that Sheila has noted a steady decline of the range during O2. This has been getting worse in January. No obvious reason was found during this shift for the worsening range. See (33155) for a test to see if closing the POP beam diverter to reduce scattering improved the range. It did not. Range trend is shown here (as an attachment to alog 33155 by Sheila) or here (by Duncan McCloud).
• The elevated glitch rate (especially around 200 Hz) first seen on 6 Jan (and previously seen in December) seems to have decreased on 10 Jan and decreased further on 11 Jan.

Caused by me trying to increase OMC length gain. (see alog 33104 and several comments)

Bubba needs several more hours at end X to clear snow for the CP delivery next Tuesday.
PCAL clipping at end Y needs investigation.

Both of these will take place tomorrow (Thursday).

Have remained locked since the beginning of the shift. No issues to report. Have not had to damp any PI modes. Snow removal has continued on both arms.

TITLE: 01/12 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 58.2425Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    Wind: 2mph Gusts, 1mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.24 μm/s 
QUICK SUMMARY: Locked and observing with double coincidence. TCSY chiller flow is low verbal alarm when I arrived. Flow had dropped to around 2.2, just came back to around 3.1.

TITLE: 01/12 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 54.185Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY:
LOG:
11:20 LLO was down, A2L had looked bad since I arrive, so ran A2L script

12:30 Lockloss, back to observing at 13:09

15:30 Bubba and Ken to MX to check on temps

TITLE: 01/12 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 53.5793Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY:

Other than an odd EQ (thanks Krishna for pointing out the high freq (0.3-1Hz which we don't have up on the wall) of the EQ---at any rate, not your typical EQ), in OBSERVING all shift and PI modes were straightforward.
LOG:

• Before 0:00 - 0:50 Snow Plowing around office buildings and access road
• 0:14 OBSERVING
• 2:02-3:02 GRB Stand Down time
• 2:05 PI Mode27 rung & damped
• 3:38-4:20 EQ lockloss & back to Observing
• 4:33 PIMode27 rung up & damped

• EQ seen on USGS & Terramon after lockloss at 3:38utc (L1 also dropped a few minutes earlier), but NOTHING showed up on BLRMS until 3:48utc (very odd!) & didn't see huge signal on tidal striptool...so was hesitant to mark this as an EQ, but it finally showed up on BLRMS.
• Magnitude:  5.3
• Location:  Guatamala
• Starting time of event:  Pretty much the H1 lockloss was when I noticed it and saw that it was already on USGS/Terramon
• Lock status?  L1 dropped out of lock followed by H1 a few minutes later.

TITLE: 01/12 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 53.5793Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 7mph Gusts, 6mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.26 μm/s

No snow!  Winds under 10mph, a balmy 19degF, & seismic isn't too bad (other than some plowing at the beginning of this shift).  Roads were plowed & clear on way in.
QUICK SUMMARY:
Patrick took H1 to OBSERVING as we made the shift change.
There was some snow plowing in the Corner Station area at the beginning of this shift.

M5.5 - 42km SSW of Betafo, Madagascar

Reported twice by Terramon, once by USGS

Was it reported by Terramon, USGS, SEISMON? Yes, Yes, No

Magnitude (according to Terramon, USGS, SEISMON): (5.4, 5.5), 5.5, NA

Location: 42km SSW of Betafo, Madagascar, 20.158°S, 46.633°E, 8.7 km depth 

 

Starting time of event (ie. when BLRMS started to increase on DMT on the wall): ~ 23:20 UTC

Lock status? Not locked at time

EQ reported by Terramon BEFORE it actually arrived? Unknown.

model restarts logged for Tue 10/Jan/2017
2017_01_10 08:47 h1nds1

Complete h1tw1 offloading, reconfigure daqdrc on nds1.

model restarts logged for Mon 09/Jan/2017
2017_01_09 10:02 h1tw1

Restart tw1 after NFS failure Fri 06

model restarts logged for Sun 08/Jan/2017 - Sat 07/Jan/2017 No restarts reported (minute trends unavailable due to h1tw1 NFS error)

model restarts logged for Fri 06/Jan/2017
2017_01_06 08:13 h1nds0
2017_01_06 08:13 h1nds1

Restart both nds's as tw1 offloading starts. h1tw1 stopped NFS exporting at 17:20 this day.

model restarts logged for Thu 05/Jan/2017 - Wed 04/Jan/2017 No restarts reported

Outside of the NDS, TW1 and FW0 restarts, the rest of the DAQ has now been running for 37+ days (DC, FW1, FW2, GDS-BRCSTR).

TITLE: 01/11 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 60.9258Mpc
INCOMING OPERATOR: Jim may or may not decide to venture in (I have been in contact with him this evening)
SHIFT SUMMARY:
H1 has been in OBSERVING for almost 6hrs at a fairly steady 60Mpc.

Continue to experience non-normal winter weather with forecast for possibly more snow overnight & freezing temperatures.  Have also had fairly blizzard like conditions with winds just below 20mph.  Have been in contact with OWL shift operator with regards to coverage & they will do what feels safe.  

I am leaving NOW to brave roads home & so H1 will be flying on automatic pilot for a few hours or until the morning. 

I have talked with William Parker (LLO operator) and aprised him of our situation.

LOG:

DIAG_MAIN message:   PCAL:  Y RX PD is 0.01 OFF

• Last person other than me....at 4:30pm (0:28utc)
• H1 has been UNDISTURBED since 22:43utc
• 0:34-1:34 GRB Stand Down Time
• 2:14 PI Mode 27 quickly rang up.  Sign change damped it.
• 2:33 TCSy Chiller LOW flow (no action taken)

WP 6428

This morning the CO2 Laser Interlock Chassis D1200745 was replaced. This work is part of the ongoing investigation of the TCS flow sensor alarms/glitches. See alog 32776. Verified trip point for the temperature shutoff of the laser on new chassis. Steps taken to replace chassis:

1. Turn off laser at key
2. Turn off chiller in mechanical room
3. Turn off chassis and unplug all connections
4. Install new chassis, rocker switch set to CW (OPS) position
5. Redo connections to chassis & power on
6. Turn on chiller
7. Check there are no red lights on chassis front panel
8. Key on laser and press gate button
9. Check laser power actually powers on (MEDM screen).

Old Chassis S1302125
New Chassis S1302122

Fil, Richard, Nutsinee, Alastair

This morning we sat in nominal low noise without going to observing from 19:21 to 19:51 UTC (Jan 9th) in a configuration that should be much better for the 1084Hz glitches. (WP6420)  

On Friday we noticed that the 1084Hz feature is due to OMC length fluctuations, and that the glitch problem started on Oct 11th when the dither line amplitude was decreased (alog 30380 ).  This morning I noticed that the digital gain change described in alog 30380 that was intended to compensate for the reduced dither amplitude didn't make it into any guardian, so that we have had a UGF that was a factor of 8 lower than what I used when projecting OMC length noise to DARM: 30510 The first attachment shows open loop gain measurements from the 3 configurations: before oct 11th (high dither amplitude), after october 11th (lower dither amplitude, uncompensated) and the test configuration (lower dither amplitude, compensated).  

We ran with the servo gain set to 24 (to give us the nominal 6Hz ugf) and the lowered dither line amplitude from 19:21 UTC to 19:51 UTC Jan 9th.  You can see the spectrum durring this stretch in the second attached screenshot, in the test configuration the peak around 1083Hz is gone, with just the pcal line visible, and the OMC length dither at 4100Hz is reduced by more than an order of magnitude. You can also compare the glitches from this lock stretch with one from yesterday  to see that the glitches at 1084 Hz seem to be gone. This is probably the configuration we would like to run with for now, but we may try one more test with increased dither line amplitude.  

Other notes because we don't have an operator  today due to weather:

This morning all 4 test mass ISIs were tripped probably from the Earthquake last night that brought the EQ  BLRMS to 10 um/second around midnight UTC.  ITMY tripped again while it was re-isolating, no problem on the second try. 

Richard topped added 400mL to the TCSY chiller around 10:15 or 10:30 local time, since we were getting low flow alarms. The flow alarms came back a few minutes before 11am local time.  

I went through inital alingment witout problems and got to DC_readout transition. Then I measured the UGF of the OMC length loop in preparation for increasing the dither line height   From that measurement and trends it became clear that when the OMC dither amplitude was reduced, the compensation of the OMC digital gain described in didn't make it into the guardian.  This means we have been operating with a UGF in the OMC length loop that was a factor of 8 too low since mid october.  

We arrived in low noise at 19:21 UTC with the OMC ugf increased to 6Hz.  After about a half hour PI modes 27 and 28 rang up, and I wasn't fast enough to get them under control so we lost lock.  

Ran the diaggui template for the HAM and BSC ISI CPSs (CPS'...).

No overall issue with one sensor being elevated.

I found one thing that is maybe a known and understood feature, but I didn't find it in the alog with my searching (maybe the wrong search words?).

I notice that there is noise in HAM2, HAM3, HAM4, and HAM6 around 41.3Hz, and the elevated noise level goes from 41Hz to about 41.6Hz.

This noise is not present in the 1 Dec 2016 plots, there seems to be hint of it in the 14 Dec 2016 plots, and it's clearly visible in the 1 Jan 2017 plots.

Attached:

• BSC
• HAM
• HAM, zoomed in to 40-70Hz

I have produced filters for offline calibration of Hanford data from the beginning of O2 A until the end of 2016. The filters can be found in the calibration SVN at this location:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/GDSFilters/H1DCS_1163173888.npz

For information on the calibration model, see
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=31693
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32329
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32907

For suggested command line options to use when calibrating this data, see:
https://wiki.ligo.org/Calibration/GDSCalibrationConfigurationsO2

The filters were produced using this Matlab script in SVN revision 4050:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/TDfilters/H1_run_td_filters_1163173888.m

The parameters files used (all in revision 4050) were:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/Common/params/IFOindepParams.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/params/H1params.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/params/2016-11-12/H1params_2016-11-12.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/params/H1_TDparams_1163173888.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Scripts/CAL_EPICS/D20161122_H1_CAL_EPICS_VALUES.m

Several plots are attached. The first four (png files) are spectrum comparisons between CALCS, GDS, and DCS. Kappas were applied in both GDS and DCS plots with a coherence uncertainty threshold of 0.4%. Time domain vs. frequency domain comparison plots of the filters are also attached. Lastly, brief time series of the kappas and coherences are attached, for comparison with CALCS.