|Message: Re: Help: G4VIntersectionLocator::GetSurfaceNormal Warning||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)|
Dear Evan, The warning is generated when Geant4 is checking if a tracking is entering a volume or not. So it can be relevant or important - but typically it is not critical and the simulation will give the correct answer even if a warning is issued. It is difficult to say with certainty when it might important for your simulation. This is used to avoid a particle bouncing on a surface. So if the simulation progresses, likely it is ok. > > > My questions are: > > 1. Is there a way to "fix" my code such that Geant4 correctly calculates > the surface normal? The only way that this could be avoided would be to implement the solid that has this problem in a different way. > 2. If 1. isn't easily solved, should I even be concerned about this > warning in the first place? Best regards, John Apostolakis P.S. Please mention your institution and the field of your application.