Skip to content

Fix training script paths in README and dataset config docs - #69

Open
rakhimovv wants to merge 1 commit into
BeingBeyond:mainfrom
rakhimovv:docs/training-paths-and-dataset-config
Open

rakhimovv wants to merge 1 commit into
BeingBeyond:mainfrom
rakhimovv:docs/training-paths-and-dataset-config

Conversation

@rakhimovv

Copy link
Copy Markdown

Two small documentation fixes.

Summary

  • README training commands point at scripts/train_libero_example.sh; the scripts live under
    scripts/train/. docs/training.md already gives the correct paths.
  • docs/data_configuration.md Steps 3 and 4 describe a schema the code does not accept. Steps 1, 2
    and 5 were already accurate and are unchanged.

Root Cause

1. README paths.

-bash scripts/train_libero_example.sh
+bash scripts/train/train_libero_example.sh

2. Dataset-registration schema.

Step 3 shows DATASET_REGISTRY entries as dicts with path and data_config keys. In
configs/dataset_info.py, DATASET_REGISTRY maps a dataset group name to a dataset class
(LeRobotIterableDataset), and the paths live in a separate DATASET_INFO dict under
{group: {dataset_name: {'dataset_path': ...}}}.

Step 4 shows the YAML as a dataset_config: list of {dataset_name, data_config, weight} entries.
BeingH/train/train.py loads the YAML and BeingH/dataset/base_dataset.py reads it as a top-level
group name whose value carries parallel lists dataset_names / data_config_names /
embodiment_tags, plus sampling options — the shape used by
configs/posttrain/libero/libero_all.yaml.

Following the documented schema produces a config the loader cannot read. The updated text matches
configs/dataset_info.py and the shipped YAML.

Test plan

The corrected Step 3/4 schema was used verbatim to register and train on a LIBERO dataset (10-step
run on libero_spatial, 1×H100), and the documented Step 5 verification command works as written.

README pointed at scripts/train_*.sh; the scripts live under
scripts/train/. docs/training.md already had the correct paths.

docs/data_configuration.md Steps 3 and 4 described a DATASET_REGISTRY
shape and a dataset_config: YAML list that configs/dataset_info.py and
BeingH/dataset/base_dataset.py do not accept. Update both to match the
registry/info split and the parallel-list YAML used by
configs/posttrain/libero/libero_all.yaml.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant