Success rate is a fundamental performance metric in robotics and reinforcement learning that measures the percentage of evaluation trials in which an agent or policy successfully completes a predefined task. It is defined as (Number of Successful Trials / Total Number of Trials) * 100%. A trial, or real-world episode, is typically considered successful if the agent achieves a specific goal state within allowed time and action constraints. This binary metric provides a clear, interpretable measure of policy robustness and task mastery, making it a cornerstone of sim-to-real benchmarking protocols.
Glossary
Success Rate

What is Success Rate?
Success rate is the primary quantitative metric for evaluating robotic task performance in sim-to-real transfer learning.
While intuitive, success rate alone can mask important performance nuances. It is therefore often reported alongside complementary metrics like cumulative reward, Success Weighted by Path Length (SPL) for navigation, or Mean Average Precision (mAP) for manipulation. In rigorous evaluation protocols, success rate is calculated over a statistically significant number of trials, often across randomized initial conditions, to account for stochasticity and provide a reliable estimate of out-of-distribution (OOD) generalization capability after zero-shot transfer from simulation.
Key Characteristics of Success Rate
Success rate is a primary evaluation metric in robotics that measures the percentage of trials in which a policy or agent successfully completes a defined task. Its interpretation and utility depend on several defining characteristics.
Binary Outcome Definition
Success rate is fundamentally a binary metric. A trial is scored as a success (1) or failure (0) based on a clear, predefined terminal condition. This condition must be objective and measurable, such as:
- An object being placed within a tolerance zone.
- A robot reaching a target pose.
- A task being completed within a time limit. The strictness of this definition directly impacts the reported metric, making precise task specification critical for meaningful comparison.
Statistical Reliability & Sample Size
As a proportion, success rate's confidence depends heavily on the number of independent trials (N). A reported rate of 80% from 5 trials carries high uncertainty, whereas the same rate from 500 trials is statistically robust. Standard practice involves:
- Running a large number of episodes (often 100-1000) to compute a reliable mean and standard error.
- Ensuring trials are statistically independent (different random seeds, environment resets).
- Reporting confidence intervals (e.g., 95% CI) to communicate uncertainty, which is essential when comparing policies or reporting sim-to-real transfer performance.
Task-Specific & Non-Holistic
Success rate measures completion of a single, specific task and does not capture the quality or efficiency of the execution. Two policies with identical success rates can differ drastically in:
- Path efficiency (excess movement, energy use).
- Execution speed (time to completion).
- Motion smoothness or safety.
- Generalization to minor task variations. Therefore, success rate is almost always reported alongside secondary metrics like cumulative reward, path length, or completion time to provide a complete performance profile.
Primary Sim-to-Real Transfer Signal
In sim-to-real research, the relative drop in success rate from simulation to physical hardware is a direct, quantitative measure of the reality gap. It answers the core question: "How well does simulation training transfer?"
- A high sim success rate with a low real-world rate indicates a large domain shift or poor simulation fidelity.
- A minimal drop indicates effective domain randomization or adaptation techniques. This makes it the headline metric for most sim-to-real benchmark papers, as it directly correlates to engineering viability.
Limitations and Complementary Metrics
While intuitive, success rate has key limitations that necessitate complementary metrics:
- No partial credit: It ignores near-successes or graceful degradation.
- Sensitivity to thresholding: Slight changes in success criteria can cause large metric swings.
- No insight into failure modes: It doesn't explain why failures occur. Hence, it is used in conjunction with metrics like:
- Success weighted by Path Length (SPL): For navigation, penalizes inefficient successful paths.
- Mean Average Precision (mAP): For detection/segmentation tasks within a pipeline.
- Robustness scores: Measuring performance under distribution shift or adversarial conditions.
Benchmarking and Reproducibility
For success rate to be a valid tool for comparison across research, it must be computed under a standardized evaluation protocol. This includes:
- A fixed, public benchmark suite of tasks (e.g., MetaWorld, RLBench).
- A defined number of random seeds and environment initializations.
- Identical success condition definitions and evaluation code.
- Reporting of aggregate statistics (mean, std, confidence intervals) across all tasks. Without this rigor, reported success rates are not reproducible or comparable, undermining scientific progress in sim-to-real transfer learning.
Calculation and Context in Sim-to-Real
In sim-to-real transfer, success rate is a primary but nuanced metric. Its calculation and interpretation are deeply tied to the experimental protocol and the definition of the task's terminal condition.
Success rate is the percentage of evaluation trials in which a robotic policy achieves a predefined task objective. In sim-to-real benchmarking, this is calculated as (Number of Successful Episodes / Total Evaluation Episodes) * 100%. The critical nuance lies in the unambiguous, programmatic definition of success criteria, such as object placement tolerance or navigation goal proximity, which must be consistent between simulation and physical deployment to ensure valid comparison.
The metric's value is meaningless without its experimental context. Reporting must specify the number of trials, random seeds, hardware reset conditions, and whether it represents zero-shot transfer or post-adaptation performance. A high simulation success rate that collapses in real-world trials highlights the sim-to-real gap, while consistent rates across both domains indicate a robust policy and effective domain randomization or adaptation techniques.
Frequently Asked Questions
Success rate is a fundamental, quantitative metric for evaluating robotic policies. This FAQ addresses common questions about its definition, calculation, interpretation, and role within the broader context of sim-to-real transfer learning and benchmarking.
Success rate is a primary evaluation metric that measures the percentage of trials in which a robotic policy or agent successfully completes a defined task. It is calculated as (Number of Successful Trials / Total Number of Trials) * 100%. A trial, or real-world episode, is typically defined from a standardized initial state to a terminal condition (e.g., task completion, timeout, or catastrophic failure). The binary success criterion must be explicitly defined per taskāfor example, an object being placed within a tolerance zone, a door being fully opened, or a navigation goal being reached without collision.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Success rate is a primary but often insufficient metric. Robust evaluation requires complementary measures that account for efficiency, safety, and generalization under distribution shift.
Normalized Score
A performance metric scaled relative to a baseline policy (e.g., random or expert) to enable fair comparison across tasks with different reward scales. In sim-to-real, it's used to contextualize raw success rates.
- Calculation: (Agent Score - Random Score) / (Expert Score - Random Score).
- Purpose: Mitigates the issue where a 90% success rate on a simple task may be less impressive than a 60% rate on a complex one.
Success Weighted by Path Length (SPL)
A composite navigation metric that penalizes success based on the excess path length taken by an agent compared to an optimal shortest path. It balances success rate with efficiency.
- Formula: SPL = (Success) * (Optimal Path Length / Actual Path Length).
- Application: Critical for evaluating mobile robots and embodied AI, where a meandering successful path is less desirable than a direct one.
Cumulative Reward
The sum of all reward signals received by an agent over an episode in reinforcement learning. While success rate is binary, cumulative reward provides a nuanced, continuous measure of performance quality.
- Insight: A policy that completes a task clumsily (low cumulative reward) may have the same success rate as one that does it elegantly (high cumulative reward), highlighting different aspects of robustness.
Sample Efficiency
Measures the number of environmental interactions (samples) an algorithm requires to achieve a target performance level. It's a key economic metric for sim-to-real transfer.
- Real-World Impact: A high success rate achieved after billions of simulation samples may be impractical if the policy cannot adapt to reality with limited, costly real-world episodes.
Policy Robustness
The ability of a learned control policy to maintain stable performance despite variations in environmental conditions, sensor noise, or actuator dynamics not seen during training. It is the qualitative property that a high success rate should imply.
- Evaluation: Tested by measuring success rate across a benchmark suite of randomized conditions or through ablation studies that introduce perturbations.
Out-of-Distribution (OOD) Generalization
The ability of a model to perform accurately on input data from a statistical distribution significantly different from its training data. A high in-simulation success rate with poor OOD generalization indicates overfitting and predicts sim-to-real transfer failure.
- Related Techniques: Domain randomization and invariant risk minimization (IRM) are explicitly designed to improve OOD generalization from simulation to reality.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us