100 likes | 104 Views
Traditional Components in HEP Offline Software. Vincenzo Innocente CERN CMS. Online vs. Offline. Where Offline starts? Are differences so great to justify: Different Operating Systems VxWorks vs. Unix Different GUIs (Analysis Environments) LabView vs. Explorer Different Databases?.
E N D
Traditional Components in HEP Offline Software Vincenzo Innocente CERN CMS V.Innocente HEP Components
Online vs. Offline • Where Offline starts? • Are differences so great to justify: • Different Operating Systems VxWorks vs. Unix • Different GUIs (Analysis Environments) LabView vs. Explorer • Different Databases? V.Innocente HEP Components
R&A Framework Components • Event objects manager • Event filter • Detector set-up • Raw data access • Asynchronous data (calib’s, param’s) access • Reconstruction policy • User persistent objects manager • UI • Visualization V.Innocente HEP Components
A Layered Model USER CMS Quality HEP Extensions HEP Specific Commercial & Public Domain Higher V.Innocente HEP Components
LHC++ Model • Promoted by CMS, ATLAS & IT/ASD • Use standard widely-used components to minimize risks and cost • HEP contribution limited to HEP specific extensions and applications V.Innocente HEP Components
Plug & Play? • Consistent user view of experimental data • Plug-in user module no changes to analysis framework • Modularized Framework • Interchangeable Standard Basic components “User” code stays the same Recompilation would not be avoided... V.Innocente HEP Components
Common “Analysis” Software • ATLAS and CMS address exactly the same physics but ATLAS is a Toroid, CMS a Solenoid • Their Event Models are today different: should they use a common one? • Should they have common Kalman filters, common jet finders, common Higgs finders Where the software becomes a qualifying difference? V.Innocente HEP Components