PyDYNA
Overview
PyDYNA is a Pythonic package for providing a more convenient and complete way to build an Ansys DYNA input deck, submit it to the Ansys LS-DYNA solver, and finally postprocess the results.
Pydyna contains two modules:
keywords: This module provides the ability to create keyword files for LS-DYNA without using gRPC.
run: This module provides the ability to start the LS-DYNA solver. This does not require any client-server library or Docker container.
Once you have results, you can use the Ansys Data Processing Framework (DPF), which is designed to provide numerical simulation users and engineers with a toolbox for accessing and transforming simulation data. DPF can access data from Ansys solver files and from several files with neutral formats, including CSV, HDF5, and VTK. Using DPF’s various operators, you can manipulate and transform this data.
The ansys-dpf-post package provides a simplified Python interface to DPF, thus enabling rapid postprocessing without ever leaving a Python environment. For more information on DPF-Post, see the DPF-Post documentation.
Documentation and issues
Documentation for the latest stable release of PyDyna is hosted at PyDYNA documentation.
For examples on how to use PyDYNA, see Examples in the PyDYNA 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.
On the PyDYNA Issues page, you can create issues to report bugs and request new features. On the PyDYNA 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.
License
PyDYNA is licensed under the MIT license.
PyDYNA makes no commercial claim over Ansys whatsoever. This library extends the functionality of Ansys LS-DYNA by adding a Python interface to LS-DYNA without changing the core behavior or license of the original software. The use of the interactive control of PyDYNA requires a legally licensed local copy of LS-DYNA.
For more information on LS-DYNA, see the Ansys LS-DYNA page on the Ansys website.
1 maintainer
Release files for ansys-dyna-core 0.12.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ansys_dyna_core-0.12.1.tar.gz | 5.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansys_dyna_core-0.12.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:16.5 MB
Release files / ansys_dyna_core-0.12.1.tar.gz
| Download URL | ansys_dyna_core-0.12.1.tar.gz |
|---|---|
| Size | 5.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
538cec940c730fce9d2139aca63d82fc858a29e9119606977d89af15249f55bc
|
|
BLAKE2b-256 checksum How to use checksums |
8d202ff04a94b83c6e8c4785bf9d51f12a14f1fdd91a99778c62642fcf3e30d1
|
| 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 May 18, 2026.
Transparency logRelease files / ansys_dyna_core-0.12.1-py3-none-any.whl
| Download URL | ansys_dyna_core-0.12.1-py3-none-any.whl |
|---|---|
| Size | 11.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6210d64fad8c4a9e73bf6f9cadc64e103fd1ea6c466ba95cde1e27395395ab71
|
|
BLAKE2b-256 checksum How to use checksums |
00b6a1008574cf2410e34986b48de203559bcef0c5673ed37a81417007d46194
|
| 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 May 18, 2026.
Transparency log
