SimReady Conform FET_022_MUJOCO
Purpose
Use this exact feature skill when the selected profile, validation report, or user request names FET_022_MUJOCO. It repairs or stages MuJoCo driven-joint conformance without drifting into another runtime contract.
Default to FET_022_MUJOCO@0.1.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_022_MUJOCO-0.1.0.json
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_022_MUJOCO.md
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/capabilities/physics_bodies/physics_driven_joints/requirements/mujoco-joint-api.md
nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/capabilities/physics_bodies/physics_driven_joints/requirements/mujoco-actuator-targets.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
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_022_MUJOCO manifest, feature markdown, and MuJoCo requirement docs before editing.
- 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_022_MUJOCO manifest and its dependencies.
- Preserve existing USD joint topology, body relationships, and authored limits unless a reported validation failure requires a narrow correction.
- Apply
MjcJointAPI to non-fixed articulation joints that belong to the MuJoCo driven-joint contract.
- Author or repair MuJoCo joint tuning attributes only on USD physics joint prims. Keep
mjc:armature finite and non-negative.
- Author or repair
MjcActuator prims so each actuator has exactly one mjc:target relationship to a valid MjcJointAPI joint.
- Keep authored actuator ranges finite and ordered, and keep authored gain and bias parameter arrays numeric.
- Rerun the same profile gate or the narrowest available feature/capability validation gate. If MuJoCo runtime evidence is unavailable, report that limitation instead of claiming a runtime pass.
- Summarize the selected
FET_022_MUJOCO version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.
Feature Guidance
- Repair only the requirements listed by the selected
FET_022_MUJOCO manifest and its dependencies.
- Do not add schemas, metadata, or runtime behavior for a sibling runtime feature.
- Do not delete standard
UsdPhysics joint topology or MuJoCo robot multibody data when repairing the current version; FET_022_MUJOCO@0.1.0 depends on FET_004_ROBOT_MUJOCO@0.1.0.
- Do not delete
PhysicsDriveAPI or joint-state schemas unless the selected validation report or user request explicitly asks for a MuJoCo-only overlay. When both standard drives and MuJoCo actuators are present, preserve authored data and report the ambiguity.
- Report missing MuJoCo runtime/tooling evidence as a validation limitation instead of claiming a runtime pass.
Report Fields
| Field |
Meaning |
feature |
Exact feature ID and version, for example FET_022_MUJOCO@0.1.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-022-mujoco3description: "Use for repairing exact FET_022_MUJOCO SimReady conformance for MuJoCo driven-joint conformance. Use when a profile, validation report, or user request names FET_022_MUJOCO; default to version `0.1.0` unless a profile or report pins another version."4license: Apache-2.05metadata:6 source: https://skillmd.com/skills/nvidia/simready-foundation-conform-fet-022-mujoco7 author: "Shaad Boochoon <sboochoon@nvidia.com>"8 tags:9 - simready10 - conformance11 - mujoco12---1314# SimReady Conform FET_022_MUJOCO1516## Purpose1718Use this exact feature skill when the selected profile, validation report, or user request names `FET_022_MUJOCO`. It repairs or stages MuJoCo driven-joint conformance without drifting into another runtime contract.1920Default to `FET_022_MUJOCO@0.1.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.2122## Source of Truth2324Before changing an asset or package, read:2526- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_022_MUJOCO-0.1.0.json`27- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/features/FET_022_MUJOCO.md`28- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/capabilities/physics_bodies/physics_driven_joints/requirements/mujoco-joint-api.md`29- `nv_core/tiers/simready_foundation_tier_core/simready/foundation/tier_core/capabilities/physics_bodies/physics_driven_joints/requirements/mujoco-actuator-targets.md`3031Treat 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.3233## Feature Versions3435| Version | Dependencies | Requirements |36|---|---|---|37| `0.1.0` | FET_004_ROBOT_MUJOCO@0.1.0 | `DJ.011`, `MUJOCO.DJ.001`, `MUJOCO.DJ.002` |3839## Workflow40411. Confirm the input exists and identify the exact selected feature/version from the profile TOML, validation report, or user request.422. Load the selected `FET_022_MUJOCO` manifest, feature markdown, and MuJoCo requirement docs before editing.433. Create or use a staged output location unless the user explicitly asks for in-place edits.444. Repair only the requirements listed by the selected `FET_022_MUJOCO` manifest and its dependencies.455. Preserve existing USD joint topology, body relationships, and authored limits unless a reported validation failure requires a narrow correction.466. Apply `MjcJointAPI` to non-fixed articulation joints that belong to the MuJoCo driven-joint contract.477. Author or repair MuJoCo joint tuning attributes only on USD physics joint prims. Keep `mjc:armature` finite and non-negative.488. Author or repair `MjcActuator` prims so each actuator has exactly one `mjc:target` relationship to a valid `MjcJointAPI` joint.499. Keep authored actuator ranges finite and ordered, and keep authored gain and bias parameter arrays numeric.5010. Rerun the same profile gate or the narrowest available feature/capability validation gate. If MuJoCo runtime evidence is unavailable, report that limitation instead of claiming a runtime pass.5111. Summarize the selected `FET_022_MUJOCO` version, changed files, validation evidence, and the first remaining blocker or next exact feature gate.5253## Feature Guidance5455- Repair only the requirements listed by the selected `FET_022_MUJOCO` manifest and its dependencies.56- Do not add schemas, metadata, or runtime behavior for a sibling runtime feature.57- Do not delete standard `UsdPhysics` joint topology or MuJoCo robot multibody data when repairing the current version; `FET_022_MUJOCO@0.1.0` depends on `FET_004_ROBOT_MUJOCO@0.1.0`.58- Do not delete `PhysicsDriveAPI` or joint-state schemas unless the selected validation report or user request explicitly asks for a MuJoCo-only overlay. When both standard drives and MuJoCo actuators are present, preserve authored data and report the ambiguity.59- Report missing MuJoCo runtime/tooling evidence as a validation limitation instead of claiming a runtime pass.6061## Report Fields6263| Field | Meaning |64|---|---|65| `feature` | Exact feature ID and version, for example `FET_022_MUJOCO@0.1.0`. |66| `input` | Source asset, package root, or package definition inspected. |67| `output` | Staged output path, or `in-place` only when explicitly requested. |68| `requirements_repaired` | Requirement IDs repaired in this pass. |69| `validation` | Command or inspection used to verify this exact feature. |70| `status` | `passed`, `failed`, `skipped`, or `blocked`. |71| `next_step` | The next exact feature skill or user/runtime evidence needed. |