Page History

...

• Three levels of API?
  • Low level (equivalent to Geant4 geometry objects)
    • Initially dumb objects, sufficient to create Geant4 geometry
  • Medium level (similar to GEAR::Vertex::API)
  • High level (allows finding which detectors exist)
• have collection of driver classes
  • one subdetector level
  • gcj comliant Java ( to be called from C++/Marlin)
  • read in 'free format' from parameters from xml elements
    • should probably be similar to compact/gear
• create "queue" of geometry instructions
  • logical volumes
  • physical volumes
  • placements
  • material
  • etc
• have converters that go through queue of instructions adn create
  • G4Detector
  • HepRep
  • GDML / LCDD

points to cover

• GEAR++ interface deifinition (mediun level)
  • tracking (and clustering PFA)

• • • average material volumes
    • intersection with 'next' volume
    • dE/dx

• • • field maps

• • volumes ?
  • extensions of detectors ( a la gear)
    • e.g. #layers, thickness, width,...

• material database
• field maps
• properties (sampling fractions)dE/dX
• readout properties
  • cellId <-> position
  • cellid range (noise simulation)
  • cell sizes
  • neighbors