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.
hexgen — abc_v1 training data
Training pairs for a decoder that reads a CAD solid and emits a program which
compiles to a hexahedral finite-element mesh. Exported from the hexgen-corpora
Modal Volume by modal_app/share_corpus_fn.py.
| path | contents | size |
|---|---|---|
hexgen_abc_v1/pairs.jsonl |
133,238 (part, program) training records, one JSON object per line | 2,335 MB |
hexgen_abc_v1/holdout_graphs.tar.gz |
10,179 .brepgraph.json — held-out CAD parts, never trained on |
188 MB raw |
hexgen_abc_v1/holdout_tess.tar.gz |
10,179 .tess.json — the same parts triangulated, matched by filename |
186 MB raw |
hexgen_abc_v1/export_summary.json |
export provenance | 838 B |
A .brepgraph.json describes one CAD solid: faces with surface type and
parameters, edges with curves, vertices with positions, and the loops tying them
together. A .tess.json is that solid as triangles; the mesh-vs-CAD tools take
the two as a pair.
uvx hf download hexproj-collab/hexgen-share --repo-type dataset --local-dir ./hexgen-data
cd hexgen-data/hexgen_abc_v1
mkdir -p holdout_graphs holdout_tess
tar xzf holdout_graphs.tar.gz -C holdout_graphs
tar xzf holdout_tess.tar.gz -C holdout_tess
Do not regenerate the .tess.json files. They were produced by the CAD kernel
on x86 and are frozen; tessellation is not reproducible across architectures, so
rebuilding them on ARM silently changes every downstream score.
- Downloads last month
- 15