NAGL
| Latest release | |
|---|---|
| Status | |
| Community |
A playground for applying graph convolutional networks to molecules, with a focus on learning continuous "atom-type" embeddings and from these classical molecule force field parameters.
Note: This project is still in development and liable to substantial API and other changes.
This framework is mostly based upon the End-to-End Differentiable Molecular Mechanics Force Field Construction preprint by Wang, Fass and Chodera.
NAGL is bound by a Code of Conduct.
Documentation
See our documentation for notes on installation, basic usage, theory, and examples!
Copyright
The NAGL source code is hosted at https://github.com/openforcefield/openff-nagl and is available under the MIT license (see the file LICENSE). Some parts inherit from code distributed under other licenses, as detailed in LICENSE-3RD-PARTY).
NAGL inherits from Simon Boothroyd's NAGL library at https://github.com/SimonBoothroyd/nagl.
Metadata
Release files for openff-nagl 0.6.1.post3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| openff_nagl-0.6.1.post3.tar.gz | 89.5 MB | With provenance | Details for openff_nagl-0.6.1.post3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openff_nagl-0.6.1.post3-py3-none-any.whl | Python 3 | none | any | Details for openff_nagl-0.6.1.post3-py3-none-any.whl |
Total release size: 89.6 MB
Release files / openff_nagl-0.6.1.post3.tar.gz
| Download URL | openff_nagl-0.6.1.post3.tar.gz |
|---|---|
| Size | 89.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a48693b8d5aa5e44a55f77138fd234b39eb891d1a9f772349400840ca973c6b
|
|
BLAKE2b-256 checksum How to use checksums |
a7b3675e1eff89ccf8e285c4a312cf05f5222f879e97b75043cad9f991a5abbb
|
| 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 Nov 20, 2026.
Transparency logRelease files / openff_nagl-0.6.1.post3-py3-none-any.whl
| Download URL | openff_nagl-0.6.1.post3-py3-none-any.whl |
|---|---|
| Size | 160.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33491cce71eabf9bb2aad5ab37f1ef7b06c5cb9af50d788da59df4c405be3baa
|
|
BLAKE2b-256 checksum How to use checksums |
2abb8172ed200017a90ddc3ab5780e563eb91c8b52d00de216a8830f4a2a06d9
|
| 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 Nov 20, 2026.
Transparency logSecurity for openff-nagl 0.6.1.post3
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
Both files in this release have been uploaded with provenance metadata.
Attestation for openff_nagl-0.6.1.post3.tar.gz
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 Nov 20, 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.