Skip to content

feat(genesis): unify device-resident DR lifecycle - #477

Merged
TATP-233 merged 2 commits into
mainfrom
dev/issue-unilab-2520-genesis-dr-lifecycle
Oct 26, 2026
Merged

TATP-233 merged 2 commits into
mainfrom
dev/issue-unilab-2520-genesis-dr-lifecycle

Conversation

@TATP-233

Copy link
Copy Markdown
Contributor

Goal

Unify whole-MJCF and portable Genesis scenes on one device-resident runtime DR lifecycle and remove the legacy portable host reset/interval path.

Motivating UniLab roadmap: Motphys/UniLab#2520.

Contract

  • DomainRandomizationCapabilities is split authoritatively by plane.
  • Active exact CUDA/AMDGPU Genesis sessions declare only:
    • device reset: body_mass, kp, kd
    • device interval: body_force, body_torque
  • Host term sets are empty, including portable and CPU/no-lifecycle sessions.
  • Portable host reset/interval runtime paths and compatibility aliases are removed.
  • Runtime validation/scatter/commit stays device-resident; host/CPU payloads fail closed naming term and plane.
  • Cold materialization/startup/index/default-table work remains explicit and separate from hot DR.

Validation

  • uv run pytest -q — 1864 passed, 120 skipped
  • ruff check . — passed
  • ruff format --check — passed
  • mypy src/unisim — passed
  • pyright — passed
  • check_support.py --check-docs — passed
  • Real-CUDA portable lifecycle acceptance passed on RTX 4090
  • CPU-masked fail-closed process test passed (CUDA_VISIBLE_DEVICES="")

Follow-up

After this is released, UniLab PR Motphys/UniLab#2523 will bump the default and ROCm unisim-core pins and regenerate both lockfiles. That PR intentionally remains non-mergeable until the release exists.

@TATP-233
TATP-233 merged commit 4f30b52 into main Oct 26, 2026
5 checks passed
@TATP-233
TATP-233 deleted the dev/issue-unilab-2520-genesis-dr-lifecycle branch October 26, 2026 09:42
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