|Message: Re: Disable G4Navigator Overlap Check||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)|
Hi Anders, with version 10.2.p01 you can have the check automatically disabled if you install Geant4 in no-verbose mode (i.e. GEANT4_BUILD_VERBOSE_CODE=OFF in your CMake configuration). Cheers, Gabriele -------------- On Tue, 12 Apr 2016 12:03:54 GMT, herr_apa wrote: > Hi, > > I hope this is the right forum for this request. > > In G4Navigator.cc, there is a check for what to do when a particle takes > a step with zero length. After a certain number of zero-length steps (10 > by default) the particle is pushed some distance. After even more > zero-length steps (25 by default), the track is killed. When G4Navigator > kills a track, it also checks the current volume for overlaps. I would > like to have the option to disable this check. > > I'm currently working with a geometry that contains a very large > (several million) number of elements. The geometry is "flat", so they > all have the same mother volume. If a simulation has bad luck and gets a > few killed tracks, the time spent in G4PVPlacement::CheckOverlaps can > easily be 50% of the overall simulation time. There are no overlaps in > the geometry (the check always returns false), so choosing not to do the > check seems to be the way forward. > > Thanks! > > // Anders