Visual Interactive Simulation Object Renderer (VISOR)
Demo
You can view a demo of VISOR to see it in action.
Overview
VISOR is a Python-based 3D visualization web component.
You can use VISOR to integrate with the following tools:
SAF (Solution Application Framework) to provide 3D visualization capabilities.
Ansys Dynamic Reporting to support dynamic reporting workflows.
PyAnsys Visualization Interface Tool to connect PyAnsys libraries to different plotting backends.
You can use VISOR for 3D visualization on desktop and on premises. VISOR customizes existing rendering frameworks to meet functional and nonfunctional requirements, including integrability, scalability, performance, and usability for solution apps.
You run VISOR with VTK (Visual Toolkit) rendering and Trame to support a client-server architecture and Python integration workflows. You target VTK WASM with WebGL because WebGPU support is not yet available.
Installation
To set up prerequisites and install VISOR, see Getting started in the VISOR documentation.
Quick start
For a basic usage example, see Quick start in the VISOR documentation.
Development
To set up your development environment, see the Contributing.md file in the VISOR repository.
Usage
You can use VISOR through the following entry points. Links are to the relevant information in he VISOR documentation.
Standalone Python
Launch a desktop VISOR app with the Python package ansys.visor.viewer to visualize files.
See VISOR Python API for API usage examples.
See API reference for details about the Python API.
VISOR HTTP service
Manage multiple VISOR instances through the VISOR HTTP API.
Integrate with PIM (Product Instance Management) to manage VISOR instances in SAF apps.
See VISOR HTTP service for usage examples.
See HTTP API reference for API details.
Dash frontend app
Connect to a VISOR instance from a Dash app with the VISOR Dash component in ansys.visor.dash.dash_visor_viewer.
See VISOR Dash component for details.
For advanced usage and configuration options, see the following VISOR documentation:
User guide and Examples in the VISOR sections.
Metadata
Release files for ansys-visor-viewer 1.0.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 | Provenance | Actions |
|---|---|---|---|---|
| ansys_visor_viewer-1.0.1.tar.gz | 50.1 MB | With provenance | Details for ansys_visor_viewer-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ansys_visor_viewer-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for ansys_visor_viewer-1.0.1-py3-none-any.whl |
Total release size: 100.5 MB
Release files / ansys_visor_viewer-1.0.1.tar.gz
| Download URL | ansys_visor_viewer-1.0.1.tar.gz |
|---|---|
| Size | 50.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f788afc8449b0ecd4a1824866cec29a7817dbcca6fb3ca1d8749c7f3eff756b1
|
|
BLAKE2b-256 checksum How to use checksums |
1f445a7261d465cc16ca979d26496a72518631e769f472307a260f00be66cca4
|
| 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 11, 2026.
Transparency logRelease files / ansys_visor_viewer-1.0.1-py3-none-any.whl
| Download URL | ansys_visor_viewer-1.0.1-py3-none-any.whl |
|---|---|
| Size | 50.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8f7406aaa27abaa2dcd6e53ac35a3f1dbebc0035f8149f06c192f95fdebe3b6e
|
|
BLAKE2b-256 checksum How to use checksums |
1c80a6b7f549095775e14e7f41c86081c0186031a85ae86eb6dea3b87e7dd731
|
| 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 11, 2026.
Transparency logSecurity for ansys-visor-viewer 1.0.1
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_visor_viewer-1.0.1.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 11, 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.