-
There are a few bugs with the deployment:
- [x] For some reason, the CD job does not run anymore upon creating a release
- [x] The notebooks don't work anymore on Google Colab. When running `pip ins…
-
As the `expertsystem` is slowly refactored and new features are introduced, we need to reconsider the current module structure. Probably best to have a few main modules like `particles`, `amplitude`, …
-
Classes and functions like `ParticleCollection` and `load_pdg` (#190) start to become more standalone and can be isolated to a separate module.
Suggested name: `expertsystem.particles`.
Notice t…
-
Since #153
> I will try to work with a class decorator here.
> ```python3
> @ComplexEnergy
> class ComplexEnergyState():
> ...
> ```
> Maybe that can resolve all our issues here
>
_Origina…
-
When generating an Amplitude Model for the decay Lambda_c^+ -> proton K- pi+, the magnitudes and phases of weak decays are automatically coupled due to parity, although parity violation in weak decays…
-
A new function that can check for all violated rules is needed. I propose the form
```python3
check_violations(initial_state, final_state, interaction_type: Optional[InteractionTypes]) -> List[str]
…
-
It turns out to be quite difficult to refactor the codebase. As a first step, it may therefore be smart to add type hints to all functions and variables, because they reveal intention of the functions…
-
Reason:
* More conventient handling of particle info
* @Leongrim has some bug
Ideally, we wait until the `expertsystem` is further refactored and has a more stable release, but this is needed for…
-
The total number of found solutions is 48. It would be good to do a little bit more fined grained testing of the solutions. This would improve the quality of the test and also make it easier to unders…
-
The core part of the `expertsystem` is building a decay topology based on quantum numbers and conservation rules. This can be done independently of building the amplitude model.
The end goal: _an i…