1 / 6

S3 Data Quality Investigation

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/

kato
Download Presentation

S3 Data Quality Investigation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. John Zweizig LIGO/Caltech S3 Data Quality Investigation

  2. 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.

  3. 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)

  4. 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

  5. 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)

  6. 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?

More Related