Make quality specific to the task
A high-resolution room render does not establish that the scene supports your robot. Define what it must do: navigate a passage, reach a work surface, open a door or place an object. That gives the review a concrete target.
Use this checklist for generated environments, library content and custom digital twins. It is an inspection framework, not a certification or a guarantee of sim-to-real transfer.
Review the environment at three levels
| Level | Questions to answer |
|---|---|
| Package | Does the entry file open with all required dependencies? Are licence and version details available? |
| Asset | Are task-relevant dimensions, contacts, moving parts and labels appropriate? |
| Scene | Do placement, clearances, resets and interactions work together in the target runtime? |
Keep failures separate. A package can be complete while a door interaction is unsuitable. A single well-authored asset can also behave poorly when placed in an invalid scene state.
Choose tolerances from the interaction
Do not use an unsupported submillimeter claim as a substitute for an acceptance test. A narrow insertion task and a wide navigation aisle have different sensitivity to geometry and calibration. State which measurements matter and what evidence supports them.
For a replica of a real facility, agree the references and tolerance checks before authoring. A photorealistic image is not a measurement report. The digital twin service is scoped around the facility and required interactions.
Check profile and runtime evidence
NVIDIA SimReady Foundation organizes content requirements by profile. Record the selected profile and version with the result. Our validator reports supported checks; interpret findings within that coverage.
Then run a representative task in your chosen simulator. Record build, scene revision, starting conditions, robot or controller configuration and the expected outcome. Repeat the reset and interaction, rather than accepting one successful run as complete coverage.
Keep a clear acceptance record
For each requirement, mark pass, fail, not tested or not applicable, with evidence and an owner for follow-up. Do not merge not-tested checks into a single passed badge.
Browse environment packages and inspect their available specifications. Keep the checklist with the selected package so future edits, conversions and optimizations can be reviewed against the same requirements.