LeonOverload/errand-assets

ERRAND assets

Versioned scene and robot assets for ERRAND. Repository access is private. Authenticate with an account that has access before downloading.

Release: errand-assets-v2

Use the readable revision tag errand-assets-v2 to obtain the fixed release.

Archive	Contents	Compressed bytes
errand-assets-v2-scenes.tar.zst	Scene layers, geometry, materials and fixtures	1,841,122,380
errand-assets-v2-robot.tar.zst	Prepared S1 robot and dependencies	221,018,836

The 4,730 files cover twelve shared layouts, two mobile MVP profiles and six variants used by seven BLADE/STACK reference sequences. Preserve manifest.json, relocations.json and the release README with both archives. Raw human episodes, training exports and model weights are excluded.

Download and install

Run from an installed ERRAND checkout with Python 3.12:

.venv/bin/hf auth login
.venv/bin/python tools/asset_bundle.py download \
  --repo LeonOverload/errand-assets \
  --revision errand-assets-v2 \
  --output /path/to/asset-download
.venv/bin/python tools/asset_bundle.py unpack \
  /path/to/asset-download/errand-assets-v2 \
  --output /path/to/asset-install
.venv/bin/python tools/asset_bundle.py verify /path/to/asset-install
export ERRAND_ASSET_ROOT=/path/to/asset-install
.venv/bin/python tools/configure_assets.py setup "$ERRAND_ASSET_ROOT" --output local/runtime
.venv/bin/python errand --workspace local/runtime tasks validate

Choose a new installation and runtime directory. Setup derives local USD reference overlays without changing raw source assets. Native simulation needs the external Isaac Sim 6 / Isaac Lab 3 environment. See the source repository's asset guide and implementation status for validation evidence and runtime requirements.

Attribution and evidence

Licenses apply per source, as recorded in errand-assets-v2/manifest.json. The 126 attribution records include CC0-1.0, CC-BY-4.0 and Astribot BSD-3-Clause SDK / Apache-2.0 description notices. Preserve attribution and source revisions when copying assets; the release does not assign one license to all contents.

Kit material modules come from the Isaac installation. Path/size verification and USD dependency checks do not establish robot task success; historical demonstrations remain bound to their recorded scene and observer profiles.