|Message: Re: Ntuple fills per-event instead of per-hit||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Thank you both for your swift replies.
The simulation generates a fission event in the SponFissIsotope class which creates a range of neutron and gamma primaries according to standard multiplicity distributions. I'm presently reading out the number of particles, and then for each primary their initial energies and direction of emission.
I also wish to include the energy deposited by a particle in my sensitive detector, as well as the time since the fission event of that particle. At present this information is recorded by the EventAction in EndOfEventAction(). Regardless of the event multiplicity (0-20 for each n and g) it only ever records a single particle (I varied the size of my detector to maximise solid angle coverage), I assume that this is the last primary dealt with, so if that happens to not hit my detector it obviously returns a 0 for energy deposition.
If I can fill the nTuple through PreUserTrackingAction() that would seem to avoid the once-per-event issue, but then the question becomes whether you can call the hitCollection at that stage too?
|Inline Depth:||Outline Depth:||Add message:|