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.

(Filling in for Ed till Patrick comes on shift)

• 21:15 Jim, Fil out. Possibly seemed to have fixed the issue. See their alog for more info.
• 21:23 Jim, Fil back out to double check their connections.
• 21:42 Jim, Fil out.

The HAM5 CPS issue seems to be fixed, so we are on our way back up.

16:29 Fil , J. Batch ad John Worden out to LDAS.

16:42 Jim. Johm and Fil back from LDAS. Electrical panels are tripped. Electrician is on his way to investigate. Still not sure what order things went down.

16:46 Lockloss EQ

16:50 Switched ISI config for Large EQ in Northern California.

17:04 Switch ISI config back to Windy after quick decay of EQ

17:20 GRB alert. H1 not locked

17:34 H1 locked and observing. Monitoring f1 violin modes which are slightly rung up.

19:14 Fil reports that the LDAS power panel trips were due to the room, first, overheating. Queries into remote monitoring of LDAS room temps are being made.

19:17 filed FRS ticket for noisy ops station computer fan.

20:12 lockloss HAM5 and 6 ISI tripped

20:20 HAM5 CPS glitching. Jim out to power cycle chassis in CER.

20:34 Jim and Fil out to LVEA to physically "exercise" CPS connections.

21:30 Recieved Hanford Release advisory. Decided that I should get my non-snow ready vehicle home. TJ is there as well as Patrick who is the evening shift operator.

2:20 pm local

Took 30 sec to overfill CP4 at 70% open using Patrick's new automation code. See aLOG https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32573

More testing Friday.

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.

The h1fw0 frame writer was restarted about 12:30 PM PST.  The cause of the shutdown was a power failure caused by a cooling system failure in the LDAS room where the file system for frames is located.  

The h1fw1 frame writer ran without interruption, so no data was lost.  

J. Kissel, for the people actually doing the work: J. Warner, F. Clara

We've lost lock because HAM5 ISI capacitive position sensors (CPS) have suddenly started going terribly glitchy and saturating. Jim and Fil are investigating, but this'll likely involve some electronics power cycling, if not swapping. Stay tuned for further details.

• 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.