i4h-workflow-e2e

Runs the Isaac for Healthcare end-to-end agentic pipeline from recording through validation.

3.2k|370|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill i4h-workflow-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i4h-workflow-e2e
Source: https://github.com/NVIDIA/skills/tree/main/skills/i4h-workflow-e2e
Command: npx skills add https://github.com/NVIDIA/skills --skill i4h-workflow-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running the full Isaac for Healthcare robot-learning pipeline requires coordinating nine stages (record, mimic, annotate, replay, convert, visualize, finetune, validate, summary) with correct environment configuration, resume logic, and monitoring, which is error-prone when done manually.

Core Features & Use Cases

  • Full Pipeline Orchestration: Executes the complete agentic workflow via the e2e run script with a single environment name, handling stage ordering and artifact output automatically.
  • Resume and Skip Controls: Supports skipping stages (mimic, annotate, replay, viz) and resuming from a prior run with --from-stage and --run-dir.
  • Dry-Run Validation: Verifies the environment configuration before committing to a long pipeline run.
  • Use Case: A robotics engineer asks the agent to run an end-to-end smoke pipeline for the scissor pick-and-place task; the skill resolves the i4h-workflows repo, runs all stages in the foreground, and reports the run directory, per-stage status, and key artifacts.

Quick Start

Ask your agent to run the full end-to-end smoke pipeline for the scissor pick-and-place task using the i4h workflow.

Frequently Asked Questions about i4h-workflow-e2e

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

FAQPage Schema
How do I run the full Isaac for Healthcare end-to-end pipeline?

Run workflows/agentic/scripts/e2e/run.sh with --env <env> from the i4h-workflows repository root. The script executes all stages in order: setup, record, mimic, annotate, replay, convert, viz, finetune, validate, and summary.

How do I resume an i4h pipeline run from a failed stage?

Pass both --from-stage <stage> and --run-dir <existing-run> to run.sh to resume from a prior run. Using --from-stage without a matching --run-dir will fail because the script cannot locate the previous outputs.

Can I skip stages in the i4h e2e pipeline?

Yes, run.sh supports --skip-mimic, --skip-annotate, --skip-replay, and --skip-viz flags. Note that assemble_trocar is inference-only, so finetune and checkpoint validation are skipped automatically for that environment.

Why does the i4h e2e run fail with .venv not found?

This error means the workflow environment was not set up before running the pipeline. Run the i4h-workflow-setup skill first to create the .venv, since setup is the first pipeline stage and all later stages depend on it.

How do I monitor a long-running i4h pipeline?

Track progress from a separate shell by tailing runs/.latest/logs/workflow.log for live per-stage output. Once the run finishes, read runs/.latest/logs/SUMMARY.txt for the final report.

What are the limitations of the i4h e2e pipeline?

The assemble_trocar environment is inference-only, so finetune and checkpoint validation are skipped and no checkpoint outputs are produced. Checkpoint artifacts exist only for trainable environments, and headless mode requires explicitly setting ARENA_HEADLESS=1.