The algorithmic differentation tool for DOLFIN/FEniCS
The full documentation is available here
Installation
First install FEniCS.
Then install dolfin-adjoint with:
python3 -m pip install git+https://github.com/dolfin-adjoint/dolfin-adjoint.git@main
or using the Pypi-package for the latest stable release
python3 -m pip install dolfin-adjoint
Reporting bugs
If you found a bug, create an issue
Contributing
We love pull requests from everyone.
Fork, then clone the repository:
git clone https://github.com/{your_username}/dolfin-adjoint.git
Make sure the tests pass:
python3 -m pytest tests
Make your change. Add tests for your change. Make the tests pass:
python3 -m pytest tests
Push to your fork and submit a pull request. At this point you're waiting on us. We may suggest some changes or improvements or alternatives.
Some things that will increase the chance that your pull request is accepted:
- Write tests.
- Add Python doc-strings that follow the Google Style.
- Write good commit and pull request message.
License
This software is licensed under the GNU LGPL v3.
Release files for dolfin-adjoint 2025.0.0
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 | |
|---|---|---|---|---|
| dolfin_adjoint-2025.0.0.tar.gz | 37.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dolfin_adjoint-2025.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 92.1 kB
Release files / dolfin_adjoint-2025.0.0.tar.gz
| Download URL | dolfin_adjoint-2025.0.0.tar.gz |
|---|---|
| Size | 37.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29c57ca6186a6bb4cf2a32732261e589cef8748f08829663cc27e8f1c8fdb3f4
|
|
BLAKE2b-256 checksum How to use checksums |
a74e88feed5fe74d9e6ec5536284d33d12f16a7264b21f1dd3c997a487a2dfd4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Jun 22, 2025.
Transparency logRelease files / dolfin_adjoint-2025.0.0-py3-none-any.whl
| Download URL | dolfin_adjoint-2025.0.0-py3-none-any.whl |
|---|---|
| Size | 55.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e02a8604c9bdf3e3aac7ab4873adec6b891683890bf35ee018c18d24b669d08
|
|
BLAKE2b-256 checksum How to use checksums |
e1f4a1dd5abaec3794f99d9c3fbb1dce701450ac1f064486deb40e295c552b92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Jun 22, 2025.
Transparency logSecurity for dolfin-adjoint 2025.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for dolfin_adjoint-2025.0.0.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 Jun 22, 2025.
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.
