Clarification on RoboMimic suboptimal classifier training: mixed-task or per-task?

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python

Research direction

Start with curation/scripts/subop_train_robomimic.sh and the HDF5Dataset implementation described in the issue. Compare the paper's RoboMimic experiment setup with how data_dir recursively discovers and interleaves HDF5 files. Done means documenting whether classifiers are trained jointly or per task and showing the correct directory layout.

Written by the indexing model from the issue text.

Description

Hi, thanks for releasing the SCIZOR code.

I have a question about the RoboMimic suboptimal classifier training script:

curation/scripts/subop_train_robomimic.sh

In this script, the training data is specified by:

--config.hdf5_dataset_kwargs.data_dir PATH_TO_ROBOMIMIC_HDF5_DATASET_FOLDER

From my reading of the code, HDF5Dataset recursively walks through data_dir and loads all .hdf5 files under that directory:

for root, dirs, files in os.walk(self.hdf5_config['data_dir']):
    for file in files:
        if file.endswith('.hdf5'):
            self.paths.append(os.path.join(root, file))

Then all discovered HDF5 files are wrapped as sub-datasets and interleaved for training.

I would like to clarify the intended RoboMimic setup used in the paper:

For the RoboMimic experiments, was the suboptimal classifier trained jointly on multiple tasks, e.g. Can MH + Square MH, or was a separate suboptimal classifier trained for each task?

Should users point data_dir to a root folder containing multiple RoboMimic tasks, such as:

robomimic_data/
├── can/mh/*.hdf5
└── square/mh/*.hdf5

or should they run subop_train_robomimic.sh separately with task-specific folders, such as:

robomimic_data/can/mh/
robomimic_data/square/mh/

Thanks! This clarification would be very helpful for reproducing the RoboMimic results and for understanding how to set up data_dir correctly.

Dominant language
Python
Stars
28
Forks
3
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from UT-Austin-RPL/SCIZOR

All issues in UT-Austin-RPL/SCIZOR

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.