Update README.md for direct data extraction layout

README.md

@@ -27,15 +27,15 @@ VLAC2 is a video-progress benchmark for long-horizon robot manipulation. This re
 
 ## Usage
 
-1. Unpack the benchmark video archives into `vlac2_release_data/`.
+1. Unpack the benchmark video archives directly into `data/`.
 
 ```bash
 bash scripts/extract_vlac2_release_raw_archives.sh \
   /path/to/vlac2_release/data \
-  /path/to/vlac2_release/vlac2_release_data
+  /path/to/vlac2_release/data
 ```
 
-If both arguments are omitted, the script defaults to `data/` and extracts into `vlac2_release_data/` under the release root.
+If both arguments are omitted, the script defaults to `data/` and extracts into `data/` under the release root.
 The script expects exactly the released benchmark archives: `test_videos.tar` and `train_videos.tar` (or their `.tar.zst` variants).
 
 2. Extract benchmark frames from the unpacked raw videos.
@@ -44,6 +44,7 @@ The script expects exactly the released benchmark archives: `test_videos.tar` an
 python scripts/extract_vlac2_release_frames.py --release-root /path/to/vlac2_release
 ```
 
+Here `--release-root` should be the top-level release directory that contains `README.md`, `benchmark_splits/`, `data/`, and `scripts/`.
 If `--output-root` is not specified, extracted frames are written to `/path/to/vlac2_release/_extracted_frames/`, which is created automatically by the script.
 
 3. Use the benchmark files for training or evaluation. Frame paths in the JSONs use the prefix `__VLAC2_FRAMES_ROOT__/...`. Replace `__VLAC2_FRAMES_ROOT__` with the absolute path of the extracted-frame directory. For example, if extracted frames are written to `/data/VLAC2-Benchmark/_extracted_frames`, then `__VLAC2_FRAMES_ROOT__/ARX-data/...` becomes `/data/VLAC2-Benchmark/_extracted_frames/ARX-data/...`. If you choose a custom `--output-root`, substitute that directory instead.