The winds have died down to ~15 mph, so I have begun attempting to lock again.

TITLE: "10/30 [DAY Shift]: 15:00-23:00UTC (08:00-16:00 PDT), all times posted in UTC"

STATE Of H1: No lock attempt. Too windy to even try.

SUPPORT: Evan, Sheila, Hugh

SHIFT SUMMARY: We've tried to lock for several hours in the morning. The wind speed was higher when the time the ifo lost lock so we decided that it's not going to happen and left the ifo alone for the rest of the shift. Wind speed stays above 40mph for the past 10 hours.

INCOMING OPERATOR: Travis

ACTIVITY LOG:

15:12 Chris (with the sealing crew) going to X arm beam tube

15:14 Switched blend filters to 90 mHz (was at 45mHz)

15:53 switched back to 90mHz after lost lock while locking DRMI

16:13 switched from quiet 90 and quiet 250 to windy 90 (X,Y) and windy 250 (RX, RY). Leave ETMs with the quiet filters.

16:19 locked DRMI 4F

16:23 Lockloss at CARM 5PM

16:52 Switched EX and EY blend to Windy 90 (X,Y) and Windy 250 (RX, RY). I was awared of the ISI trip issue with these filters but I had nothing better to do. I was hoping that Once ISI trip we can untrip them and move on.

16:53 kyle to X28

16:54 Untripped all the ISI WD, but there was still some issue and we couldn't move on. I switched all the ETMs ISI blend back to Quiet.

17:27 DRMI locked very quickly this time. Took ~ 1 minute.

17:29 We decided to wait for the wind to calm down. No point continue kicking the optics.

18:59 Kyle back for lunch

19:32 Richard to EY to do some safety work (near electronic racks I think).

20:06 Richard back

           Kyle to high bay then LVEA to retrieve some stuff.

20:24 Kyle out of LVEA and going back to X28

20:26 Switched all windy blends back to quiet.

20:54 Richard to HAM6 to do more safety work

21:11 Richard back

22:14 Kyle back from X28

22:30 Bubba to Mid to check on Chris.

22:51 Bubba back

This week we installed and caulked aluminum strips on a total of 120 meters of enclosure. We have completed the upper section on 840 meters of enclosure between Mid X and End X.

It is known that if the little test-masses in the STS-2s get too far from center, then noise of the instrument gets worse.
They should all be in the -2V -> +2V range, and one of the End-Y masses might be at -8 V.

Because we are fortunate, Ben Abbott attached the mass-location-monitor to our ADCs.
see pg 11 of the BSC SEI system wiring schematic
https://dcc.ligo.org/LIGO-D0901301
The UVW/ mass positions are being send to ADC 3, chns 20, 21, 22 (for nums 0-31)

Because we are knuckleheads, we do not seem to be monitoring these channels.  
An integration issue has been filed: https://services.ligo-wa.caltech.edu/integrationissues/show_bug.cgi?id=1148

Because we are committed to excellence, all the inputs from the ADC are saved as EPICS records.
I think that the epics channels for the end station are
H1:IOP-SEI_EY_MADC3_EPICS_CH20
H1:IOP-SEI_EY_MADC3_EPICS_CH21
H1:IOP-SEI_EY_MADC3_EPICS_CH22

the other STSs should be at
   - end X -
H1:IOP-SEI_EX_MADC3_EPICS_CH20
H1:IOP-SEI_EX_MADC3_EPICS_CH21
H1:IOP-SEI_EX_MADC3_EPICS_CH22

and for the 3 in the corner station

S1:IOP-SEI_[B1|B2|B3]_MADC3_EPICS_CH[20|21|22]

(or maybe it is B6, but I don't think so)


I looked at the channels for End Y, and it seems that the STS-2 at End Y needs re-centering.

It would be smart to 
1) watch the monitor channels when you mash the re-center button. If they are the right channels, it will be very clear.
2) check the other sensors, too.

We aren't trying to lock anymore. Just waiting for the wind to settle. Free maintence day today.

With commissioners and run manager approval, WP 5584, TFs were started at 1940utc.  The forecast from the scripts is almost 6 hours but I hope that is good to 50%.  This doesn't include the lowest frequency bands, I expect to get an opportunity to collect those on Saturday.

The full report is posted on the O1 DQ Shift wiki 

• The overall duty cycle was 39.1%, this was mostly due to violin modes and microseisms on Monday, then maintenance on Tuesday, but we finished strong with 79% duty cycle on Wednesday!
• The small amount of time that was locked on Monday was clean.
• The Tuesday locks had a few loud glitches that had high enough to X^2-weighted SNR to be troublesome to the BBH search but we tracked that down to DAC overflow glitches.
  • After looking at the OmegaScans, it looked like the glitches will be picked up in the autogating portion of the offline searches.
• Wednesday was a good day and there were no loud glitches that aregoing to mess up BNS or BBH searches.  There was a dip in the range starting around 11:30 that was correlated with increased seismic noise seen in the BLRMS.  HVETO also concentrated most of its efforts in the later part of the day.

Sheila, Nutsinee

I looked at the PRMI to DRMI transition attempts that TJ and Nutsinee logged in the past 2 days, (22972 and 22951), zoomed in plots of both are attached. 

As you can see for the sucsesfull transition AS90 was high (about 400 counts in the unnormalized channel) when the SRCL feedback came on, and in the unsucsesfull one AS90 was low, about 50 counts.  I have added code to the DRMI guardian that changes the SRCL trigger to AS90 before attempting to turn on the SRCL feedback, with an on threshold of 200 (the trigger uses the normalized channel, so this is something like 450-500 counts in the unnormalized channel ploted here) and an off threshold of 50 coutns.  Since the wind is high today and locking the full IFO is not really an option, nutsinee will give this a try if it is compatible with Hugh's measurements. 

I looked at cosmic ray triggers within one minute around each blip glitch at LHO during ER8 and the first week of O1.  I then put that information into the attached histogram, where each time is relative to the nearest blip glitch.  Each blip could contribute however many triggers were within a minute around the time.

Total time analyzed: 4440 seconds (74 blips, 60 seconds each)

Total Cosmic Triggers: 640 (10.49 per bin in the histogram)

Trigger Rate: 0.144 Hz

Histograms for the triggers around every individual blip glitch can be found here .

I also analyzed 8 hours (from 4 different days) of arbitrarily chosen time from O1 to get a sense of the overall cosmic trigger rate.  I found that the average cosmic trigger rate was exactly the same, .144 Hz .  So the cosmic trigger rate near to blip glitches (within 30 seconds) seems to be exactly the same as the overall average cosmic trigger rate.  This, along with the apparently random distribution of triggers in the histogram, would suggest to me that there is no correlation between blip glitches and cosmic ray triggers.

The original blip times come from this page , however Marissa Walker has gone through the list of times and removed glitches that don't appear to be blips under close inspection.  This significantly reduced the number of times.  The most recent time that I included in my analysis was from Sept 23rd.  I would be happy to run over more recent times if anyone has a more recent list of blip glitches.

The DTT template for showing the MICH spectrum on the control room wall is suffering from leakage,  preventing us from seeing some features in the 8 to 11 Hz range. The current parameters and window are:

Window: Hanning

Start/end frequencies: 0/74444Hz 

BW: 0.1Hz 

Overlap: 70% 

Avarages: 3

Resulting BW: 0.18Hz

After playing with the available windows (but keeping all other parameters fixed so it will refresh with the same latency), I have found that Flat-Top reduces the resulting BW to 0.24Hz but also reduces the leakage problem. This would allow us to see features over the problematic range. The first two attached figures correspond to 2015-10-28 14:48:24 ; they show how the Hanning window suffers from a real leakage problem while Flat-top maintains it’s performance. The feature over 8Hz corresponds to a problem solved by Bubba on log (22939). 

In 22947, I said "...the coil driver sent a bad status..."  This is too broad and points fingers at the Coil Driver.  While the zero bit may have originated at the coil driver, as we believe that occurrance will latch the state it is very possible the bit dropping to zero may have originated down stream.  There is the binary interface chassis bundling all the 9pin channels into db37s and then the Bin I/O card in the I/O chassis.  Trouble shooting these doesn't appear easy, especially in O1 time.

It makes sense that we tailor the model side to not trip the ISI when these less than a second changes occur.  Otherwise we should just wait to see if it is a problem.  Looking back a month, the first time it occurred was during the power outage but that was legit.  Otherwise, it occurred Tuesday but Richard says that might have been him exploring, experimenting or some other exing.  And then yesterday.  So other than the model change which we'll discuss that what should be a simple code adjustment, we'll leave it til it breaks for now.

TITLE: "10/30 [DAY Shift]: 15:00-23:00UTC (08:00-16:00 PDT), all times posted in UTC"

STATE Of H1: Lock Acquisition

OUTGOING OPERATOR: TJ

QUICK SUMMARY: Wind ~30 mph. Switched to 90mHz blend. TJ reported he had trouble with DRMI when so he had to switched it back to 45 mHz. Just had a lockloss at DRMI so I'm gonna try switching the blend back to 45 before doing DRMI. Things don't look very hopeful.

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

• State of H1: Unlocked since 12:42 UTC (5:42 PST)
  

• Shift Summary: The wind started picking up halfway through my shift, I'm pretty sure a large gust or two took us out of lock. I have been trying different things to get it back up and running with no success. Finished Initial Alignment and leaving it for Nutsinee.

• Incoming Operator: Nutsinee

• Activity Log:

• 12:42 Lockloss
• 13:02 switch blends X and Y dof from the 45mHz to the Quite_90's. I had a handful of locklosses before it would aquire DRMI, but it would aquire ALS nicely. With this and the still high useism, I thought I would give the 90's a try.
• 13:08 Switch back to 45's. The switch to the 90's immediately looked bad, I couldn't advance to DRMI.
• 14:00 Loss at SWITCH _TO_QPDS
• 14:11 Loss at SWITCH _TO_QPDS
• 14:20 Started Initial Alignment. In the past, if it fails at SWITCH_TO_QPDS repetitively, this could be the sign of bad alignment. Thought it was worth a try.

Here is some info that Sheila wanted.

13:50 started to try PRMI

13:52 PRMI locked

13:56 Transition start and fail

(A few trends attached one just zoomed in more than the other)

Lockloss at 12:42 UTC, seemed to be a few large gusts right before the we lost it. EX trace hit 50mph.

Kiwamu reported in 22781 about a couple lock losses due to the drive to HEPI hitting the 250um limit.  HEPI can handle more than this but should not need to if the PSL (likely Ref Cav) temperature does not trend off somewhere.

Attached are several PSL Temp channels for 14 days with the limit hit time noted on the run away Tidal Channel.  Certainly many of the PSL Temp channels show a trend that correlates pretty well with the run away.  In iLIGO we had tight temp control of the Ref Cav, do we have a temp of the Ref Cav now or is there another signal that would best represent that?