The dataset viewer is not available for this subset.
Exception: SplitsNotFoundError
Message: The split names could not be parsed from the dataset config.
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
for split_generator in builder._split_generators(
~~~~~~~~~~~~~~~~~~~~~~~~~^
StreamingDownloadManager(base_path=builder.base_path, download_config=download_config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/webdataset/webdataset.py", line 81, in _split_generators
first_examples = list(islice(pipeline, self.NUM_EXAMPLES_FOR_FEATURES_INFERENCE))
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/webdataset/webdataset.py", line 32, in _get_pipeline_from_tar
fs: fsspec.AbstractFileSystem = fsspec.filesystem("memory")
~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/fsspec/registry.py", line 302, in filesystem
cls = get_filesystem_class(protocol)
File "/usr/local/lib/python3.14/site-packages/fsspec/registry.py", line 239, in get_filesystem_class
raise ValueError(f"Protocol not known: {protocol}")
ValueError: Protocol not known: memory
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/split_names.py", line 71, in compute_split_names_from_streaming_response
for split in get_dataset_split_names(
~~~~~~~~~~~~~~~~~~~~~~~^
path=dataset,
^^^^^^^^^^^^^
config_name=config,
^^^^^^^^^^^^^^^^^^^
token=hf_token,
^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
info = get_dataset_config_info(
path,
...<6 lines>...
**config_kwargs,
)
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 291, in get_dataset_config_info
raise SplitsNotFoundError("The split names could not be parsed from the dataset config.") from err
datasets.inspect.SplitsNotFoundError: The split names could not be parsed from the dataset config.Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
3D-WM Atomic — v3 (batches b07–b14)
Synthetic CAD construction videos paired with per-frame atomic action ops, for training video→action (inverse-dynamics) and image→video world models.
v3 extends the v2 dataset (batches b01–b06) with b07–b14. Identical format and contract.
Format: v2-continuous-mm
Raw float-millimeter op parameters (no quantization); each clip is translation-canonicalized so the final-mesh bbox is centered at the world origin. The full schema — atomic op vocabulary, scale/camera metadata, the SKETCH_BEGIN depth-DOF caveat, and the recommended near-blank reader filter — is documented in the companion dataset_spec.md.
Layout
data_hula_b07 … data_hula_b14/ # one prefix per source batch
b0000 … bNNNN/train/shard-*.tar # tar shards, ~25 clips each (~10 shards/batch-idx)
Each clip = one (case, view):
0000.png … NNNN.png— per-op construction-animation frames (256×256)meta.json— scale / camera / canonicalization + per-frameop_spansops.json— atomic op tuples (raw-mm floats) + human-readableops_human
5 views per case (iso / front / side / top / random) sharing one auto-fit scale anchor — identical world_diag_mm / approx_mm_per_pixel across siblings, only the camera angle differs.
Quality gates (at generation time)
- Geometry validity — OCC
BRepCheck; invalid / self-intersecting solids are dropped. - Near-blank — a case that renders near-blank from every view (measured on a neutral palette) is dropped (valid-but-tiny solids).
Every shipped clip is therefore a valid, visibly non-blank solid.
Scale
~8000 cases/batch × 8 batches × 5 views ≈ 300k clips.
🤖 Generated with Claude Code
- Downloads last month
- 2,353