Download README.md from dAAAb/ware-kitchen-simready: direct link, hf CLI and curl.
- Browser
- Download file 2.04 kB
-
https://huggingface.co/datasets/dAAAb/ware-kitchen-simready/resolve/main/README.md
- Command line
-
hf download hf://datasets/dAAAb/ware-kitchen-simready/README.md
-
curl -L -o README.md https://huggingface.co/datasets/dAAAb/ware-kitchen-simready/resolve/main/README.md
license: other
language:
- en
- zh
pretty_name: WARE.KITCHEN SimReady Object Warehouse
size_categories:
- n<1K
task_categories:
- other
tags:
- simready
- openusd
- robotics
- simulation
- kitchen
- 3d
- glb
WARE.KITCHEN SimReady Object Warehouse
This is the public object warehouse behind ware.kitchen. A local RTX 5090 reconstructs kitchen objects, deterministic tools prepare OpenUSD and physics data, and publication is blocked until NVIDIA SimReady validation passes.
Status
The first five records are real TAI KIT reconstructions generated on the local RTX 5090. Their lightweight GLBs are browser-preview variants. The corresponding OpenUSD packages passed simready-validate 2026.8.0 with the Robotics-Prop 4.0.0 profile and remain canonically hosted in dAAAb/tai-kit-simready-100.
simready_status = passed applies to the linked OpenUSD package, not to the browser GLB. Physics values are estimates. Public records contain technical asset metadata only; source images, URLs, attribution records and review evidence are retained in a separate private provenance archive.
Autonomously generated public objects are released as CC0-1.0. The five TAI KIT seed previews retain their existing project license. The repository-level license remains other because the warehouse contains both groups.
Pipeline
- Discover a CC0 or public-domain source; attribution-bearing candidates are deferred to private legal review.
- Reconstruct high- and mobile-resolution GLB files on the local RTX 5090.
- Repair geometry deterministically and author OpenUSD/physics layers.
- Run NVIDIA SimReady validation; failed assets remain unpublished.
- Archive provenance privately, publish only sanitized 3D and technical metadata, then let the object fall into the persistent scene at ware.kitchen.
The local worker makes outbound HTTPS requests only. No home-network port is exposed.