i4h-workflow

작성자: nvidia

Overview of `workflows/agentic/` (IsaacLab-Arena + GR00T/openpi). Use when the user asks what i4h workflow is, what's supported, or where to start.

npx skills add https://github.com/nvidia/skills --skill i4h-workflow

i4h Agentic Workflow

Purpose

Orient on the agentic workflow before touching a specific stage: which envs/robots/policies are supported, how the workflows/agentic/ subprojects fit together, and which per-stage skill to invoke next. This skill routes — it runs no pipeline stage itself.

Base Code

These steps drive the i4h-workflows base code (the workflows/agentic/ tree). To reuse an existing checkout, set I4H_WORKFLOWS to its path (no clone happens). Otherwise this resolves the current repo, or clones to ~/i4h-workflows — pick that default without prompting. Run every command below from the resolved root:

# Resolve the i4h-workflows base code (provides workflows/agentic/).
ROOT="${I4H_WORKFLOWS:-$(git rev-parse --show-toplevel 2>/dev/null)}"
if [ ! -d "$ROOT/workflows/agentic" ]; then
  ROOT="${I4H_WORKFLOWS:-$HOME/i4h-workflows}"
  [ -d "$ROOT/workflows/agentic" ] || git clone https://github.com/isaac-for-healthcare/i4h-workflows "$ROOT"
fi
export I4H_WORKFLOWS="$ROOT"; cd "$ROOT"

Basics

  • Env YAMLs at workflows/agentic/config/environments/<env>.yaml are the source of truth.
  • Each pipeline stage has its own skill. Compose them or use [[i4h-workflow-e2e]] for full runs.
  • For env authoring or scene-edit source changes, load skills/i4h-workflow/references/repo-map.md before generating code.

Supported Envs

Fallback when --list-envs fails (setup incomplete):

EnvRobotPolicy
scissor_pick_and_placeSO-ARM 101GR00T N1.5 (N1.7 alternative)
locomanip_tray_pick_and_placeUnitree G1GR00T N1.6 (shared policy.locomanip.*)
locomanip_push_cartUnitree G1GR00T N1.6 (shared policy.locomanip.*)
assemble_trocarUnitree G1 + Dex handsGR00T N1.5 (inference-only)
ultrasound_liver_scanFranka-style armopenpi PI0
surgical_reach_psmdVRK PSMGR00T N1.5 or scripted state machine
surgical_reach_dual_psmdVRK dual PSMGR00T N1.5 or scripted state machine
surgical_reach_starSTARGR00T N1.5 or scripted state machine
surgical_lift_blockdVRK PSMGR00T N1.5 or scripted state machine
surgical_lift_needledVRK PSMGR00T N1.5 or scripted state machine
surgical_lift_needle_organsdVRK PSMGR00T N1.5 or scripted state machine

Run

Run the step below before answering. Each step is a separate bash call; variables persist in the local agent's tmux session.

Step 1 — list supported envs

REPO_ROOT="${I4H_WORKFLOWS:-$(git rev-parse --show-toplevel 2>/dev/null)}"; [ -d "$REPO_ROOT/workflows/agentic" ] || REPO_ROOT="$HOME/i4h-workflows"
"${REPO_ROOT}/workflows/agentic/policy/run.sh" --list-envs

If the command fails, use the Supported Envs fallback table above.

Subprojects

DirectoryPurpose
workflows/agentic/arena/IsaacLab-Arena envs, scenes, tasks, teleop, record, replay
workflows/agentic/policy/Policy daemons and train dispatchers
workflows/agentic/dataset/HDF5 → LeRobot conversion and visualization
workflows/agentic/mimic/HDF5 trajectory expansion
workflows/agentic/annotator/VLM success labels and filtering
workflows/agentic/cosmos/Optional Cosmos Transfer video augmentation
workflows/agentic/common/Shared config, messaging, robot constants

Skill Index

SkillPurpose
i4h-workflow-setupInstall / sync / check third-party deps
i4h-workflow-createAdd a new env
i4h-workflow-scene-editEdit an existing scene / task / camera
i4h-workflow-dataset-teleopRecord human demos
i4h-workflow-dataset-replayReplay HDF5 episodes
i4h-workflow-dataset-mimicExpand HDF5 demos with noise
i4h-workflow-dataset-annotateVLM label / filter episodes
i4h-workflow-dataset-convertConvert HDF5 to LeRobot
i4h-workflow-finetuneTrain supported envs
i4h-workflow-validateRoll out / evaluate policy checkpoints
i4h-workflow-e2eRun the full pipeline
i4h-lerobot-vizOpen the LeRobot HTML viewer

Prerequisites

  • For any hands-on stage, set up the workflow first — see [[i4h-workflow-setup]] (component venvs and third-party checkouts present).
  • Env YAMLs at workflows/agentic/config/environments/<env>.yaml are the source of truth.

Limitations

  • Overview/routing only — each pipeline stage has its own skill; this one performs no recording, training, or rollout.

Troubleshooting

  • Error: env not found / unsupported — Cause: typo, unregistered env, or setup incomplete. Fix: run workflows/agentic/policy/run.sh --list-envs; if that fails, run [[i4h-workflow-setup]] first; otherwise check the Supported Envs table.

Final Response

The response is incomplete unless it includes all three parts below, each separated by a blank line. Do not reply with prose only or run sections together without spacing.

  1. Orientation — one short paragraph: env YAMLs, subprojects, sim-to-policy pipeline.

  2. Supported envs — heading plus markdown table from Step 1 (--list-envs output: env, stack, description) or the Supported Envs fallback table.

  3. Available skills — heading plus the full Skill Index table copied into the response.

Then (after another blank line) recommend [[i4h-workflow-setup]] if setup is not done, and name one next stage skill matched to the user's goal.

nvidia의 다른 스킬

compileiq-debug
nvidia
무언가 잘못되었을 때 사용: Search()가 멈추거나, 모든 평가가 INVALID_SCORE를 반환하거나, 점수가 개선되지 않거나, 모든 설정이 동일한 숫자를 반환하거나, ptxas 오류 등이 발생할 때
create-github-pr
nvidia
gh CLI를 사용하여 GitHub 풀 리퀘스트를 생성합니다. 사용자가 새 PR을 만들거나, 코드 리뷰를 제출하거나, 풀 리퀘스트를 열고자 할 때 사용합니다. 트리거 키워드 -…
nemoclaw-maintainer-cross-issue-sweep
nvidia
다른 열린 이슈들을 스캔하여 주어진 PR이 함께 수정하거나 실수로 망가뜨릴 수 있는 이슈를 찾습니다. 인접 수정 기회와 모순 위험을 file:line…과 함께 출력합니다.
fhir-basics
nvidia
에이전트에게 FHIR R4 API의 작동 방식, 사용 가능한 리소스, 검색 매개변수를 사용한 쿼리 방법, 모든 응답 형식을 올바르게 파싱하는 방법을 가르칩니다…
compileiq-validate-result
nvidia
검색이 완료된 후, 속도 향상을 청구하거나 ACF를 발송하기 전에 사용합니다. dump_results CSV를 로드하고, 상위 K개 후보(단일 목표)를 추출합니다…
changelog-audit
nvidia
릴리스 전에 Warp CHANGELOG.md를 감사합니다: 누락된 항목 복구, 사용자 영향별 정렬, 항목 언어 다듬기, 줄 바꿈, (릴리스 브랜치 모드) 비교 업데이트…
maintain-dynamic-plugins
nvidia
NeMo Relay 동적 플러그인 로더, 매니페스트, Rust 네이티브 SDK, gRPC 워커 프로토콜, Python 워커 SDK, 문서, 테스트 및 릴리스 워크플로 커버리지를 유지 관리합니다.
dgx-diagnose
nvidia
일반적인 DGX Station GB300 문제 진단 — CUDA 충돌, 잘못된 GPU 타겟팅, vLLM/SGLang 컨테이너 버그, MIG 상태 문제, NVLink/Fabric Manager 오류,…