simultaneous use of auxdetgeometry service with geometry service
We need to access AuxDetGeometryCore via the auxdetgeometry service. At the same time, we need to access GeometryCore via geometry service. My understanding is that the auxdetgeometry service has problems in this use case. What course of action is recommended?
#3 Updated by Gianluca Petrillo 9 months ago
That is because there is a poor-man synchronisation attempt between the two services.
One is a fork of the other, and both attempt to initialise a geometry representation from a GDML file.
Since this happens via ROOT... ça va sans dire. ROOT
gGeoManager (if I remember the name right), and
g stands for "ROOT loves g lobal state".
There was also the request at the time (LArIAT, I think) that
AuxDetGeometry service could be loaded without
My dream at the time was to have a
GeometrySource which managed the shared resource, and the other two services would interface with it as needed... never happened.
#6 Updated by Biswaranjan Behera 3 months ago
- Priority changed from Normal to High
Kyle Knoepfel wrote:
Thanks, Gianluca, for the info. Chris, can you send us a FHiCL file, which would load both services according to your desired use case? That will help us explore the entanglements and pursue a solution to any problems that arise.
Sorry for the delay on replying back.
I have added these line in order to use AuxdetGeometry.
- CRT Auxiliary detector service configuration
- geometry configuration bundle
} # icarus_crt_channelmapping_services
and my g4.fcl file is located here.
input to this fhicl file is located here: /icarus/app/users/bbehera/work/crt/chmap/gen.root
gdml file can be found in this location:
Please let me know if I could provide more information.
#7 Updated by Gianluca Petrillo 2 months ago
I have taken a quick look at
AuxDetGeometry. It seems that the functionality carried by it is not overwhelming...
I can imagine the possibility of transferring it into
In fact, only two channel mapping methods (
PositionToAuxDetChannel()) are unique to