Skip to main content

Robotics and Runtime Handoff

Use this guide when a Physical AI scenario must be consumed by SimRunner, Omniverse, Isaac, PhysX, Newton, robotics middleware, or another approved runtime.

Handoff Flow​

Prerequisites​

RequirementWhy it matters
Runtime ownerConfirms target runtime, adapter, physics settings, and output format.
Scene packageGeometry, semantics, constraints, and source data need stable identity.
Safety reviewerRobotics or equipment training scenarios need engineering review.

Inputs​

InputRequired preparation
Scene identityTenant, scene ID, model assets, versions, and source references.
Geometry and semanticsComponents, units, coordinate system, materials, labels, and articulation hints.
Operating constraintsTask sequence, safety zones, speed limits, load limits, and environment conditions.
Runtime settingsTarget runtime, adapter version, physics settings, seed, duration, and output format.
Review outputKPIs, logs, screenshots, render outputs, .digrec, or semantic scene JSON.

Procedure​

  1. Confirm target runtime and adapter requirements.
  2. Prepare the SimReady asset package and scenario data.
  3. Export semantic scene JSON or the runtime-specific package.
  4. Run the scenario through SimRunner or the target runtime.
  5. Review output against the engineering question.
  6. Feed geometry, semantic, or constraint changes back into FactVerse records.

Expected Output​

The output is a handoff package that lets the runtime consume governed scene identity, geometry, semantics, constraints, and review evidence.

Validation Checklist​

  • Runtime and adapter version are recorded.
  • Coordinate system and units match runtime expectations.
  • Safety and operating constraints are included.
  • Output files and logs are linked to the scenario.
  • Changes discovered in runtime are fed back to the asset package.

Failure Handling​

SymptomResponse
Runtime import failsCheck file format, coordinate system, required semantics, and adapter version.
Robot or equipment behavior is unrealisticReview physical assumptions, controller settings, and task sequence.
Output cannot be tracedRecord scene ID, run ID, runtime version, and exported files.
Safety constraints are missingKeep the package out of training or field trial use until reviewed.