geti-library-dev

name

geti-library-dev

description

Develop and validate changes in `library/` for the `getitune` Python package (the Geti training library). Use when touching `library/src/**`, `library/tests/**`, `library/pyproject.toml`, recipes, model manifests, or any Python API, CLI, model, training, export, or utility logic owned by the library. Helps with `uv` and `just` setup, choosing cpu, cuda, or xpu extras, the multi-backend model architecture, adding models and recipes, and running the smallest relevant lint, unit, model, or integration checks.

Geti Library Development

For the full architecture reference (package layout, multi-backend design, how to add models, recipes, and manifests) read library/AGENTS.md.

Quick Start

• Work from library/.
• Create or refresh the environment with just venv --device cpu for routine work.
• Switch to just venv --device cuda or just venv --device xpu only when the task needs accelerator-specific behavior.
• Run just lint before wider test runs.

Architecture Essentials

• Source lives under src/getitune/. Public API entry points must stay stable because application/backend/ consumes them.
• Multi-backend design: compute backends live under src/getitune/backend/ — lightning/ (PyTorch Lightning training), openvino/ (inference-only), and optional ultralytics/. src/getitune/models/ re-exports model classes from each backend into one namespace.
• Device abstraction: DeviceType (src/getitune/types/device.py) and () abstract accelerator choice. Guard device-specific (CUDA vs XPU) code with capability checks in — never at import time.