PTENES
Start / Fundamentals / Module 1.4
MODULE 1.4

🗄️ Datasets: Open X-Embodiment and DROID

The data that powers VLAs — scale, diversity, and format. From millions of robot trajectories to the RLDS pipeline that transforms raw collection into foundation models.

6
Topics
~35 min
Duration
Basic
Level
Data
Category
Data Pipeline: Raw Trajectories → RLDS → Generalist VLA Open X-Embodiment 1M+ traj · 22 embodiments DROID 76k trajectories · 564 in-the-wild scenes BridgeData V2 60k trajectories · household RLDS pipeline Episodes → Steps Observation · Action · Reward TFDS · shuffle · prefetch Normalization Action space · tokens VLA Generalist multi-robot 21 institutions · teleoperation · data scaling laws · quality > quantity
1

🌐 Open X-Embodiment: the dataset that changed everything

Open X-Embodiment (OXE) is the largest collaborative robotics data effort ever undertaken. More than 1 million trajectories collected by 21 institutions, covering 22 different embodiments—from industrial arms to bipedal robots. It’s the foundation that made generalist VLAs possible.

Why OXE is a historic milestone

22
Embodiments

Franka, UR, Kuka, Spot, Hello Robot, and more — diverse bodies in a single dataset.

21
Institutions

Google, Stanford, Berkeley, CMU, and others collaborating on an open dataset.

1M+
Trajectories

Each trajectory is a sequence of steps with an observation, action, and language metadata.

✓ What OXE enables

  • ✓ Cross-embodiment pretraining (RT-X, OpenVLA)
  • ✓ Transfer learning across robots from different families
  • ✓ Reproducible research with a common baseline
  • ✓ Study of scaling laws for robotics

✗ Real OXE limitations

  • ✗ Uneven distribution: some robots have 10x more data
  • ✗ Controlled laboratory environments — little in-the-wild testing
  • ✗ Quality varies across contributors
  • ✗ Inconsistent language annotations across institutions
Cross-embodiment learning

Training on a multi-robot dataset lets the model learn policies that transfer across different bodies.

RT-X

A family of Google models trained on OXE; showed that collaborative data outperforms isolated proprietary data.

Robotic trajectory

Episodic sequence of (observation, action, reward) that records how a robot performed a task.

Data scaling law

Empirical pattern: more diverse trajectories → better generalization. But diversity matters more than raw volume.

2

🏙️ DROID: in-the-wild diversity

The DROID (Distributed Robot Interaction Dataset) offers something OXE doesn’t: uncontrolled real-world environments. With 76 thousand trajectories across 564 distinct scenes—offices, kitchens, bathrooms—and a single standardized piece of hardware (Franka arm), DROID is the largest openly available in-the-wild manipulation dataset.

📊 DROID numbers

76k
Trajectories
564
Distinct scenarios
86
Tasks
1
Hardware (Franka)

💡 Why a single robot is an advantage

Using only the Franka eliminates hardware variance. The only diversity factor is the environment — exactly what we want to study. The model learns to generalize to new spaces, not new bodies. This is the right abstraction for environmental robustness research.

✓ DROID excels at

  • ✓ Robustness to lighting and layout variations
  • ✓ Deployment in non-laboratory environments
  • ✓ Fast fine-tuning for new spaces

✗ DROID limitations

  • ✗ Only 86 tasks — low semantic diversity
  • ✗ Single-arm only — no bimanual control or locomotion
  • ✗ Does not generalize across embodiments on its own
In-the-wild

Data collected in real, uncontrolled environments, with objects and scenarios that were not prepared — the opposite of a lab setting.

Distributed collection

Coordinated collection across multiple sites using the same hardware and protocol, ensuring consistency despite diverse environments.

3

🍳 BridgeData V2: kitchen-scale manipulation

BridgeData V2 is the dataset that proves accessible, reproducible data collection works. With more than 60,000 trajectories collected with a low-cost WidowX arm and focused on kitchen household tasks, it became the standard benchmark for fine-tuning and cross-evaluation among VLAs.

How BridgeData evolved:

V1
BridgeData V1 (2022)

First ~7k trajectories with WidowX. Shows the feasibility of low-cost data collection for household manipulation.

V2
BridgeData V2 (2023)

Scales to 60k+ trajectories, diversifies tasks and kitchen environments. Integrated into OXE as a subset.

Today
Current use as a benchmark

Standard for evaluating VLA transfer, comparing fine-tuned policies, and testing language instruction generalization.

💡 WidowX as proof of concept

The WidowX costs ~$3,000 — a fraction of the cost of industrial arms. BridgeData proves that the barrier to data collection isn’t expensive hardware, but protocol consistency e a task variety. This democratized VLA research beyond the major labs.

Task diversity

A variety of tasks within the same environment provides a rich signal for language-action alignment.

Fine-tuning benchmark

BridgeData is the standard dataset for measuring how well a generalist VLA adapts to new home environments.

Low-cost collection

Low-cost hardware + consistent protocol = scalable data collection. The robot's cost does not determine the quality of the data.

4

📦 RLDS / TFDS format

RLDS (Reinforcement Learning Datasets) is the de facto standard for robotic data. Built on TFDS (TensorFlow Datasets), it organizes trajectories as sequences of episodes with structured steps—enabling efficient streaming of datasets with millions of trajectories.

Structure of an RLDS episode Episode Step t obs: img + state action: [Δx,Δy,Δz,…] reward · done · info Step t+1 obs: img + state action: [Δx,Δy,Δz,…] reward · done · info ··· Step N obs: img + state action: [0,0,0,…] ← stop done = True TFDS shuffle + prefetch batch · cache efficient streaming

💡 Action normalization: the critical step

Each dataset has its own action space: torque commands, joint velocities, delta position, absolute coordinates. To combine OXE + DROID + BridgeData in a single training run, you need to normalize all actions to the same range. This single step determines whether fine-tuning will converge or diverge.

Episode

Complete sequence of steps for a task: from the initial state to completion (success or failure). Basic unit of learning by imitation.

Step

A single timestep: current observation → action taken → reward received → next state. The granularity of learning.

TFDS streaming

Loads data from disk on demand without needing everything in RAM. Enables training on millions of trajectories with limited hardware.

Observation keys

Standardize names such as image_primary, state, action is required to combine heterogeneous datasets in a single DataLoader.

5

🎮 Data Collection via teleoperation

Almost all VLA data comes from human teleoperation: one operator controls the robot in real time while observations and actions are recorded. Operator quality, the collection setup, and demonstration density directly affect the learned policy.

Teleoperation methods compared

Joystick / SpaceMouse
Simpler setup. The operator controls it with a 6DoF mouse. Low latency, but a moderate learning curve. Used in DROID and OXE.
Kinesthetic teaching
The operator physically guides the robot arm. Produces natural, smooth trajectories. High cost per demonstration. Good for precise tasks.
Exoskeleton / ALOHA
The operator uses a master arm that mirrors the robot arm. Intuitive and captures nuances of human movement. Used in ALOHA and ACT.
VR / mocap
Virtual reality tracks the operator’s hands. Maximum naturalness, but requires expensive hardware and complex setup.

✓ Data collection best practices

  • ✓ Smooth demonstrations, without excessive hesitation
  • ✓ Vary the objects' initial positions between episodes
  • ✓ Include failure recovery (recovery demos)
  • ✓ Multiple operators to cover different styles

✗ Common data collection errors

  • ✗ Repeated hesitation "contaminates" the policy with pauses
  • ✗ Fixed position → robot learns the position, not the task
  • ✗ Ignore failure episodes that could be informative
  • ✗ Single operator → movement-style bias

💡 The effect of hesitation on the policy

If the operator hesitates before grasping an object, the model learns that hesitation is part of the policy. The robot will pause before each grasp—even when it doesn't need to. Clean, fluent demonstration data produce more decisive and robust policies than abundant but highly hesitant data.

6

⚖️ Quality vs. Quantity and Scaling Laws

In NLP, more data = better model is almost always true. In robotics, the relationship is more subtle: diversity and quality outweigh raw volume. Understanding the scaling laws for robotic data is essential to avoid wasting collection resources.

📊 What scaling laws tell us about robotic data

→

Double the data volume of same environment delivers diminishing marginal gains after a certain point.

→

Add new task types or new ones environments delivers consistent gains even with few new demos.

→

Poor-quality data (hesitation, collisions, anomalous trajectories) does more harm than good — filtering is important.

→

Larger models make better use of large datasets—but small models can saturate with just 10k high-quality demos.

✓ Efficient data strategy

  • ✓ Prioritize task diversity over volume
  • ✓ Filter episodes with anomalies (collisions, timeouts)
  • ✓ Balance datasets when mixing sources (OXE + DROID)
  • ✓ Measure the action distribution before training

✗ Pitfalls of large datasets

  • ✗ Assume that more demos always = a better policy
  • ✗ Mix datasets without normalizing action spaces
  • ✗ Ignore the imbalance (90% grasping, 10% releasing)
  • ✗ Does not check for correlations between language and action in the data

💡 Emergent capabilities at scale

VLAs trained on the full OXE show capabilities that do not appear in smaller subsets: task composition, generalization to unseen objects, and following ambiguous instructions. These abilities emergent emerge at scale — but only if the source data covers sufficient semantic diversity, not just volume.

Scaling laws in robotics

Empirical relationship between data volume, model size, and performance. In robotics, task diversity scales better than sheer volume.

Data balancing

A sampling technique that ensures smaller datasets (BridgeData) aren’t eclipsed by larger datasets (OXE) during training.

Emergent capabilities

Abilities that emerge in larger models trained on more data without being explicitly programmed — zero-shot generalization, task composition.

Episode filtering

Process of removing anomalous trajectories, collisions, and low-quality demonstrations before training. Has a disproportionate impact on the quality of the final policy.

✅ Module Summary

✓
OXE and DROID are complementary — OXE provides cross-embodiment scale; DROID provides in-the-wild environmental diversity.
✓
RLDS is the standard format — structured step episodes + TFDS enable efficient training on datasets with millions of trajectories.
✓
Teleoperation is the primary source — the quality and fluency of human demonstrations directly affect the learned policy.
✓
Diversity > volume — scaling laws in robotics favor a variety of tasks and environments over simply accumulating trajectories.

Next module

1.5 — Hardware: Cobots, Humanoids, and Platforms