Problem 723 - Severe problem with G4IntersectionSolid
Summary: Severe problem with G4IntersectionSolid
Status: RESOLVED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: geometry/solids (show other problems)
Version: 6.2
Hardware: PC Linux
: P1 critical
Assignee: Vladimir.Grichine
URL: http://agata.pd.infn.it/documents/sim...
Depends on:
Blocks:
 
Reported: 2005-02-14 07:33 CET by farnea
Modified: 2005-02-22 03:21 CET (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this problem.
Description farnea 2005-02-14 07:33:05 CET 
I noticed that, defining the same shape in different ways, the results depend
strongly on the
specific implementation of the geometry. What is most worrying is that, in the
case of
G4IntersectionSolid, the results depend on the order with which the intersection is
performed (solid A intersecated solid B gives a different result than solid B
intersecated
solid A). I wrote a small program to show this effect, which I placed in:

http://agata.pd.infn.it/documents/simulations/data/bugIntersection.tgz

In the package you will also find a modified version of G4IntersectionSolid
which should
solve this problem. This should work also for geant4.7.0
Comment 1 Vladimir.Grichine 2005-02-22 03:21:59 CET 
The algorithm proposed by Dino Bazzacco <dino.bazzacco@pd.infn.it>
was tested and accepted for G4IntersectionSolid::DistanceToIn(p,v).