PyResultExplorer
PyResultExplorer is a Python client library for Ansys Result Explorer, which is a tool to explore and visualize structural simulation results. With PyResultExplorer you can:
- Launch a new or connect to an existing Result Explorer session
- Automate and customize your Result Explorer post-processing workflows
Installation
For users
To install PyResultExplorer:
python -m pip install ansys-result-explorer-core
For developers
Installing PyResultExplorer in developer mode allows you to modify the source and enhance it.
Start by cloning this repository:
git clone https://github.com/ansys/pyresultexplorer
Create a fresh-clean Python environment and activate it:
# Create a virtual environment
uv venv
# Activate it in a POSIX system
source .venv/bin/activate
# Activate it in Windows
.venv\Scripts\activate
Install with latest required build system, doc, and testing dependencies:
uv sync --all-groups
The style checks take advantage of pre-commit. You can install it with pre-commit install.
Basic usage
The following code snippet shows how to launch a new Result Explorer instance, create a solution and load a displacement view.
import os
from ansys.result_explorer.core import launch_result_explorer
# Launch a new Result Explorer session
rx = launch_result_explorer()
# Create a solution from an APDL RST file
sol = rx.create_solution(
name="PyRX Solution",
file_path=os.path.join("tests", "data", "multiple_connections.rst"),
)
# Create a new workspace and load a displacement view
workspace = rx.create_workspace(name="PyRX Workspace")
views = sol.views
print("Views in solution:")
for v in views:
print(f" - {v}")
view = next((v for v in views if "Displacement" in v.name), None)
viewport = workspace.assign_view(view=view, wait=True)
# Take a screenshot of the view and save to disk
snapshot_data = viewport.take_snapshot()
print("Saving snapshot to file...")
with open(view.name + ".png", "wb") as image_file:
image_file.write(snapshot_data)
License
This project is licensed under the Apache 2.0 license agreement. See the LICENSE file for details.
Resources
For general PyAnsys questions, email pyansys-core@synopsys.com.
Metadata
Release files for ansys-result-explorer-core 0.1.2
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 | Actions |
|---|---|---|---|---|
| ansys_result_explorer_core-0.1.2.tar.gz | 47.8 kB | With provenance | Details for ansys_result_explorer_core-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ansys_result_explorer_core-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for ansys_result_explorer_core-0.1.2-py3-none-any.whl |
Total release size: 105.6 kB
Release files / ansys_result_explorer_core-0.1.2.tar.gz
| Download URL | ansys_result_explorer_core-0.1.2.tar.gz |
|---|---|
| Size | 47.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6dbad675cc4514fa56e9b6564e7cee74ce3d38f4acbc8abbca59214c69450a1a
|
|
BLAKE2b-256 checksum How to use checksums |
96a51563aa71437633aa642af5b74bdebe4b9857ebd5ec3749efd650f76909b2
|
| 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 Sep 14, 2026.
Transparency logRelease files / ansys_result_explorer_core-0.1.2-py3-none-any.whl
| Download URL | ansys_result_explorer_core-0.1.2-py3-none-any.whl |
|---|---|
| Size | 57.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cd5d975614e9716fb071a5317a2afb05444990a373cb13cb9a6200fc4e02ca64
|
|
BLAKE2b-256 checksum How to use checksums |
f96d99637c728490e85426981993ebeb11dbe486838eea52c13e5addbbb4ff06
|
| 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 Sep 14, 2026.
Transparency logSecurity for ansys-result-explorer-core 0.1.2
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
Both files in this release have been uploaded with provenance metadata.
Attestation for ansys_result_explorer_core-0.1.2.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 Sep 14, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.