CBM Simulation

1
CBM Simulation Analysis FrameworkCoding
Convention
2
(No Transcript)
3
Software distribution

• CBM software distributed via CVS (also geometry
  files)code is tested at GSI on Debian3.0 gcc3.2,
  RedHat9 gcc3.2, Suse9 gcc3.3(tested also for
  RedHat7.3 gcc3.2 at CERN)should run on other
  Linux platforms, but do not use gcc lt 3.2
• External packages (GEANT3, GEANT4, CLHEP,
  CERNLIB, ROOT, PLUTO, PYTHIA, VENUS,
  GEANT4_VMC)binaries provided for Redhat9 and
  SuSe9 from CBM webpageFor other operating
  systems, the packages have to be installed.

4
Conventions (proposal)

• We adopt the ROOT C coding conventions(see
  http//root.cern.ch/root/Conventions.html)
• All class names start with CBM
• One class per file only
• The source file name is ltclassnamegt.cxx, the
  header file name is ltclassnamegt.h
• Every member function should be commented like
  / ltcommentgt / in the header file(so the
  comment can be used in doxygen)
• STL containers are not to be used for data
  storage

5
Software organisation

• Current status ( top level directory
  cbm_vmc/ )
• base/     framework
• cbmgeant4/ framework
• config/  framework configuration
• data/      geometry, materials, field maps
• delta/      Analysis of delta electrons (P.
  Koczon)
• generators/      Event generator interfaces
• itrack/      Tracking (I. Kisel)
• lib/      Shared libraries
• macro/      ROOT macros
• passive/      Passive modules (target, beam
  pipe, magnet)
• rich/     
• sts/     
• tof/      Detector definition
• trd/

6
Modularity

• ConceptDetector modules (sts, trd, rich, tof,
  ecal) contain detector specific implementations
  up to the hit level (MCPoint, Digit, RecoHit)?
  No interdependencies between detector modules!?
  libraries can be loaded independently
• Guideline for further developmentsReduce
  interdependencies as much as possible

7
Geometry implementation

• General considerations Not hardcoded Editable
  (ASCII) files
• "General" description for transport (VMC)
  Position, shape, materials, sensitivity in
  ASCII geometry files (STSgeom.v03a.nml)
• Detailed description for digitisation Granularity
  , readout in parameter files (to be defined)

8
Data levels (reconstruction)
Raw data
Hits
Local tracks
Global tracks
Vertices