Benjamin Morgan authored Jan 22, 2021 and Andrei Gheata committed May 20, 2021

CMake prior to 3.10 did not fully know C++ compile features for
the Intel compiler. VecGeom currently supports 3.8 and newer.

Add a module to set known compile features for newer Intel compilers
when CMake 3.10 or earlier is used. remove custom setting of -std
flag in VECGEOM_CXX_FLAGS.

Benjamin Morgan authored Mar 12, 2021 and Andrei Gheata committed May 20, 2021

GNU/Intel use the same flag, Clang has the same concept just a different
name

             normal. Also contains a bug fix happening for the cone when rmin==rmax

             Cone generally calls all the functions of ConeStruct.
             But for Normal Calculation, there is a redundant definition of
             Normal in UnplacedCone and in ConeStruct, which is actually not
             required and cone can safely call Normal of ConeStruct.

             Now Cone calls the Normal of ConeStruct.

             NOTE : CONE STILL DOESN'T HAVE A VECTORIZED DEFINITION OF NORMAL

Benjamin Morgan authored May 04, 2021 and Andrei Gheata committed May 06, 2021

Reinstate original `bool Frontend::Load` function to ensure
compatibility for older clients.

Implement trivial `Parser` struct with `Load` member function returning
the Middleware unique_ptr and same signature as free Load function.

The BVH (bounding volume hierarchy) is a common data structure in
computer graphics and ray tracing. This commit adds a BVH class to
VecGeom, as well as auxiliary classes required to provide navigation
functionality using the BVH.

Updates to VGDML showed need to easily lookup LogicalVolume Ids (int)
from names (string) and vice versa. Whilst current interfaces allow
retrieval of LogicalVolume pointers, manual use/checks are then
needed to get the Id/Name leading to repeated code.

Provide new member functions to return the Id(Name) of a LogicalVolume
given a Name(Id). Implement basic tests of expected behaviour.

The GDML schema provides for arbitrary data to be attached to <volume>
elements and the <userinfo> element through 0-N <auxiliary> tags. This
tag can itself can hold 0-N child <auxiliary> tags, thereby modeling a
tree structure. This structure, and the values of the attributes of
the tag attributes are left up to the client.

Process and expose any volume and userinfo data in an input GDML file
through vgdml's Middleware interface. Provide a class modelling the
<auxillary> tag/tree structure, with interfaces in Middleware to
expose:

- A map between VecGeom logical volume ids (int) holding auxiliary data
  and the list of the held auxiliary tags
- A list of auxiliary tags in the <userinfo> element, if any.

Implement basic tests of Auxiliary class and correct extraction of data
from GDML by Middleware

[VECGEOM-572] vgdml::Frontend::Load returns now the Middleware pointer exposing material and region info.

The commit closes VECGEOM-572, exposing internal maps stored in the Middleware class after calling Frontend::Load with a GDML file. An example ReadMiddlewareData was provided to demonstrate in detail the usage of these maps.

Eg. extend the host/device forward decl.

Evgueni Tcherniaev authored Feb 25, 2021 and Gabriele Cosmo committed Feb 25, 2021

Transform -> InverseTransform in PlacedVolume.cpp; UnplacedContains -> Contains in VolumeUtilities.h

This hardware is now discontinued and no longer supported by Intel.
Clients of VecGeom requiring support should use the previous tag
or earlier.

Setting the millimeter value is a property dependent of the geometry conversion method, so it is more appropriate to pass it as parameter to vgdml::Frontend::Load and only record it statically in GeoManager. Other conversion methods to be done in the same way.

GeoManager statically holds now the value corresponding to 1 mm (0.1 by default, i.e. cm is the default unit). This can be changed using vecgeom::GeoManager::SetMillimeterUnit() **before** invoking vgdml::Frontend::Load to change the internal unit.