L1 epochs

The top two panels are numbers calculated from Kleine-Welle triggers generated on DARM_ERR. The top panel is the fraction of each day's data when the KW trigger rate (calculated each minute) was larger than 2Hz. The middle panel is the fraction of each day's data that contained at least one minute with a trigger with significance larger than 50. The lower panel is the daily median of the SenseMon range, from times in science mode (there are adays when there was no science mode, in which case the median range is zero).

From Laura's page. These plots are produced from minute-trend trigger rates of KW triggers (removing injections and 1 minute before/after lock). The right plot shows RATE vs time in a 12hr average period. The horizontal lines give the percentile levels for the run.

0. 815155213 = Nov 04 2005 16:00:00 UTC = S5 day 0
    Beginning of H1/H2 S5 up to beginning to L1 S5 (no L1 data here).
   
   
1. 816019213 = Nov 14 2005 16:00:00 UTC = S5 day 10.00 = Segs 1-289
   Noisy S5 start, up to Dec 17, when input beam was realigned and MC WFS gain was reduced.
   
   
2. 818888413 = Dec 17 2005 21:00:00 UTC = S5 day 43.20 = Segs 290-772
   A quiet epoch. 
   
   • The BS dewhitening filters used in the beginning of the run had  been causing the bounce modes to ring up.  The filters were swapped  on Jan17.
3. 822758414 = Jan 31 2006 16:00:00 UTC = S5 day 88.00 = Segs 773-1245
   A noisy epoch starts on Jan 31, nothing obvious in the elog to explain the increased KW rate.
   
   • Microseismic noise was responsible for a larger downtime in this epoch (~8%) than in others (as seen in pie charts).
   
   
4. 826387214 = Mar 14 2006 16:00:00 UTC = S5 day 130.00 = Segs 1246-1819
   A relatively quiet epoch, probably due to realignment of beam on ISCT1 and restart of RBS servo; noticeable increase in range too.  There's a couple of bad days (176-177) that may merit DQ flags, but not their own epochs. Epoch ends with ITMY incident: problem starts on May 2,  mirror is freed on May 5.  There is no data in science mode after May 2 15:02 UTC, so there's an low-duty factor time at the end of this epoch.
   
   
5. 831139214 = May 08 2006 16:00:00 UTC = S5 day 185.00 = Segs 1820-2941
   Epoch starts with better range after "ITMY incident". There are some noisy days (220-223, 257-258), but they seem isolated.
   
   • The PSL periscope PZTs were glitching throughout July, causing  transients in the MC and in REFL_I, and the occasional lockloss.  They were disabled on Aug6.
   
   
6. 840902414 = Aug 29 2006 16:00:00 UTC = S5 day 298.00 = Segs 2942-3121
   A noisy September, when high input power and seismic noise conspired for some very glitchy segments.
   
   
7. 843516014 = Sep 28 2006 22:00:00 UTC = S5 day 328.25 = Segs 3222-3687
   Some WFS commissioning made the range higher and the interferometer less glitchy, also visible in Rejean's spectrograms. There are some noisy days in this epoch.
   
   • The Autoburt glitching started on Oct6, and the effect is visible  in the Rejean's spectrograms.
   • Sam and Valera boosted the tidal servo gain on Nov30.  We've been less sensitive to the microseism since then, but it's still been pretty bad.
     
   End of 1st year: 847555214 = Nov 14 2006 16:00:00 UTC = S5 day 375.00
   

Epoch#	Epoch start	Epoch end	Epoch Plot	Epoch beginning	Epoch end
0 Beginning of H1/H2 S5 up to beginning to L1 S5 (no L1 data here).	815155213 Nov 04 2005 16:00:00 UTC  S5 day 0	816019213 Nov 14 2005 16:00:00 UTC  S5 day 10.00
1 Noisy S5 start, up to Dec 17, when input beam was realigned and MC WFS gain was reduced.	816019213 Nov 14 2005 16:00:00 UTC S5 day 10.00	818888413 Dec 17 2005 21:00:00 UTC S5 day 43.20
2 A quiet epoch.	818888413 Dec 17 2005 21:00:00 UTC S5 day 43.20	822758414 Jan 31 2006 16:00:00 UTC  S5 day 88.00
3 A noisy epoch starts on Jan 31, nothing obvious in the elog to explain the increased KW rate.	822758414 Jan 31 2006 16:00:00 UTC  S5 day 88.00	826387214 Mar 14 2006 16:00:00 UTC S5 day 130.00
4 A relatively quiet epoch, probably due to realignment of beam on ISCT1 and restart of RBS servo; noticeable increase in range too.  There's a couple of bad days (176-177) that may merit DQ flags, but not their own epochs. Epoch ends with ITMY incident: problem starts on May 2,  mirror is freed on May 5.  There is no data in science mode after May 2 15:02 UTC, so there's an low-duty factor time at the end of this epoch.	826387214 Mar 14 2006 16:00:00 UTC S5 day 130.00	831139214 May 08 2006 16:00:00 UTC S5 day 185.00
5 Epoch starts with better range after "ITMY incident". There are some noisy days (220-223, 257-258), but they seem isolated.	831139214 May 08 2006 16:00:00 UTC S5 day 185.00	840902414 Aug 29 2006 16:00:00 UTC S5 day 298.00
6 A noisy September, when high input power and seismic noise conspired for some very glitchy segments.	840902414 Aug 29 2006 16:00:00 UTC S5 day 298.00	843516014 Sep 28 2006 22:00:00 UTC S5 day 328.25
7 Some WFS commissioning made the range higher and the interferometer less glitchy. There are some noisy days in this epoch. The epoch ends on Day 375, end of "S5 1st  calendar year".	843516014 Sep 28 2006 22:00:00 UTC S5 day 328.25	847555214 Nov 14 2006 16:00:00 UTC S5 day 375.00