|Message: G4Transportation is killing track...||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)|
using a user magnetic field profile, I frequently get the following message: "G4Transportation is killing track that is looping or stuck" (roughly in 10% cases for 1MeV electrons and 9T central field).
- First of all, can one explain a bit more, what can be a reason of such "looping etc"?
- Secondly, what exactly happens to this tracks? is the whole event killed or only at certain point this event is stopped?
I want to understand it because if, for instance, one needs to estimate the efficiency, how to interpret these type of events?
For example, I have 100 initial events, 15 of them are registred in a detector but for 10 I get above mentioned error message, so is the efficiency of registration 15 over 100 or over (100 - 10) = 90 or something else?
P.S. Is there any ability to "mark" such cases in order to "look them back" in stored data file?
|Inline Depth:||Outline Depth:||Add message:|