From vmandic@ligo.caltech.edu Tue May 10 14:41:07 2005
Date: Tue, 10 May 2005 11:41:05 -0700 (PDT)
From: Vuk Mandic <vmandic@ligo.caltech.edu>
Reply-To: Vuk Mandic <mandic_v@ligo.caltech.edu>
To: Keith Riles <kriles@umich.edu>
Subject: Re: [DASWG] Data quality integer bit flag word  - anyone using it?

Hi Keith,
I send you the GPS times that affect the coherence plots. I have not made
a systematic search for all the glitches that may be problematic in this
sense - I may do that in the future, but in the stochastic group we would
like to try a different cut first (using the sliding estimator approach),
which may remove all these glitches at once in our analysis. So, the list
I give here is likely not complete, but it does make the coherence trends
smoother.

For H1L1 study, the following times were problematic:

1) H1: 793712588-601. 
2) H1: 794611646-656, 794612416-456, 794612556-566, 794612636-646. 
ILOG notes winds and H2 losing lock around this time.
3) L1: 794907679-789, 794908019-029. ILOG notes a small train.
4) L1: 794911217-377, 794911537-747, 794911947-2037. ILOG notes a train.
5) L1: 794925247-257, 794925327-337, 794925467-677. ILOG notes a train.
6) L1: 794925758-978. ILOG notes a train.
7) H1: 795459217-227. ILOG notes some seismic events.
8) H1: 795652378-398. ILOG notes wind and seismic events.

For H1H2 study, the following times were problematic:

1) H1: 793253789-799. ILOG notes possible seismic events.
2) H2: 793728700-718. ILOG notes blasting.
3) H2: 795520320-332. ILOG notes seismic events.

Please let me know if you need any further information. Thanks,
                                                            Vuk