Validate SimReady Assets with Schemas#
This page expands the answer to Would schemas allow for primary and secondary validation?.
Primary validation covers range checks, regular expression validation, and similar checks. Secondary validation covers constraint checks and co-dependent variables.
Yes. Profile-based checks can verify individual properties, such as required values, types and ranges, and constraints between properties. Static checks examine authored structure, properties and relationships; simulation-based tests evaluate behavior under specified runtime conditions. Conformance reports should identify the profile and version they cover and any unsupported or skipped required checks.
Primary Validation#
Primary validation covers range checks, type checks, and presence checks.
Handled directly by rules.
Examples: “every rigid shape must carry a
CollisionAPI” (RB.COL.001), “upAxis shall be Z” (UN.006), “meshes shall have normals” (VG.027).Each failure traces to the exact USD property at fault.
Secondary Validation#
Secondary validation covers constraint checks and co-dependent variables.
Also handled by rules: the rule framework is arbitrary Python, not limited to single-property checks.
Example: “if property A is set, property B must also be present and within a compatible range.”
The SimReady Standardization Workflow (Phase 3) requires producing validators alongside each specification.
Profiles#
Profiles organize validation.
Profiles scope validation. An asset is checked against the specific Features and Requirements of its target Profile (such as
Prop-Robotics-Neutral), not against all of SimReady.Different Profiles share Requirements where they overlap.
Asset Validation and Runtime Testing#
Static checks examine authored structure, properties and relationships.
Runtime testing verifies simulation behavior, including physics, robot articulation, gripper and grasp performance, and visual tests, by running actual simulations, capturing outputs, and reviewing results.
Think of validation as “does this asset meet the spec?” and runtime testing as “does this asset behave correctly in simulation?”