|Message: Warning: theListOfSecondaries() is not empty||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'm running a Geant4 simulation of a 100 TeV muon passing through a very large volume of water (10m x 10m x 1km, for now.) I'm interested in accumulating all electrons and positrons passing every meter of a 100m sensitive region after the 1km.
The program works excellently for low energies- up to about 275GeV. At 290 GeV and above, however, it spits out the "Warning: theListOfSecondaries() is not empty" error message, and exits early. It does -not- segfault. It prints out all the information I request and exits cleanly otherwise, with the exception of that error message.
The issue is that I'm saving all secondary tracks for the purposes of plotting the distribution of electrons, and when this error message begins to appear, the number of tracks drops steeply. The 275GeV file was about twice the size of the 290 GeV file- 198k versus 97k This may simply be a statistical fluctuation- I was going to repeat with a larger number of statistics/etc, but I'm running it at a computing center which is currently offline. Yet more confusing, despite the fact that Geant doesn't seem to be printing -all- of the secondary tracks or counting them in the 100m-layer region, it doesn't have a problem printing -more- tracks. When I attempted the 100TeV simulation, it created a 26 gigabyte file. The number of secondaries in the 100TeV case is also too low, which is what lead me to find the 275/290 cutoff.
My current intuitions regarding the structure of Geant lead me to believe that there's some limitation on the maximum number of allowed secondaries created by a physics process, but I can't figure out where it might be, or how to disable it.
Any commentary or direction would be appreciated at this point.
|Inline Depth:||Outline Depth:||Add message:|