Analysis Validation

Problem: How do we know that analyses are doing what they say they are doing?

GOAL: Can we make some tools to provide some quality checks?

  • The way people do it currently:
    • Synchronization exercises
    • Providing common tools
    • Provenance tracking
    • ???

  • How can we improve?
    • Tracking user code?
    • Tracking cvs checkouts?
    • What to do about TTrees?
      • Pragmatically people will do it
      • What about reducing PAT as much as possible? Read access speeds, etc? 38x developments helped this.
      • ADVERTISING tools as much as possible.
      • Devil's advocate: Make everyone switch to edmTuples?
        • What about edmTuples to edmTuples?
      • Pragmatist's advocate: People hate the naming schemes from edmTuples.

  • Nuances:
    • How do we know that the code on your laptop is running the same way as on lxplus, etc?
    • 32bit vs 64bit
    • Mac OS X vs Linux

-- SalvatoreRoccoRappoccio - 23-Sep-2010

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2010-09-23 - SalvatoreRRappoccio
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback