Overview
Ansys ModelCenter Workflow is a Python client library for Ansys ModelCenter, a suite of products delivering tools for creating and automating engineering workflows.
Documentation and issues
Documentation for the latest stable release of Ansys ModelCenter Workflow is hosted at Ansys ModelCenter Workflow documentation.
The documentation has four sections:
Getting started: Learn how to install Ansys ModelCenter Workflow.
User guide: Understand how to use Ansys ModelCenter Workflow to create and run workflows.
API reference: Understand how to use Python to interact programmatically with Ansys ModelCenter. Workflow API endpoints and how to use them to interact programmatically.
Contribute: Learn how to contribute to the Ansys ModelCenter Workflow 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.
On the Ansys ModelCenter Workflow Issues page, you can create issues to report bugs and request new features. On the Discussions page on the Ansys Developer portal, you can post questions, share ideas, and get community feedback.
If you have general questions about the PyAnsys ecosystem, email pyansys.core@ansys.com. If your question is specific to Ansys ModelCenter Workflow, ask your question in an issue as described in the previous paragraph.
License
Ansys ModelCenter Workflow is licensed under the MIT License.
Ansys ModelCenter Workflow makes no commercial claim over Ansys whatsoever. This library extends the functionality of interacting with Ansys ModelCenter by adding a Python interface without changing the core behavior or license of the original software. The use of Ansys ModelCenter requires a legally licensed copy of Ansys ModelCenter.
To get a copy of Ansys ModelCenter, see the Ansys ModelCenter page on the Ansys website.
Release files for ansys-modelcenter-workflow 0.1.3
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_modelcenter_workflow-0.1.3.tar.gz | 47.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansys_modelcenter_workflow-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 161.1 kB
Release files / ansys_modelcenter_workflow-0.1.3.tar.gz
| Download URL | ansys_modelcenter_workflow-0.1.3.tar.gz |
|---|---|
| Size | 47.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80da179c27a51b97737bd9e0057a4609e00251db5d1321866b1f21fa74a6a3b3
|
|
BLAKE2b-256 checksum How to use checksums |
9a7e764377b2dde7630c238a139bf9cc746b7693fcbfea259bd0ba646bb9aaa7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 2, 2026.
Transparency logRelease files / ansys_modelcenter_workflow-0.1.3-py3-none-any.whl
| Download URL | ansys_modelcenter_workflow-0.1.3-py3-none-any.whl |
|---|---|
| Size | 113.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
888aba169721e2280da3b78d723c3128784172bd7a6386570d88b5c6e0081537
|
|
BLAKE2b-256 checksum How to use checksums |
251cee8354e242e7118f68fedc56ab92ef6a2c5600c18985a888b47d34841532
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jan 2, 2026.
Transparency log