Datasets:

AlayaLab
/

EditHero

pretty_name: EditHero
license: other
license_name: mixed-cc
license_link: https://huggingface.co/datasets/AlayaLab/EditHero/blob/main/LICENSE-DATA.md
task_categories:
  - image-to-3d
  - text-to-3d
  - image-to-image
  - image-text-to-text
language:
  - en
tags:
  - 3d
  - 3d-editing
  - 3d-generation
  - part-level
  - benchmark
  - multi-turn
  - long-horizon
  - llm
  - vlm
  - agent
  - code-generation
  - vibe-modeling
  - glb
size_categories:
  - 1K<n<10K
configs:
  - config_name: edits
    data_files:
      - split: test
        path: preview/*.parquet

EditHero data

EditHero is a benchmark for long-horizon, part-level 3D editing. Each chain starts from a textured, part-segmented host object and applies a sequence of edits (add, remove, replace, retexture), each with a natural-language instruction and an exact target state. 457 chains, 2,755 edits, 3,212 states, 252 host objects.

Paper and project page: https://alaya-lab.github.io/EditHero/. Code (data engine, rebuild, render script): https://github.com/AlayaLab/EditHero.

Browse

The dataset viewer above shows every edit (2,755 rows): chain, turn, operation, the cond view of the state before and after the edit, the mask of the edited parts in that view, and the instruction. The same table is in preview/*.parquet:

from datasets import load_dataset
edits = load_dataset("AlayaLab/EditHero", "edits", split="test")

sample/ holds one complete chain (A/1a3267df_s0) unpacked, with its instructions (sample/chain.json, sample/README.md).

Download

Everything except the index files comes as uncompressed tars, one per chain family (A, G, M, P, R, X) and per part source. Download what you need and extract it in the same folder; the tars recreate the data/ layout below.

huggingface-cli download AlayaLab/EditHero --repo-type dataset --local-dir EditHero
cd EditHero && for t in data/*/*.tar; do tar -xf "$t" && rm "$t"; done
# only some of it, e.g. the renders and part masks:
huggingface-cli download AlayaLab/EditHero --repo-type dataset --local-dir EditHero --include "data/renders/*" "data/part_masks/*" "data/*.json"

Layout

Path	Contents
`data/chains.json`	Index of the chains: host object, operations, instructions, licenses of the source objects the chain uses
`data/cameras.json`	Fixed four-view camera rig per chain. View 0 is the conditioning view (`cond`), views 1-3 are held out (`heldout`)
`data/states/<chain>/turnNN.glb`	The correct state after every turn (turn00 is the initial object)
`data/renders/<chain>/turnNN/view{0..3}_{cond,heldout}.png`	Every state rendered with the chain's rig (420 x 420, RGBA)
`data/part_masks/<chain>/turnNN/{source,target,edit}_view{0..3}_{cond,heldout}.png`	Pixels of the parts edited in turn NN, in the same four views: `source` = those parts in the previous state, `target` = in the new state, `edit` = union. `masks.json` per chain lists the edited nodes and pixel counts
`data/recipes/<chain>/`	The recipe of each chain (`place_report.json`, `turn00_manifest.json`, `checks.json`, `provenance.json`) and the derived files it uses (retexture bakes, part copies repaired during review)
`data/parts/`	Every part the recipes use: `partverse_xl/<object>/<part>.glb` from PartVerse-XL, `hy3d/<object>/<part>.glb` from HY3D-Bench (textured by us)
`ATTRIBUTION.csv`	Every source object: uid, source, title, author, URL, license, chains that use it

An editing method gets the instruction and, if it takes an image, the cond view of the target state. The heldout views are for checking the result from angles the method never saw.

Rebuild and render

The states and renders are included, so nothing has to be rebuilt to use the data. To regenerate a chain from its recipe and verify it with the code repository:

python part_assembly/tools/assemble.py --pv-root data/parts/partverse_xl --hy3d-root data/parts/hy3d \
    --chain data/recipes/A/1a3267df_s0 --out out/A_1a3267df_s0
# PASS A/1a3267df_s0 (verified vs checks.json)

Every state is verified node by node (vertex count, sum of |v|, texture hashes) against checks.json. All renders were made with blender_kit (Blender 4.2, Cycles); scripts/render_state.py in the code repository renders any state, or your own edited GLB, with a chain's rig. If blender_kit saves you an afternoon of arguing with Blender, a ⭐ on it would make its author's day.

Licenses

See LICENSE-DATA.md.