You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
DD4hep expects detectors to have a <type_flags> definition in the compact file. This can be used to determine if e.g. an event had any hits in a tracker or to disable or enable all calorimeters (though we don't actively use this in CI or production). In theory, we could use the DetectorSelector mechanism to enable only trackers instead of defining our tracking_only.xml geometry.
However, not every detector sets these flags. Only (some of the) trackers do. This is some of the output of dumpdetector $DETECTOR_PATH/$DETECTOR_CONFIG.xml:
Is your feature request related to a problem? Please describe.
DD4hep expects detectors to have a
<type_flags>
definition in the compact file. This can be used to determine if e.g. an event had any hits in a tracker or to disable or enable all calorimeters (though we don't actively use this in CI or production). In theory, we could use the DetectorSelector mechanism to enable only trackers instead of defining our tracking_only.xml geometry.However, not every detector sets these flags. Only (some of the) trackers do. This is some of the output of
dumpdetector $DETECTOR_PATH/$DETECTOR_CONFIG.xml
:Describe the solution you'd like
Someone should go through and enable the appropriate flags.
Describe alternatives you've considered
This is low priority, so the alternative is to leave this alone.
The text was updated successfully, but these errors were encountered: