Dataset card

README.md

@@ -35,17 +35,27 @@ configs:
 
 # 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.
+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, in six families: A (additions), P (replacements),
+R (removals), M (material changes), G (mixed geometry edits) and X (geometry and material edits mixed).
 
-Paper and project page: https://alaya-lab.github.io/EditHero/. Code (data engine, rebuild, render script):
+Paper and project page: https://alaya-lab.github.io/EditHero/. Code (data engine, rebuild, rendering, annotation):
 https://github.com/AlayaLab/EditHero.
 
+## What is in a chain
+
+For every turn: the instruction (English and Chinese), the 3D state after the turn (GLB), renders of that state from
+four fixed views, and masks of the parts the turn edited. For the chain: the recipe that rebuilds every state exactly
+from the parts, and the source objects with their licenses.
+
+An editing method gets the instruction and, if it takes an image, the `cond` view (view 0) of the target state. The
+three `heldout` views are for checking the result from angles the method never saw.
+
 ## 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`:
+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`:
 
 ```python
 from datasets import load_dataset
@@ -56,8 +66,9 @@ edits = load_dataset("AlayaLab/EditHero", "edits", split="test")
 
 ## Download
 
-Everything except the index files and the captions comes as uncompressed tars, one per chain family (A, G, M, P, R, X), per part source, and one for the annotation files.
-Download what you need and extract it in the same folder; the tars recreate the `data/` layout below.
+The index files and captions are plain files; everything else comes as uncompressed tars, one per chain family
+(A, G, M, P, R, X), one per part source and one for the annotation files. Extract them in the same folder; the tars
+recreate the `data/` layout below.
 
 ```bash
 huggingface-cli download AlayaLab/EditHero --repo-type dataset --local-dir EditHero
@@ -66,7 +77,6 @@ cd EditHero && for t in data/*/*.tar; do tar -xf "$t" && rm "$t"; done
 huggingface-cli download AlayaLab/EditHero --repo-type dataset --local-dir EditHero --include "data/renders/*" "data/part_masks/*" "data/*.json"
 ```
 
-
 ## Layout
 
 | Path | Contents |
@@ -83,27 +93,19 @@ huggingface-cli download AlayaLab/EditHero --repo-type dataset --local-dir EditH
 | `data/annotations/assembly/A/<chain>/` | Every intermediate file of the 97 family-A chains that assemble a host from its own parts: planner input (`parts.json`), assembly plan (`plan.json`), annotator brief, Qwen draft, agent revision, left/right check, relational rewrite and Qwen check of the instructions (shipped as `data/annotations/assembly.tar`). The pipeline and its prompts are in the code repository (`part_assembly/annotate/`) |
 | `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:
-
-```bash
-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)
-```
+## Rebuild, render, build new chains
 
-The instructions in `chains.json` were rewritten from the engine's template sentences (kept in every recipe record as
-`instruction_original`) by the rules in the code repository's `docs/INSTRUCTIONS.md`, and reviewed by us.
+Everything below uses the code repository (https://github.com/AlayaLab/EditHero).
 
-Every state is verified node by node (vertex count, sum of |v|, texture hashes) against `checks.json`. All renders were made with
-[blender_kit](https://github.com/AuroraRyan0301/Blender-Visualization-Skill) (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.
+- **Rebuild and verify.** `bash jobs/rebuild_all.sh EditHero/data out/` regenerates every state from its recipe and checks
+  it node by node (vertex count, sum of |v|, texture hashes) against `checks.json`.
+- **Render.** `scripts/render_state.py` renders any state, or your own edited GLB, with a chain's four-view rig, exactly
+  like the renders here. All renders were made with [blender_kit](https://github.com/AuroraRyan0301/Blender-Visualization-Skill)
+  (Blender 4.2, Cycles). If it saves you an afternoon of arguing with Blender, a ⭐ on it would make its author's day.
+- **Build new chains.** The data engine builds chains on any part-segmented host, with the part library and the captions
+  of this dataset: `docs/DATA_ENGINE.md` in the code repository walks through it step by step.
+- **Instructions.** The instructions were rewritten from the engine's template sentences (kept in every recipe record as
+  `instruction_original`) by the rules in `docs/INSTRUCTIONS.md`.
 
 ## Licenses