TITLE:  Sep 14 EVE Shift 23:00-07:00UTC (16:00-00:00 PDT), all times posted in UTC

STATE Of H1: Observing

SUPPORT: Jenne Driggers was called about comb oscillation in DARM

INCOMING OPERATOR: Nutsinee

05:50 a 2Hz comb appeared in DARM from ~20Hz to ~100Hz (as far as I can tell as it gets lost in the bucket)) which resulted in a drop in range to ~63Mpc. I placed a call to Jenne who was on call to inquire as to how I should proceed and the advice was as long as were locked, stay locked. So, we're still locked and Observing at 63Mpc.

C. Cahillane

I have made a file in /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER8/H1/Scripts/compare_actcoeffs_ER8_craig_extrapolation.m
The purpose of this file is to find the frequency dependence of our uncertainty in A_pu and A_tst.  It takes our three measurements from August 26, 28, and 29 and finds their weighted means and weighted standard deviations at all frequencies.  (Thank you Jeff, Kiwamu, and Darkhan for the code infrastructure.)

I have used the Pcal measurements only for our uncertainty calculations since it is has the lowest uncertainty and is the main method of calibrating our actuators.  Free Swinging Mich and ALSDIFF are used to determine the accuracy of Pcal, and Pcal is relatively very precise.
Our measurements go from 3 Hz to 100 Hz, but I need uncertainty from 3 Hz to 5000 Hz, so I am currently using a Zeroth Order Extrapolation, which is basically where I take our final uncertainty value at 100 Hz and let that be our uncertainty value for all data points from 100 Hz to 5000 Hz.  
It is expected that the actuation term will fall off quickly after 100 Hz and this will be sufficient for our first-order result.  If actuation is the main contribution to uncertainty more intelligent steps must be taken to ensure we aren't underestimating our uncertainty.

I will do the same tomorrow with the sensing function residual C_r, probably using Zeroth Order Extrapolation down to low frequency in this case.

Plot 1, 2, and 3 represent our UIM, PUM, and TST actuation stages.  For now I will fold systematic error and statistical uncertainty together, i.e. if we have an |A_tst| std of 0.5 m/ct and a systematic residual of 3%, I will make our total uncertainty be 0.5^2 + ( 0.03 * |A_tst| )^2.  

Summary: IFO locked since my shift started. Aside from the earlier noise trouble we’ve been locked at ~ 72Mpc. No EQs showing and wind is calm. A couple of ETMY glitches dropped te range to 10Mpc. Rick and the Pcal team still hard at work.

00:55UTC The Transient Injection was toggled to "Disable"

TITLE: Sep 14 EVE Shift 23:00-07:00UTC (16:00-00:00 PDT), all times posted in UTC

STATE Of H1: Observing

OUTGOING OPERATOR: Jim Warner

QUICK SUMMARY:Control room is pretty full of the usual suspects. Lights are on in the LVEA. Wind is below 20mph. EQ activity is quiet. IFO is experiencing some anomalous broad band noise. Commissioners are working on a solution.

J. Kissel

Since updates to the CAL-CS model have been a little sporadic over the past few days, I recap below what happened when, as logged by the filter archive.
What Changed                                                                    Local Time (PDT)    Corresponding Archive of Change    Corresponding aLOG

SUS dynamical model update is complete                                          Thu Sep 10 13:50    H1CALCS_1125953445.txt             LHO aLOG 21322

Cavity pole frequency changed from 389 to 341 [Hz] (+optical gain name change)  Thu Sep 10 14:03    H1CALCS_1125954209.txt
Optical gain is renamed (no substantial change)                                 Thu Sep 10 14:03    H1CALCS_1125954234.txt   
DARM_ERR Optical gain is tuned                                                  Thu Sep 10 17:49    H1CALCS_1125967809.txt             LHO aLOG 21385

Installed inverse actuation filter                                              Sun Sep 13 22:35    H1CALCS_1126244167.txt             LHO aLOG 21487

Kiwamu changes L1 and L2 violin modes                                           Mon Sep 14 09:03    H1CALCS_1126281835.txt             LHO aLOG 21500

Copied new inverse actuation filter over to blind injection                     Mon Sep 14 09:08    H1CALCS_1126282148.txt             
Changed the names of the blind injection filter banks (no substantial change)   Mon Sep 14 09:09    H1CALCS_1126282176.txt             LHO aLOG 21499
(Note the filter files are tagged with the GPS time that they're created. so they're more accurate (to the second) than the local time I quote.)

Given that the DARM calibration was tuned at Sep 10 2015 17:49:00 PDT = Sep 11 2015 00:49:00 UTC, and Kiwamu started the PCAL to CAL-DELTAL_EXTERNAL transfer function at Sep 10 2015 18:08:12 PDT = Sep 11 2015 01:08:12 UTC, I would conlcude that 
the front-end calibration has been stable for LHO since the first lock stretch that was placed in observation mode after that measurement, which starts at 
     1125972087 = Sep 11 2015 02:01:10 UTC = Sep 10 2015 19:01:10 PDT
until the last observation stretch -- which ended at 
     1126281754 = Sep 14 2015 16:02:17 UTC = Sep 14 2015 09:02:17 PDT
-- before Kiwamu's change at Sep 14 2014 09:03:00 PDT = Sep 14 2015 16:03:00 UTC. 

I say the front end calibration has been "stable" instead of "valid" because because we know that Kiwamu's work this morning was to correct a systematic error from a bug that had been found.

We only briefly took the IFO out of observation mode (though the IFO stayed happily locked) while Kiwamu loaded new SUS filters and I the copy of inverse actuation filters. We resumed a new observation segment Sep 14 2015 16:10:43 UTC.

As noted in Kiwamu's most recent aLOG about updating the calibration this morning (LHO aLOG 21500), his update changed the UIM and PUM stages, and for features well-above the cross-over frequencies of those stages (TST/ PUM ~30-40 [Hz], PUM / UIM ~ 2 [Hz]). The update was a bug fix, and it means that the front is now more accurately representing the violin modes that were already correct in the DARM model. We all suspect this is a small change in the overall actuation function, but the recent discovery of how poorly the PUM has been rolled off (LHO aLOG 21419), means we have to verify. 

After these messages, we'll be riiiight back. *whistle glitch*

P.S. Since Matt and I performed all of our inverse actuation filter design on the original matlab model of the DARM actuation function, the inverse actuation filter design and implementation is unaffected by Kiwamu's change, nor was it impacted by the systematic error that he found.

Mike Landry & Vern Sandberg  ER8 to O1 Transition

Cancellation of Tuesday Maintenance Day, September 15, 2015 to allow for IFO ER8-Quality data collection.

• Title: 9/14 Day Shift: 15:00-23:00UTC all times posted in UTC

• State of H1: Observation Mode at 70Mpc for the last 8hrs

• Support: All the commissioners

• Shift Summary: Mostly quiet, but worsening range at the end 

• Activity Log:

• 15:30 Ken working at warehouse, hooking up wiring for fire suppression system
  16:00 ChrisS and JoeD working on arm, recalled at 18:20, 
  16:00 Kiwamu and JeffK working on calibration and hardware injections for a couple minutes
  16:15 Bubba and JohnW driving down Xarm to investigate an air compressor 250m from EX, done 17:20
  16:45 Hugh at EY
  16:45 Fil to CER, out at 16:55
  17:00 Hugh at EX, out at 17:10
  17:55 Hugh in Mechanical Room checking HEPI fluid levels
  ~22:20 Range starts getting ratty and DMT OMEGA scans on control room display shows we are getting glitchy, numerous ETMY saturations
   
   
   

Checked the Reservoir Levels this morning.  All steady; no further maintenance called for.

Attached are 60 day means of the HEPI Drive outputs.  The expectation is that if we have a bad valve, this would show in a trend up or step up as the valve is failing.

Not sure about the efficacy of this manner of investigation and this 60 day look could easily be too coarse to see the needed details plus it is confused with platform trips and maybe the occasional alignment change, but for now, it looks like there is no obviously bad or failing valve. I'll continue with weekly or bi weekly shortly duration trends.  We are attempting to avoid doing the invasive Valve Check routine.

From the tinj log files, and visible on https://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/day/20150914/plots/H1-ALL_893A96_ODC-1126224017-86400.png, I see that two scheduled burst injections were successful this morning.  The GPS times were 1126270500 and 1126280500.  That's good, because it seems to mean that yesterday's problem with injections was temporary.

These injections were only done at LHO; LLO was not observing at those times.

Beverly, Jess

• For this DQ shift, the duty factor over the 4 days was 33.0% with the range mostly around 75 Mps or so.
• 50 Hz glitches: An unexpected round 2 winner in Hveto was traced to 50 Hz glitches that were shown to be related to ground motion in EX (alog) and later correlated with the turning on of an air compressor located there (alog).
• Range drops: The ETMY "saturations" (apparently due to DAC crossings ( alog)) continue to be present causing range reductions. Possibly interesting is the time series in h(t) and ETMY for a glitch causing a small range drop (see Fig. 1). Throughout this DQ shift, there appeared to be no obvious noise associated with the range drops visible in the h(t) spectrograms in the Summary pages. However, a feature (at the frequencies of the bounce and roll modes) in the h(t) spectrogram for  the lock on 13 Sept was seen to coincide with a range loss (see Fig. 2).
• New lines visible: Lines at about 500 Hz (violin modes) and 2400 Hz (unknown) were seen in the early part of locks on 10 and 11 Sept. The 2400 Hz line did not appear on subsequent days.
• Feature associated with bad alignment: A feature seen in the early parts of locks on 10 and 11 Sept in the range of 300-350 Hz (see Fig. 3) are probably due to lines associated with the PSL Periscope. We consulted Paul Altin who believes that this feature was a precursor to increasing noise due to worsening alignment. This feature did not appear on 12-13 Sept.
• CBC glitching: CBC BBH Omegagrams showed several categories of glitches although this study is still in progress.

The full details for the shift may be found here. 

Bubba and I inspected the instrument air compressors at both end stations and the corner.

The two end stations have failed vibration isolators. Bubba is checking our inventory of spares.

The corner station is in good condition - and has been mounted in a different fashion.

Attached are two photos; shorted.jpg is one of the end station units, notshorted.jpg is the corner.

Ref; https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=21436

Things were quiet. Then Stefan arrived, and I realized I had set the observatory mode but forgot the Intent Bit, and which spiraled into a bunch SDF differences. The LSC guardian showed a difference on a t-ramp (annoying that this kind of difference would keep us from going into Observe) and ASC had two diffs that I guess Evan logged about last night but didn't accept. Then Stefan went and set a bunch of ODC masks (this also would have kept us from going into observe, so also annoying) as well as tuning the whitening the IM4 QPD (which was saturating, Stefan assures me is out of loop so shouldn't affect anything). Guardian recovered from the earlier lock loss in 20 minutes (not annoying!) back to 70 mpc and it has been otherwise quiet.

While we were in commisioing mode, we had a strange non stationary spectrum, with large non stationary noise also appearing in MICH and PRCL.  I quickly looked at some triple witness sensors, since we've had issues with these recently, but didn't see anything obvious.  

The strange noise started a few minutes before 2:50:34 UTC Sept 10, seemed to get better for a few minutes and then got worse again around 2:57:21. 

We don't think that this was related to any comissioning we were doing.  Evan had temporarily lowered the DARM ugf and put a notch in, (which should cause anything like this).  He undid both changes when we saw the unusual noise, but the noise was unaffected by his change.  

We aren't going to investigate any further right now since the problem seems to have gone away.  

Dan, Evan

This evening we made a qualitative study of the coupling of beam jitter before the IMC into DARM.  This is going to need more attention, but it looks like the quiescent noise level may be as high as 10% of the DARM noise floor around 200Hz.  While we don't yet understand the coupling mechanism, this might explain some of the excess noise between 100-200Hz in the latest noise budget.

We drove IMC-PZT with white noise in pitch, and then yaw.  The amplitude was chosen to raise the broadband noise measured by IMC-WFS_A_I_{PIT,YAW} to approximately 10x the quiescent noise floor.  This isn't a pure out-of-loop sensor, and since we were driving the control point of the DOF3 and DOF5 loops of the IMC alignment channels we will need to work out the loop suppression to get an idea of how much input beam motion was being generated.  Unfortunately we don't have a true out-of-loop sensor of alignment before the IMC.  We may try this test again with the loops off, or the gain reduced, or calibrate the motion using the IMC WFS dc channels with the IMC unlocked.  Recall that Keita has commissioned the DOF5 YAW loop to suppress the intensity noise around 300Hz.

The two attached plots show the coherence between the excitation channel (PIT or YAW) and various interferometer channels.  The coupling from YAW is much worse: at 200Hz, an excitation 10x larger than normal noise (we think) generates coherence around 0.6, so the quiescent level could generate a few percent of the DARM noise.  Looking at these plots has us pretty stumped.  How does input beam jitter couple into DARM?  If it's jitter --> intensity noise, why isn't it coherent with something like REFL_A_LF or POP_A_LF (not shown, but zero)? 

The third plot is a comparison of various channels with the excitation on (red) and off (blue).  Note the DCPD sum in the upper right corner.  Will have to think more about this after getting some slpee.