Dave Barker, TJ

The new version of ext_alert.py (the scripts that polls GraceDB and reports events) is now running here at LHO. It has been running at LLO while they tested it and we got the OK from Duncan Macleod today. This new version will alert for "E" type events and now "G" type as well. The new events can be seen on the CAL_INJ_CONTROL.adl medm screen.

As a test, psinject is running excitations to the h1calcs model.  Note that the actual injection is turned off using the hardware injection control MEDM screen.  The psinject process is under control of Monit on h1hwinj1.  This will be turned off at the conclusion of Tuesday maintenance.

The following servers have been patched and rebooted:
ldr.ligo-wa.caltech.edu
ldas-pcdev2.ligo-wa.caltech.edu

The following servers were patched but were not and will not be rebooted today:
detchar.ligo-wa.caltech.edu
all compute nodes (node[1-270], gpu-node[1-5])

We saw a large glitch in the RF AM monitors with high coherence with DARM at around 16:13 UTC on Sept 22nd, while the IFO was locked and maintence was happening.  There werw people in the LVEA (though not near the PSL) and people in the CER but they were near the SEI and SUS racks, not the ISC racks. The first attached plot shows this on a 5 hour time scale, the second plot has 5 days.  This can be compared to Evan's plots of the last 3 weeks (21766) 

The full report can be found on the detchar wiki, but here are the main highlights:

• Nice long locks. Duty cycle 72%. Majority (5/9) of lock losses seem to be due to earthquakes
• Main downtime during these 4 days has been due to Chile earthquake which took place just before the start of the shift (16th at ~23:30 UTC) and subsequent aftershocks.
• The 48/49 Hz glitches seem to be becoming more prominent; hveto picks out PEM-EX_ACC_BSC9_ETMX_Z_DQ, HPI-ETMX_BLND_L4C_RX_IN1_DQ, HPI-ETMX_BLND_L4C_Y_IN1_DQ channels as good witnesses
• The 60 Hz glitches are continuing; hveto picks SUS-ETMY_M0_DAMP_Y_IN1_DQ and SUS-ETMY_L2_WIT_L_DQ channels as good witnesses
• 300-400Hz glitchy region (periscope?) is much worse at the beginning/end of a lock stretch. Also noticing this region more around the times of earthquakes/seismic activity (which is not so surprising). ASC channels are good witnesses of this region.
• Looking more in to the RF45 AM stabilization issues and generating DQ flags for these times.

TITLE: Sept 22, Day Shift: starting 15:00UTC

STATE Of H1: Locked/Commissioning, Range is 50+MPC, trying to stay locked for filter tests

OUTGOING OPERATOR: Corey

QUICK SUMMARY: Maintenance started at 15:00UTC.  Many people/trucks on site and people in VEAs and in the LVEA.  Attempting to stay locked for ASC filter tests: Sheila.

- Jeff, forklift,  dust monitor, mechanical building and high bay

- Christina - out buildings, no real cleaning, but checking for problems

- Ken, hammering 250m from end stations

- Richard, vault

- Bubba, 3IFO checking storage, and placing cones to protect elec.

- Jodi, 3IFO checks

- Pepsi, two trucks, on site

- Hanford Fire, hydrant checks 

- Hugh, checking HEPI fluid levels, 

- Jim, troubleshooting hardware injections, may glitch...

- Joe, taking Fire Dept. guy through LVEA and both end stations

- Mike, film crew, LVEA

- Praxair is onsite, though came through the open gate, so I don't know where they are

- Sheila, loading filter, started 15:20UTC

- Sprague, spraying perimiter

TITLE:  9/22 OWL Shift:  7:00-15:00UTC (00:00-8:00PDT), all times posted in UTC

Just chatted with Brian and Jeremy at LLO about the start of their Maintenance time (which is usually 8amCT [13:00UTC]), and they said they are going to let L1 stay in Observation Mode beyond their usual Maintenance start time so we can have more double coincident time (they will let L1 drop out whenever activities/contractors bump it out of lock.)

(For the record, LHO's Maintenance Time starts at 8am PST [15:00UTC]).  

H1 in Observation Mode for 2.5+hrs @75Mpc.  Looks like L1 just came back @60Mpc.

Seismic band of 0.03-0.1Hz um/s has finally returned to 0.01um/s (took about 3.5hrs).  Winds under 5mph.

As mentioned earlier, Terramon reported EQ around 8:00utc....it was off about about 2min with a lockloss at 8:02utc.  Here is evidence this was an earthquake lockloss:

• Terramon alarm
• Oscillations observed in POP-A & AS-RF90 about a minute before the lockloss.  
• On the Tidal striptool, PRM_M3 showed oscillations ~90sec before lockloss.  
• Seismically, 0.03-0.1 um/s increased from 0.01 um/s and peeped up to 0.4um/s and hovered above 0.1um/s off/on over a 1-hr span.

Here's a timeline of how this event occurred:

• 7:30 L1 lost lock 
• 8:02 eq lockloss, no watchdogs tripped
  • 8:08 Waiting for DRMI (should have switched Observatory Mode to Lock Acuquisition at this point)  
  • 8:19 DRMI locked on wrong mode, and I increased BS pitch on-the-fly to get Guardian to take over.
  • 8:20 DRMI locked
  • 8:33 Observatory Mode switched to Lock Acquisition (should have been around 8:08!)
• 8:34 Back to Observation Mode

TITLE:  9/22 OWL Shift:  7:00-15:00UTC (00:00-8:00PDT), all times posted in UTC

STATE OF H1:   Jim handed over a nice boring shift (just how I like it!).  Earth is not rumbling & winds are calm (below 10mph).  He mentioned issues with RF45 they had at the beginning of the current lock (it sounds like if this occurs again, we ride it out?  Stay in Observing Mode?)

OUTGOING OPERATOR:  Jim W. 

SUPPORT:  Solo.  (Sheila is on-call, if needed)

QUICK SUMMARY:   H1 sailing along at 75Mpc.  

Guardian has a YELLOW notification about HAM5 related to Master Switch.

A quick scan of DARM (compared to 9/10/15 reference):

• 27.4Hz peak not seen 
• 645Hz peak not seen
• A few bumps around 315 & 343Hz observed.

• Title: 9/21/2015 Eve Shift: 11:00-7:00UTC 

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

• Support: Evan,Jenne,Sheila, others in control room for most of shift

• Shift Summary: Travis relocked right before I arrived, quiet aside from occasional ETMY glitches, ground and wind mostly quiet

• Activity Log:

• 0:10 Chris Biwer wants to do an injection, I take IFO out of observe, put mode into Planned Engineering (for want of a more accurate option)
  0:50  Chris is done, intent bit switched back
•  

To ride out earthquakes better, we would like a boost in DHARD yaw (alog 21708)  I exported the DHARD YAW OLG measurement posted in alog 20084, made a fit, and tried a few different boosts (plots attched).  

I think a reasonable solution is to use a pair of complex poles at 0.35 Hz with a Q of 0.7, and a pair of complex zeros at 0.7 Hz with a Q of 1 (and of cource a high frequency gain of 1).  This gives us 12dB more gain at DC than we have now, and we still have an unconditionally stable loop with 45 degrees of phase everywhere.  

A foton design string that accomplishes this is

zpk([0.35+i*0.606218;0.35-1*0.606218],[0.25+i*0.244949;0.25-i*0.244949],9,"n")gain(0.444464)

I don't want to save the filter right now because as I learned earlier today that will cause an error on the CDS overview until the filter is loaded, but there is an unsaved version open on opsws5.  If anyone gets a chance to try this at the start of maintence tomorow it would be awesome.  Any of the boosts in the DHARD yaw filter bank currently can be overwritten. 

Chris B., Jeff K.

We performed a series of single-IFO hardware injections at H1 as a test. The intent mode button was off at the time.

All injections were the same waveform from aLog 21744.

tinj was not used to do the injections. The command line used to do the injections was:

awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 H1-HWINJ_CBC-1126257410-12.txt 0.2 -d -d
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 H1-HWINJ_CBC-1126257410-12.txt 0.5 -d -d >> log.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 H1-HWINJ_CBC-1126257410-12.txt 0.5 -d -d >> log.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 H1-HWINJ_CBC-1126257410-12.txt 0.5 -d -d >> log.txt
awgstream H1:CAL-INJ_TRANSIENT_EXC 16384 H1-HWINJ_CBC-1126257410-12.txt 1.0 -d -d >> log.txt

I've attached the log (log.txt) which contains the standard output from running awgstream.

Taken from the awgstream log the corresponding times are approximates of the injection time:

1126916005.002499000
1126916394.002471000
1126916649.002147000
1126916962.002220000
1126917729.002499000

The expected SNR the waveform is ~18. The scale factors applied by awgstream should change the SNR by a factor of 0.2 and 0.5 when used.

I've attached timeseries of the INJ-CAL_HARDWARE and INJ-CAL_TRANSIENT. The injections did not reach the 200 counts limit of the INJ_HARDWARE filterbank that we saw in the past.

Watching the live noise curve in the control room we did not notice any strong indication of ETMY saturation which usually manifests itself as a rise in the bucket of the noise curve. But this needs followup.

I've attached omegascans of the injections.

I took higher resolution spectra of the supposed 41Hz HSTS roll mode tonight (see first attachment).  There are 2 peaks, however only the first peak has any coherance with anything.  The 2 peaks are at:

40.9375 Hz  (lots of DARM-PRC-SRC coherence)

41.0117 Hz  (no coherence with anything I looked at)

The second attachment shows the set of 41Hz peaks in 3 of the last lock stretches.  I attempted to use the ASC signals to check for coherence with DARM, but:

- the OSEM sensors on the HSTS suspensions are too noise, so see no coherence

- there is coherence with BOTH SRC and PRC, unfortunately, so hard to pin point where

- there is coherence with SRC1 which talks to SRM - is it cross-coupling thru ASC/LSC?

- there is no coherence with SRC2 likely because it is a noisy detector (AS DC), so can't tell if the SRM and SR2 combination that it talks to contribute to the 41Hz

- PRC1 not plotted, no ASC drive there, but witnessed that there is no coherence there

- PRC2 goes to PR3, so while there is coherence there (not plotted) it is likely because it is cross-coupling  from SRC to PRC

- IMC_TRANS_P not plotted, but witnessed no coherence, again too noisy of a detector?