What problem does it solve?
Validating a trained robot policy or checkpoint in Isaac for Healthcare (i4h) requires coordinating a policy daemon and the Arena simulator, configuring environment YAMLs, and capturing verification episodes to HDF5 — a multi-step process that is easy to get wrong, especially in non-interactive agent sessions.
Core Features & Use Cases
- Policy and Checkpoint Rollouts: Launch the policy daemon and Arena together to evaluate a policy or a specific
checkpoint-NNNN/ directory against an i4h environment, recording episodes to verify.hdf5.
- State-Machine Smoke Runs: Run scripted surgical state-machine controllers (e.g.,
surgical_reach_psm) via Arena --state-machine without starting a policy daemon.
- Non-Interactive Session Handling: Provides a controlled single-shell rollout (Step 2A) for Claude Code
--print and Codex exec sessions so the policy daemon is not orphaned between tool calls.
- Use Case: Ask your agent to "run eval using new checkpoint for 300 timesteps" and it resolves the latest checkpoint, sets
MAX_TIMESTEPS=300, runs the rollout, and reports episodes saved plus log paths.
Quick Start
Ask your agent to evaluate scissor pick and place for 2 episodes and it will run the i4h validation workflow and record the verification HDF5.