|Message: Re: Simulation hang up||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)|
In the MT mode, to minimize the communication traffic between the master thread and the worker threads, not individual events but bunch of events are tasked to each worker thread. For your case, given you are running as much as 10^8 events, by default a bunch contains about 10^4 events. Thus, once your run comes to the end, some threads have finished their assigned events while some others might have almost full bunch of 10^4 events. This could explain why you saw some threads became quiet at the end of the run. You may want to try the following UI command to see if it gives any difference.
/run/eventModulo NNN 1
where NNN means the size of the bunch (number of events tasked at one time). Please do not make NNN too small, as it would affect to the performance seriously. The second argument "1" should give you much better performance for an application with many events with relatively low-energy primary particles, though this option would not guarantee event-by-event reproducibility.
I note here that what I discuss here does not explain the occasional crash you saw at the end of run, and it might be some other reason for this.
Hope this helps,
|Inline Depth:||Outline Depth:||Add message:|