Dataset Viewer
The dataset viewer is not available for this subset.
Cannot get the split names for the config 'default' of the dataset.
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.12/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
                  for split_generator in builder._split_generators(
                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/packaged_modules/folder_based_builder/folder_based_builder.py", line 246, in _split_generators
                  raise ValueError(
              ValueError: `file_name`, `*_file_name`, `file_names` or `*_file_names` must be present as dictionary key in metadata files
              
              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 65, in compute_split_names_from_streaming_response
                  for split in get_dataset_split_names(
                               ^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
                  info = get_dataset_config_info(
                         ^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/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.

DONUT (Dataset Of MaNifold strUcTures)

This repository contains a dataset of 3D samples made of watertight meshes and corresponding point clouds. Each sample is composed of one or several watertight mesh components and one 8192-point cloud representation.

The dataset contains 29,517 samples in total.

Overview

The figure below shows a few samples from the dataset together with their labels.

A few DONUT samples and their labels

Contents

The repository is organized as follows:

.
├── metadata.csv
├── obj/
│   ├── shard_0/
│   ├── shard_1/
│   └── shard_2/
└── pcd/
    ├── shard_0/
    ├── shard_1/
    └── shard_2/
  • obj/ contains the mesh files as .npz archives.
  • pcd/ contains the point clouds as .npy files.
  • metadata.csv contains one row per sample with topological metadata.

There are 29,517 mesh files in obj/ and 29,517 point cloud files in pcd/.

File Format

Meshes

Each mesh sample is stored as an .npz file in obj/. The archive contains:

  • vertices.npy
  • faces.npy

A sample may contain one or several watertight connected mesh components.

Point Clouds

Each point cloud sample is stored as a .npy file in pcd/.

Each point cloud contains 8192 points and corresponds to the sample with the same id.

Sample Identification

Each sample is identified by a unique id string.

The same id is used in:

  • the filename in obj/
  • the filename in pcd/
  • the id column in metadata.csv

For example, if a sample has id abc123, its files are:

  • obj/.../abc123.npz
  • pcd/.../abc123.npy

Metadata

metadata.csv contains the following columns:

  • id: unique identifier of the sample
  • genus: total number of holes across all mesh components in the sample
  • components: total number of connected mesh components in the sample
  • sample_code: array of 6 integers describing how many components of each genus are present

Meaning of sample_code

sample_code is an array of 6 integers:

[n0, n1, n2, n3, n4, n5]

Here, ni is the number of mesh components in the sample whose genus is i.

So:

  • n0 is the number of genus-0 components
  • n1 is the number of genus-1 components
  • n2 is the number of genus-2 components
  • n3 is the number of genus-3 components
  • n4 is the number of genus-4 components
  • n5 is the number of genus-5 components

From sample_code, the metadata values are computed as:

genus = sum(i * ni for i in [0, 1, 2, 3, 4, 5])
components = sum(ni for i in [0, 1, 2, 3, 4, 5])

In other words:

  • genus is the total number of holes in the full sample
  • components is the total number of connected components in the full sample

The distribution of labels in the dataset is shown below.

Distribution of DONUT labels

Examples

sample_code = [2, 1, 0, 0, 0, 0]

This means:

  • 2 components of genus 0
  • 1 component of genus 1
  • total genus = 0 * 2 + 1 * 1 = 1
  • total components = 2 + 1 = 3

Summary

DONUT is a dataset of 29,517 samples of manifold 3D structures.

Each sample provides:

  • one mesh file in .npz format
  • one 8192-point cloud in .npy format
  • one metadata entry in metadata.csv

The metadata describes the global topology of each sample through its total genus, number of connected components, and component-wise genus distribution.

Downloads last month
12,043