This project is mirrored from https://gitlab.cern.ch/VecGeom/VecGeom. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
  1. 16 Jun, 2021 2 commits
  2. 08 Jun, 2021 1 commit
  3. 04 Jun, 2021 1 commit
  4. 01 Jun, 2021 1 commit
  5. 31 May, 2021 7 commits
  6. 27 May, 2021 1 commit
  7. 20 May, 2021 16 commits
  8. 18 May, 2021 1 commit
  9. 17 May, 2021 1 commit
    • Raman Sehgal's avatar
      VECGEOM-571; Fixes FPE related issues, happening when the normal is not a valid · 1e28f077
      Raman Sehgal authored
                   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
      1e28f077
  10. 14 May, 2021 1 commit
  11. 11 May, 2021 1 commit
  12. 10 May, 2021 1 commit
  13. 07 May, 2021 2 commits
  14. 06 May, 2021 1 commit
  15. 05 May, 2021 1 commit
  16. 30 Apr, 2021 2 commits
    • Benjamin Morgan's avatar
      Add GeoManager member functions to lookup logical volume id<->name · 243eeaba
      Benjamin Morgan authored
      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.
      243eeaba
    • Benjamin Morgan's avatar
      Expose GDML user and volume auxiliary data · effabf7b
      Benjamin Morgan authored
      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
      effabf7b