Robotics

TL;DR for operators Robot-learning infrastructure is usually discussed as if the central choice were the model or accelerator. The operational loop is broader: collect or generate experience, simulate behavior, train a policy, validate it, move it onto a robot, observe failures, reconstruct relevant environments, and repeat. Qing Yang and colleagues’ Real2Sim2Real for Vision-Language-Action Manipulation: An AMD ROCm-Based Pipeline1 is best read as evidence that many of those stages can be kept inside one ROCm + PyTorch-oriented software environment. The authors generate demonstrations in Genesis, fine-tune SmolVLA-450M, validate it in simulation, and deploy it to a physical Franka arm. They also connect real-scene reconstruction, synthetic-data generation, and reinforcement-learning workloads to the broader stack. ...

TL;DR for operators A robot can predict a plausible future and still take the wrong action. The operational question is therefore not simply how accurately a system models what happens next, but how that prediction is represented and connected to control. The tutorial distinguishes world models, which predict future task-relevant observations or states under actions, from world action models, which couple future prediction with action generation. It then turns this distinction into an architecture map: predict raw observations or compact states; expose the future explicitly or keep it latent; connect prediction to action through a separate controller, predictive features, joint generation, or auxiliary training. ...

TL;DR for operators A familiar robotics design question is where to draw the boundary between understanding and control: should one learned system interpret the scene, choose where to go next, and explain that choice, or should those functions remain distributed across separate perception and planning modules? VISOR1 tests a middle position. Its 3B model combines language understanding, visual-spatial reasoning, target recognition, and high-level destination selection, while a conventional planner handles the low-level movement. It is not the strongest navigator on the leaderboard, but on OVON its post-trained model records a 21.70% success rate on Val Seen and 22.00% on Val Unseen, an unusually small seen-to-unseen change even though stronger baselines achieve much higher absolute success rates. ...

TL;DR for operators If a robotics team replaces a gripper, controller, sensor suite, or robot body, it should not automatically have to rebuild the system’s physical reasoning from scratch. Liang et al. argue that today’s embodied-AI stacks often make that reuse difficult because action semantics, coordinate frames, controller assumptions, verification logic, and model responsibilities remain entangled inside project-specific implementations.1 ...

TL;DR for operators A robot can perceive more of its environment than its planner should necessarily receive. In the experiments summarized here, adding task-irrelevant objects to structured scene representations increases the burden on classical planners and can leave harder problems unsolved. The proposed response is not a new end-to-end planner. It is a learned relevance layer that decides which objects and relations should survive into the planning problem. ...

TL;DR for operators A robot action can look reasonable from the current camera image and still fail because its physical consequence is wrong, its coordinates are slightly off, or familiar skills must be composed in an unfamiliar order. World Action Planner (WAP)1 addresses that gap by putting prediction and search between action proposal and execution: a vision-language model proposes an action, a world model imagines its consequences, semantic feedback can revise the proposal, and local search resolves finer manipulation choices. ...

TL;DR for operators The most revealing moment in this study is not that GPT-5.1 moved a robot toward a plush penguin. After the robot struck the target, the model reversed to regain visual perspective, saw that the penguin was still upright, commanded another strike, then reversed again to verify the result. That sequence suggests something more operationally relevant than one-shot visual command generation: the controller retained a task state across several actions, interpreted the likely consequence of a collision, gathered new evidence, and corrected its plan. ...

TL;DR for operators An embodied agent can receive the correct user instruction and still plan toward the wrong objective if the internal description of its environment has been manipulated. Liu et al. test this failure mode by altering planner-visible state semantics rather than changing the instruction, model, planner, executor, or environment itself.1 ...

TL;DR for operators A robotics system can generate a readable plan, revise that plan after an error, and improve its overall task-completion rate without demonstrating that its language component is correctly grounded in the physical environment. That attribution problem is the focus of a review by Yifan Guo and colleagues.1 The authors audit 105 foundation-model-enabled embodied-agent papers by separating two questions: what responsibility does language carry inside the system, and what evidence actually tests that responsibility? ...

TL;DR for operators When an imitation-learned robot drifts outside the situations represented in its demonstrations, detecting that something looks unusual solves only half the operational problem. A deployment system must also decide when human takeover is warranted, when the recovery has progressed far enough to return control, and whether that intervention can improve the next policy rather than disappear as one-off operational labor. ...