BridgeData V2
A broad collection of robot manipulation trajectories spanning tasks, objects, and environments.
About
BridgeData V2 is designed around diversity in everyday manipulation. The corpus is useful for studying how policies transfer across task descriptions, scenes, and object configurations.
A focused visual audit can reveal how camera placement, action ranges, and episode boundaries vary. Those details matter when combining the data with another robot corpus.
Suggested agent workflows
Copy a prompt into your agent of choice. Each workflow starts small, respects the source terms, and makes the result inspectable in Rerun.
Audit a training slice
Fetch BridgeData V2 from its official source at https://rail-berkeley.github.io/bridgedata/. Read and preserve its source terms and citation requirements. Build a reproducible manifest for a representative slice, then load it into Rerun. Inspect the RGB video, Robot state, Actions streams for timestamp gaps, missing samples, calibration problems, and annotation inconsistencies. Summarize the findings and save both the validation script and a Rerun recording that makes every issue easy to review.
Build a baseline pipeline
Use BridgeData V2 to scaffold a baseline pipeline for Imitation learning, Manipulation. Start with a small deterministic cohort and document the selection criteria. Create the dataset adapter, preprocessing steps, train and validation splits, and one lightweight baseline. Log inputs, labels, predictions, losses, and representative failures to Rerun so I can inspect the full experiment timeline. Include exact setup and reproduction commands.
Find useful failure cohorts
Analyze BridgeData V2 and propose a practical cohort taxonomy for Imitation learning, Manipulation. Use available metadata and the RGB video, Robot state, Actions signals to identify hard cases, rare conditions, coverage gaps, and possible leakage between splits. Materialize the cohorts as queryable metadata, log examples from each cohort to Rerun, and produce a short report explaining which cohorts should become regression tests. Do not infer labels that are not present in the source data.