Topics for DD4hep meeting 04.09.13
--------------------------------------------
- How can we improve the Documentation ?
- Introduction/Overview ( a few pages)
- describe basic design and concepts
[-> talks prepared by Markus ]
- could be added to Doxygen mainpage
- some simple code snippets with key "use cases"
- volumes, materials and placements
- how to add user extensions
- how to navigate in and between - geometry hierarchy objects:
Volumes, PlacedVolumes, DetectorElements,
SensitveDetectors
TGeoVolumes,.....
G4Volumes,.....
- add and use user extensions
(Question: can we also add generic extension classes (e.g. w/ default c'tor) ?)
[-> most exist already in existing examples and implementation
code - just need to collect and clean-up ]
- Doxygen documentation seems somewhat erratic:
- multiple inheritance relations shown for the same class
- too many namespaces shown, e.g. DetElement,...
- Improvements to the cmake build system:
- need to create DD4hepConfig.cmake
in order to allow to build against DD4hep with
FIND_PACKAGE( DD4hep )
- general clean-up of package and build structure:
- building examples on request
- specifying (optional) external dependencies (LCIO, GEAR,...)
- can we get rid of the ". thisdd4hep.sh " between cmake and make ?
- can we introduce a save way of dealing with units
(geant4 and TGeo have different default units, e.g. mm vs cm) ?
-> would like to write code, like:
Tube t = DetElement(tpcData->innerWall).volume().solid() ;
double inner_r = t->GetRmin() / mm ; // inner radius in mm
- observed issue with ILDExSimu example on SL5/SL6 and ubuntu,
where navigation in geant4 simulation seems to be broken
( in SL problem occurs only w/ -o2 )
-> anyone seen similar problems ?
- through the round: recent activities wrt. DD4hep