About
PyScadeOne is a Python library for the Ansys Scade One model-based development environment.
This library allows:
Data access
Reading projects and navigating in models
Reading and editing simulation data files
Reading test results
Reading information about the generated code
Ecosystem integration
Exporting FMI 2.0 components
Prerequisites
PyScadeOne requires .NET runtime 8.0.
Installation
Refer to the official installation guidelines.
Documentation
The documentation of PyScadeOne contains the following chapters:
Getting started. This section provides a brief overview and instructions on how to get started with the project. It typically includes information on how to install the project, set up any necessary dependencies, and run a basic example or test to ensure everything is functioning correctly.
User guide. The user guide section offers detailed documentation and instructions on how to use the project. It provides comprehensive explanations of the project’s features, functionalities, and configuration options. The user guide aims to help users understand the project’s concepts, best practices, and recommended workflows.
API reference. The API reference section provides detailed documentation for the project’s application programming interface (API). It includes information about classes, functions, methods, and their parameters, return values, and usage examples. This reference helps developers understand the available API endpoints, their functionalities, and how to interact with them programmatically.
Examples. The examples section showcases practical code examples that demonstrate how to use the project in real-world scenarios. It provides sample code snippets or complete scripts that illustrate different use cases or demonstrate specific features of the project. Examples serve as practical references for developers, helping them understand how to apply the project to their own applications.
Documentation contains UML diagrams generated by PlantUML.
License
The license of the PyScadeOne project is MIT. Read the full text of the license in the LICENSE file.
Release files for ansys-scadeone-core 0.8.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 | |
|---|---|---|---|
| ansys_scadeone_core-0.8.2.tar.gz | 2.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansys_scadeone_core-0.8.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.5 MB
Release files / ansys_scadeone_core-0.8.2.tar.gz
| Download URL | ansys_scadeone_core-0.8.2.tar.gz |
|---|---|
| Size | 2.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5809a2316f8f78307ab8e0a57f7890e988774a1294ef4a47ee2cd580ceb00e9b
|
|
BLAKE2b-256 checksum How to use checksums |
a7ba9b7498387adc47c6c21428c129f38e1217b8cf5d4fa28b3e20d97a37651a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Mar 10, 2026.
Transparency logRelease files / ansys_scadeone_core-0.8.2-py3-none-any.whl
| Download URL | ansys_scadeone_core-0.8.2-py3-none-any.whl |
|---|---|
| Size | 2.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
12fc87baac13bdecc6f38b1f379517be8d1479aa58c2d6c0b718a0e15aa03b5e
|
|
BLAKE2b-256 checksum How to use checksums |
34be30e78f8ed0cfe1a0cda0090a08480aa478f9ef445124d138c1ed99dae83d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Mar 10, 2026.
Transparency log