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
While trying to generate a 4-body decay with the isobar model (for #27), I found it would be nice to inspect the generated Topology instances (so the uninitialized ones) prior to running StateTransitionManager.find_solutions, because find_solutions may take a long time and you want to check if those topologies make sense.
Now it is possible to easily create ComPWA compatible data using
python. This means ComPWA Particle, Event and DataPoint structures can
now be created (FixesComPWA#30). Furthermore the HelicityKinematics
`convert()` method is now available in the python UI. The documentation
for importing data was also improved.
* Extended the Event, Particle and DataPoint structure in the python
UI.
* Also made these classes more pythonic, so their members are read only
properties.
* Added docstrings to the necessary members.
* Updated ComPWA submodule to newest version. This resulted in removing
the gsl dependency.
* Adapted a test to the PreFactor change coming from ComPWA. There the
PreFactor is now part of the CoefficientAmplitude and not the
SequentialAmplitude.
* The read and write section in the docs was improved.
* A new jupyter notebook was added to the examples section. This
example also appears in the docs.
redeboer
added a commit
to redeboer/ComPWA-qrules
that referenced
this issue
Apr 30, 2022
While trying to generate a 4-body decay with the isobar model (for #27), I found it would be nice to inspect the generated
Topology
instances (so the uninitialized ones) prior to runningStateTransitionManager.find_solutions
, becausefind_solutions
may take a long time and you want to check if those topologies make sense.See also ComPWA/expertsystem#342
The text was updated successfully, but these errors were encountered: