← Latest papers
🤖 AI

Offline Policy Evaluation for Manipulation Policies via Discounted Liveness Formulation

This paper proposes a novel offline policy evaluation framework for robotic manipulation that utilizes a discounted liveness-based Bellman operator to effectively handle sparse rewards, non-monotonic task progression, and finite-horizon truncation bias, thereby outperforming classical methods in accurately reflecting task progress.

Original authors: Hao Wang, Joshua Bowden, Colton Crosby, Somil Bansal

Published 2026-05-13
📖 5 min read🧠 Deep dive

Original authors: Hao Wang, Joshua Bowden, Colton Crosby, Somil Bansal

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 watching a robot learn to fold a towel or pick up a bowl. Sometimes, the robot succeeds. Sometimes, it drops the bowl, slips, or runs out of time before finishing.

In the world of robotics, we need a way to grade these attempts. We want to know: "How good is this robot's strategy?" The problem is that the robot only gets a grade at the very end of the attempt: Pass (Task Done) or Fail (Time's Up). It doesn't get a score for every single step along the way.

This paper introduces a new, smarter way to grade these robots, specifically when they are allowed to keep trying even after making mistakes.

The Problem: The "Time-Out" Trap

Imagine a student taking a test. If they run out of time, the teacher marks the whole test as "Incomplete." But what if the student was actually on the right track and just needed two more minutes? Or what if they got stuck on one hard question, took a break, solved an easier one, and then came back to the hard one?

In robotics, this is called truncation bias. Because the robot's "test" (the episode) has a hard time limit, standard grading methods assume that if the robot stopped because time ran out, it was a total failure. They don't realize the robot might have been almost there or was in the middle of a recovery. This makes the robot look worse than it actually is.

The Solution: The "Liveness" Score

The authors propose a new way to think about the score. Instead of asking, "How much reward did you get?", they ask, "How close are you to being 'alive' (successful)?"

They treat the task like a game of "Hot or Cold":

  • Goal State (Success): The robot is "hot." The score is very low (like -1).
  • Failure/Time-out: The robot is "cold." The score is high (like 1).
  • In Between: The score tells you how many steps it should take to get to the goal.

The clever part is how they handle the "Cold" moments.

The "Bootstrap" Trick: Learning from Near-Misses

Here is the magic ingredient: Bootstrapping.

Imagine you are watching a robot try to pick up a bowl.

  1. Attempt 1: The robot picks up the bowl, drops it, picks it up again, and succeeds.
  2. Attempt 2: The robot picks up the bowl, drops it, and then the timer runs out.

A standard grader would say Attempt 2 is a total failure. But our new method looks at Attempt 2 and says, "Wait a minute! The robot dropped the bowl in Attempt 2, just like it did in Attempt 1. But in Attempt 1, the robot recovered from that exact same drop and finished the task."

So, the method says: "Even though Attempt 2 ran out of time, the robot was in a state it knows how to recover from. Let's give it a better score."

This is the Bootstrap Mechanism. It looks for moments in "failed" attempts that look exactly like moments in "successful" attempts. If it finds a match, it upgrades the score of the failed attempt, realizing that the robot wasn't doomed; it was just running out of time.

What They Found

The authors tested this on three different scenarios:

  1. Picking up a bowl (Simulation): The robot dropped the bowl, recovered, and finished. The new method correctly gave the robot credit for the recovery, while old methods thought it was a failure.
  2. Putting a square peg in a hole (Simulation): This was harder because the robot didn't have a "recovery" strategy. If it dropped the peg, it was truly stuck. The new method was still good at spotting progress, but it couldn't magically fix the fact that the robot couldn't recover from a bad drop.
  3. Folding a towel (Real Robot): A human was controlling the robot. Humans often struggle, drop the cloth, and try again. The new method was excellent at realizing that even when the human struggled, they were still making progress toward the goal, whereas old methods just saw "struggling = failure."

The Trade-off

The paper admits a small downside. Because the method is so good at giving credit for "almost there" moments, it sometimes gets a little too optimistic. It might think a failed attempt was actually a success because it looked similar to a real success. However, the authors argue that this is a fair trade: it's better to be slightly too optimistic about a robot's ability to recover than to unfairly punish it for running out of time.

In a Nutshell

This paper gives robots a "second chance" in their grading system. Instead of failing a robot just because the clock ran out, the new method looks at the robot's history. If the robot has shown it can recover from a specific mistake before, the method gives it credit for being on the right track, even if the current attempt didn't finish in time. It turns a simple "Pass/Fail" grade into a nuanced map of how close the robot really is to success.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →