... | ... | @@ -36,3 +36,7 @@ This is an as detailed as possible outline of the requirement list for physics p |
|
|
1. processes lists are ordered. They are executed in the order of appearance in the code.
|
|
|
|
|
|
1. in particular thinking about point 6.4.1/2 we have to either further break down the interface, or we define a way to let "SecondariesProcesses" act only in specific cases. Consider a ```thinning``` SecondariesProcess, which should act on the output of ```collisons``` but *not* on the output of ```decays``` etc. Thus, logically we would like to distinguish ```interaction << decay << thinning``` from ```(interaction << thinning) << decay```
|
|
|
|
|
|
Notes from HD:
|
|
|
- Thinning should be handled by a process, not by the sequence. A ThinnedInteractionProcess would derive from the generic InteractionProcess and apply thinning to its output. For the ProcessSequence this is transparent.
|
|
|
- Interactions and Decays are very similar and called by the ProcessSequence in essentially the same way. This common aspect of the two classes should be factored into a base. |
|
|
\ No newline at end of file |