The description of the tracking detector volumes and layers is now moved to an external JSON file instead of being hardcoded to the MuColl_v1 geometry. The format of the JSON file is the same as used by the ACTS TGeo example as the ACTSMCC instructions for generating material maps.
The processors that use the geometry now take a TGeoDescFile attribute with the path to the JSON file. For backwards compatibility, the default is set to the newly included data/MuColl_v1.json.
This does not remove all hardcoded dependence on MuColl_v1 as the mapping tool (GeometryIdMappingTool) still needs to be configurable.
The description of the tracking detector volumes and layers is now moved to an external JSON file instead of being hardcoded to the
MuColl_v1
geometry. The format of the JSON file is the same as used by the ACTS TGeo example as the ACTSMCC instructions for generating material maps.The processors that use the geometry now take a
TGeoDescFile
attribute with the path to the JSON file. For backwards compatibility, the default is set to the newly includeddata/MuColl_v1.json
.This does not remove all hardcoded dependence on
MuColl_v1
as the mapping tool (GeometryIdMappingTool
) still needs to be configurable.