From desai@gravity.psu.edu Thu Mar 27 19:10:37 2008
Date: Thu, 27 Mar 2008 19:10:30 -0400 (EDT)
From: Shantanu Desai 
To: Keith Riles ,  
Subject: Proposed H2 DQ flag around November 1 2006 for SUS-MMT3_ASC_YAW saturation

Hi
Keith,
As you know people in the glitch group have started scanning the elogs. The
first thing I noticed on the first day of my assigned shift is that H2 had
some troubles around November 1 2006 because of SUS-MMT3_ASC_YAW saturation.
This is described  in more detail at
http://tinyurl.com/2dxgdj

I think this deserves a separate DQ flag (unless Gaby has already provided
the relevant intervals while scanning the H2 elogs or if anyone else is
working on it) I looked one of  the relevant channels indicative of the
problem (H2:SUS-MMT3_ASCYAW_OUT16) which is saturated at 0.1526 and it
affects the inspiral range.
You can see its effect on the inspiral range and its correlation with
this channel at https://gravity.psu.edu/~psurg/glitch/H2ascyawsaturation.png
Could the interval between 846398109 and 846441633 in H2 be DQ flagged for
this purpose? Probably it will be a category 3 or 4 flag
The intervals was obtained from the second trends and the exact start and
end time may not be accurate, but should be good enough for now.

I think this is a one-time problem only and was soon fixed (since I don't
see any more examples of saturations for the next few days), but if we find
more intervals then this flag can be updated. If you have more questions,
let me know.

On a different note from the elogs there are many intervals indicated by
operators for vehicular related activities and these segments are maked as
"Activity " flags. If I recall right someone (either you  or John or someone
else) was specifically working on flagging those from the conlog entries. Is
that the case and should we ignore all such instances of vehicular activiies
noted in the elog?

Or should we note down such intervals in case no one else is actively
working on the "vehicular" flags? Thanks
shantanu