1 / 15

Tracking data quality

Tracking data quality. M.Weber, FNAL 2/22/04. Outline. Data quality Bad runs Reasonable runs This is more about trackers, for tracking see Tue morning. Data quality. Detector hardware status Readout Reconstruction. Enabled ? Data integrity. Time evolution / stability. Bad runs.

gefen
Télécharger la présentation

Tracking data quality

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. Tracking data quality M.Weber, FNAL 2/22/04

  2. Outline • Data quality • Bad runs • Reasonable runs This is more about trackers, for tracking see Tue morning M.Weber, FNAL

  3. Data quality • Detector hardware status • Readout • Reconstruction • Enabled ? • Data integrity Time evolution / stability M.Weber, FNAL

  4. Bad runs • Flagged manually (with scripts) based on e-log / shifter rating / experts info /run database • Runs with unrecoverable data are marked as “bad”. • Runs with somewhat lower efficiency that is measurable are marked as “reasonable” When one or more readout crates are not included in the run or not in the trigger M.Weber, FNAL

  5. The e-log Very good job by shifter, but sometimes… Run Type Events SMT Quality 175030 PDAQ/PHYSICS 55020 GOOD 175031 PDAQ/PHYSICS 36106 GOOD 175033 PDAQ/PHYSICS 434401 GOOD 175034 PDAQ/PHYSICS 0 GOOD Run 175033 M.Weber, FNAL

  6. SMT more in detail • What makes a run bad? Missing crates. Large scale HV problems. Solenoid • What compromises data quality? Missing VRBs. Threshold screw ups that affect many HDIs. Suspicious examine histos • What does not degrade run quality? Reduced HV on a few HDIs. Disabled HDIs. M.Weber, FNAL

  7. How much do we flag bad ? • SMT 2003: W/LUMI: 1122 runs with 148.60 pb-1NO LUMI:        91 runs with ? pb-1 BAD:            74 runs with   0.89 pb-1GOOD:            0 runs with   0.00 pb-1REASONABLE:   1134 runs with 147.05 pb-1UNKNOWN:         3 runs with    0.64 pb-1SPECIAL:         2 runs with    0.02 pb-1NO INFO:         0 runs with    0.00 pb-1 M.Weber, FNAL

  8. CFT 2003 W/LUMI: 1122 runs with 148.60 pb-1NO LUMI:        91 runs with ? pb-1 BAD:            22 runs with   0.23 pb-1GOOD:             0 runs with   0.00 pb-1REASONABLE:      0 runs with    0.00 pb-1UNKNOWN:      1191 runs with 148.37 pb-1SPECIAL:         0 runs with    0.00 pb-1NO INFO:         0 runs with   0.00 pb-1 M.Weber, FNAL

  9. CTT 2003 W/LUMI: 1122 runs with 148.60 pb-1NO LUMI:        91 runs with ? pb-1 BAD:            54 runs with   8.34 pb-1GOOD:          637 runs with  99.22 pb-1REASONABLE:    134 runs with  15.71 pb-1UNKNOWN:       385 runs with  25.32 pb-1SPECIAL:         3 runs with    0.01 pb-1NO INFO:         0 runs with    0.00 pb-1 M.Weber, FNAL

  10. Post shutdown data verification • See ADM talks 12/15/03 and 12/19/03 • Before 178721 • After 185868 M.Weber, FNAL

  11. SMT Recovered HDI Lost one more… M.Weber, FNAL

  12. CFT M.Weber, FNAL

  13. Tracking M.Weber, FNAL

  14. Problematic HDIs… M.Weber, FNAL

  15. Conclusions / Comments • In 2003 5% runs are bad (<1 %lumi, ~4%CTT) • Flagging BAD at Lumi block level ?Not manually ! • SMT is not worse • CFT lost % channels • There are a lot of monitoring plots in RecoCert, does anybody look at them ? • Monitoring of stability/time evolution ? • Get feedback from physics to detector groups M.Weber, FNAL

More Related