Cuvis.AI Core
Overview
Cuvis.AI is an opensource and extensible framework for building AI powered processing pipelines for hyperspectral video data.
It allows you to process and structure spectral data, train and apply machine learning models, visualize and interpret results, and deploy applications in real time environments.
Pipelines are built from reusable modular nodes and can be extended with custom plugins or external integrations.
Cuvis.AI bridges the gap between hyperspectral hardware and real world applications and enables faster development, testing, and deployment of new solutions.
cuvis-ai-core is the foundational framework underneath Cuvis.AI. While the cuvis-ai repository contains the catalog of domain-specific nodes and pre-built models, cuvis-ai-core provides the essential infrastructure that makes those modular pipelines work:
- Node System: Base classes for creating processing nodes with typed input/output ports
- Pipeline Infrastructure: Graph-based pipeline orchestration, execution, and visualization
- Plugin System: Dynamic node loading from Git repositories or local filesystem paths
- Serialization & Restoration: Save and restore complete pipeline states and configurations
- Type Safety: Strongly-typed port system with runtime validation
- gRPC Services: Remote pipeline management, training, and inference APIs
- Training Framework: Integration with PyTorch Lightning for model training workflows
This separation allows the core framework to evolve independently while the catalog of domain-specific nodes grows through a plugin architecture.
Installation
Prerequisites
If you want to directly work with cubert session files (.cu3s), you need to install cuvis C SDK from here.
Local development now relies on uv for Python and dependency management.
If uv is not already available on your system you can install it following their installation instructions.
Install from PyPI (Recommended)
# Install cuvis-ai-core from PyPI
uv add cuvis-ai-core
PyTorch will be installed automatically with CUDA support if available on your system.
Local development with uv
Create or refresh a development environment at the repository root with:
uv sync --all-extras --dev
This installs the runtime dependencies declared in pyproject.toml. uv automatically provisions the Python version declared in the project metadata, so no manual interpreter management is required.
Enable Git Hooks (Required)
After cloning the repository, enable the git hooks for code quality enforcement:
git config core.hooksPath .githooks
This configures Git to use the version-controlled hooks in .githooks/ which automatically enforce code formatting, linting, and testing standards before commits and pushes. See docs/development/git-hooks.md for details.
Advanced environment setup
When you need the reproducible development toolchain (JupyterLab, TensorBoard, etc.) from the lock file, run:
uv sync --locked --extra dev
Use uv run to execute project tooling without manually activating virtual environments, for example:
uv run pytest
Collect coverage details (the dev extra installs pytest-cov) with:
uv run pytest --cov=cuvis_ai --cov-report=term-missing
Ruff handles both formatting and linting. Format sources and check style with:
uv run ruff format .
uv run ruff check .
The configuration enforces import ordering, newline hygiene, modern string formatting, safe exception chaining, and practical return type annotations while avoiding noisy Any policing.
Validate packaging metadata and build artifacts before publishing:
uv build
To build the documentation, add the docs extra:
uv sync --locked --extra docs
Combine extras as needed (e.g. uv sync --locked --extra dev --extra docs). Whenever the pyproject.toml or uv.lock changes, rerun uv sync --locked with the extras you need to stay up to date.
1 maintainer
Metadata
1 maintainer
Release files for cuvis-ai-core 0.12.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 | |
|---|---|---|---|
| cuvis_ai_core-0.12.1.tar.gz | 739.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cuvis_ai_core-0.12.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 978.0 kB
Release files / cuvis_ai_core-0.12.1.tar.gz
| Download URL | cuvis_ai_core-0.12.1.tar.gz |
|---|---|
| Size | 739.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
626135256fdd583789c04cade6b6ae904641cae1b2334655494bf3cf4a2fcd96
|
|
BLAKE2b-256 checksum How to use checksums |
bfec1527b46af651a0f5db9c9a55e794fba728877d4835daaf4a4785165bb1ca
|
| 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 Aug 20, 2026.
Transparency logRelease files / cuvis_ai_core-0.12.1-py3-none-any.whl
| Download URL | cuvis_ai_core-0.12.1-py3-none-any.whl |
|---|---|
| Size | 238.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
850c32fd03ad8bcafee9139d9767eb247e917531bc07257b93b2108d92171283
|
|
BLAKE2b-256 checksum How to use checksums |
8b416b90737584df06138fc5511e3424716a9e21593157a068d59a715e331817
|
| 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 Aug 20, 2026.
Transparency log
