Problem 635

Summary:	Bug in cone definition in OLAP tool
Product:	Examples/Extended	Reporter:	Alexandre.Bagoulia
Component:	geometry/olap	Assignee:	Gabriele Cosmo <Gabriele.Cosmo>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	P2
Version:	6.1
Hardware:	All
OS:	Linux

Description Alexandre.Bagoulia 2004-06-17 08:10:50 CEST

We wanted to use examples/extended/geometry/olap for check of the geometry and
have found
out in our opinion a bug in the description of a cone.
In the file SolidAnalyser.cc in function "G4int SolidAnalyser::GetParam" The
sequence of parameters coincides with how it is made in the description of a
cone in the GEANT4 documentation, but differs from sequence of parameters in
definition of a cone.
The same story is with Momo(GGE) package. If we append Cone segment and try to
set its parameters (InnerRadiusAt-dz,InnerRadiusAt+dz, etc.) ant then press
button "View", we shall not see anything similar to a cone. But if we shall not
pay attention to names of columns, and in them we shall fill in sequence, as in
definition of a cone (InnerRadiusAt-dz,OuterRadiusAt-dz,
InnerRadiusAt+dz,OuterRadiusAt+dz) we shall receive the image of a cone.

Comment 1 Gabriele Cosmo 2004-06-28 02:54:59 CEST

For conveninence, the issue has been resolved and the update to the OLAP tool
will be included in the next development tag of the source code.
To be noticed however, that it is NOT guaranteed that the order of storage of
the internal parameters in the tool strictly follows the interface for the solid
construction. This is valid for the 'cone' AND for any other solid supported by
the tool. Solids may have different constructors and different parameters or
specifications by which they can be generated, which are not necessarily
covered by representations in the tools.