Currently we describe the entire detector geometry used in simulation and reconstruction in Mu2eG4/geom. This breaks the design intent that GeometryService be agnostic, since we can't run reconstruction without Mu2eG4 (and its Geant4 dependency) in the release/path. A truly agnostic solution requires putting base geometry and material definitions in a neutral package. With that, a pure reconstruction release could omit Mu2eG4 and its dependencies. That location would then be a natural place then to put this KinKal material config.
Currently we describe the entire detector geometry used in simulation and reconstruction in Mu2eG4/geom. This breaks the design intent that GeometryService be agnostic, since we can't run reconstruction without Mu2eG4 (and its Geant4 dependency) in the release/path. A truly agnostic solution requires putting base geometry and material definitions in a neutral package. With that, a pure reconstruction release could omit Mu2eG4 and its dependencies. That location would then be a natural place then to put this KinKal material config.