ML4CPS
ML4CPS is a Python package for learning and analysis of hybrid dynamical systems, with the focus on Cyber-Physical Systems (CPS). The code was developed for several research publications (bibtex).
- Website (ml4cps.ai4cps.com)
- Contact (contact@ai4cps.com)
Installation
Install the core package without PyTorch or MLflow:
pip install ml4cps
For DEBTA models and tensor-based tools, install the optional PyTorch dependency:
pip install "ml4cps[torch]"
For experiment tracking and MLflow model integration, install:
pip install "ml4cps[mlflow]"
Combine both extras with pip install "ml4cps[torch,mlflow]".
Core CPS simulation, visualization, and DEBTA with log_mlflow=False work
without MLflow. Tracking calls require the mlflow extra.
The dev extra includes both PyTorch and MLflow for development and tests.
Data
In the folder "data" there are several datasets that can be easily loaded using the ml4cps.examples module.
Bugs
If you find any bugs, please contact us at bugs@ai4cps.com.
License
See LICENSE.
If you use this code in your research, please cite our work.
1 maintainer
Metadata
1 maintainer
Release files for ml4cps 0.2.14
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 | |
|---|---|---|---|---|
| ml4cps-0.2.14.tar.gz | 1.6 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ml4cps-0.2.14-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.3 MB
Release files / ml4cps-0.2.14.tar.gz
| Download URL | ml4cps-0.2.14.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a0014ba5e06e6a584a4284b9ca47868a8d23fa493f72a9ff7894b6ced4f0449
|
|
BLAKE2b-256 checksum How to use checksums |
2caa4616cebeb450ef5d11467577c8b57e8319416ca37b4e9acf7b410df7ccb1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 20, 2026.
Transparency logRelease files / ml4cps-0.2.14-py3-none-any.whl
| Download URL | ml4cps-0.2.14-py3-none-any.whl |
|---|---|
| Size | 1.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
90a8989451e3a409e1fefd9ea0c281bef77b0e11155cc357b696e1aa94a04e94
|
|
BLAKE2b-256 checksum How to use checksums |
851b506369720631ba615fdf1f3054145dafdeee7b32dbc88ba48f09c805e169
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 20, 2026.
Transparency logSecurity for ml4cps 0.2.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ml4cps-0.2.14.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 20, 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.
