Message: Re: Infinite Loop in G4SubtractionSolid::DistanceToIn() Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

More Re: Infinite Loop in G4SubtractionSolid::DistanceToIn() 

Forum: Geometry
Re: Question Infinite Loop in G4SubtractionSolid::DistanceToIn() (Stefan E. Mueller)
Re: None Re: Infinite Loop in G4SubtractionSolid::DistanceToIn() (Makoto Asai)
Date: 09 Sep, 2014
From: Stefan E. Mueller <Stefan E. Mueller>

Hello,

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,

Stefan

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:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 None: Re: Infinite Loop in G4SubtractionSolid::DistanceToIn()   (Makoto Asai - 09 Sep, 2014)
1 More: Re: Infinite Loop in G4SubtractionSolid::DistanceToIn()   (Stefan E. Mueller - 10 Sep, 2014)
1 More: Re: Infinite Loop in G4SubtractionSolid::DistanceToIn()   (Stefan E. Mueller - 11 Sep, 2014)
2 None: Re: Infinite Loop in G4SubtractionSolid::DistanceToIn()   (Vladimir Grichine - 17 Jan, 2016)
1 None: Re: Infinite Loop in G4SubtractionSolid::DistanceToIn()   (Vladimir Grichine - 18 Jan, 2016)
 Add Message Add Message
to: "Re: Infinite Loop in G4SubtractionSolid::DistanceToIn()"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews


[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]