60 likes | 156 Views
John Zweizig LIGO/Caltech. S3 Data Quality Investigation. S3 Data Quality Segments. Data quality results will be presented as segments Segment list available at: http://tenaya.physics.lsa.umich.edu/~keithr/S3DQ/
E N D
John Zweizig LIGO/Caltech S3 Data Quality Investigation
S3 Data Quality Segments • Data quality results will be presented as segments • Segment list available at: http://tenaya.physics.lsa.umich.edu/~keithr/S3DQ/ • Current status of Data Quality investigations at http://www.ligo.caltech.edu/~jzweizig/S3_Data_Quality • Build segment list using 'segwizard' • Seqwizard GUI included with LigoTools. • Select tags • Also searches based on full/playground, minimum time, etc.
Data Quality Issues (so far) • Missing data • Summary trends • E-Log notes • Timing Errors (next talk) • Photodiode Saturation. • Calibration lines • FE Synchronization • Data Acquisition Errors • Environmental Issues? (mseism, wind, LN dewers)
E-Log Summaries • Issues noted in E-Log during running • Environmental issues (seismic, wind, microseism, etc) • Configuration changes/errors (e.g. gain / filtering changes) • Unusual noise noted • Calibration l ine errors • Hanford E-Logs summarized by Betsy Bland
Scan of Trend Data • Looked for FE synchronization errors • Scanned ETP and FE_SYNC counter channels • L1:ETMX errors in segments L1-97 (21 min) and L1-392 (12 min) • Missing calibration lines • Looked at excitation channel and SenseMonitor trends • Photodiode overflows (AS, REFL, POB) • Counters kept by FE software • Total Data lost (minutes)
DAQ Readout Errors • DAQ readout errors • During VME data transfers? • Affects only low order byte of 32-bit words transferred. • Symptoms • Glitches in slowly moving adc data (see fig 0x322d-0x32ff) • Non integers in float data • LSB of known values wrong • Effect on GW data • Not fully known • Effects limited to 1:65k • Reconstruct DARM? Cal lines?