Update README.md
Browse files
README.md
CHANGED
|
@@ -10,7 +10,7 @@ license: other
|
|
| 10 |
|
| 11 |
# VLAC2 Benchmark Release
|
| 12 |
|
| 13 |
-
VLAC2 is a video-progress benchmark for long-horizon robot manipulation. This release provides benchmark JSON files
|
| 14 |
|
| 15 |
## Contents
|
| 16 |
|
|
@@ -22,17 +22,22 @@ VLAC2 is a video-progress benchmark for long-horizon robot manipulation. This re
|
|
| 22 |
- `scripts/extract_vlac2_release_raw_archives.sh`
|
| 23 |
- `scripts/extract_vlac2_release_frames.py`
|
| 24 |
- `scripts/vlac2_release_common.py`
|
| 25 |
-
- `
|
|
|
|
| 26 |
|
| 27 |
## Usage
|
| 28 |
|
| 29 |
-
1. Unpack
|
| 30 |
|
| 31 |
```bash
|
| 32 |
-
bash scripts/extract_vlac2_release_raw_archives.sh
|
|
|
|
|
|
|
| 33 |
```
|
| 34 |
|
| 35 |
-
|
|
|
|
|
|
|
| 36 |
|
| 37 |
```bash
|
| 38 |
python scripts/extract_vlac2_release_frames.py --release-root /path/to/vlac2_release
|
|
@@ -40,10 +45,11 @@ python scripts/extract_vlac2_release_frames.py --release-root /path/to/vlac2_rel
|
|
| 40 |
|
| 41 |
If `--output-root` is not specified, extracted frames are written to `/path/to/vlac2_release/_extracted_frames/`, which is created automatically by the script.
|
| 42 |
|
| 43 |
-
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
|
| 44 |
|
| 45 |
## Notes
|
| 46 |
|
| 47 |
- The benchmark JSON files are ready to use; users do not need to rebuild them.
|
| 48 |
- A video decoder backend is required for frame extraction: `opencv-python` or `imageio`.
|
| 49 |
-
-
|
|
|
|
|
|
| 10 |
|
| 11 |
# VLAC2 Benchmark Release
|
| 12 |
|
| 13 |
+
VLAC2 is a video-progress benchmark for long-horizon robot manipulation. This release provides the benchmark JSON files, the minimal raw-video subset required by the released protocol, and a lightweight frame-extraction workflow for reproducible evaluation.
|
| 14 |
|
| 15 |
## Contents
|
| 16 |
|
|
|
|
| 22 |
- `scripts/extract_vlac2_release_raw_archives.sh`
|
| 23 |
- `scripts/extract_vlac2_release_frames.py`
|
| 24 |
- `scripts/vlac2_release_common.py`
|
| 25 |
+
- `video_archives/vlac2_benchmark_train_main_path_videos.tar`
|
| 26 |
+
- `video_archives/vlac2_benchmark_test_main_path_videos.tar`
|
| 27 |
|
| 28 |
## Usage
|
| 29 |
|
| 30 |
+
1. Unpack the benchmark video archives into `vlac2_release_data/`.
|
| 31 |
|
| 32 |
```bash
|
| 33 |
+
bash scripts/extract_vlac2_release_raw_archives.sh \
|
| 34 |
+
/path/to/vlac2_release/video_archives \
|
| 35 |
+
/path/to/vlac2_release/vlac2_release_data
|
| 36 |
```
|
| 37 |
|
| 38 |
+
If both arguments are omitted, the script defaults to `video_archives/` and extracts into `vlac2_release_data/` under the release root.
|
| 39 |
+
|
| 40 |
+
2. Extract benchmark frames from the unpacked raw videos.
|
| 41 |
|
| 42 |
```bash
|
| 43 |
python scripts/extract_vlac2_release_frames.py --release-root /path/to/vlac2_release
|
|
|
|
| 45 |
|
| 46 |
If `--output-root` is not specified, extracted frames are written to `/path/to/vlac2_release/_extracted_frames/`, which is created automatically by the script.
|
| 47 |
|
| 48 |
+
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.
|
| 49 |
|
| 50 |
## Notes
|
| 51 |
|
| 52 |
- The benchmark JSON files are ready to use; users do not need to rebuild them.
|
| 53 |
- A video decoder backend is required for frame extraction: `opencv-python` or `imageio`.
|
| 54 |
+
- This repo only contains the raw videos required by the released benchmark splits. The full raw-data release is distributed separately.
|
| 55 |
+
- The raw-video subset and the extracted-frame cache are intentionally separated so that users can regenerate frames locally under their own storage layout.
|