Datasets:
Reproduce the object packages
USD authoring uses Python 3.12 and OpenUSD 26.8. Install the versions in pyproject.toml in an isolated environment. Source assets are pinned to the NVIDIA revision in the case records.
python scripts/acquire_packages.py
python scripts/build_broken_objects.py
python scripts/verify_broken_objects.py
python scripts/package_broken_objects.py
python scripts/build_release_metadata.py
python scripts/build_case_viewer.py
The source downloader verifies every file against its upstream Git or LFS digest. The object builder materializes the selected PhysX configuration, applies named fault recipes and reopens the exported bytes to check each authored predicate. Archive assembly retains resources, NVIDIA notices and a per-file SHA-256 manifest, then reads every archive member back for verification.
records/Rxx/damage-verification.json records source composition, topology, injected opinions and geometric measurements. package-verification.json identifies the complete archive. These authored-state checks are distinct from dynamic motion, contact, effective-mass and rendering measurements. Runtime measurements carry their own scope and software versions.
instruction.md and evidence.json inside each package describe the object task. Damaged components remain present and inspectable. Pristine source stages and fault recipes belong outside a repair actor’s input directory.