1. Stefan Hild S4 Data Workshop, Hannover, Mai 2005 Title MU3 glitches Max-Planck-Institut für Gravitationsphysik (Albert-Einstein-Institut)

2. Stefan Hild S4 Data Workshop, Hannover, Mai 2005 GEO‘s sensitivity during S4 (cal V2) MU3- Glitches Extremly windy day (see labbook p.2265) BLRMS 220-230 Hz BLRMS 989-999 Hz

3. Stefan Hild S4 Data Workshop, Hannover, Mai 2005 MU3 Glitches and Data quality Instrumental viewpoint: Was tracked down to be related to MU3 or MU3-IM being stuck. Glitches were present on the RF going to EOM.  Glichtes entered MI at input and passed through the MI to detection via the light. Cured problem, by moving MU3 to different position (no touching) DA, DC viewpoint: Which part of the data should be used for which gw searches ? What is a proper indicator for data quality ? (chi square) What is a useful threshold for declaring data as not useful ?

4. Stefan Hild S4 Data Workshop, Hannover, Mai 2005 BLRMS for first 10 days of S4 (cal V2) 8 stretches of each about 8 hours with MU3-glitches On the whole about 40-60 hours (mostly nighttime) are ‚contaminated‘ / affected

5. Stefan Hild S4 Data Workshop, Hannover, Mai 2005

6. Chi^2 for first 120 h of S4

7. Stefan Hild S4 Data Workshop, Hannover, Mai 2005 To Do Definition of reasonable CHI^2 thresholds 99% of data lies below chi^2 = 2e5. more than 90% of the data lies below chi^2 = 2000 chi^2 below 10000 is not always bad chi^2 above 10000 seems to be mostly bad LABBOOK: page 2269