TITLE: 12/15 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 73.335Mpc
INCOMING OPERATOR: Cheryl later if the winter weather/roads cooperate
SHIFT SUMMARY:

Have been in locked for all but 1hr of the shift (down for two locklosses).  Weather is the big news of the shift thus far.  There have been delayed work advisories issued and the latest is a Work Cancellation for the Hanford site---this is all due to Adverse Weather Conditions.  

I have talked with the LLO operator and have notified them of our situation & we should talk to them as soon as we get coverage back here, so they can stand down with covering for us.

LOG:

• Dust Monitor Alarms for the LVEA up to 30k+
• EY Saturations:  11:49, 11:57
• 8:09 Topped of TCSy Chiller
• 9:32-10:05 Lockloss
• 10:28 Snow plow passing by the site on Rt10
• 11:25 Topped PSL Crystal Chiller
• 13:15-13:45  Lockloss
• 13:45 Snowblower near Control Room

The Hanford site has just cancelled work for today; (http://www.hanford.gov/c.cfm/advisory/)

Hanford Site Work Cancellation due to Adverse Weather Conditions

13:15utc Lockloss Nothing Environmental

Had another lockloss with a quiet Environment.  Ran a lockloss2 script, and if I squinted I could maybe see the BS glitching (attached) before the lockloss, but not obvious.

• Only minor optics tweaks to get H1 back to NLN in 29min.
• Did have ANOTHER DIFF for H1SYSECATY1PLC2:
  • H1:ALS-Y_REFL_SERVO_COMBOOST was 2.00, now 1.00 (attached)
  • ACCEPTED this 

Is there a reason why we are having ALS DIFFs all of a suddent for my last (2) Locks?

• The Bounce (& Roll to lesser extent) were a bit elevated at the beginning of the lock (perhaps this was due to the noisy snow blower right outside the Control Room?).  Thought of damping these guys out, but L1 was UP & the modes were smaller than the reference on the DTT session I was running.  So I left H1 in Observing.

13:45utc Back to OBSERVING

• Staff at 200W & all 100 Areas will report to work at 9:00am.
• 200E & south of WYE Barricade (LIGO is in this area) will report at 9:30am.  

Hanford Site Advisories are posted here:  http://www.hanford.gov/c.cfm/advisory/

Topped off the Crystal Chiller with 175mL.  Diode Chiller was OK.

Closing FAMIS#6501.

9:32UTC LOCKLOSS

Rather random lockloss because environmentally we were quiet quiet.  lockloss2 script has a few possible lockloss candidates and the SRM seems to be the most obvious reason for a lockloss as several SRM channels ramp up just prior to the lockloss.  Ther were also some MICH signals getting noisy as well.  PRM also has similar ring up like the SRM.

As for getting back to OBSERVING, basically made it back UP in 33min.  Here are some notes from locking.

• For the ALS Green Arms, I tweaked up the TMSx & y to raise up the powers.
• Then the usual aligntment tweaks for ETMs, BS, & PRM
• Once at NLN, had PLC2 Diffs at the CS & EY (attached).  Accepted both which were:
  • H1:ALS-C_LOCK_REQUESTY (for H1SYSECATC1PLC2):   was "Red Locked" & now "End Locked"
  • H1:ALS-Y_LOCK_STATEMENT (for H1SYSECATY1PLC2):  was "Red Locked" & now "End Locked"

10:05UTC OBSERVING

TITLE: 12/15 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 73.4048Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 13mph Gusts, 8mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:

Winds are dying & the useism has been dropping as well.  Patrick handed over a locked H1 (although we did get an OBSERVING drop out TCSy).

Weather conditions on site:

Snowing lightly.  4-6" of snow on the roads (Rt10, 240, & Twin Bridges were not plowed).  Luckily very minimal traffic on road for the drive in.  I mainly drove around 45-55mph.  (at 1:25amPST, Patrick informed me he made it home safely.)

DOE's Hanford Site issued a cancellation of their graveyard shift tonight.

TITLE: 12/15 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 68.8843Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Struggled with PI mode 26, which is unusual. Called Terra and she ended up changing the bandpass filter by .5 Hz. Seems to be damping again. TCSY chiller seems to be acting up. The flow dropped a number of times (see attached) and at the end of the shift it may have kicked us out of observing. Ran a2l script towards end of shift after checking the coherence with Keita's template. Ran initial alignment after first lockloss.

First attached screenshot is of ETMX UL WD trip.
Second attached screenshot is of accepted SDF from PI mode 26 change.
chiller.pdf is a trend of the TCSY chiller flow over the last 8 hours.

LOG:
23:33 UTC Diag reset timing error on h1iopasc0
23:37 UTC NLN
23:41 UTC Observing.
~23:52 UTC Workstation frozen for ~ 3 sec.
00:03 UTC Changed sign of gain for PI mode 28
00:50 UTC Lock loss. Could not damp PI mode 26. Changed phase and gain to no effect. Kicked out of observing when I tested turning off the output to the BP filter module. Lost lock trying to manually go down to 10 W. 
00:58 UTC Y arm green power is low. Starting initial alignment.
02:00 UTC Reached DC_READOUT. Diag message: ETMX RMS ['UL'] WD has tripped. See screenshot. Wrote 1 and then 0 to H1:SUS-ETMX_BIO_L2_UL_RMSRESET. Stopped at DC readout and looked at violin modes. Did not decide on a course of action. Moved on.
02:25 UTC NLN
02:30 UTC Observing
02:32 UTC Stepped out of control room
02:51 UTC Changed sign of gain for PI mode 28
02:55 UTC Changed phase of PI mode 27
03:38 UTC Lock loss. Was on phone with Terra trying to diagnose PI mode 26 again.
04:31 UTC Back to DC readout. Called Terra. Said to stay here while the mode rings down.
Terra changed the frequency of the bandpass filter for mode 26 from 209 to 209.5.
05:08 UTC Observing. Accepted SDF difference for change in PI mode 26 frequency. Terra watching remotely.
05:33 UTC Changed phase and sign of gain of mode 27
06:32 UTC Terra called. She has been changing the phase for PI mode 26, but thinks it should be stable now.
07:41 UTC Out of observing to run a2l. Part way through the script it reported an error but continued on:

H1:ASC-ADS_YAW5_DEMOD_Q => ON: FM2
H1:ASC-ADS_YAW5_DEMOD_Q => OFF: FM1
Traceback (most recent call last):
  File "/opt/rtcds/userapps/trunk/isc/common/scripts/decoup/run_1TM_a2l.py", line 54, in 
    decoupObject.runMain()
  File "/opt/rtcds/userapps/trunk/isc/common/scripts/decoup/deMod_deCoup.py", line 510, in runMain
    os.mkdir('rec_%s/'%self.siteName)
OSError: [Errno 17] File exists: 'rec_LHO/'
H1:SUS-ETMX_L2_DRIVEALIGN_P2L_GAIN => 1.4402
H1:SUS-ETMY_L2_DRIVEALIGN_P2L_GAIN => 0.5411

07:46 UTC Back to observing
07:58 UTC Got kicked out of observing by TCS_ITMY_CO2 guardian node. Possibly chiller servo?
08:02 UTC Put back in observing.
08:09 UTC Corey to mechanical room to check on TCS chiller.

A comparison of narrow lines in 133.5 hours of O2 DARM to those
seen in 107 hours of ER10 DARM shows very similar structures and
strengths. On the whole, the low-frequency lines are generally higher
in the O2 data than in ER10, but the upconversion around the quad
violin modes & harmonics is better in the O2 data, consistent with the
significant mitigation of low-frequency doublets with a splitting of
0.0467 Hz, suspected to be due (somehow) to beating of the 2nd quad violin
harmonics 1009.4414 and 1009.4881 Hz.

For reference, zipped tar files of sub band spectra up to 2000 Hz are attached,
where the orderings of the two overlain curves (ER10, O2's 1st 13 days) are
reversed, to make more apparent in which data sets individual lines are stronger.

Lost lock twice after PI mode 26 rang up. Nothing I tried seemed to affect it. Called Terra while the mode was ringing up the second time. She is now logged in remotely to see if she can help diagnosis it.

TCSY chiller flow is glitching.

C. Cahillane

Reported are the 1-sigma (68%) uncertainties in the calibration parameters, and the plots of these parameter's impact on the sensing, actuation, and response function uncertainties.

These are the uncertainties due entirely to MCMC fits of the calibration parameters given the November 12 reference measurements.  This does not take into account unmodeled changes in the calibration, i.e. systematic errors.  Those are characterized by the Gaussian Process method and will be reported later in the total uncertainty + systematic error budget.


Plot 1 shows the LHO sensing function parameters and cornerplots.  Parameter 68% and 95% confidence intervals are posted below:

= = = = = = = = ==  Median  =====  - 68% CI  == + 68% CI  == - 95% CI  == + 95% CI 

Optical gain     = +1.1527e+06     -0.088 %     +0.088 %     -0.174 %     +0.174 % [cnts/m]
Cavity pole      = +3.4674e+02     -0.390 %     +0.389 %     -0.766 %     +0.777 % [Hz]
Time delay       = +2.3216e-06     -49.15 %     +49.54 %     -96.2  %     +97.4  % [usec]
Spring frequency = +7.3837e+00     -1.101 %     +1.078 %     -2.150 %     +2.123 % [Hz]
Spring Inverse Q = +4.5749e-02     -8.57  %     +8.62  %     -16.9  %     +17.0  % 


Plot 2 shows the sensing function Nov 12 measurement and its model fit given the MAP parameters.

Plot 3 is the UIM actuation parameters cornerplots.  Parameter confidence intervals:

= = = = = = = = Median  = = =  - 68% CI  =  + 68% CI  =  - 95% CI  =  + 95% CI 

Gain UIM     = +8.1807e-08     -0.220 %     +0.218 %     -0.434 %     +0.431 % [N/ct]
Time delay   = +9.3546e-05     -44.226 %    +45.798 %    -81.585 %    +90.190 % [s]


Plot 4 is the UIM actuation Nov 12 measurement and model fit given MAP parameters.

Plot 5 is the PUM actuation parameters cornerplots.  Parameter confidence intervals:

= = = = = = = = Median  = = =  - 68% CI  =  + 68% CI  =  - 95% CI  =  + 95% CI 

Gain PUM     = +6.8377e-10     -0.034 %     +0.034 %     -0.067 %     +0.068 % [N/ct]
Time delay   = +9.5548e-06     -8.855 %     +8.849 %     -17.395 %     +17.405 % [s]


Plot 6 is the PUM actuation Nov 12 measurement and model fit given MAP parameters.

Plot 7 is the TST actuation parameters cornerplots.  Parameter confidence intervals:

= = = = = = = = Median  = = =  - 68% CI  =  + 68% CI  =  - 95% CI  =  + 95% CI 

Gain TST     = +4.3880e-12     -0.044 %     +0.044 %     -0.087 %     +0.087 % [N/ct]
Time delay   = +4.8062e-06     -12.882 %    +12.788 %    -25.492 %    +25.184 % [s]


Plot 8 is the TST actuation Nov 12 measurement and model fit given MAP parameters.

Plot 9 is the response function  R(f) = 1/C + D*A plotted with its components.  This shows what dominates where.

Plot 10 is the relative response function uncertainty due entirely to the MCMC results.  It is < 0.5% and < 2 degrees everywhere between 5 and 5000 Hz.  This is not the total uncertainty budget, just those due to the uncertainty in calibration parameters.

This is interesting because it tells us a couple of things about calibration parameters. (1) They are extremely well-determined, and (2) marginalizing over just calibration parameters may not be enough to capture the total uncertainty budget.  Stay tuned

What remains to be done:
(1) Take out time-dependence from the measurements.
(2) Run Gaussian Process on all measurements with time-dependence removed.
(3) Compile total uncertainty budget including systematic error.

For a similar budget at LLO, see LLO aLOG 30440

Commented out in configuration file and committed to svn.

Josh, Andy, David

After stumbling on the ringing phones in the LVEA in O2 (entry 32503) we sent this request, to find other times in h(t) that look like phone ringing glitches, to GravitySpy citizen scientists. Though it's dirty laundry airing this is a way to engage a network of many interested folks to find issues.  

The reply from user @EcceruElme pointed to two similar glitches in O1/ER10/O2.
One is in Livingston at 1132398529.14 (Nov 24th 11:08 UTC - link) and looks like an ER10 instance of engaging violin mode damping while in observation ready but before SDF checks were being enforced, so ok.
One is in Hanford at 1128269436.32 which is 2015-10-07 at 16:00 during a long nice science mode lock (summary page for that day). This sounds a little like a fax machine then some bangs and a human voice through a loudspeaker and some more bangs. In the hour around that time there are also some other loud bangs. We have no idea what it could be but it happened in otherwise unbroken excellent O1 data so perhaps folks on site know what it is and if it can be (or has been) turned off.

Attachments:

- Audio file of Input Optics Microphone with no filtering.
- Spectrogram of Input Optics Mic (it was also loud in BS Mic, others in LVEA but quiet in PSL room Mics) and Strain
- OmegaScan of Strain (from GravitySpy) 

TITLE: 12/14 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 76.3748Mpc
OUTGOING OPERATOR: Ed / TJ
CURRENT ENVIRONMENT:
    Wind: 20mph Gusts, 14mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.20 μm/s 
QUICK SUMMARY: Back to observing. Diag reset to clear timing error on h1iopasc0.

Chandra lifted the lead for TE252A. Kyle put the CP4 LLCV into PID and disabled. The script to fill CP4 was run:
vacuum@vacuum1:/ligo/home/patrick.thomas/svn/scripts$ python cp4_fill.py 70 -60 3600
Starting CP4 fill. TC A error. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 30 seconds. LLCV set back to 35.0% open.
Chandra put back the lead for TE252A.

Chandra lifted the lead for TE202B. Kyle put the CP3 LLCV into PID and disabled. The script to fill CP3 was run:
vacuum@vacuum1:/ligo/home/patrick.thomas/svn/scripts$ python cp3_fill.py 50 -30 3600
Starting CP3 fill. TC B error. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 110 seconds. LLCV set back to 19.0% open.
Chandra put back the lead for TE202B.

Both scripts are in svn under /trunk/scripts in the projects repository. Revision 4023.

• Was it reported by Terramon, USGS, SEISMON?  USGS report@time of quake; Terramon reported @ 16:48; Seismon not running
• Magnitude (according to Terramon, USGS, SEISMON) -  USGS reports 5.0; Terramon reported ≈9µm/s then updated to 16.1327 ?!; Seismon not running
• Location (according to Terramon, USGS, SEISMON) -  See attached image  below.
• Starting time of event (ie. when BLRMS started to increase on DMT on the wall) - probably a minute or two before the lockloss
• Lock status?  Did H1 lose lock, get a glitch, or showed no effect? - Lockloss
• EQ reported by Terramon BEFORE it actually arrived? - NO

Interesting to note: After I noted all of the pertinent information for the California quake. USGS updated and inserted 3 more quakes in between the one reported here and the previous one in California. (2 that could have contributed to the detriment of the lock) See far right attached image.

I have increased the heat in the LVEA in sections 1A and 5 by 1 ma each.