feat(datasets): merge multiple local datasets into a new one - #110
Open
ravediamond wants to merge 1 commit into
Open
ravediamond wants to merge 1 commit into
ravediamond wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #109.
Wraps
lerobot.datasets.dataset_tools.merge_datasets(). NewPOST /merge-datasetsendpoint takes a list of local repo_ids and an output name, loads each dataset (repairing an unfinalized recording first), and writes the merged result to the local cache. Originals are untouched.Added a "Merge" button on the dataset browser page that opens a dialog to pick datasets and name the result — on success it navigates straight to the merged dataset.
Validation only (no dataset merged): need at least 2 datasets, a non-empty output name that doesn't collide with an existing one, same path-traversal guard as delete-dataset.
Tested: pytest (268 + 4 new, all passing), ruff check/format, tsc, eslint, prod build all clean. Not tested manually against real datasets — happy to do that before merge if useful, or if someone with a couple of local datasets handy can try it.