Robots Atlas>ROBOTS ATLAS
Data

Weak Pair Data

2026ActivePublished: 23 September 2026Updated: 23 September 2026Published
Key innovation
Names and isolates the cheapest, most abundant kind of human–robot data — matching only in task intent — in order to clearly separate it from genuinely synchronized data.
Category
Data
Abstraction level
Pattern
Operation level
TrainingRobot control
Use cases
Cheap, large-scale collection of demonstration dataInitial pre-training on human dataBaseline for assessing paired-data qualityAnalysis of the embodiment gap

How it works

Human recordings and robot executions are collected for the same task description, independently of one another — at different times, often in different scenes and at different speeds. The result is a dataset where correspondence exists at the task-label level but not at the frame or state level. A model trained on such data must infer the visual mapping (human hand vs gripper) and the kinematic one (a different motion profile) by itself, which is the source of the embodiment gap. PsiBot points out that moving from this regime to strongly paired data — rather than further increasing the number of recorded hours — was the key change in the Psi-R2.5 training pipeline.

Problem solved

Weak pair data does not itself solve a problem — it is the cheap default way of collecting human–robot data. The concept solves a terminological problem: it lets you state precisely what such data lacks (temporal alignment and scene consistency) and why the sheer scale of human footage does not translate into robot policy quality.

Components

Semantic intent matchThe pair's only condition

The human recording and the robot execution concern the same task in the sense of its description, with no further requirements.

Absence of temporal alignmentThe distinguishing feature versus strong pair data

There is no frame-to-frame or state-to-state correspondence between the demonstration and the execution.

Implementation

Implementation pitfalls
The illusion of scaleHigh

Increasing the number of hours of weakly paired footage does not remove the embodiment gap and yields diminishing returns in policy quality.

Fix:Invest in pair alignment and validation rather than in additional hours of footage.
Confusing it with strong pair dataMedium

A dataset labelled "paired" is often in fact weakly paired, if temporal alignment, scene consistency and action replayability were never checked.

Fix:Require an explicit robot replay test for the actions as the dataset classification criterion.

Evolution

2026
Concept introduced together with the Psi-R2.5 model

PsiBot defined weak pair data in the Psi-R2.5 technical blog as the contrast to strong pair data.