With Richard's sanction, I wiggled the binary cables from the ITMY coil driver but no glitches resulted...

These are all within a four hour period with the last one ~1855utc.

There are no others since I reported on them yesterday.  Actually, as I dig deeper and look at full data (as the minute trend bands looked too wide,) I see that there are 8 drops of the V3 status bit.  Most lasting several seconds.  I'm tempted to go wiggle a few cables since the IFO is not locking with the high winds.

Oh yes, Jeffery reminded me that even the rogue excitation alarm triggered on more than half of these.  That occurs when we still have DAC drives when the WD is tripped or something like that.  I'm not worried about that aspect of this but it just indicates the irritation of this problem.

   Wind appeared to be dropping (down into the mid-teens) and seismic activity was also coming down. At 19:50 (12:50) tried relocking. The wind came back up at almost the same time. Only made it to LOCK_ALS one time. At 20:10 (13:10) put the IFO back into a down state until conditions improve.  

   20:30 (13:30) recording constant winds into the 30s & 40s with gusts at End-X well over 50mph. (Just had all 5 weather stations reporting sustained over 30mph).    

   Environmental conditions remain difficult, but may be improving. Wind has dropped to be consistently below 20mph. Seismic activity is also dropping a bit, but is still high. 

   Having trouble with the ITM-Y "Coil Driver Chassis Bio" and ST1 and ST2 watchdog trips, (see #22947 姁). Spoke with Hugh earlier in the shift and have a call into him as these event are becoming more frequent.

   If conditions continue to improve and ITM-Y gets sorted out, will attempt to relock the IFO.         

    After 1.5 hours of attempting to relock and only making it to DRMI-1F twice before lock loss. Most lock breaks occurred during ALS or FIND_IR. Environmental conditions are not favorable for relocking. Will try to relock when conditions improve.    

Carlos, Dave:

The CDS /ligo file system got filled to 100% yesterday. We temporarily made space by removing a large backup and are working on extending/replacing this file system, in the mean time if you can compress or remove any large files (they are all on tape backup) that would be appreciated.

Title:  10/31/2015, Day Shift 15:00 – 23:00 (08:00 – 16:00) All times in UTC (PT)
	
State of H1: 15:00 (08:00) IFO is down due to environmental conditions. 

Outgoing Operator: TJ

Quick Summary:  Wind is a fresh to strong breeze (17-27) with gusts in the mid-30s. Microseism is elevated due to winds and coastal storm conditions. Have been unsuccessful at relocking. Will continue to attempt to relock. If not successful will put the IFO into a down state until conditions improve.  		

• Title: 10/31 OWL Shift: 7:00-15:00UTC (00:00-8:00PDT), all times posted in UTC
  

• State of H1: Unlocked
  

• Shift Summary: Locked for about 6 hours of my shift, then lost it at 12:41. I brought it all the way up only to lose it while running the A2L script. Winds are picking up to the low 30's now, and the forcast calls for gust up to 50mph today (normally forcasted much lower than actual speeds). useism is at 0.4um/s.

• Side note: ran into a few errors in different places reporting "disk space full." Patrick sent Dave an email about this last night, but this is preventing me from posting screenshots, so sorry for the lack of lockloss info posted.

• Incoming Operator: Jeff B

• Activity Log:

• 12:41 Lockloss. Wind wasn't too high, not too sure what happened. PRC1 and SRC1 seemed to have have a growing oscillation that showed up before anything else, but this is probably a symptom not a cause.
• 13:06 PRMI to DRMI transition fail
• 13:47 NOMINAL_LOW_NOISE
• 13:54 Lockloss during A2L. winds were beginning to pick up a bit, and the signals looked very similar to the last lockloss.

More on the PRMI to DRMI Transition

Since I can't post screenshots, I will write it out. Like Sheila said in alog22982 AS90 was on the low side, about 250 counts, POP18 was around 130, and POP90 at 85.

Lost lost at Nominal Low Noise while I was running the A2L script( 13:54 UTC).

Let's try this again.

Lockloss at 12:41 UTC

Wind ~20mph, useism 0.4um/s. I will post plots momentarily.

Observing @ 72Mpc

Environment:

• Wind - ~15mph
• useism - 0.4um/s
• Site - empty, just me

For the Operator Thursday Maintenance item that was tmissed this week, I topped off the chiller with 150mL.

Title: 10/30 Eve Shift 23:00-7:00 UTC (16:00-24:00 PST).  All times in UTC.

State of H1: Observing

Shift Summary: After the wind calmed to a reasonable level a few hours into my shift, I began a slow progression of locking.  I got to do a few things that were new to me, such as being involved in restarting a (really) frozen guardian node, and engaging the ISS 2nd loop manually.  Locking in Observing after engaging 45 mHz blends.  Microseism coming up slowly.  Winds calm, at last.

Incoming operator: TJ

Activity log:

0:07 Jeff K starting charge measurements

1:28 Jeff K done

1:52 HAM 1 HEPI restored after Hugh's measurements finished

1:53 Start locking

2:30 Adjusted ISS ref. signal after diffracted power low notification

3:01 Jeff K attempts restart of PRM guardian node

4:45 Start initial alignment after many unsuccessful locking attempts

5:15 PRMI to DRMI transition unsuccessful

5:51 GRB alert

6:00 45 mHz blends turned on

6:26 manually engaged ISS 2nd loop after getting stuck

6:34 Observing

I made some plots to get a sense of how wind and microseism are affecting our duty cycle so far in O1. The first plot is a histogram of duty cycle vs percentiles of wind/microseism. The second plot is a timeseries that shows the microseism and wind plotted for all of O1 (until Oct 31 00:00 UTC) with the percentiles of each superimposed and locked segments along the bottom. All data are minute trend maximums. I used the flag H1:DMT-DC_READOUT_LOCKED for the locked state. 

Comparing with long term wind / microseism statistics:

8-year wind study from Margarita: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=12996

Long term study of the seismic environment: P040015

Below I have included a table of actual values for each percentile. The 8 year study of wind has higher values (I inferred the 8-year percentiles from the first plot in Margarita's aLog). Note that the 8 year study used hourly max trend data as opposed to minute trends.  Also, keep in mind Margarita's study has already shown that historically September / October are less windy then spring/summer months.

The long term microseism numbers (taken from fig. 5 of the paper) agree more closely with O1 results so far.

The code used to generate these plots is located here: https://ldas-jobs.ligo-wa.caltech.edu/~jordan.palamos/duty_cycle/

This is a followup on Ed's alog22918 where he reported seeing MICH glitch around the same time DHARD magnitude became large. Miquel found that the MICH "breathing" was actually a result of bad FFT windowing but it could have hidden the 8.6 Hz line that became apparent in DARM the morning of October 28th (and disappeared on the next day). Plot 1,2 and 4,5 attached show spectrum of DHARD Pitch, MICH, and ground motion near HAM2 during the time DHARD oscillation time reported in alog 22918 and alog 22875 compare to their nominal. Plot 3 and 6 are the timeseries of DHARD ptich and yaw during those time. DHARD oscillation frequency is ~21mHz on 10/28 plot and ~39 mHz on 10/27 plot. To show that this oscillation has nothing to do with MICH 8.6 Hz glitch I've attached a set of spectrum and  timeseries during the time 8.6Hz began to make its appearence in DARM (7, 8, and 9). The low frequency oscillation isn't there and 8Hz peak shows up clearly in every channel.

I will continue to look for any environment factor that might have caused the DHARD instability. Although Jenne did mentioned that a wrong gain could have caused the loop to become unstable. I was told the that gain hadn't changed for months until somebody lowered it recently to help with the oscillation (Kiwamu?).

While locking DRMI, we noticed that the POP_90 signal looked strangely much larger than it normally does.  Evan noticed that PRM was still aligned during this phase when it (and SRM) should normally be misaligned.  The PRM guardian was showing that the request was 'MISALIGNED' while the state readback still showed 'ALIGNED'.  Looking at the guardian log for PRM, I see that it stopped logging ~3 hours prior to starting to attempt locking.  See attached screenshot for error messages.

J. Kissel

Taking advantage of the windy down time, I grabbed another set of optical lever charge measurements this evening on both the ETMs. Two bits of news:
(1) The results from Tuesday had shown good agreement between optical lever vs. photon calibrator (cal lines, or kappa_TST) estimations of the H1 SUS ETMY ESD actuation strength, until the recent ETMY bias flip. However, with today's points, we can see that the first measurement after the flip was an outlier and the latests two match the slope much better. All is well, it just re-re-reminds us that it's difficult at best to claim a trend from only one or two optical lever charge measurements, you need several measurements over the course of days to establish a reliable trend.
(2) The H1 SUS ETMX effective bias voltage or charge continues to remain stagnant. Unlike prior to the start of the run, where the rate of increase (or decrease) in charge would stay constant after a bias sign flip, ETMX broke the mold by leveling off after teh start of the run. Recall that we've had a pretty good low-noise duty cycle, which means that the ETMX ESD Bias has been turned OFF for 70-80% of the past few months. This is great evidence to show how turning off or reducing the bias on the ESD attacts less charge. It's also good evidence to support the theory that it is indeed the high ESD bias voltage that is attracting whatever free charged particles are left in the chamber -- as opposed to the alternative mechanism of slow drift in the electric potential of the cage.

Apologies, I don't have updates to the kappa_TST coefficient, but given its consistency, I don't expect that it's slope has changed at all, and youu can just draw a mental line through the past ~week's trend.