|Message: Re: Infinite Loop in G4SubtractionSolid::DistanceToIn()||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)|
for the random seeds I have tried, the error message appears after several 1000 events, sometimes already after 1000 events, sometimes it takes more events till the "problematic" track configuration is reached.
As proposed, I activated G4ScoringManager in my main, and commented all /score-commands in my macro. I tried 2 jobs with seeds that produced the error message before (reproducibly). Now one of the jobs runs through 10000 events apparently without problem, the other however still produces the error.
All my runs are identical in geometry and physics. In principle, only the random seed changes (via /random/setSeeds from UI, (this had a bug: http://bugzilla-geant4.kek.jp/show_bug.cgi?id=1657, but I have a patch that should fix it)).
Strange thing is that simply activating the G4ScoringManager changes the results. I did not expect the scoring to have an influence on the track histories for identical seeds, but apparently, it has.
The conclusion is that commenting the /score-commands in the macro doesn't help (always) to get rid of the error.
I will try to do more checks,
PS: I tried the two jobs in my MacBook, and they ran through 10 000 events without error message. But I noticed that same random seeds produce different event histories on our computing cluster (UBUNTU) and my Mac with OS X 10.9. Maybe I simply was lucky on the Mac!
On Mon, 08 Sep 2014 14:56:28 GMT, Makoto Asai wrote:
> Hello, > > Could you explain a bit more on how you encountered to this infinite > loop? > When did it happen? Was it the first step, first track, first event, > and/or first run? You can check it by specifying proper verbosity. > > If it was not in the first run but in the second run, did you do > something special, e.g. changing geometry? > > To illustrate the issue more clearly, could you please try the > following? > - Access to G4ScoringManager in your main(), but > - Comment out all UI commands for scoring. > Do you still see the infinite loop? > > Thanks, > Makoto >
|Inline Depth:||Outline Depth:||Add message:|