Datasets:
Create reconstruction.md
Browse files- metadata/reconstruction.md +29 -0
metadata/reconstruction.md
ADDED
|
@@ -0,0 +1,29 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# SFT-Eval Split Reconstruction
|
| 2 |
+
|
| 3 |
+
## Relevant Assets
|
| 4 |
+
|
| 5 |
+
- QA rows for `eval split` and `sft split` in splits/
|
| 6 |
+
- Split manifests and split counts in splits/
|
| 7 |
+
|
| 8 |
+
## How to inteprete the QA rows
|
| 9 |
+
|
| 10 |
+
Each row exposes three reconstruction-oriented fields:
|
| 11 |
+
|
| 12 |
+
- `visual_ref`
|
| 13 |
+
- `source_episode_ref`
|
| 14 |
+
- `reconstruction_key_json`
|
| 15 |
+
|
| 16 |
+
These are designed to be stable, path-free references. They are sufficient to map a released item back to the corresponding source episode or recording once you have obtained the upstream dataset under its original terms.
|
| 17 |
+
|
| 18 |
+
## Source-specific units
|
| 19 |
+
|
| 20 |
+
- `GM-100`: grouped by `(task_id, episode_id)`.
|
| 21 |
+
- `RH20T`: grouped by `recording_id`.
|
| 22 |
+
- `REASSEMBLE`: grouped by `recording_id`.
|
| 23 |
+
- `AIST-Bimanual`: grouped by `recording_id`.
|
| 24 |
+
|
| 25 |
+
## Expected workflow
|
| 26 |
+
|
| 27 |
+
1. Obtain upstream datasets under their original terms.
|
| 28 |
+
2. Use `source`, `source_task_id`, `source_unit_id`, `camera`, and `frame_indices_json` from the public release.
|
| 29 |
+
3. Reconstruct the required visual inputs with the source-specific evaluation scripts in the main codebase.
|