From jzweizig@ligo.caltech.edu Thu Mar 10 12:08:43 2005
Date: Thu, 10 Mar 2005 09:06:34 -0800 (PST)
From: John Zweizig <jzweizig@ligo.caltech.edu>
To: Keith Riles <kriles@umich.edu>, cadonati@ligo.mit.edu, kats@ligo.caltech.edu
Subject: burstMon DQ flags

Hi Keith,

I have attached the segment lists for burstMon cluster>2 fraction > 0.5
for >= 5 consecutive minutes. There are separate lists for the 1kHz and
2kHz jobs (total 6 segment lists). These have the usual provisos, i.e.

  1) they are run from burstMon trends... if the trends are missing or
     invalid (e.g. because travertine was doing its thing) bad data
     segments won't be included for those times.

  2) The cuts haven't been tuned. I can try the same for e.g. f_c > 0.6.
     Now that I have everything set up it should be much easier.

The bottom line is that for the 1kHz the data losses aren't too bad. For
the L1 2kHz sample though, the flagged segments are of order 30% of the
live time, which sounds like it's not make a very specific choice.
Anyway Have fun with the above segment lists, and let me know if you'd
like to see more, e.g. f_c>0.6 (or 0.7?, 0.8?) or a different minimum
time.
Best,

John


    [ Part 2, ""  Text/PLAIN (Name: "H1-burstScan_2kHz.week2_summary") ]
    [ 40 lines. ]
    [ Unable to print this part. ]


    [ Part 3, ""  Text/PLAIN (Name: "H2-burstScan_2kHz.week2_summary") ]
    [ 188 lines. ]
    [ Unable to print this part. ]


    [ Part 4, ""  Text/PLAIN (Name: "L1-burstScan_2kHz.week2_summary") ]
    [ 284 lines. ]
    [ Unable to print this part. ]


    [ Part 5, ""  Text/PLAIN (Name: "H1-burstScan.week2_summary")  45 ]
    [ lines. ]
    [ Unable to print this part. ]


    [ Part 6, ""  Text/PLAIN (Name: "H2-burstScan.week2_summary")  8 ]
    [ lines. ]
    [ Unable to print this part. ]


    [ Part 7, ""  Text/PLAIN (Name: "L1-burstScan.week2_summary")  90 ]
    [ lines. ]
    [ Unable to print this part. ]