humanoidsdata.com

Search

Search companies, datasets, articles, and glossary terms for humanoids and embodied AI.

← All glossary terms

Models & learning

Dataset aggregation

Dataset aggregation is an interactive imitation-learning method that repeatedly runs the current learner, asks an expert to label the states that learner actually visits, and adds those state-action examples to a cumulative training dataset. The canonical algorithm is DAgger; it reduces train-deployment distribution shift but still depends on an expert, a safe collection environment, and faithful labels.

Also known as: DAgger, data aggregation algorithm

Updated

The learner collects the states that need labels

Ordinary behavioural cloning trains on a fixed set of expert demonstrations. At deployment, a small prediction error can move the learner into a state the expert dataset rarely contains. Later predictions then have to operate outside the distribution on which they were trained.

DAgger changes the collection loop. It runs the current policy, records the states produced by that policy, queries an expert for the action that should be taken in each state, aggregates those examples with earlier data, and retrains. Repeating this process makes training data reflect the learner's own state distribution rather than only clean expert trajectories.

The expert can be a person, controller, planner, simulator policy, or other system able to label the visited state. Dataset aggregation describes how examples enter the training set; it does not specify the model architecture or require reinforcement learning.

DAgger is interactive even when the learner is not updated online

The deployed policy may remain fixed during one collection rollout. The process is interactive because later training data depends on states visited by the learner, and the newly aggregated labels affect a later policy revision.

This differs from online robot exploration, where environment outcomes may teach the system without an expert action label. It also differs from ordinary policy distillation on a fixed teacher dataset. DAgger queries the teacher on student-induced states.

In OmniInteract, a shared flow policy controls two simulated humanoids above a frozen motion tracker. At every paired state the student visits, the relevant residual expert labels one corrective action for each humanoid before the simulator advances. Those two examples update the same student. The task identity routes the teacher but is withheld from the student input.

Aggregation moves rather than removes collection risk

DAgger needs a way to visit imperfect-policy states without unacceptable harm. A physical robot may require a simulator, supervisor, shield, recovery controller, emergency stop, or a mixture schedule that limits learner control. Expert labels can also be delayed, inconsistent, or impossible for unsafe states.

A reusable aggregation record should retain the policy revision, rollout seed, observation, learner action, expert label, expert identity and version, intervention, timing, safety event, and dataset round. Mixing labels from different experts or policy versions without provenance makes later failures difficult to diagnose.

Sources