physical-ai-video-data-augmentation

Plan and execute NVIDIA VDA workflows on the OSMO platform.

Updated May 29, 2026
One-click install
npx skills add https://github.com/rblake2320/vigil --skill physical-ai-video-data-augmentation-rblake2320
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: physical-ai-video-data-augmentation
Source: https://github.com/rblake2320/vigil/tree/main/.claude/skills/physical-ai-video-data-augmentation
Command: npx skills add https://github.com/rblake2320/vigil --skill physical-ai-video-data-augmentation-rblake2320

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, omegaconf, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill orchestrates end-to-end video data augmentation workflows on NVIDIA's OSMO platform, enabling safe, reproducible execution from preflight to output retrieval.

Core Features & Use Cases

  • End-to-end workflow orchestration across augmentation, auto-labeling, and e2e variants for rapid, scalable video labeling.
  • Per-video config generation with deterministic seeds and variable sampling to produce diverse augmented outputs.
  • Built-in preflight, pre-submit guard checks, dataset URL validation, and GPU pool readiness to prevent failed submits.
  • Supports demo datasets and a separate setup_model_cache path for environments without a full data backend.

Quick Start

Submit a VDA run by providing storage_url, dataset, run_id, video, and gpu_platform, then monitor the workflow via the standard osmo commands.

Frequently Asked Questions about physical-ai-video-data-augmentation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate video data augmentation workflows on the NVIDIA OSMO platform?

Orchestrate video data augmentation on NVIDIA OSMO by submitting a run with storage_url, dataset, run_id, and gpu_platform. The workflow manages the complete pipeline, deriving storage and enforcing preflight guard checks before execution.

What video augmentation flows are supported for auto labeling and super resolution?

Supported video augmentation flows include augmentation_and_al, auto_labeling, e2e, and e2e_super_resolution. These enable scalable video labeling and generate per-video configurations with deterministic seeds and variable sampling for diverse outputs.

How do I prevent failed job submissions when running OSMO video augmentation tasks?

Prevent failed OSMO video augmentation submissions by enforcing built-in preflight and pre-submit guard checks. The system validates dataset inputs, cache wiring, GPU pool availability, and credential provisioning before allowing any workflow to execute.

Can I run video augmentation workflows without a full data backend configured?

Run video augmentation without a full data backend by utilizing the provided demo datasets and the setup_model_cache path. This allows workflow execution in environments lacking complete storage infrastructure for testing and validation.

What inputs do I need to start an end-to-end video data augmentation run?

Start an end-to-end video augmentation run by providing a storage_url, dataset, run_id, video, and gpu_platform. The system derives the necessary storage URL from the dataset input and validates it during the preflight phase.

Why does my video augmentation workflow require preflight guard checks before execution?

Video augmentation workflows require preflight guard checks to ensure storage and orchestration safety. Validating dataset URL inputs, cache wiring, GPU availability, and credentials before submission prevents resource allocation failures during execution.