ANTsNormalizingFlows
An updated PyTorch package (from normflows) for discrete normalizing flows.
Quick start
import antsnormflows as nf
# Base distribution (2D diagonal Gaussian)
base = nf.distributions.base.DiagGaussian(2)
# Real NVP with simple MLP conditioner
flows = []
num_layers = 8
for _ in range(num_layers):
param_map = nf.nets.MLP([1, 64, 64, 2], init_zeros=True)
flows.append(nf.flows.AffineCouplingBlock(param_map))
flows.append(nf.flows.Permute(2, mode="swap"))
model = nf.NormalizingFlow(base, flows)
loss = model.forward_kld(x) # x: (batch, 2)
loss.backward()
Documentation
Citation
If you use antsnormflows, please cite the corresponding papers:
-
Stimper et al. (2023). normflows: A PyTorch Package for Normalizing Flows. Journal of Open Source Software, 8(86), 5361, JOSS.
BibTeX
@article{Stimper2023, author = {Stimper, Vincent and Liu, David and Campbell, Andrew and Berenz, Vincent and Ryll, Lukas and Schölkopf, Bernhard and Hernández-Lobato, José Miguel}, title = {normflows: A PyTorch Package for Normalizing Flows}, journal = {Journal of Open Source Software}, volume = {8}, number = {86}, pages = {5361}, publisher = {The Open Journal}, doi = {10.21105/joss.05361}, url = {https://doi.org/10.21105/joss.05361}, year = {2023} }
-
Tustison et al. (2026). Deep Computational Anatomy via Latent-Aligned Multiview Normalizing Flows. bioRxiv.
BibTeX
@article{Tustison2026.05.05.723039, author = {Tustison, Nicholas James and Avants, Brian B. and Cook, Philip A. and Gee, James C. and Stone, James R.}, title = {Deep Computational Anatomy via Latent-Aligned Multiview Normalizing Flows}, elocation-id = {2026.05.05.723039}, year = {2026}, doi = {10.64898/2026.05.05.723039}, publisher = {Cold Spring Harbor Laboratory}, url = {https://www.biorxiv.org/content/early/2026/05/10/2026.05.05.723039}, eprint = {https://www.biorxiv.org/content/early/2026/05/10/2026.05.05.723039.full.pdf}, journal = {bioRxiv} }
Metadata
Release files for antsnormflows 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| antsnormflows-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for antsnormflows-1.0.0-py3-none-any.whl |
Release files / antsnormflows-1.0.0-py3-none-any.whl
| Download URL | antsnormflows-1.0.0-py3-none-any.whl |
|---|---|
| Size | 80.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d7f682a1c74706c7008800d914dfd0d80e89e778ff1327695b8c332d73ed6d8
|
|
BLAKE2b-256 checksum How to use checksums |
ce42d7b51ce7bbf31b01fc35f669c9188b8e5dd649c7df1f6f977e6852a99e5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logSecurity for antsnormflows 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
1 file in this release has been uploaded with provenance metadata.
Attestation for antsnormflows-1.0.0-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.