PySimAI
A Python wrapper for Ansys SimAI
How to install
At least two installation modes are provided: user and developer.
For users
In order to install PySimAI, make sure you have the latest version of pip. To do so, run:
python -m pip install -U pipThen, you can simply execute:
python -m pip install ansys-simai-coreFor developers
Installing PySimAI in developer mode allows you to modify the source and enhance it.
Before contributing to the project, please refer to the PyAnsys Developer’s guide. You will need to follow these steps:
Start by cloning this repository:
git clone https://github.com/ansys/pysimaiInstall uv. NB: If you are a Windows user, make sure that Python is installed on your system and it is added to the Path.
Use uv to run commands
uv run pytest -xlvFinally, verify your development installation by running:
uv tool install tox --with tox-uv toxAlternatively, you can also run tasks defined in pyproject.toml using poethepoet:
uv tool install poethepoet uv run poe lint uv run poe test uv run poe doc
How to test
This project takes advantage of tox. This tool allows to automate common development tasks (similar to Makefile) but it is oriented towards Python development.
Using tox
As Makefile has rules, tox has environments. In fact, the tool creates its own virtual environment so anything being tested is isolated from the project in order to guarantee project’s integrity. The following environments commands are provided:
tox -e style: will check for coding style quality.
tox -e py: checks for unit tests.
tox -e py-coverage: checks for unit testing and code coverage.
tox -e doc: checks for documentation building process.
Raw testing
If required, you can always call the style commands (ruff) or unit testing ones (pytest) from the command line. However, this does not guarantee that your project is being tested in an isolated environment, which is the reason why tools like tox exist.
A note on pre-commit
The style checks take advantage of pre-commit. Developers are not forced but encouraged to install this tool via:
uv tool install pre-commit && pre-commit installDocumentation
For building documentation, you can either run the usual rules provided in the Sphinx Makefile, such as:
uv run make -C doc/ html && open doc/html/index.htmlHowever, the recommended way of checking documentation integrity is using:
tox -e doc && open .tox/doc_out/index.htmlDistributing
uv commands can help you build or publish the package
uv build
uv publish1 maintainer
Metadata
1 maintainer
Release files for ansys-simai-core 0.4.8
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 | |
|---|---|---|---|---|
| ansys_simai_core-0.4.8.tar.gz | 1.0 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansys_simai_core-0.4.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / ansys_simai_core-0.4.8.tar.gz
| Download URL | ansys_simai_core-0.4.8.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd07e5b6065fc99d7b01b6fe407e82e0134e45bd52d32a8ed08c48a75a65577a
|
|
BLAKE2b-256 checksum How to use checksums |
bf6465814c84a1dd23130fa1c4817f47e43e15fcc41c8d351f0a777661d063f9
|
| 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 Oct 19, 2026.
Transparency logRelease files / ansys_simai_core-0.4.8-py3-none-any.whl
| Download URL | ansys_simai_core-0.4.8-py3-none-any.whl |
|---|---|
| Size | 164.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0bceb8bf1b3547face55e9c1152873c6f360f7cf46e8d8d1c5785627137c5e78
|
|
BLAKE2b-256 checksum How to use checksums |
0fefaaf6fe46076ea52e144012660e672657ce08755ceee243125e3e630570b0
|
| 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 Oct 19, 2026.
Transparency logSecurity for ansys-simai-core 0.4.8
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 ansys_simai_core-0.4.8.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 Oct 19, 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.
