Skip to content

feat(env): support named-keyframe Manager defaults - #1088

Merged
TATP-233 merged 1 commit into
dev/issue-1042-manager-based-apifrom
feat/issue-1087-named-keyframe-default-state
Aug 18, 2026
Merged

feat(env): support named-keyframe Manager defaults#1088
TATP-233 merged 1 commit into
dev/issue-1042-manager-based-apifrom
feat/issue-1087-named-keyframe-default-state

Conversation

@TATP-233

Copy link
Copy Markdown
Collaborator

Summary

  • add SceneCfg.default_keyframe_name as the optional Manager-Based default-state selector
  • resolve and validate one detached read-only keyframe qpos snapshot during env initialization
  • inject the same snapshot into Entity root/joint defaults and ResetStateTransaction
  • preserve the unconfigured qpos0 path and existing lazy reset behavior
  • fail closed for invalid selectors, missing keyframes/capabilities, and invalid qpos arrays

Scope accounting

  • files: 5 modified
  • additions: 369
  • deletions: 24
  • source: 145 additions / 24 deletions
  • tests: 224 additions

Local validation

  • focused Manager-Based env: 33 passed
  • adjacent entity/reset/event regression: 58 passed
  • ruff: passed
  • mypy: passed
  • pyright: passed
  • make test-all: passed (2002 passed, 27 skipped, 276 deselected, 1 xfailed; benchmark module mode 32/33 and script mode 33/34, with one platform-optional MLX skip in each mode)

Per the #1042 child workflow, all gates ran locally on final head 55ce742; remote CI/Docs are intentionally not triggered.

Refs #1042
Closes #1087

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant