Transcript Mokka_-_Geometry_Integration - Indico

Mokka and integration of the geometry
AIDA kick-off meeting
WP2 session: Common software tools
17 February 2011 – CERN
Paulo Mora de Freitas and Gabriel Musat
Ecole polytechnique
Mokka
detectors
Mokka
Geometry drivers
Geometry
Database
Paulo Mora de Freitas
2
Mokka’s kernel framework
Geant4
Mokka
Kernel
Geometry
Drivers
Geometry
Database
Paulo Mora de Freitas
3
The detector models in DB
 A model = a set of sub detectors (TPC, Ecal, Hcal, etc.)
 A sub detector = a driver <-> DB association
Paulo Mora de Freitas
4
Mokka, other geometry
features
 “Scaling”, the user is able to modify
the model's main parameters at launch
time
 To easily be able to study different
detector options, like TPC size, number of
layers in calorimeters, etc.
 “Cooking”, the user is able to modify
the model ingredients at launch time
 To easily be able to study different
detector technologies, like analogical
versus digital Hcal, etc.
Paulo Mora de Freitas
5
Scaling
 Example :
/Mokka/init/globalModelParameter TPC_outer_radius 800
Paulo Mora de Freitas
66
Cooking
 Example :
/Mokka/init/EditGeometry/rmSubDetector SHcal01
Paulo Mora de Freitas
7
Parameters in Mokka DB
Parameter values are overwritten by the sub_detector default, then the
model_parameter default, then steering file value if any, and finally by the
environment value if modified at run time by a previous driver.
Scaling follow the model build_order in ingredients
Paulo Mora de Freitas
8
Geometry has to be shared
Generator
Detailed
simulation
Need to share the
same geometry !!!
Reconstruction
Analysis
And nobody never tried to retrieve geometrical information via
SQL queries, except in the geometry drivers in MOKKA !!!
Paulo Mora de Freitas
9
Mokka - Common Geometry
Access API (F77, C++,C, Java)
Simulation
(Mokka)
Geometry
Database

Reconstruction
(user code)
Analysis
(user code)
CGA Extension
CGA API
Geometry drivers
Implements some reconstruction utilities.
Gabriel Musat L.L.R. – Ecole polytechnique
About CGA
 Good features in CGA:
 Provides a full consistent geometry system for
simulation, reconstruction and analyses.
 Provides a scan mechanism to explore the
detector geometry and material proprieties
(geantino tracking)
 But…
 Links against Geant4 libraries
 Exports only low level geometry (G4 volumes
level)
 a few users only
 Available with Mokka since 2004, anyway
Paulo Mora de Freitas
11
ILD Current framework
LCIO Persistency Framework
MARLIN
Generator
Geometry
Database
MOKKA
Simulation
Reconstruction
Java, C++, Fortran
Analysis
GEAR
Geometry API for Reconstruction
Paulo Mora de Freitas
12
Improvements from GearCGA
 Usual GEAR properties (detector parameters)
now available without having to previously
run Mokka to generate the GEAR file
 together with the Point+Distance Properties
 information is now supplied by the CGA
interface
 the libraries belonging to Mokka, Geant4,
CLHEP, MySQL, GEAR, LCIO are put together in
one library after linking Mokka
Gabriel Musat L.L.R. – Ecole polytechnique
13
GearCGA
Simulation
(Mokka)
Reconstruction
(user code)
GEAR
GearCGA
GearXML GearTGeo
CGA Extension
CGA API
Geometry
Database
Geometry drivers
Gabriel Musat L.L.R. – Ecole polytechnique
Towards a new geometry tool
• MOKKA history rises a set of user’s
requirements for the Geometry
Toolkit
• To be generic, flexible and friendly for
the final user, etc.
• To adopt a CAD graphic interface:
• No more script language neither XML
edited by hand
• See http://www.opencascade.org
Paulo Mora de Freitas
15
Towards a new geometry tool
• Abstraction levels for the detector geometry:
• To cope with the different views for simulation,
reconstruction, analysis, event displays…
• To use metadata to describe the abstraction
levels, to keep the tool as generic as possible
• To provide a Data Manipulation Language (DML)?
• To define an abstract API (C++, Java, etc.)
• To provide at least one implementation for this
API
• To provide at least one simulation/ reconstruction
/ event display chain compliant with it.
Paulo Mora de Freitas
16