IFO locked and observing for past 9 hours. Seismic and microseism are flat and mostly within normal range bounds. Microseism is near the top of the range bounds. Winds are up to a light breeze (up to 7mph), outside temps are 18F for all reporting stations. There have been several ETM-Y saturations, however the remains around 80Mpc.      

Our cdsfs1 backup machine once again crashed, was not accessible via the network. I was able to remotely power cycle it via IPMI.

O1 day 107

model restarts logged for Sat 02/Jan/2016 No restarts reported

  Transition Summary:
Title:  01/3/2016, Day Shift 16:00 – 00:00 (08:00 – 16:00) All times in UTC (PT)
	
State of H1: 16:00 (08:00), The IOF has been in Observing mode for last 5.5 hours. Range and power are normal. Environmental conditions are good. There have been several saturations during the last shift. Will clear the timing error on H1SUSETMY (CPU max at 63uS) at the next out of Observing opportunity.  
 
Outgoing Operator: TJ

• Title: 1/3 OWL Shift: 08:00-16:00UTC (00:00-8:00PDT), all times posted in UTC
  

• State of H1: Observing at 78Mpc for 5hrs

• Shift Summary: One lockloss with some odd happenings just before. The POP power was degrading over the prior few hours and the control signals didn't look good (see previous alogs from me and Travis for more info). Had to play with green a bit and then the OMC to get things back up.

• Incoming Operator: Jeff B

• Activity Log:

• 08:07 - Out of Observing to change blends
• 08:15 - Observing
• 08:16 - Lockloss
• 10:11 - Lockloss at DC_READOUT
• 10:41 - Observing

Observing at 77Mpc for 3hrs.

Environment is calm, CW inj running, Timing error on H1SUSETMY

I had to fiddle with ALS for a bit, run through an initial alignment, change the PZT sweep starting voltage in omcparams.py again to -30 (see alog24609 for the last time),and then lost it at DC_READOUT. But it came right back up after and we are back to observing!

When I arrived the IFO wasn't looking good, H1:LSC-POP_A_LF_OUTMON had been dropping in power since ~5UTC and the control signals were all over the place. The DARM spectrum wasnt looking good below 70Hz or so. EX ISI had a large amount of movement in it, but the dropping POP power and lack of useism doesn't explain our usual blends ringing up.  I decided to try changing the blends anyway, mainly because it was the only idea I had. This calmed the ASC slightly but a few minutes later AS90 started to dive and then lockloss.

This seemed to have happened a month ago (alog23941).

Now out of lock, we resumed the SDF monitoring of the PMC REF V channel, restored the original 1.34615V setting as per Jason, and accepted it in SDF.

Title: 1/2 Eve Shift 0:00-8:00 UTC (16:00-24:00 PST).  All times in UTC.

State of H1: Observing

Shift Summary: Locked in Observing for my entire shift.  However, we have witnessed a brief drop in range and ringing up of ASC loops and tidal signals (see earlier aLog 24645) in the middle of the shift.  Towards the end of the shift, we have seen a drop in transmitted power via H1:LSC-POP_A_LF_OUTPUT (see attached screenshot) that is very reminiscent of a situation for which I was also the on-duty operator.  Perhaps is it coincidental, but this earlier instance of these issues occurred EXACTLY one month earlier (see aLog 23921 for related evidence of the tidal relation amd aLog 23941 for the analysis and comparative plot).  If Jenne's conclusion still holds true, sorry TJ!

Incoming operator: TJ

Activity log:

0:17 Betsy to optics lab

1:38 Betsy out

3:46 Ringing up of ASC loops is noticed and DIAG notification of tidal approaching its limit, range degrades ~15 MPc

4:04 ASC loops ring down and range returns to normal

We noticed that the range had dropped and the ASC loops had rung up.  Guardian DIAG was also notifying us that the tidal control was nearing its limits at both ETMx and ETMy.  While digging through the aLog for solutions (and finding only speculative fixes involving switching of ISI blends), things seemed to have calmed down and returned to normal.  However, plotting the TIDAL_CTRL signals for both X and Y shows that the control signal is much larger than we have seen in quite some time.  The first plot is a 2 day plot of the TIDAL_CTRL signal for both arms, and the second is a 30 day plot.

Activity Log: All Times in UTC (PT)

00:00 (16:00) Take over from TJ
21:20 (13:20) SDF difference on EY ECAT PLC2 – Called Sheila (see aLOG #24640)
21:35 (13:35) Kyle – On site to over fill Mid-Y CP3
22:20 (14:20) Kyle – Leaving site
22:29 (14:29) GRB Alert – In 1 hour hold. LLO down. 
23:30 (15:30) Stand down from GRB alert hold
00:00 (16:00) Turn over to Travis


  
End of Shift Summary:

Title:  01/02/2015, Day Shift 16:00 – 00:00 (08:00 – 16:00) All times in UTC (PT)

Support:  Vinny, Sheila,  
 
Incoming Operator: Travis

Shift Detail Summary:   Fiber Wrong Polarization was getting very close to limit of 40. Trend shows swings over time. This will not affect the IFO while in lock, but could make relocking difficult if still high. At shift end, this had dropped to around 32. 

    OK shift – In Observing mode for full shift. Environmental conditions were good for the shift. Range was in the high 70s to low 80Mpc for the shift. There were several (15 plus) ETM-Y saturations, which knocked down the range a bit.

   It has stopped snowing. Since it was a dry light snow, there was not much accumulation. Still very cold at the site – around 18F.

Looking at the spectrograms and glitchgrams on the summary pages for January 2nd there seems to be some interesting behaviour from about 10 - 35 Hz at LHO.  The noise drops in this band over the course of the day and glitches in this band become less frequent as well.  It does not seem to correlate to wind speed or ground motion, at least not in an obvious way.  Looking at the ground motion BLRMS page of the summary pages, there do seem to be some spikes between 4 - 6 UTC, in multiple bands.  However these spikes are relatively short-lived and the noise in the spectrograms starts before that.  I've attached a few images showing noise and glitches from the band of interest..  The plots are also visible on the summary pages.

    Noticed SDF was showing a difference for EY ECAT PLC2. The fiber temperature control had switched off at 12:50. Called Sheila. While talking to Sheila noticed two other channels related to fiber temperature  were cycling on an off. Sheila said this would not be a problem maintaining lock but could be a problem for relocking. 

   Sheila noticed that the Fiber Wrong Polarization percentage was close to its limit of 40. It was between 37 and 39 percent. This should not be a problem while we are locked, but should be addressed at the next lockloss.       

Noticed dewar vapor pressure indicating 10 psi which is lower than what I had remembered for the nominal value for this dewar -> Exhaust check valve bypass opened, LLCV bypass opened 1/2 turn ccw, LN2 appeared exiting pipe after ~45 seconds -> let fill for ~2 minutes

    IFO has been locked and Observing for the past 6.5 hours. PSL power is holding at 21.7W, range has been moving around a bit due to several ETM-Y saturations, but is mostly in the high 70s to low 80Mpc. These saturations do not appear to be associated with RF45 glitches. The wind is running at a light to gentle breeze (4-12mph). It is currently snowing and starting to accumulate. Seismic plots are mostly flat and within normal operating bands. The EY Y-axis in the 0.03-0.1Hz band has been climbing over the past 2 hours. Microseism looks normal and is centered around 0.3um/s.      

Happy New Year all!

H1 has historically not has as bad of RF beat / whistle problems as L1 has. In fact, the last alog report is for data on October 30th. But dec 31st shows a high density of glitches above 100Hz and densest above 500Hz, which have the signature shape of RF beats we've seen before and are correlated with PRCL and SRCL, similar to one of the manifestations of whistles seen at LLO. 

• Figure 1 shows the SNR vs frequency of the glitches at H1 for December 31st. The low-SNR red triggers above 100Hz are mostly whistles that hveto found correlated to PRCL and SRCL.
• Figure 5 shows the time-frequency behavior, where I circled the red dots that include whistles, where one can see how many of these quiet whistles were happening on Dec 31. 
• Figures 2,3,4 show example omega scans of these low-SNR whistles. Note that these extend to low enough frequency to reach the CBC signal range.

Note 1: we produce auto omega scans for the loudest glitches that hveto finds, and these whistles are all very quiet. If anyone wants to follow these up in more detail, you can get GPS times for the high-frequency low-snr triggers for Dec 31 correlations with PRCL and SRCL at those links. 

Note 2: Dec 31 looks like the worst day, but there might have been some weak whistles occuring on other days too, but we'd have to follow up some low SNR triggers on those days (e.g. today Jan 1 and the past few days).