Tensorwaves

_See all documentation for this version [here](//tensorwaves.rtfd.io/en/0.2.9)._

🔨 Internal maintenance

- TensorWaves v0.2.9 can be installed with TensorFlow v2.6 and higher versions of [`phasespace`](https://github.com/zfit/phasespace) (#447)

_See all documentation for this version [here](https://tensorwaves.rtfd.io/en/0.2.8)._

💡 New features

<details>
<summary>A time estimate is now provided when generating data (286)</summary>

Fixes the `tqdm` progress bar so that it gives a time estimate when calling `generate_phsp` and `generate_data`.

</details>


🐛 Bug fixes

<details>
<summary>Analytic continuation can now be activated safely when using JAX as backend (284)</summary>

Implementation of [TR-001](https://compwa-org.readthedocs.io/report/001.html). Requires https://github.com/ComPWA/ampform/pull/75 and AmpForm v0.9.2 (upcoming).

</details>


🖱️ Developer Experience

<details>
<summary>Milestone are automatically closed when a matching release is published (282)</summary>

</details>

<details>
<summary>A new notebook show how to activate analytic continuation (285)</summary>

</details>

_See all documentation for this version [here](https://tensorwaves.rtfd.io/en/0.2.7)._

💡 New features

Larger SymPy expressions that take a long time to lambdify can now be lambdified faster (order of 10-100x) with `split_expression()`, `optimized_lambdify()`, and the `max_complexity` argument.
https://tensorwaves.rtfd.io/en/0.2.7/usage/faster-lambdify.html

_See all documentation for this version [here](https://tensorwaves.rtfd.io/en/0.2.6)._

💡 New features

<details>
<summary>Constructing an Estimator from a Function (272)</summary>

If the amplitude model is complicated, it can take over an hour to lambdify it to a `Model`. So it's annoying to have to do that twice if you use the same backend for data generation and fitting. This PR allows reusing a `LambdifiedFunction` for fitting.

</details>



<details>
<summary>Data can now be generated with JAX as well (271)</summary>

Simple fix: just casts [`ScalarSequence`](https://ampform.readthedocs.io/en/0.9.1/api/ampform.data.html#ampform.data.ScalarSequence) back into a `numpy` array so that a lambdified `Function` can handle it.

</details>

<details>
<summary>Python 3.9 and TensorFlow 2.5 are now supported (275)</summary>

Many thanks to mayou36 for releasing [`phasespace` v1.3](https://github.com/zfit/phasespace/releases/tag/1.3.0)!

</details>

_Added support for analytic continuation. See all documentation for this version [here](https://tensorwaves.rtfd.io/en/0.2.5)._

💡 New features

<details>
<summary>Upgrade to AmpForm v0.9.x (270)</summary>

Adds support for analytic continuation in particular.

</details>

🐛 Bug fixes

<details>
<summary>Lambdify to numpy, not numpy.__dict__ (f0cbcaa)</summary>

Lambdifying to with `modules=numpy.__dict__` does not work with conditionals (`sympy.Piecewise`). If using numpy.**dict**, Piecewise is lambdified to if-else (which doesn't worky with numpy arrays), while it should convert to `numpy.select`.

</details>

🖱️ Developer Experience

<details>
<summary>Run notebooks with pytest (982aa21)</summary>

</details>

<details>
<summary>Simplified usage examples to speed up CI (0737f49)</summary>

</details>

_See all documentation for this version [here](https://tensorwaves.rtfd.io/en/0.2.4)._
(Maintenance release: mainly improves mobile version of the website.)

⚠️ Interface

<details>
<summary>Optional dependency section "extras" has been renamed to "all" (6ff7ecc)</summary>

</details>

🔨 Internal maintenance

<details>
<summary>Switch to first (non pre-)release of qrules and ampform (265)</summary>

In addition, extract pytest configuration to `pytest.ini` and define `testpaths` there. Since b9b72ed, it is become impossible to run tests through VSCode. Defining testpaths fixes this. In addition, it removes the last 'non-tox' section from the tox.ini file (see 7eb3866)

</details>

🖱️ Developer Experience

<details>
<summary>Move dependency definitions back back to setup.cfg (264)</summary>

With the release of [`pip-tools` v6.1.0](https://github.com/jazzband/pip-tools/releases/tag/6.1.0), `pip-compile` now correctly handles [`extras_require`](https://setuptools.readthedocs.io/en/latest/userguide/dependency_management.html#optional-dependencies). This allows for a big clean-up of the set-up introduced by https://github.com/ComPWA/expertsystem/pull/412.

Advantages:

- Easier for the user and developer! Just run: `pip install -e .[dev]` to get started developing, `pip install -e .[dev] -U` to try out upgrades, and `pip install -c .constraints/py3.8.txt -e .[dev] -U` in case you exactly want to reproduce the dependencies for some commit.
- The upgrade jobs become significantly faster: [bit over 1min](https://github.com/ComPWA/qrules/runs/2346236017?check_suite_focus=true) versus almost [3min](https://github.com/ComPWA/qrules/runs/2322145112?check_suite_focus=true)
- All requirements, their version domains, and the dependencies between each of the requirement sections can be nicely overseen and maintained within `setup.cfg`
- Git diffs for pull requests that affect dependencies become easier to oversee
- Less complexity and fewer changes per commit

</details>

<details>
<summary>Add PR template + GitPod extensions (266)</summary>

</details>

<details>
<summary>Annotations in API are abbreviated if they are links (267)</summary>

Makes it easier to understand function signatures.

</details>

<details>
<summary>Doctests are now verified through pytest (b9b72ed)</summary>

</details>

<details>
<summary>Updated installation instructions (8f94021)</summary>

Added references to requirement pinning

</details>

<details>
<summary>Added more flake8 plugins and fixed identified issues (feefdfb)</summary>

Also cleans up the `.pylintrc` config file

</details>

<details>
<summary>Split all config files for dev tools (7eb3866)</summary>

Better to only keep tox job definitions in the tox.ini file. Note that config files are only extracted if their respective tools supports a config file name that starts with a dot

</details>