Auditing Demonstration Curation Metrics: Action-Only Scorers Fail on the Structural Defects That Degrade Imitation Policies
This paper introduces a controlled testbed to audit demonstration curation metrics and reveals that while action-only scorers fail to detect structural errors that degrade imitation policies, metrics analyzing state trajectories are necessary to identify such defects, though even the best methods only partially recover downstream performance.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are trying to teach a robot to pick up a cup and put it on a table. The robot learns by watching videos of humans doing the task, a process called "imitation learning." The paper argues that the robot is only as smart as the videos it watches. If the videos are bad, the robot learns bad habits.
The big question the authors asked is: How do we automatically find and delete the bad videos before teaching the robot?
There are many computer programs (called "curation metrics") designed to score these videos, giving a high score to "good" ones and a low score to "bad" ones. The authors set up a controlled experiment to test seven of these programs. They created a robot task, injected specific types of mistakes into some videos, and then asked: Do these programs actually spot the mistakes, and does deleting the "bad" videos actually make the robot better?
Here is what they found, explained with simple analogies:
The Two Types of "Bad" Videos
The authors tested two very different kinds of mistakes:
- The "Shaky Hand" (Subtle Perturbations): Imagine a human doing the task perfectly, but their hand is just a little bit jittery, or the video cuts off a second too early. It's like a singer hitting the right notes but having a slight tremor in their voice.
- The "Wrong Move" (Structural Errors): Imagine a human doing the task correctly until the very end, where they accidentally drop the cup. This isn't just a little shake; it's a fundamental, catastrophic mistake at a critical moment. It's like a chef cooking a perfect meal but then throwing it on the floor right before serving it.
The Results: The "Shaky Hand" vs. The "Wrong Move"
1. The "Shaky Hand" is Easy to Spot and Fix
When the videos had the "shaky hand" errors, the computer programs were very good at finding them.
- The Analogy: It's like a music teacher listening for a shaky voice. The programs could easily say, "This video is noisy; let's throw it out."
- The Result: Once the noisy videos were removed, the robot learned almost perfectly. The "bad" data was just background noise that washed away when the robot saw enough good examples.
2. The "Wrong Move" is Invisible to Most Programs
This is where the study got surprising. When the videos contained the "dropped cup" error, most of the computer programs failed completely.
- The Analogy: Imagine a program that only listens to the volume of the chef's voice. If the chef screams while dropping the cup, the program thinks, "Wow, that chef is very energetic and expressive! That's a 10/10 video!"
- The Result:
- Blindness: Programs that only looked at the actions (the hand movements) couldn't see that the cup was dropped. They thought the "dropping" video was actually better than the clean ones because the movements looked more "active" or "varied."
- Making it Worse: In some cases, using these programs to filter the data actually made the robot worse than if they hadn't filtered anything at all. They threw away the good videos and kept the bad ones.
- The Only Hope: Only one type of program worked here: one that looked at the entire path the hand took (the state trajectory). It could see, "Wait, the hand went to the cup, then suddenly went to the trash can." But even this best program only fixed about one-third of the problem.
The Big Lesson: "Detecting" Doesn't Mean "Fixing"
The most important takeaway is that finding a mistake doesn't guarantee you can fix the robot.
- The Analogy: Imagine a doctor who is great at spotting a specific symptom (like a fever) but gives the wrong medicine. The doctor successfully "detected" the problem, but the patient didn't get better.
- The Paper's Claim: The authors found that two programs could both be equally good at spotting the "dropped cup" error (detecting it), but one would help the robot learn, while the other would barely help at all.
Summary for the Everyday Person
If you are training a robot by showing it videos:
- Don't trust the "Action-Only" filters: If a program only looks at how fast or smooth the movements are, it might think a disaster (like dropping an object) is actually a "high-energy" success.
- Look at the whole story: You need a system that watches the entire path of the object, not just the hand movements, to catch big mistakes.
- Test the robot, not the filter: The only way to know if your data cleaning is working is to actually train the robot and see if it succeeds. A high score on a "quality metric" doesn't mean the robot will be smarter.
The authors released their testbed (a simulation environment) so others can check these claims, but they emphasize that for now, structural errors (big mistakes) are very hard to catch, and many popular tools might actually hurt your robot's performance if you use them blindly.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.