Difference between revisions of "MOLLERsim application coding guidelines"
From Hall A Wiki
(→Geometry) |
(→General) |
||
Line 12: | Line 12: | ||
## on the farm... | ## on the farm... | ||
## with the "approved" environment variables | ## with the "approved" environment variables | ||
+ | ## update your version and make sure your changes work with the latest version before committing | ||
== Geometry == | == Geometry == |
Revision as of 10:22, 4 December 2012
Contents
General
- comment for DOxygen
- use object-oriented code
- use GEANT4 classes - don't reinvent the wheel
- guarantee that it works on the farm
- use "central" GEANT4 installation
- We like OpenInventor?
- We want to be able to use GNUMake?
- if someone gets it working on other platforms, may offer support
- use "central" GEANT4 installation
- when you make a change, you need to make sure that it works!
- on the farm...
- with the "approved" environment variables
- update your version and make sure your changes work with the latest version before committing
Geometry
- use GDML (need to decide about how to do modular geometry)
- hard-code materials?
- parameterize where possible
Generators
Analysis
- Define tracking in correct places (step, event, run, etc.)