Difference between revisions of "Thursday, July 12, 2012"
From Hall A Wiki
(→Kernel II) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
=== Scoring II === | === Scoring II === | ||
| + | * don't do heavy string manipulations in Hits (sin, cos, etc) because done event by event | ||
| + | * don't get information from track, but from preStepPoint | ||
| + | * postStepPOint should only be used to get position? | ||
| + | ** for example, if you need mid-point of step, can combine pre- and post- positions | ||
| + | ** still would need history to get the local position... | ||
| + | ** all other info should come from preStepPoint? (Slides seem to indicate the oposite thing) | ||
| − | |||
| − | |||
<br> | <br> | ||
=== User Documents and Examples II === | === User Documents and Examples II === | ||
| − | * | + | :: not much is said that is not on the slides |
| − | * | + | * each topic has one or more examples |
| + | * should start from an example that does something like what you want | ||
<br> | <br> | ||
=== Kernel II === | === Kernel II === | ||
| − | * | + | * to compare G4 to other simulations, may want to implement fMinEkine |
| − | * | + | * not a good list of classes which you shouldn't sub-class |
| + | ** if a class has an allocator, shouldn't sub-class it | ||
| + | * Examples/extended/runAndEvent/RE01: SourceTrackID <-- can remember | ||
| + | * avoid string manipulation whenever possible | ||
| + | * user stacking action - can change how things are handled | ||
| + | * once urgent stack is empty, then waiting stack moved to urgent, can have new stacking action | ||
| + | * only continue to track events of interest - checking that 4 muons were in that event, and then that they deposit enough energy, etc. so you don't waste time tracking events that don't matter | ||
<br> | <br> | ||
Latest revision as of 15:31, 12 July 2012
Contents
Morning Talks
Scoring II
- don't do heavy string manipulations in Hits (sin, cos, etc) because done event by event
- don't get information from track, but from preStepPoint
- postStepPOint should only be used to get position?
- for example, if you need mid-point of step, can combine pre- and post- positions
- still would need history to get the local position...
- all other info should come from preStepPoint? (Slides seem to indicate the oposite thing)
User Documents and Examples II
- not much is said that is not on the slides
- each topic has one or more examples
- should start from an example that does something like what you want
Kernel II
- to compare G4 to other simulations, may want to implement fMinEkine
- not a good list of classes which you shouldn't sub-class
- if a class has an allocator, shouldn't sub-class it
- Examples/extended/runAndEvent/RE01: SourceTrackID <-- can remember
- avoid string manipulation whenever possible
- user stacking action - can change how things are handled
- once urgent stack is empty, then waiting stack moved to urgent, can have new stacking action
- only continue to track events of interest - checking that 4 muons were in that event, and then that they deposit enough energy, etc. so you don't waste time tracking events that don't matter
Hands-on IV
Afternoon Talks
Geometry IV
Event Biasing
Hands-on V
Return to JLAB GEANT4 Workshop, July 9-13, 2012
Return to MOLLER GEANT4 Simulations
Return to MOLLER at 11 GeV E09-005
