PyDPF-Post
PyDPF-Post is part of the Ansys Data Processing Framework (DPF), which provides reusable operators that let you access and transform simulation data coming from different Ansys and third-party result files.
PyDPF-Post leverages PyDPF-Core, a package for building more advanced and customized workflows using Ansys DPF. After loading a simulation's result file in PyDPF-Post, you can extract simulation metadata and results and then apply postprocessing operations on them.
PyDPF-Core is physics-agnostic and operator-oriented. It is a direct exposure of the DPF features and objects with a few helpers. It is not restricted to postprocessing.
PyDPF-Post on the other hand provides a high-level, physics-oriented API for postprocessing. It has a more Pythonic and user-friendly API dedicated to postprocessing, with new objects meant to provide a specific interface for each type of physics and analysis (such as mechanics static versus transient versus fluids). Most importantly, there is no need to manipulate operators or workflows.
Documentation and issues
Documentation for the latest stable release of PyPDF-Post is hosted at PyDPF-Post documentation.
The PyDPF-Post documentation has five sections:
- Getting started: Learn how to install PyDPF-Post in user mode and quickly begin using it.
- User guide: Understand key concepts for using PyDPF-Post.
- API reference: Understand how to use Python to interact programmatically with PyDPF-Post.
- Examples: Explore examples that show how to use PyDPF-Post to perform nay different types of operations.
- Contribute: Learn how to contribute to the PyDPF-Post codebase or documentation.
In the upper right corner of the documentation's title bar, there is an option for switching from viewing the documentation for the latest stable release to viewing the documentation for the development version or previously released versions.
You can also view or download the PyDPF-Post cheat sheet. This one-page reference provides syntax rules and commands for using PyDPF-Post.
On the PyDPF-Post Issues page, you can create issues to report bugs and request new features. On the PyDPF-Post Discussions page or the Discussions page on the Ansys Developer portal, you can post questions, share ideas, and get community feedback.
To reach the project support team, email pyansys.core@ansys.com.
1 maintainer
Metadata
1 maintainer
Release files for ansys-dpf-post 0.12.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 | Reset |
|---|---|---|---|---|
| ansys_dpf_post-0.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / ansys_dpf_post-0.12.0-py3-none-any.whl
| Download URL | ansys_dpf_post-0.12.0-py3-none-any.whl |
|---|---|
| Size | 168.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e279d550d9bf1e32b41f75a3cd4ecded4706c413aba4f3b9c082b70853a2b660
|
|
BLAKE2b-256 checksum How to use checksums |
bca438850fa23f9d1e82ef27c22e42face2108d64bbd1a5822eb8c2367aba7cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Apr 28, 2026.
Transparency log
