Loading video...

Video Failed to Load

Go Home

Robot arms can be extremely heavy compared to the objects they are asked to manipulate, especially with their metal links and highly geared motors. But is that actually a problem for robot learning, or are learning algorithms powerful enough to handle it? Are we paying any hidden costs for...

15,166 views • 4 days ago •via X (Twitter)

18 Comments

Younghyo Park ✈️CoRL's profile picture
Younghyo Park ✈️CoRL4 days ago

[2/n] For decades, roboticists have pursued low-inertia arms: direct drive, cable drive, series elastic actuators, quasi-direct drive, and more. Meanwhile, robot learning took off on all kinds of arms, as if the hardware didn't matter. Seeing these two research directions side by side really made me curious: does high inertia carry a hidden cost for learning?

Younghyo Park ✈️CoRL's profile picture
Younghyo Park ✈️CoRL4 days ago

[3/n] To find out, we varied robot and object mass in a controlled environment, and tried to see how RL and BC gets impacted by different configurations. RL was able to find competent solutions at every mass pair. But BC revealed a hidden cost of using high-inertia hardware: it became less reliable as the robot grows heavier relative to the object.

Younghyo Park ✈️CoRL's profile picture
Younghyo Park ✈️CoRL4 days ago

[4/n] Some might ask: do we need to switch to a new, lighter robot? Actually, there might be something you can do with your existing arm. Task-space inertia for an articulated arm depends on the configuration and its contact direction, which opens up some practical action items: a lighter workspace or lighter demonstrations. BC succeeds more often on both.

Younghyo Park ✈️CoRL's profile picture
Younghyo Park ✈️CoRL4 days ago

[5/n] One last thing before we wrap up: does this mean expensive robots are bad, and that it's time to switch to low-cost arms? I want to be clear that our study does not reach this conclusion yet. Yes, cheaper arms in the market often do have lower inertia (you can compare different arms on our project page), along with lighter payloads. But they also tend to come with other confounding properties: no torque control with accurate feedforward modeling, significant backlash, and more. How much those limits cancel out the benefit of low inertia is still an open question.

Younghyo Park ✈️CoRL's profile picture
Younghyo Park ✈️CoRL4 days ago

TL;DR: When robots present far more inertia than the objects they handle, RL finds a way, but BC might be paying a cost that could worsen the data scaling law. We hope this brings robot's own dynamics back into the conversation for robot learning. There are quite a few nuanced details we had to think through to study this problem that we couldn't cover in this thread. We recommend reading the paper if you're interested! 📄arxiv: 🔗website:

Younghyo Park ✈️CoRL's profile picture
Younghyo Park ✈️CoRL4 days ago

Joint work with @BronarsToni and @pulkitology!

Elie Aljalbout's profile picture
Elie Aljalbout4 days ago

kudos for (once again) looking into the details most people take for granted! Great work @younghyo_park @BronarsToni @pulkitology

Tristan Lecourtois's profile picture
Tristan Lecourtois3 days ago

I think hardware and learning should be designed together much earlier. expecting the policy to compensate for every mechanical choice feels like an expensive habit.

Mateo Guaman Castro's profile picture
Mateo Guaman Castro4 days ago

very interesting results! do you expect these results to be exacerbated or mitigated when training BC policies with multi-embodied data? also, nice to see that RL works regardless :D

Krishna Murthy's profile picture
Krishna Murthy4 days ago

Interesting work. Similar question to what @nicks_robots had. I noticed, for fairness, you're scaling PD gains so trajectories across robots (at least in free space) are similar. If inertia effects were instead compensated for by the controller level, would findings change?

Younghyo Park ✈️CoRL's profile picture
Younghyo Park ✈️CoRL3 days ago

@nicks_robots We haven't tried inertia shaped controllers yet -- but I think it's def worth investigating! My bet is that it would bring the same benefit as lighter robots if perfectly implemented, which could be quite challenging depending on how good the force sensing is (cc @nicks_robots)

Krishna Murthy's profile picture
Krishna Murthy3 days ago

@nicks_robots Doing it on the controller side has it's issues too. e.g., we can tune an impedance controller to have low gain, which works well for contact, but isn't ideal for free-space motion. If we'd like variable gains, then need to deal with switching dynamic modes, smoothness, etc.

Nick K's profile picture
Nick K4 days ago

Quick question - do you try any inertia shaping / torque control methods on the larger robots to see if that has any useful effects on downstream performance? If so, then policies may be able to adjust their dynamics to help with attaining goals.

GigaCrafter's profile picture
GigaCrafter4 days ago

This is why we print lightweight parts for anything that moves! Every gram on the arm is a gram you pay for twice. Would love to see how hollow printed links stack up in your tests

clankr's profile picture
clankr4 days ago

Everybody talk so much about the learning algorithm that it’s easy to forget how much the arm itself might be holding it back.

Jamie WhiteBelly's profile picture
Jamie WhiteBelly4 days ago

My instinct says it's less the mass and more the geared motor dynamics that hurt. Looking forward to being proven wrong.

AUTONOMOUS's profile picture
AUTONOMOUS4 days ago

relatable mismatch with heavy arm & light object

Soumil Bhandari's profile picture
Soumil Bhandari4 days ago

My guess is it hurts force control way more than position control. Reflected inertia goes with gear ratio squared, so a heavy geared arm basically hides the contact force from the motors. Did lighter arms need less data to learn contact-rich tasks?

Related Videos

Experiments in progress. The one on the right has been learning for ~3 hours, the one in the middle for ~1 hour, and the one on the left just started a few minutes ago. The initial motivation for making the physical Atari was just to commit ourselves to a subset of algorithms that can make progress in this setup. This commitment rules out algorithms that require billions of samples to learn (or worse, require multiple environments running in parallel). Atari games are simple enough that we should be able to show learning on them in a short amount of time with no prior knowledge. Since then, I've realized that this setup is also a good way to compare different paradigms in robotics in a principled way. These paradigms are sim2real, learning from tele-operated data, and learning directly on the robots. So far, I have observed that getting sim2real to work reliably is hard. It requires tweaks that don't scale. Policies that can play perfectly in simulation fall apart because of latencies and the messiness of the real world. These aspects could be modeled to improve the simulation, but not without sinking significant human engineering hours. I have higher hopes for learning from tele-operated data, but that requires a human to learn the task first. These experiments are on my to-do list. I have to learn to play some of the games well through the robot. I’m half-decent at playing Pong and Ms Pacman now. Learning directly on robots is looking like the most promising approach. This approach takes away pesky distribution shifts and makes it possible to have algorithms that continually improve with more data and time without any human intervention. It feels great to let experiments run overnight and wake up to find improved policies. With learning on robots, I should, in principle, be able to go on a long vacation and come back to find better policies for complex tasks beyond Atari games. Whether that is possible with current learning algorithms is a different question.

Khurram Javed

52,110 views • 11 months ago