4th Concept Software Status Report

1
4th Concept Software Status Report
2
ILCroot a summary of features

• CERN architecture (based on Alices Aliroot)
• Full support provided by Brun, Carminati,
  Ferrari, et al.
• Uses ROOT as infrastructure
• All ROOT tools are available (I/O, graphics,
  PROOF, data structure, etc)
• Extremely large community of users/developers
• Four MDC have proven robustness, and reliability
  and portability

3
Event Generators
4
The Virtual Montecarlo Concept

• Virtual MC provides a virtual interface to Monte
  Carlo
• It decouples the dependence of a user code on a
  concrete MC
• It allows to run the same user application with
  all supported Monte Carlo programs
• The concrete Monte Carlo (Geant3, Geant4, Fluka)
  is selected and loaded at run time

5
VMC Advantages

• It allows the comparison between Geant3 Geant4
  and Fluka using the same geometry and data
  structure (QA)
• You can generate and simulate different events
  with different MCs and merge the digits
• Example
• Geant4 for signal event
• Fluka for beam background

digitization
6
TGenerator Concept

• TGenerator is an abstract base class
• It interfaces ROOT and the various event
  generators (thanks to inheritance)
• Possible to study
• Full events (event by event)
• Single processes
• Mixture of both (Cocktail events)
• Generation of Cocktail of different processes
• Rate and weighting control
• Allow easy mixing of signal and background
• More than a dozen Generators built-in

7
ILCroot Strategy Modularity

• ILCroot Building Block The Detector Class
• Detector-centric approach (vs Processor-centric)
• Main policy each detector is responsible for its
  code data
• Cross-modules calls are not allowed

• Easy to work for groups across many countries
• Allow for several versions of the same detector
  or several detector of the same kind (ex. TPC
  DCH)

8
The Detector Class

• Both sensitive modules (detectors) and
  non-sensitive ones are described by this base
  class.
• This class must support
• Geometry description
• Event display
• Simulation by the MC
• Digitization
• Pattern recognition
• Local reconstruction
• Local PiD
• Calibration
• QA
• Data from the above tasks
• Several versions of the same detector are
  possible (choose at run time)

9
Coordinating the Detectors

• Detector stand alone (Detector Objects)
• Each detector executes a list of detector
  actions/tasks
• On demand actions are possible but not the
  default
• Detector level trigger, simulation and
  reconstruction are implemented as clients of the
  detector classes
• Detectors collaborate (Global Objects)
• One or more Global objects execute a list of
  actions involving objects from several detectors
• Data are exchanged using a whiteboard techinque
• The Run Manager
• executes the detector objects in the order of the
  list
• Global trigger, simulation and reconstruction are
  special services controlled by the Run Manager
  class
• The Offline configuration is built at run time by
  executing a ROOT macro

10
Software Status

• Bangalore version of ILCroot frozen (and
  dismissed)
• Most of the algorithms are OK
• Too much hard-coding in the reconstruction
• Only DREAM and EMCAL geometry are 4th Concepts
  realistic
• Calorimeter response has some troubles
• Stable version OK for training

11
Status of ILCroot Framework

• Framework upgraded to last CERN version
  (4.04.rev.06, Aug. 2006)
• Fluka, Geant3 and Geant4 interface work smoothly
  (special derogation obtained for Fluka from CERN)
  (V. Di Benedetto)
• GDML interface added (thanks to R. Brun)

12
Status of ILCroot TPC (F. Ignatov)

• New TPC for DCR implemented
• All passive materials from Alice (walls, support,
  electronics, cable, cage, etc.)
• Gas Ar-CF4 97-3 (from M. Ronan, V. Lepeltier)
• Readout
• 5 layers of Micromegas (from. P. Colas)
• 2 chip/layer -gt 512 pixels
• 55 mm pitch
• 150 layer of pads
• Pad Inner  Width 0.23 cm   Length 0.42 cm
• Pad Outer1 Width 0.34 cm   Length 0.56 cm
• Pad Outer2 Width 0.34 cm   Length 0.85 cm
• All the gas-related Physics is simulated
  (diffusion, finite pad size, noise, etc.).
  Electronics is not.

13
Status of ILCroot DREAM (V. Di Benedetto)

• Geometry completed. (including Endcaps). Two
  versions available 1 m and 1.5 m
• Easily switch from Cu to W (however, need to
  change calibration values of hS and hC)
• 2 months spent with CERN people trying to fix
  G3/G4/Fluka issues.
• Fluka seems working fine. We will be using it for
  Valencia and DCR.
• First studies will be out next week (after
  calibration processes are completed)

14
Status of ILCroot Muon Spectrometer (E. Cavallo,
G. Terracciano)

• DoD geometry is completed
• ESAs CAD2GDML converter not ready -gt positioning
  tubes using TGeo (root)
• Hits Event Display will be ready for Valencia
• Full tracking (with hits smearing) hopefully
  ready for final DCR studies (Jan. 2007?)

15
Status of ILCroot Tracking (F. Ignatov)

• New code with maximum parametrization
• However, still depends on layout (planar vs
  circular layer)
• VXD being incorporated (need to adjust for the
  materials in the new SiDmay06 version)
• Barrel only for Valencia. Endcap will be included
  for the DCR studies

16
More Issues

• VXD
• See Annas talk
• PID
• Only in the DREAM module
• Magnetic Field
• New B-field maps for extended DREAM (E. Cavallo)
• Will add SiD map for our cooperative studies (M.
  Demarteau)
• Generators and Physics Studies
• See Annas talk
• Background Studies
• Bob Kutschke Daniele Barbareschi

17
Conclusions

• Work is proceeding quickly
• Many thanks to Marcel for his large support
• Good collaboration with FNAL being established
• We are planning to strenghten that next year

18
Backup slides
19
Processing Flow
20
LCIO vs MONARC
MC Generation ? Energy Deposits in Detector
MC Generation ? Energy Deposits in Detector
SDigitization ? Detector response from single
particle
Digitization ? Tracker Hits
Digitization ? Detector response combined
Pattern Recognition ? Recpoints
Track Finding ? Tracks
Track Finding ? Tracks
Track Fitting ? Track Parameters
Track Fitting ? Track Parameters