feat: extract DynamicsSelector class #240
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HelicityAmplitudeBuilder.__dynamics_choices
has been extracted to a newDynamicsSelector
class. This reduces the responsibilities of theHelicityAmplitudeBuilder
and makes it easier to implement new implementations for selection of dynamics.Something similar has been done for 'collector' attributes like
HelicityAmplitudeBuilder.__parameter_defaults
and__components
. This will be useful when implementing TR-014, which will require keeping track of amplitude definitions.Note: once QRules v0.10 is out, ComPWA/qrules#156 and ComPWA/qrules#157 make it possible to define the dynamics choices as a mapping over topologies and visualize them as graphviz.