Difference between revisions of "Monday, July 9, 2012"

Revision as of 11:46, 9 July 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.

User Documents and Examples I

• 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

• Secondary production cuts!!!

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

• HyperNews forum - hypernews.slac.stanford.edu/HyperNews/geant4/cindex - join!!!

User Interface I

• UI commands - command syntax, macro file, G4UI

• <directory>/<command> <parameters>

• 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

• /control/manual [directory]
• /control/createHTML [directory] - will create a manua for you

• /myCmd/getFile {file1{run}} after creating aliases for file1 and run

• /control/loop - slide 9

• pwd, ls, other commands on slide 11 - can't be used in macro file

Return to JLAB GEANT4 Workshop, July 9-13, 2012
Return to MOLLER GEANT4 Simulations
Return to MOLLER at 11 GeV E09-005