Clarify mesh-only stage identifiers
Browse files
README.md
CHANGED
|
@@ -34,6 +34,8 @@ Each complete group contains the following ordered stages:
|
|
| 34 |
2. `image1_edit1`: the first edited mesh and the instruction applied to the base stage.
|
| 35 |
3. `image2_edit2`: the second edited mesh and the instruction applied to the first edited stage.
|
| 36 |
|
|
|
|
|
|
|
| 37 |
The package provides two manifest views:
|
| 38 |
|
| 39 |
- `manifest/eva01_edit_three_stage.jsonl` contains one record per complete group and preserves the full three-stage chain.
|
|
|
|
| 34 |
2. `image1_edit1`: the first edited mesh and the instruction applied to the base stage.
|
| 35 |
3. `image2_edit2`: the second edited mesh and the instruction applied to the first edited stage.
|
| 36 |
|
| 37 |
+
The `image0_base`, `image1_edit1`, and `image2_edit2` strings are retained as stable stage identifiers from the source manifests. They identify mesh stages only: every stage contains a GLB mesh and prompt metadata. This release does not contain image files and does not provide an image modality.
|
| 38 |
+
|
| 39 |
The package provides two manifest views:
|
| 40 |
|
| 41 |
- `manifest/eva01_edit_three_stage.jsonl` contains one record per complete group and preserves the full three-stage chain.
|