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 66, 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.
RoboEval → openpi LeRobot dataset (roboeval_all)
Vision-language-action dataset for fine-tuning π0.5 (openpi) on the RoboEval bimanual-manipulation benchmark (arXiv 2507.00435).
Built by replaying RoboEval's lightweight demos (seed + action) with a camera on and rendering the observations, then packing to an openpi-native LeRobot v2.1 dataset.
- 4135 episodes, ~5.47M frames, 33 task variants (10 language instructions), bimanual Panda
- Features:
observation.images.external(224×224),observation.state(38),action(16, absolute joint), per-episode task prompt - ~15 GB
Why tar shards
A LeRobot dataset is ~8k small files (one parquet + one mp4 per episode), which trips Hugging Face's
upload API rate limits. It's shipped here as roboeval_all.tar.part00, part01, … (4 GB each, no
compression — the mp4/parquet are already compressed).
Download & reassemble
huggingface-cli download ethenj/roboeval_all --repo-type dataset --local-dir /tmp/roboeval_tar
mkdir -p ~/lerobot-cache/roboeval
cat /tmp/roboeval_tar/roboeval_all.tar.part* | tar xf - -C ~/lerobot-cache/roboeval/
# -> ~/lerobot-cache/roboeval/roboeval_all (a standard LeRobot v2.1 dataset)
Use
Full fine-tuning + eval code: https://github.com/EthenJ/roboeval-pi05
License: Apache-2.0. Derived from RoboEval (Apache-2.0) and openpi (Apache-2.0). π0.5 weights are distributed separately by Physical Intelligence.
- Downloads last month
- 7