Difference between revisions of "MOLLERsim application coding guidelines"
From Hall A Wiki
(→General) |
(→General) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
# guarantee that it works on the farm | # guarantee that it works on the farm | ||
## use "central" GEANT4 installation | ## use "central" GEANT4 installation | ||
| − | ### | + | ### Visualization - we will use Qt |
| − | ### We | + | ### We will use cmake |
## if someone gets it working on other platforms, may offer support | ## if someone gets it working on other platforms, may offer support | ||
# when you make a change, you need to make sure that it works! | # when you make a change, you need to make sure that it works! | ||
Latest revision as of 12:04, 10 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
- Visualization - we will use Qt
- We will use cmake
- 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.)
