ALICE OFFLINE :ORGANIZATION - PowerPoint PPT Presentation

About This Presentation
Title:

ALICE OFFLINE :ORGANIZATION

Description:

Be friendly to the user (not necessarely user friendly !) PAW was a success. 3. Toward AliRoot ... Any (most) user (about 900): Rapidly usable (even if ... – PowerPoint PPT presentation

Number of Views:13
Avg rating:3.0/5.0
Slides: 21
Provided by: Sch8159
Learn more at: https://www.star.bnl.gov
Category:

less

Transcript and Presenter's Notes

Title: ALICE OFFLINE :ORGANIZATION


1
ALICE OFFLINE ORGANIZATION
  • A user point of view
  • Yves Schutz, SUBATECH, France

(PHOS biased)
2
Toward AliRoot
  • A single framework for all computing activities
    in ALICE
  • Simulation Online Offline (ReconstructionAnal
    ysis)
  • Be friendly to the user (not necessarely user
    friendly !)
  • PAW was a success

3
Toward AliRoot
  • The framework must be adapted to
  • The particularities of the experiment
  • Large events gt 80 Mb
  • Many events gt 2(2) Pb/year
  • Huge data flow gt 1 Gb/s

4
Toward AliRoot
  • The framework must be adapted to
  • Any (most) user (about 900)
  • Rapidly usable (even if unstable)
  • Available on all major platforms
  • Low learning threshold
  • Looks like a-postiori design criteria for Root

5
  • All OO C
  • The unique framework is AliRoot (same language
    for script and implementation)
  • Fortran is tolerated (GEANT3.21 wrapped)
  • Open source (user potential developper)

An often disputed (at CERN) choice but it works !
6
Organisation
7
Alice User
Talks to root Through a macro
8
Alice User
Talks to root Through a macro
9
Alice User
Talks to root Through a macro
10
Alice User
Talks to root Through a macro
11
Alice User
12
Simulator
13
Reconstructioner
14
Developers and users
  • About 900 potential users
  • About 50 developers scattered arround the world
  • Steering group at CERN ( 5 persons )
  • 1-2 developper-librarian/detector
  • About 5 (regularoccasional) developpers/detector

15
To stay within the frame(work)
  • The offline board
  • The steering group
  • The librarians
  • Meets every week (micro), 6 weeks (macro)
  • Users training
  • 4 one-week meetings/year
  • Users developpers
  • Presentations classes

16
but not enough
  • ALICE defined Coding Conventions
  • Strictly enforced (blame/shame)
  • Automatic tool
  • Syntax
  • Naming
  • Style
  • make check
  • .viol

17
Maintenance
  • CERN based CVS Repository
  • Librarian have exclusive commit rights
  • Developpers are automatically informed by e-mail
  • HEAD must compile, not necessarely bug free
  • Every 2 weeks a release (3.02) bug free, usable
    by any user

18
Documentation
  • Root builds html documentation (to be improved)
  • Root does reverse engeenering (uml look alike)
  • Every detector responsible for its own
    documentation
  • Collected on a single WWW page

19
http//AliSoft.cern.ch/offline
20
Documentation
  • Root builds html documentation (to be improved)
  • Root does reverse engeenering (uml look alike)
  • Every detector responsible for its own
    documentation
  • Collected on a single WWW page
Write a Comment
User Comments (0)
About PowerShow.com