|Message: Re: Geant4 randomly stops mid-simulation (during batch run)||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)|
On Wed, 12 Sep 2018 13:13:50 GMT, David Hodge wrote:
> Not super hopeful on this one, but I thought I'd ask to see if anyone > had had similar experiences. > > I'm performing a batch run of a number of different simulations using a > macro to slightly vary the GPS parameters for each run. It works great > until a random point somewhere in the first 20 /run/beamOn events, then > the terminal freezes and will not unfreeze for love nor money. > > It *appears* that the simulation crashes while calling a modified > EventAction class, but for the life of me I can't seem to figure out > why, especially since the exact same class has worked perfectly for > literally hundreds of stand alone runs. Anybody ever seen this before? > Know any work arounds?
What kind of system are you running on? Do you have a way to monitor the memory usage of the process while it is running? On my MacOSX, if I have a memory leak, the memory usage can go up to occupy the full physical memory, and everything hangs until I can manage to kill the process.
If you have |valgrind| on your system, you can use it to run a relatively short job (maybe even just a few tens of events) and see if there are per-event leaks in your code.
You might also consider adding (temporarily!) some sort of informational output in that EventAction; perhaps some computation is falling into a NaN hole or some such thing.
-- Michael Kelsey