|Message: Re: What is that? "Warning ... PCone not able to return normal .."||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)|
From your comments I am unclear as to whether the second call to get the surface normal, the one which generates the warning, happens immediately after the first call, or when the photon encounters the surface again some distance away.
Upon reflection of a photon on any surface, a tiny step is taken by the G4Navigator. This is a quirk of GEANT4 but the G4OpBoundaryProcess is written with this in mind. Therefore, you'll find this line in the PostStepDoIt:
if (aTrack.GetStepLength()<=kCarTolerance/2) return G4VDiscreteProcess::PostStepDoIt(aTrack, aStep);
With other words, the DoIt should return and not spring back into action, at the end of this tiny intermediate step. If for some reason, this tiny step ends up to be larger than kCalTolerance/2 for the case of a G4BREPSolidPCone, then we've got a problem. I would think though that the problem would be more severe than just warning messages filling the screen.
If you were to print: aTrack.GetStepLength() in your version of the G4OpBoundaryProcess.cc code it would be interesting to see what step sizes are between calls to
theLocalNormal = theNavigator->GetLocalExitNormal(&valid);
|Inline Depth:||Outline Depth:||Add message:|