← ClaudeAtlas

voyager-runlisted

Execute inference.py for an already-selected Voyager SDK model or pipeline on Axelera AI Metis hardware with an explicit source such as video, image, USB, RTSP, dataset, or fakevideo. Use when the user provides or already has the model/pipeline and wants only a run/test/stream command. Do not create, package, validate, or evaluate a complete new solution from a natural-language request; use voyager-launch for that.
fxd0h/Axelera-Voyager-Local-Assistant · ★ 4 · AI & Automation · score 75
Install: claude install-skill fxd0h/Axelera-Voyager-Local-Assistant
# Run Inference Execute inference on Axelera AI hardware with various input sources ## Use This Skill When / Not When - Use when: a model/pipeline is already selected and the user wants to execute `inference.py` with a video, image, USB, RTSP, or dataset source. - Not when: they want a packaged end-to-end solution with validation artifacts -- route to voyager-launch. - Not when: a custom model must be compiled or quantized first -- route to voyager-deploy. ## Instructions Run inference with the specified configuration: **$ARGUMENTS** {{INCLUDE common/voyager-sdk-setup.md}} {{INCLUDE common/voyager-task-integration.md}} {{INCLUDE common/examples-catalog.md}} ### Step 1: Environment Verification - Ensure environment is activated: ```bash source venv/bin/activate ``` - Read `.voyager-runtime.json`. Only verify hardware directly when `execution.mode` is `execute_on_device`: ```bash axdevice ``` In `package_for_linux` mode, return Voyager SDK commands and the package-only caveat instead of claiming hardware execution. ### Step 2: Parse Arguments - Model/pipeline name (required) - Input source (camera, video, image, dataset, RTSP) - Display options - Output options - Examples-first: if the user described a task rather than naming a model, check `common/examples-catalog.md` for a ready-made example (or route to `voyager-launch`). ### Step 3: Input Source Configuration **USB Camera:** ```bash ./inference.py <model> usb:0 # First USB