Skip to content

feat(schemas): tendons schema-fragment API (additive)#10

Draft
vidurv-nvidia wants to merge 4 commits into
vidurv/schema-frag-frameworkfrom
vidurv/schema-frag-tendons
Draft

feat(schemas): tendons schema-fragment API (additive)#10
vidurv-nvidia wants to merge 4 commits into
vidurv/schema-frag-frameworkfrom
vidurv/schema-frag-tendons

Conversation

@vidurv-nvidia

@vidurv-nvidia vidurv-nvidia commented Jun 5, 2026

Copy link
Copy Markdown
Owner

Description

Additive tendons fragment family (override func, tune-not-apply)

  • core: FixedTendonFragment/SpatialTendonFragment markers + apply_fixed_tendon_properties/apply_spatial_tendon_properties
  • physx: PhysxFixedTendonCfg/PhysxSpatialTendonCfg override func to delegate to the existing multi-instance tendon writers (tune existing PhysxTendonAxisRootAPI:<inst>).
  • spawner fixed_tendons_props/spatial_tendons_props accept fragment lists + bridge.

Decision: the legacy mjc:* tendon branch is kept inline (future split candidate, commented). Status: authored, ruff clean, sim verification pending.

Fixes # (N/A — part of the staged physics schema-fragment refactor; no tracked public issue)

Type of change

  • New feature (non-breaking change which adds functionality)

Screenshots

N/A — no user-facing visual changes.

Checklist

  • I have read and understood the contribution guidelines
  • I have run the pre-commit checks (ruff + ruff-format) on the changed files
  • I have made corresponding changes to the documentation (the public API reference is auto-generated via ./isaaclab.sh -d; not separately authored)
  • My changes generate no new warnings
  • I have added tests that prove my feature works
  • I have added a changelog fragment under source/<pkg>/changelog.d/ for every touched package
  • I have added my name to CONTRIBUTORS.md

Add the additive schema-fragment framework for the tendons family,
mirroring the merged rigid-body pilot.

Core gains the FixedTendonFragment / SpatialTendonFragment markers and
the apply_fixed_tendon_properties / apply_spatial_tendon_properties
family writers. Tendons are a tune-not-apply family, so the writers
dispatch each fragment's func without applying a new anchor schema.

PhysX gains PhysxFixedTendonCfg / PhysxSpatialTendonCfg data-carrier
fragments that override func with thin apply_fixed_tendon /
apply_spatial_tendon wrappers delegating to the existing multi-instance
modify_fixed_/spatial_tendon_properties writers.

The from_files spawn slots are widened to accept fragment lists with a
transition bridge; legacy cfgs and writers stay intact. The legacy
writer's mjc:* branch is kept inline with a future-split-candidate
note.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant