J. Kissel

More evidence of non-linear scattered light being a problem for the low-frequency sensitivity of the IFO, I show a trend of each translational DOF of the 3-10 Hz BLRMS velocity of the ground (as reported by the ITMY GND STS, in the PEM stay-clear zone of the H1/H2 bier garten) vs. the Binary Nuetron Star range. There is clear correlation between the two. The levels of in BLRMS that show correlation are roughly ~100-200 [nm/s] RMS or ~1-5 [nm] RMS. I also show trends of the same BLRMS band for the ISI ST1 T240s and ST2 GS13s in the Z direction. While the overall amplitude is reduce by an order or two of magnitude, the variation remains identical to the ground. 

@LSCFellows, @DetChar -- it would be good to do some scattering fringe studies e.g. LHO aLOG 22405 comparing how the speed of each chamber's isolation platform (as measured by T240s and/or GS13s) relates to the various BLRMSs of the DARM spectrum. 

This may also have to do with Robert's recent discovery of problems with the ITM elliptical baffles -- see, e.g. LHO aLOG 31886. Remember that the 3-10 Hz band cover's the HEPI Crossbeam Foot resonance (see LHo aLOG 13505 and G1401167), so ground motion is amplified in this region. 

And just in case anyone want's to blame the changes in BNS range on fluctuations in optical gain due to slow alignment drifts or other optical plant changes, I attach a trend of the relative optical gain. There is no correlation there.

Since Daniel/Dave is about to boot MC1-3 SUS, ASC, LSC models, Kissel and I are trying to tackle the SDF changes in the SAFE files - specifically the ~30+ that were sitting in the ASC SDF.  Many of them were from changes made at many different times over the last 2 weeks while the IFO was down.  We have reconciled:

- ACCEPTED Sheila's threshold changes from Nov 23, 2016 - alog 31794.

- ACCEPTED changes that were accepted in OBSERVE, but not yet in SAFE, mostly loop offsets such as CSOFT, etc.

- INMATRIX_P and Y changes from

- INMATRIX_P and _Y from someone's test a while ago.  ACCEPTED as now 0

- NOT MON - ASC-ADS_SEN_MTRX dither channels - under guardian control

- NOT MON - Various loop filter switches - now under guardian control- ACCEPTED some random MC2 M3 DRIVEALIGN Out put switch that is not used.

(see WP #6377) 

We are comparing gauge drift behavior when pumped by local turbo vs. when pumped by site vacuum volume. 

The attached shows how other gauges which share the common 24VDC pwr supply respond to changing electrical demands - in this case, PT120B responds to PT180 traversing through different pressure ranges.  We aren't interested in pursing eliminating this phenomenon at this time but, rather, want to document this for future reference.  

Since Livingston was down, we took the opportunity to tweak the alignment into the reference cavity since its
transmission had fallen from ~3.9V to ~2.1V.  The alignment was tweaked (see RCAlignment.png).  However the
noise eater decided to start oscillating.  Toggling the switch restored the reference cavity transmission to
a higher value (NoiseEater.png).

     Christina also wiped/mopped the Ante-room and the Laser Room.

    We confirmed that all the computers were powered down.



Christina/Jason/Peter

J. Kissel, E. Goetz for S. Karki
WP #6368

After nice, high duty cycle weekend, we continue the schedule for this roaming line with a move from 3001.3 to 3501.3 Hz. [edit] SDF screenshot, changes are now stored in OBSERVE and SAFE.snaps for H1CALEX SDF tables.


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           Nov 28 2016 17:20:44 UTC  Nov 30 2016 17:16:00 UTC         days    @ 30 W  
1501.3       35k                      02:00                   39322.0           Nov 30 2016 17:27:00 UTC  Nov 30 2016 19:36:00 UTC         02:09   @ 30 W         
2001.3       35k                      02:00                   39322.0           Nov 30 2016 19:36:00 UTC  Nov 30 2016 22:07:00 UTC         02:31   @ 30 W
2501.3       35k                      05:00                   39322.0           Nov 30 2016 22:08:00 UTC  Dec 02 2016 20:16:00 UTC         days    @ 30 W
3001.3       35k                      05:00                   39322.0           Dec 02 2016 20:17:00 UTC  Dec 05 2016 16:58:57 UTC         days    @ 30 W
3501.3       35k                      05:00                   39322.0           Dec 05 2016 16:58:57 UTC
4001.3       40k                      10:00                   39322.0           
4301.3       40k                      10:00                   39322.0                
4501.3       40k                      10:00                   39322.0           
4801.3       40k                      10:00                   39222.0           
5001.3       40k                      10:00                   39222.0         

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           Nov 11 2016 21:37:50 UTC    Nov 12 2016 03:28:21 UTC      ~several hours @ 25 W
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                   39322.0           Nov 12 2016 03:28:21 UTC    Nov 16 2016 22:17:29 UTC      days     @ 30 W (see LHO aLOG 31546 for caveats)
4301.3       40k                      10:00                   39322.0           Nov 16 2016 22:17:29 UTC    Nov 18 2016 17:08:49 UTC      days     @ 30 W          
4501.3       40k                      10:00                   39322.0           Nov 18 2016 17:08:49 UTC    Nov 20 2016 16:54:32 UTC      days     @ 30 W (see LHO aLOG 31610 for caveats)   
4801.3       40k                      10:00                   39222.0           Nov 20 2016 16:54:32 UTC    Nov 22 2016 23:56:06 UTC      days     @ 30 W
5001.3       40k                      10:00                   39222.0           Nov 22 2016 23:56:06 UTC    Nov 28 2016 17:20:44 UTC      days     @ 30 W (line was OFF and ON for Hardware INJ)  

Maintenance today while LLO is down:

Jeff B. - move cleanroom curtains, climbing on output tube
Peter - reference cavity alignment (1/2 hour)
Richard - swap SRM analog camera for Gig-E
Richard - swap ESD HV supplies at end Y
Daniel - DAQ changes
Christina - cleaning in PSL enclosure
Betsy - charge measurements
Kyle - isolate PT180 and pump down

Rana on site Tuesday with group of artists, would like to enter LVEA if possible
TIAA-CREF representative on site

TITLE: 12/05 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 71.4238Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: Locked for my whole shift, drop in range seemed to have fixed itself because I couldn't find anything. Possibly Hanford traffic?
LOG:

• 08:18 Observing
• 08:24-08:31  Changing phase for PI Mode 28
• 08:32 Out of Observe to run a2L. This did not seem to help in the 20hz region on the dtt.
• 08:38 Observing
• 14:04 GRB

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

Been locked and observing for 5+hrs. There have been a few glitches lately, and the range has started to drop a little (from 75 -> 70Mpc). Seems to be a bit more noise in DARM around 30-90Hz. Everything else looks good aside from that though. I'll keep investigating.

TITLE: 12/05 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 4mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.50 μm/s
QUICK SUMMARY: After a 39hr lock, Ed handed me a fully locked IFO. Nice.
 

06:30 Lockoss - reason unknown. There were no alerts. There were no obvious environmental causes. Going to begin re-locking. I will switch ISI config back to WINDY as per the email that Jim just sent out. after locking, if necessary after looking at a2l DTT script I may run the a2l script.

H1 is locked for 37hours 10 min.  uSeism mean is resting about the 90%ile. Winds got a litle feisty but have calmed to less than 20mph. Some EQ activity caused a slight rise in BLRMS about 2 hours ago. There have been some EY glitches as noted in my activity log below. There was a CP4 alarm and a PSL dust moinor alarm. The TCSY chiller message was as it was on Patrick's shift. The plot of the glitch is also below.

At the beginning of my shift I ran the measurement that looks at the DARM coherence for a2l. The plot is below.

01:21 EY saturation.

01:51 Granted Carlos remote access to CDS

01:55 CP4 alarm

02:03 TCSY chiller flow message - Verbal Alarm

02:15 BIG EY glitch took the range to 4.1 Mpc

02:44 EY glitch

C. Cahillane

The ER10 LHO Actuation Uncertainty Budget

What has been done:
(1) Gathering all the Newtons/count actuation function measurements for the three stages (UIM, PUM, TST) from November 8th, 9th, 11th, 12th, and 18th.  
(2) Running an MCMC over the physical parameters gain and delay for all three stages.  (Only used freq < 10 Hz for UIM, freq < 100 Hz for PUM)
(3) Plot MCMC cornerplots and resulting residuals uncertainty budget from the MCMC PDFs.  
(4) Take the residuals from the MCMC physical parameters' fit, and plug them into a Gaussian Process with kernel k(x,y) = a + b * exp(-0.5*(x-y)**2/l**2), where a, b, and l are the hyperparameters of the GP.
(5) Train the GP on the residuals, and produce a mean posterior fit and an uncertainty budget from the trained kernel.

TL:DR : Take measurements -> Physical MCMC -> Unmodeled GP -> Frequency-Dependent Systematic Error +- Uncertainty Budget

The mean posterior fit is the frequency-dependent systematic error.  The uncertainty budget is also frequency-dependent.  
The Gaussian Process results are shown in Plots 1, 2, and 3 for the UIM, PUM, and TST stages.  The 1-sigma, 68% confidence intervals are plotted.

I want to call attention to how small the uncertainty is in the bucket.
The frequency-dependent uncertainty in the bucket is on the order of 0.1%

This is exciting, but is it real?  
Points in favor:
(1) We have five sets of measurements, and uncertainty roughly goes as 1/sqrt(N) where N = measurement number.  This allows us to win a lot where the measurements are nearly the same and the errorbars are small.
(2) The GP fit hits most of the measurement errorbars.
(3) Uncertainty expands where we have less information.
Points against:
(1) Overfitting might be a problem.  There seem to be unphysical wiggles that nail our data in the bucket. 
(2) This uncertainty budget is lower than ever before by a factor of 10.  This requires extraordinary proof.   
Rebuttals:
(1) We might be able to combat overfitting by lengthening the kernel length-scale and adding more noise to our measurements.  Also, the whole point of this method is to capture unmodeled wiggles.  
(2) The data analysis methods used are more advanced and designed to handle frequency-dependence.  

Plots 4, 5, and 6 are the UIM, PUM, and TST physical model MCMC fits with the measurements.  
Plots 7, 8, and 9 are the UIM, PUM, and TST physical model MCMC parameter cornerplots.

A couple of points: 
(1) The GP uncertainty doesn't take into account the uncertainty from the MCMC physical parameters.  The GP uncertainty dominates nearly everywhere, since the MCMC uncertainty is so tiny (See plots 4, 5, 6).  I may try to incorporate the MCMC uncertainty directly into the measurement errorbars that I input into the GP.
(2) A lot remains to be done.  LLO actuation, sensing at both sites, and final response uncertainty.  
(3) If these results hold, we may have uncertainty dominated by time-dependence.  Stay tuned.

From /opt/rtcds/userapps/release/sys/h1/scripts/VerbalAlarms/Lock_Summary.py.

End of Day Summary 
Current Status: Observing, Locked since Dec 3 14:49:59 UTC (1164811816.0) 
Total Day Locked: 33hr 10min 4sec [138.2%] (119404/86400)
Total Day Science: error [error%] (error/86400)

TITLE: 12/04 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 73.3703Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: IFO locked and in observing during entire shift. Lock stretch now past 33 hours. CP4 pump level is still glitching in and out of alarm. Evan G. is here as fellow.
LOG:
16:22 UTC Kyle left. He was working in the vacuum prep lab at the end of the hallway when I arrived.
17:44 UTC Multiple EY saturations. A comb appeared in DARM from 500 Hz to 1 kHz. Lasted ~ 1 minute. Looks similar to what Nutsinee posted in her owl shift summary.
23:10 UTC TCSY chiller flow is low verbal alarm. Trend showed it recovered.
23:44 UTC Single EY saturation. Everything in DARM below ~300 Hz jumped.
00:00 UTC Thought I briefly saw red squares on the CDS overview under end Y, but they disappeared.

Verbal alarms announced 'TCSY chiller flow is low' at 23:10:09 UTC. Plot attached (1 hour of full data). Seems to have recovered.