SimReady Conform FET_004_ROBOT_PHYSX
Purpose
Use this exact feature skill when the selected profile, validation report, or user request names FET_004_ROBOT_PHYSX. It repairs or stages simulate multi-body physics (robot physx) conformance without drifting into another runtime contract.
FET_004_ROBOT_PHYSX is deprecated. This skill exists only to preserve
compatibility with historical or external contracts and assets that explicitly
name the feature. Never select or recommend it for a new profile version; use
FET_003_PHYSX@0.4.0 and FET_004_PHYSX@0.4.0 instead.
Default to FET_004_ROBOT_PHYSX@0.4.0 when the user asks for this feature without a version. Use an older integer version only when the profile, validation report, or user explicitly pins it. If the report names a different FET_###_RUNTIME feature, switch to that feature's matching skill before editing.
Source of Truth
Before changing an asset or package, read:
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.1.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.2.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.3.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.4.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX.md
Treat the selected JSON manifest as authoritative for dependencies and requirement IDs. Use the feature markdown for human-readable contract details, requirement links, samples, benchmarks, and adapters.
Feature Versions
| Version |
Dependencies |
Requirements |
0.1.0 |
None |
RB.COL.002, RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.006, RB.007, RB.009, RB.010, JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001, RB.011, RB.012 |
0.2.0 |
None |
RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.006, RB.007, RB.009, RB.010, JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001, PHYSX.COL.001, PHYSX.COL.002, RB.011, RB.012 |
0.3.0 |
None |
RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.007, RB.009, RB.010, JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001, PHYSX.COL.001, PHYSX.COL.002, RB.011, RB.012 |
0.4.0 |
None |
RB.COL.003, RB.COL.004, RB.001, RB.003, RB.005, RB.007, RB.009, RB.010, JT.001, JT.002, JT.003, JT.ART.002, JT.ART.003, JT.ART.004, RB.MB.001, PHYSX.COL.001, PHYSX.COL.002, RB.011, RB.012 |
Feature Adapter
When the input already conforms to the neutral base feature, prefer the deterministic feature adapter to author the runtime-specific data first (via the workspace upgrade command; see nv_core/sr_specs/docs/guides/feature_adapters/feature_adapters.md), then repair only the residual requirements below.
| Adapter module |
Adapter |
Transition |
Authors |
nv_core/cip_specs/asset_handler_modules/neutral_to_physx |
rigid_body_neutral_to_robot_physx |
FET_003_STANDARD@0.1.0 -> FET_004_ROBOT_PHYSX@0.2.0 |
Mesh extents on all meshes. |
- The adapter runs on a staged output stage and never creates geometry, joints, or articulation topology; it only annotates existing prims.
- It only authors mesh extents (targeting
@2). The robot RB.*, JT.*, RB.MB.001, and PHYSX.COL.* requirements — and the @4 default — must be repaired manually per the Workflow below on existing robot link/joint topology.
Workflow
- Confirm the input exists and identify the exact selected feature/version from the profile TOML, validation report, or user request.
- Load the selected
FET_004_ROBOT_PHYSX manifest and the feature markdown before editing.
- Load requirement docs linked from the feature markdown for every reported failing requirement.
- Create or use a staged output location unless the user explicitly asks for in-place edits.
- Repair only the requirements listed by the selected
FET_004_ROBOT_PHYSX manifest and its dependencies.
- Rerun the same profile gate or the narrowest available feature/capability validation gate. If runtime evidence is required and unavailable, report that limitation instead of claiming a pass.
- Summarize the selected
FET_004_ROBOT_PHYSX version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.
Feature Guidance
- Use this legacy robot PhysX feature only when the profile pins it or needs its robot-specific collider exemption.
- Preserve robot link and joint semantics; leave robot identity to FET_021_* and driven actuation to FET_022_*.
- Do not create new geometry to satisfy this feature.
Report Fields
| Field |
Meaning |
feature |
Exact feature ID and version, for example FET_004_ROBOT_PHYSX@0.4.0. |
input |
Source asset, package root, or package definition inspected. |
output |
Staged output path, or in-place only when explicitly requested. |
requirements_repaired |
Requirement IDs repaired in this pass. |
validation |
Command or inspection used to verify this exact feature. |
status |
passed, failed, skipped, or blocked. |
next_step |
The next exact feature skill or user/runtime evidence needed. |
1---2name: simready-foundation-conform-fet-004-robot-physx3description: "Use for compatibility repair of deprecated FET_004_ROBOT_PHYSX SimReady conformance. Use only when a historical or external profile, validation report, asset stamp, or user request explicitly names FET_004_ROBOT_PHYSX; never select it for a new profile version."4license: Apache-2.05metadata:6 source: https://skillmd.com/skills/nvidia/simready-foundation-conform-fet-004-robot-physx7 author: "Shaad Boochoon <sboochoon@nvidia.com>"8 tags:9 - simready10 - conformance11 - robot-physx12---1314# SimReady Conform FET_004_ROBOT_PHYSX1516## Purpose1718Use this exact feature skill when the selected profile, validation report, or user request names `FET_004_ROBOT_PHYSX`. It repairs or stages simulate multi-body physics (robot physx) conformance without drifting into another runtime contract.1920`FET_004_ROBOT_PHYSX` is deprecated. This skill exists only to preserve21compatibility with historical or external contracts and assets that explicitly22name the feature. Never select or recommend it for a new profile version; use23`FET_003_PHYSX@0.4.0` and `FET_004_PHYSX@0.4.0` instead.2425Default to `FET_004_ROBOT_PHYSX@0.4.0` when the user asks for this feature without a version. Use an older integer version only when the profile, validation report, or user explicitly pins it. If the report names a different `FET_###_RUNTIME` feature, switch to that feature's matching skill before editing.2627## Source of Truth2829Before changing an asset or package, read:3031- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.1.0.json`32- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.2.0.json`33- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.3.0.json`34- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX-0.4.0.json`35- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_004_ROBOT_PHYSX.md`3637Treat the selected JSON manifest as authoritative for dependencies and requirement IDs. Use the feature markdown for human-readable contract details, requirement links, samples, benchmarks, and adapters.3839## Feature Versions4041| Version | Dependencies | Requirements |42|---|---|---|43| `0.1.0` | None | `RB.COL.002`, `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.006`, `RB.007`, `RB.009`, `RB.010`, `JT.001`, `JT.002`, `JT.003`, `JT.ART.002`, `JT.ART.003`, `JT.ART.004`, `RB.MB.001`, `RB.011`, `RB.012` |44| `0.2.0` | None | `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.006`, `RB.007`, `RB.009`, `RB.010`, `JT.001`, `JT.002`, `JT.003`, `JT.ART.002`, `JT.ART.003`, `JT.ART.004`, `RB.MB.001`, `PHYSX.COL.001`, `PHYSX.COL.002`, `RB.011`, `RB.012` |45| `0.3.0` | None | `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.007`, `RB.009`, `RB.010`, `JT.001`, `JT.002`, `JT.003`, `JT.ART.002`, `JT.ART.003`, `JT.ART.004`, `RB.MB.001`, `PHYSX.COL.001`, `PHYSX.COL.002`, `RB.011`, `RB.012` |46| `0.4.0` | None | `RB.COL.003`, `RB.COL.004`, `RB.001`, `RB.003`, `RB.005`, `RB.007`, `RB.009`, `RB.010`, `JT.001`, `JT.002`, `JT.003`, `JT.ART.002`, `JT.ART.003`, `JT.ART.004`, `RB.MB.001`, `PHYSX.COL.001`, `PHYSX.COL.002`, `RB.011`, `RB.012` |4748## Feature Adapter4950When the input already conforms to the neutral base feature, prefer the deterministic feature adapter to author the runtime-specific data first (via the `workspace upgrade` command; see `nv_core/sr_specs/docs/guides/feature_adapters/feature_adapters.md`), then repair only the residual requirements below.5152| Adapter module | Adapter | Transition | Authors |53|---|---|---|---|54| `nv_core/cip_specs/asset_handler_modules/neutral_to_physx` | `rigid_body_neutral_to_robot_physx` | `FET_003_STANDARD@0.1.0` -> `FET_004_ROBOT_PHYSX@0.2.0` | Mesh extents on all meshes. |5556- The adapter runs on a staged output stage and never creates geometry, joints, or articulation topology; it only annotates existing prims.57- It only authors mesh extents (targeting `@2`). The robot `RB.*`, `JT.*`, `RB.MB.001`, and `PHYSX.COL.*` requirements — and the `@4` default — must be repaired manually per the Workflow below on existing robot link/joint topology.5859## Workflow60611. Confirm the input exists and identify the exact selected feature/version from the profile TOML, validation report, or user request.622. Load the selected `FET_004_ROBOT_PHYSX` manifest and the feature markdown before editing.633. Load requirement docs linked from the feature markdown for every reported failing requirement.644. Create or use a staged output location unless the user explicitly asks for in-place edits.655. Repair only the requirements listed by the selected `FET_004_ROBOT_PHYSX` manifest and its dependencies.666. Rerun the same profile gate or the narrowest available feature/capability validation gate. If runtime evidence is required and unavailable, report that limitation instead of claiming a pass.677. Summarize the selected `FET_004_ROBOT_PHYSX` version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.6869## Feature Guidance7071- Use this legacy robot PhysX feature only when the profile pins it or needs its robot-specific collider exemption.72- Preserve robot link and joint semantics; leave robot identity to FET_021_* and driven actuation to FET_022_*.73- Do not create new geometry to satisfy this feature.7475## Report Fields7677| Field | Meaning |78|---|---|79| `feature` | Exact feature ID and version, for example `FET_004_ROBOT_PHYSX@0.4.0`. |80| `input` | Source asset, package root, or package definition inspected. |81| `output` | Staged output path, or `in-place` only when explicitly requested. |82| `requirements_repaired` | Requirement IDs repaired in this pass. |83| `validation` | Command or inspection used to verify this exact feature. |84| `status` | `passed`, `failed`, `skipped`, or `blocked`. |85| `next_step` | The next exact feature skill or user/runtime evidence needed. |