urbanverse-scene
Python API for downloading, exploring, and using UrbanVerse urban scene datasets hosted on HuggingFace.
| Dataset | Scenes | HuggingFace |
|---|---|---|
| CraftBench | 12 hand-crafted testing scenes | Oatmealliu/UrbanVerse-CraftBench |
| UrbanVerse-Scenes | 320 generated training scenes | Oatmealliu/UrbanVerse-Scenes |
Installation
pip install urbanverse-scene --extra-index-url https://pypi.nvidia.com
The
--extra-index-urlflag is required becauseisaacsimis hosted on NVIDIA's PyPI index.
Quick start
import urbanverse_scene as uvs
# (Optional) Override cache directory (default: ~/.cache/urbanverse_scenes/)
uvs.set("~/my_data/urbanverse_scenes")
# List available CraftBench scenes
descs = uvs.craftbench.get_descriptions()
# Download & extract specific scenes
result = uvs.craftbench.load_scenes(descs[:2])
usd_path = result[descs[0]] # Path to export_version.usd
# Download all 12 CraftBench scenes
uvs.craftbench.download_all()
# Check download integrity & repair missing files
uvs.craftbench.check_integrity()
uvs.craftbench.repair()
# Preview scenes in the browser (video + images)
uvs.craftbench.preview(descs[:3])
# Open scenes in IsaacSim
uvs.open(descs[:1])
uvs.open(descs[:1], headless=True, rtx=True)
API overview
| Function | Description |
|---|---|
uvs.set(path) |
Set the local cache directory |
uvs.open(descriptions, headless, rtx) |
Open scenes in IsaacSim |
uvs.craftbench.get_descriptions() |
List all 12 CraftBench scene names |
uvs.craftbench.load_scenes(descriptions) |
Download & extract specific scenes |
uvs.craftbench.download_all() |
Download the full CraftBench dataset |
uvs.craftbench.check_integrity() |
Verify download completeness |
uvs.craftbench.repair() |
Re-download missing files |
uvs.craftbench.preview(descriptions) |
Browser-based scene preview (video + images) |
Requirements
- Python >= 3.8
- IsaacSim 4.5.0 (installed automatically as a dependency; requires NVIDIA's extra index)
- huggingface_hub >= 0.34.4
License
Links
1 maintainer
Metadata
1 maintainer
Release files for urbanverse-scene 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| urbanverse_scene-0.1.0.tar.gz | 16.8 kB | Without provenance | Details for urbanverse_scene-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| urbanverse_scene-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for urbanverse_scene-0.1.0-py3-none-any.whl |
Total release size: 36.1 kB
Release files / urbanverse_scene-0.1.0.tar.gz
| Download URL | urbanverse_scene-0.1.0.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
90acd250a1e03594cdf955ac19bc3c0512a86f58d43e21aed2d9e55340ce4792
|
|
BLAKE2b-256 checksum How to use checksums |
07341f1237abd26b879c8cbc5db13d9acf89584d871aa5a1e11a2f909675a52f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.19
|
Release files / urbanverse_scene-0.1.0-py3-none-any.whl
| Download URL | urbanverse_scene-0.1.0-py3-none-any.whl |
|---|---|
| Size | 19.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d52384fd27d6014465f1e8bf914457732dee3a349a7f049cbd5ec7280aa8efb
|
|
BLAKE2b-256 checksum How to use checksums |
9bc2942ba4ff368b6d395c74fc68dc6d3e23cf51e27aadf91a31ffb54e9fd88b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.19
|
Security for urbanverse-scene 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
