Rethink detector configurables
The following discussion from !912 (merged) should be addressed:
-
@mimazure started a discussion: Currently each sub-detector represents a separate configurable. The properties can be set either using the standard
getProp
fromConfigurableUser
or via the use of decorators (subdetector
). For me it is misleading, and the use ofConfigurableUser
for sub-detectors should be dropped as we are, in fact, not using the properties and the order of the configurables is difficult to follow. A simple class should be enough configured fromGaussGeometry
.