S5 Data Quality

John ZweizigLIGO/Caltech

Hanover, October 25, 2007

Data Overview

Running time: GPS 815155200 – 875232000 (60076800s, 695d) Single IFO science mode:

» H1: 46670444s, 540d, 77.8%

» H2: 47001597s, 544d, 78.2%

» L1: 39463778s, 457d, 65.7% Double coincidence science mode

» H1 · H2: 42856054s, 496d, 71.3%

» H1 · L1: 34234457s, 396d, 57.0%

» H2 · L1: 33664680s, 390d, 56.0% Triple coincidence science mode

» H1 · H2 · L1: 31737338s, 367d, 52.8%

Range Distribution

Range by Calendar Week

Data Quality Segments

Not all data created equal - So... DQ segments

» Generated online / off-line » More will be defined as detector characterization work continues» No implied recommendation

– Chosen segment appropriate for an analysis!

– Check safety

» More information available from: http://gallatin.physics.lsa.umich.edu/~keithr/S5DQ/flaginfo.html

Segment Database

Segment DBs at CIT, LHO, LLO

» local insertion» Automatic synchronization between databses

Segment information» start-time, end-time» Active (asserted/not asserted)» provenance» version (v99 is combination of all active versions)

Insertion, interrogation tools:» LSCdataFind» Segwizard

Category 1: No Data / Bad Data

As close to a no-brainer as it comes:» IFO not in lock (or in triggered mode)» No raw data» Data not read out correctly

Most eliminated from Run Statistics on Slide 1

H1 H2 L1Segment Time (ppm) Time (ppm) Time (ppm) Time (ppm)AS_TRIGGER 3030 80 933 33 6774 206 6881 217INVALID_DARMERR 3 0 8 0 21 1 21 1MISSING_RAW 96 2 64 1 2112 54 32 1OUT_OF_LOCK 1467 31 2616 56 2242 57 3435 108

H1·H2·L1

Instrumental Glitches

Digital-loop overflows

» SEVERE_LSC_OVERFLOW» ASI_CORR_OVERFLOW

Other direct glitches» TCS Glitch» Calibration line glitches» OSEM. optical lever glitches (damping servo)

H1 H2 L1Segment Time (ppm) Time (ppm) Time (ppm) Time (ppm)SEVERE_LSC_OVERFLOW 3531 76 2942 63 15232 386 14855 468ASI_CORR_OVERFLOW 590 13 3146 67 123663 3134 99435 3133MMT3_OPTLEVER 0 0 36087 768 0 0 32 1OSEM_GLITCH 0 0 112 2 0 0 46 1CALIB_DROPOUT 8600 184 478 10 222 6 7951 251TCS_GLITCH_LOUD 307 7 158 3 0 0 242 8

H1·H2·L1

Other Segments

Wind:

» Wind_Over_30MPH» HURRICANE_GLITCHINESS

Seismic» TRAIN_LIKELY» DEWAR_GLITCH» EARTHQUAKE_GLITCHINESS

Electricity and Magnetism» POWERMAINS_DISRUPTION» POWERMAIN_GLITCH» POWMAG» SEIS_DARMERR_5_7HZ

IFO Running States» PRE_LOCKLOSS_nn» H[12]_Not_Locked» H[12]_LOCKLOSS» H[12]_LOCKGAIN

IFO related» LIGHTDIP_nn_PERCENT» SIDECOIL_ETM[XY]

[_RMS_6HZ]» CONLOG_SICK» CALIBRATION_BAD» BAD_SENSING» BAD_SERVO

Photo-diode Consistency

4 AS photo-diodes: redundant measure of AS port signal

Demodulated and recorded at 256Hz

Inconsistency can indicate» Dust in light path

» Single PD readout error

PD Consistency Test

Chi²:

» Calculated at each sample.

» χ²=Σ(αiPD

i – ¼ΣPD

j)²

» Averaged over 4s stride

» χ²max

is largest <χ²> in 1

minute

Environmental Effects

H1 periodic (~6Hz) glitches Assumed mechanism:

» Several seismic-stack resonances near 6Hz

» Pendulum “damping” worsens sideways motion

Tagging techniques» ETM[XY] side coil read-back» ETM[XY] side overflows» DARM_ERR 4-7 Hz Band» ETM[XY] side sensor 6Hz RMS

ETMX 6Hz RMS Flagging

H1 DARM_ERR glitch significance plotted vs. log RMS in ETMY 5.8-6.2Hz Band

RMS read from minute trends – 1 minute granularity

Clear population of glitches at very high significance (~104)

Significance doesn't increase with increasing RMS! Possibly overflow effect.

ETMY_RMS_6HZ flag from this Should be reanalyzed with better

granularity.