1 / 10

Traditional Components in HEP Offline Software

Explore the distinctions between online and offline components in high-energy physics software, from operating systems to databases. Delve into event object management, reconstruction policies, and user interface considerations. Discuss the benefits of using standardized components and the potential for plug-and-play functionalities in the analysis framework.

seanmedina
Download Presentation

Traditional Components in HEP Offline Software

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. Traditional Components in HEP Offline Software Vincenzo Innocente CERN CMS V.Innocente HEP Components

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

  3. V.Innocente HEP Components

  4. V.Innocente HEP Components

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

  6. V.Innocente HEP Components

  7. A Layered Model USER CMS Quality HEP Extensions HEP Specific Commercial & Public Domain Higher V.Innocente HEP Components

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

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

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

More Related