1 / 9

The MEG Offline Project

The MEG Offline Project. General Architecture Offline Organization Responsibilities Milestones. Corrado Gatto INFN. PSI 2/7/2004. Estimated Event Size and Storage. Scaling BABAR & KLOE by multiplicity. Sizes Raw data 1.2 MB/event ESD 10 KB/event

darryl
Download Presentation

The MEG Offline Project

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. The MEG Offline Project General Architecture Offline Organization Responsibilities Milestones Corrado Gatto INFN PSI 2/7/2004

  2. Estimated Event Size and Storage Scaling BABAR & KLOE by multiplicity Sizes • Raw data 1.2 MB/event • ESD 10 KB/event • AOD 2 KB/event • TAG or DPD 1 KB/event Storage • Raw data 35 TByte • Reconstructed data 13 TByte • MC generated events 40 TByte • MC reconstructed events 25 TByte Assuming 109 generated MC events DST

  3. General Architecture: Guidelines • Computing & data model: MONARC • Completely based on ROOT • Ensure high level of modularity (for easy of maintenance) • Absence of code dependencies between different detector modules (to C++ header problems) • The structure of every detector package is designed so that static parameters (like geometry and detector response parameters) are stored in distinct objects • The data structure is build up as ROOT TTree-objects (Folders)

  4. Data Access: ROOT + RDBMS Model ROOT files Oracle MySQL Calibrations Event Store histograms Run/File Catalog Trees Geometries

  5. Offline Tasks • Offline Framework: • ROOT Installation and Maintenance • Main program Implementation • Container Classes • Control Room User Interface (Run control, DQM, etc…) • I/O Development: • Interface to DAQ • Distributed Computing (PROOF) • Interface to Tape • Data Challenges • Database Development (Catalogue and Conditions): • Installation • Maintenance of constant • Interface • Contribution to Event Display • DQM • At sub-event level responsibility is of detector experts • Full event is responsibility of the Offline team • Documentation

  6. Offline Tasks 2 • Offline Software Coordination: • DAQ Integration • Coordinate the work of detector software subgroups • Reconstruction • Calibration • Alignment • Geometry DB • Histogramming • Montecarlo Integration • Data Structure • Geometry DB • Supervise the production of collaborating classes • Receive, test and commit the code from individual subgroups • Computing Coordination: • Hardware/Software Installation • Users and queue coordination • Supervise Tier-0 and Tier- 1/2 computing facilities

  7. Manpower Estimate

  8. Responsibilities & Tasks • Detector experts: • LXe: Giovanni, Shuei, Ryu • DC: Matthias (hit), Hajime (Pattern), Lecce • TC: Pavia/Genova • Trigger: Donato (Pisa)

  9. Milestones • Start-up: October 2004 • Choice of the prototype Offline system: October 2004 • Organize the reconstruction code. December 2004 • per subdetector (simulation, part of reconstruction) • central tasks (framework, global reconstruction, visualisation, geometry database …) • Write down the Offline Structure (container classes, event class, etc…) : February 2005 • MDC: 4th quarter 2005 • Keep the existing MC in the Geant3 framework. Form a panel to decide if and how to migrate to ROOT: 4th quarter 2005

More Related