Monday, July 9, 2012

Kernel 1

Physics lists models overlap in energy range.
NIM articles about GEANT4.
Use trajectory class instead of track to record trajectories
Use pre-step and post-step for reflection/refraction simulations (knows both materials)
Can use G4VTrajectory class to store all the members you need (see talk on Thursday)
Geometry in G4Track; physics in G4DynamicParticle; "static" properties in G4ParticleDefinition
Tracking and SteppingAction or G4 scoring functionality
Each hard-coded number must be multiplied by its proper unit; to get the number, you must divided by its proper unit.

Have to use cmake if you are installing GEANT4 from the source
Novice examples
- N01 - can only compile it an run it; can't change it.
- N02 - parameterized volumes (size is fn. of position); can extract hit info, visualize
- N03 - sampling calorimeter - lAr does detection, replica volumes, different ways to define materials, randomization,

random seed handling, EM physics, visualization tutorial

- N04 - collider detector, Pythia - 3 events, full set of EM and hadronic physics
- N05 - EM or pion showers - G4VFastSimulationModel - parameterize shape of EM shower (pion shower won't work)
- N06 - Optical photons with water cerenkov detector
- N07 - run based rather than event based, 3 sandwich calorimeters, ghost volumes for scoring, change geometry without

re-building world; set cuts

Code Browsers
- LXR - www-geant4.kek.jp/LXR - searchable by filename, identifier, text
- DOxygen version - www-geant4.kek.jp/Reference

some commands don't take parameters, if they do, space is delimiter, ! means default
hard-coded implementation is slow and should NOT be used in an event loop
- ---> requires string manipulations - could become order of magnitude slower
- use to read default macro file in main