Under review

Scalable Autonomous Robotic Data Collection via Data Affordance-Guided Intervention

BEDA — Bidirectional Evaluation of Data Affordance

Anonymous Submission
Author information is withheld during the review period.
System overview video. Episode-wise autonomous execution, bidirectional data affordance evaluation after each rollout, and affordance-guided decisions on when a human reset is requested.

Abstract

Large-scale robotic learning increasingly relies on diverse real-world interaction data, yet collecting such data remains difficult to scale. Although autonomous collection systems reduce the need for continuous low-level teleoperation, inherent failures and environment degradation still require human intervention when continued execution becomes infeasible. This shifts the bottleneck from controlling the robot to deciding when the environment requires a manual reset. We propose an affordance-guided robotic data collection system that maintains productive scene states by using data affordance: whether the current scene can support the continued collection of a valid interaction dataset. At its core, BEDA (Bidirectional Evaluation of Data Affordance) decomposes scene diagnosis into retrospective evaluation of trajectory validity and prospective evaluation of next-task feasibility. A task-agnostic diagnosis protocol is instantiated with task descriptions to generate task-specific checklists, enabling structured VLM-based evaluation of whether collection should continue or request intervention. Across 15 real-world tabletop tasks, our affordance-guided collection system reaches 84.3% of the throughput upper bound. Scaled multi-robot simulations further show increased operator capacity, with a single operator maintaining 91% of ideal throughput across fleets of up to 128 robots. BEDA's intervention decisions closely align with human oracle labels, and ablations confirm that both retrospective and prospective evaluations are necessary. These results establish affordance-guided intervention as a practical mechanism for scalable long-horizon robotic data collection.

15
real-world tabletop tasks
84.3%
of throughput upper bound
128
robots per operator (sim)
91%
of ideal throughput at scale

Affordance-guided data collection

Intervene when the scene can no longer support valid interaction — not merely when a task fails.

Concept figure: affordance-guided robotic data collection system
Affordance-guided robotic data collection system. The system performs episode-wise autonomous task execution, evaluates the resulting environment state using bidirectional data affordance evaluation, and uses the estimated affordance to decide when intervention is needed.

Method

Bidirectional evaluation turns open-ended failure judgment into two structured checks.

Pipeline overview: execution, bidirectional evaluation, intervention decision
Affordance-guided robotic data collection pipeline. At each episode the robot executes the current task, collects a trajectory, and reaches a post-execution state. BEDA evaluates this candidate state by combining retrospective and prospective evaluation, producing a data affordance score that decides whether to continue autonomous collection or request a reset.

Retrospective evaluation

Looks backward at the episode that just finished: was the collected trajectory a valid piece of interaction data? A nominally successful rollout can still be invalid, and a failed grasp can still leave usable data behind.

Prospective evaluation

Looks forward at the resulting scene: can the next task still be executed from here? Displaced objects, fallen items, or a jammed drawer make continued collection infeasible even after a success.

Infeasible next task
Prospective evaluation flags the scene before the next episode starts.
Degraded environment
Retrospective evaluation rejects the trajectory and triggers intervention.

Real-world data collection

15 real-world manipulation tasks, one hour of autonomous collection per task suite, repeated nine times per strategy. Human interventions happen only when the strategy asks for one.

Normalized data throughput over elapsed collection time for each strategy
(a) Normalized data throughput. BEDA accumulates valid episodes fastest and stays closest to the ideal upper bound.
Average data affordance score over elapsed collection time for each strategy
(b) Average data affordance score. BEDA sustains higher affordance throughout collection, while RADAR degrades to zero once its autonomous reset cannot recover the scene.
Long-horizon data collection performance. Shaded regions denote standard errors. BEDA reaches 84.3% of the upper bound — more than 5× the throughput of RADAR, 36.2% above Unstructured VLM, and 21.1% above Oracle-Period, while requesting no more human interventions than Oracle-Period.
Intervention strategy Data throughput ↑ Execution success ↑ (%) Data affordance ↑ Intervention freq. (/hr)
RADAR0.149 ±0.04816.8 ±5.60.178 ±0.038–
Unstructured VLM0.619 ±0.11660.4 ±11.40.615 ±0.10611.56 ±7.53
Oracle-Period0.696 ±0.08563.9 ±4.40.772 ±0.0708.80 ±1.44
BEDA (ours)0.843 ±0.03082.8 ±4.70.874 ±0.0517.87 ±2.09
Data collection comparison. Averaged across all task suites; mean ± standard error. Data throughput is normalized by the task-specific upper bound, so 0.843 is 84.3% of it.

Downstream utility

A behavior cloning policy trained on the collected demonstrations improves from 38.3% held-out success at N = 50 to 67.5% at N = 300. Under a matched collection-time budget, the policy trained on BEDA data reaches 3.1× lower normalized k-step action prediction error than the reverse transfer.

Evaluation cost

Each bidirectional evaluation takes 3.75 s and about 2,100 tokens per episode. The reported throughput already includes this latency, the reset decision, and manual reset time — so the VLM evaluation is not an added bottleneck in practice.

Both directions are necessary

Removing either half of the bidirectional evaluation costs throughput.

Data throughput over elapsed time for BEDA and the two single-direction variants
(a) Data throughput over elapsed time. Removing either evaluation reduces throughput.
Variant Throughput ↑ Exec. success ↑ (%) Affordance ↑ Interv. freq. (/hr)
Prospective-only0.38723.70.2333.04
Retrospective-only0.65658.30.62126.20
BEDA (both)0.84382.80.8747.87
Ablation on bidirectional evaluation. The prospective-only variant drops validity from the decision, so it continues from feasible scenes without accumulating successful demonstrations. The retrospective-only variant lacks foresight about recoverability and resets even when collection could have continued — it intervenes more than three times as often as BEDA.

Do the decisions match a human?

Intervention decisions compared against human data affordance labels.

Intervention decision accuracy against human labels for each evaluator
Intervention decision accuracy. BEDA reaches 0.903 accuracy — close to AHA-FT (0.937), a failure detector fine-tuned on in-domain data — without any task-specific supervision, and leads every baseline on precision, meaning fewer unnecessary resets. The gains hold across three VLM backbones (GPT-5.4, Claude Sonnet 5, Qwen3-VL).

Where the errors are

Errors concentrate in fine-grained scene assessment — object–object spatial relations judged from correct detections — and in omitted functional state, such as whether a drawer is jammed.

Why they do not compound

Reset-needed states are re-evaluated after every episode, so 92.4% of missed-detection streaks resolve within two evaluations, and invalid demonstrations make up only 2.0% of the accepted data.

Distribution of false-negative streak lengths
False-negative streak lengths. Most missed reset decisions occur as isolated or short streaks.

One operator, many robots

A human-in-the-loop simulation where a single operator oversees parallel robot streams, each becoming reset-needed with probability 0.1 after an episode.

BEDA's decision outcomes are replayed from its measured real-robot decision profile, while evaluator and operator confirmation latencies are measured online.

Normalized throughput against the number of deployed robots
(a) Normalized throughput over deployed robots. BEDA holds 91% of ideal throughput across 1–128 robots; at 256 robots even the ideal strategy approaches operator saturation.
Robot waiting time against the number of deployed robots
(b) Robot waiting time over deployed robots. Affordance-guided intervention keeps robots waiting far less than continuous supervision.

As the fleet grows, continuous supervision becomes bottlenecked by episode-wise checks, and periodic intervention stays limited by delayed detection. Allocating operator attention by affordance keeps throughput near ideal with low robot waiting.

Task suites

15 real-world manipulation tasks grouped into four transitionable task pools. Each pool pairs a forward task with the task that returns the scene, so collection can continue without a human. Three pools are shown below.

Pick & place
forward
Stack cups
forward
Open drawer
forward
Pick & place
reverse
Unstack cups
reverse
Close drawer
reverse

Hardware setup

A tabletop workspace with an AgileX PiPER arm and three RGB cameras. BEDA is instantiated with GPT-5.4 as the VLM backbone and a fixed intervention threshold of 0.9 across every task.

Robot hardware and tabletop workspace setup
Real-world tabletop workspace. One manipulator with wrist-mounted and fixed cameras collects data autonomously between human resets.