|Message: Re: G4Exception : GeomNav1002||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)|
I have suffered from same error, but I found that the G4Exception:GeomNav1002 disappered when I used other parameterisations in http://geant4.web.cern.ch/geant4/UserDocumentation/Doxygen/examples_doc/html/ExampleDICOM.html .
I tried to use the nested parameterisation and 3D optimization with G4SmartVoxel(SetRegularStructureId(0)) respectively instead of the default parameterisation and navigation, G4PhantomParameterisation/G4RegularNavigation, and there is no error message of G4Exception:GeomNav1002.
In my simulation, the nested parameterisation was much faster( a few thousands times) than 3D optimization.
I hope this will be helpful.
On Mon, 13 Feb 2017 06:39:15 GMT, elnaz yazd wrote:
> Dear Sir/Madam > > I am running DICOM example with data from CT for head. The geometry is > 110 layer with 128x128 voxels for each layer and the dimension of voxels > are (2.01562mm, 2.01562mm, 1mm). The following error is happens with > some initial seed numbers and program hangs in this format. As it is > clear the problem happens in the voxel around the origin of local point. > Please help me to get ride of this problem. > > Track stuck or not moving. > Track stuck, not moving for 10 steps > in volume -phantom- at point (1.17148,-1.36137e-10,-170) (local point (0.163671,1.00781,-0.5)) > direction: (0.0296006,4.86496e-05,0.999562) (local direction: (0.0296006,4.86496e-05,0.999562)). > Potential geometry or navigation problem ! > Trying pushing it of 1e-07 mm ...Potential overlap in geometry! > > *** This is just a warning message. *** -------- WWWW -------- > G4Exception-END --------- WWWW ------- > > With Best Regards, Yazdan >