|Message: 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)|
I've been working on producing a simulation of spontaneous fission based on the Livermore fission model built on top of the B4d example structure.
The simulation works as expected, however, when filling the ntuple to analyse the output using root I find that I am getting only a sample of the total data. It appears that the ntuple is being filled only once per fission event, rather than per particle/gamma. For my simulation of 10,000 fissions I should expect (and indeed see when reading out the neutron/gamma emission) ~37k neutrons and ~82k gammas, but each leaf has exactly 10,000 entries.
I believe the problem is caused by my implementation of the AddNtupleRow() method, as the B4d example includes this in the EventAction class file (thus explaining the "once per event" issue). The issue arises where my primary neutrons and gammas are built within separate loops determined by n/g multiplicity generated by the fission. Including AddNtupleRow at this point allows the extraction of particle energy etc. as desired, but introduces a multiple count when including the method in each loop. I also wish to extract hit data, which is called in my EventAction class (again, only occurs once per event at present).
I wonder whether the analysis from B4d is not sophisticated enough to fill different sized leaves? In which case is there a more complete/developed example that could be cannibalised? Any help/suggestions would be greatly appreciated.
|Inline Depth:||Outline Depth:||Add message:|