PyRUA-DataFarm: coding agent builds robot training data without teleoperation

PyRUA-DataFarm: coding agent builds robot training data without teleoperation

The paper starts from a familiar bottleneck. Teleoperation is still the default way to collect robot demonstrations, but every episode costs robot and operator time, and every new task starts from scratch. The authors ask whether a coding agent can take over the teleoperator's job.

Their system, PyRUA-DataFarm, works like this. The agent receives a data request and one calibration episode of the robot in the target scene. From that it rebuilds the task in simulation, writing the scene, an expert controller and a success judge. The simulator supplies exact actions. A video model conditioned on real images then renders each rollout as photographic video, generating all camera views together so they stay consistent. The output is what the authors call real-ready data: synchronized camera views labelled with the robot's actions, on which a policy can be trained directly and deployed on the real robot. Independent judges certify the expert and every rendered episode before it is admitted.

The headline result comes from five real-robot tasks. Policies trained only on farm data match policies trained on as many teleoperated episodes, with 93 versus 84 successes in 100 trials. Under an unseen tablecloth and coloured light, the farm-trained policies keep 87 successes, while the teleoperation-trained policies fall to 46.

The paper also gives costs. Adapting a task is fully automatic and costs 21 of API usage on average, paid once per task, plus 5 for a render contract. Every further episode costs 0.80 on average for simulation, rendering and review, with no robot or operator involved. One hour of three-view data for a task costs 107 on average, with those costs included. That is slightly below a quote of 117 for teleoperation in China, and below 290 in labour alone in North America.

Key facts

  • A coding agent takes a data request plus one calibration episode of the robot in the target scene, then writes the simulated scene, an expert controller and a success judge.
  • A video model conditioned on real images renders each simulated rollout as photographic video, with all camera views generated together consistently, and independent judges certify every episode before admission.
  • On five real-robot tasks, farm-trained policies match teleoperation-trained ones: 93 vs. 84 successes in 100 trials.
  • Under an unseen tablecloth and coloured light, farm-trained policies keep 87 successes while teleoperation-trained policies fall to 46.
  • Reported average costs: 21 of API usage plus 5 for a render contract per task, 0.80 per further episode, and 107 per hour of three-view data, against a quote of 117 for teleoperation in China.

Why it matters

Collecting demonstrations by teleoperation ties up a robot and an operator for every episode, and a new task means starting over. This work tries to remove both costs: the agent builds the task in simulation, so the per-episode cost is simulation, rendering and review, with no robot or operator. The video model step is what makes the simulated data usable on a real robot, since policies are trained on photographic camera views rather than simulator graphics. The paper reports that the result matches teleoperation on five real-robot tasks.

Who it affects

The paper frames the problem for anyone who collects robot demonstrations, where teleoperation is the default. The cost comparison points at data collection done by paid operators, citing a quote of 117 for teleoperation in China and labour alone above 290 in North America. Teams that train policies for real robots from demonstrations are the natural audience.

How to use it

The paper describes a workflow rather than a product. You supply a data request and one calibration episode of the robot in the target scene; the agent then adapts the task automatically and the farm produces synchronized camera views labelled with robot actions, ready for policy training. The stated costs are 21 of API usage on average per task, plus 5 for a render contract, then 0.80 per extra episode. The source does not say whether the code or data are released.

How solid is it

The evidence is a set of real-robot tests, which is stronger than a simulation-only claim. The farm-trained policies scored 93 successes in 100 trials against 84 for policies trained on as many teleoperated episodes, and 87 against 46 under an unseen tablecloth and coloured light. The source does not say how many trials were run in the second test, nor whether the 100 trials are per task or in total. The cost figures appear without a clear currency symbol in the available text. The source names no authors or institutions, and it does not name the coding agent, video model or simulator. This is a preprint summary with the authors' own results.

Risks and caveats

The text does not say what the five real-robot tasks are or which robot was used, so how far the result generalizes is unclear. The 93 vs. 84 gap comes from one set of tests with a stated trial count, and the robustness test reports success counts only. The cost comparison sets the farm's average against a single teleoperation quote from China and a labour-only figure for North America, and the farm figures include averages across tasks. Because the source names neither the agent nor the video model, the pipeline cannot be judged on its components from this text.

“We ask whether a coding agent can take over the teleoperator's job.”

— PyRUA-DataFarm paper abstract