Success weighted by Path Length (SPL) is a composite evaluation metric that measures an agent's navigation efficiency by multiplying its binary success indicator by a path-length penalty factor. The core formula is SPL = S * (L* / max(P, L*)), where S is 1 for success and 0 for failure, L* is the optimal path length, and P is the agent's actual path length. This design explicitly penalizes meandering, inefficient routes even when the goal is ultimately reached, making it the standard for benchmarks like Room-to-Room (R2R) and Habitat.
Glossary
Success weighted by Path Length (SPL)

What is Success weighted by Path Length (SPL)?
Success weighted by Path Length (SPL) is the primary quantitative metric for evaluating the performance of agents in language-guided navigation and other goal-oriented embodied AI tasks.
SPL provides a more nuanced performance signal than simple success rate by integrating the fundamental Partially Observable Markov Decision Process (POMDP) trade-off between exploration and exploitation. A high SPL score indicates an agent that not only understands the instruction grounding but also executes efficient, near-optimal trajectories. It is therefore critical for comparing language-conditioned policies and assessing progress toward practical, time-sensitive robotic applications, where minimizing movement is essential for energy efficiency and task completion speed.
Key Properties of the SPL Metric
Success weighted by Path Length (SPL) is the primary metric for evaluating language-guided navigation agents. It balances task completion with efficiency by penalizing unnecessarily long paths.
Core Mathematical Definition
SPL is formally defined as: SPL = (1/N) Σ_i^N S_i * (l_i / max(p_i, l_i)). Where:
- N is the number of evaluation episodes.
- S_i ∈ {0,1} is a binary success indicator for episode i.
- l_i is the length of the shortest path (optimal path) from start to goal.
- p_i is the length of the path actually taken by the agent.
The term l_i / max(p_i, l_i) is the path efficiency ratio, which is 1.0 only if the agent's path equals the optimal length, and decreases as the agent's path grows longer.
Interpretation and Scale
SPL produces a single scalar score between 0.0 and 1.0 that holistically evaluates an agent.
- SPL = 1.0: The agent succeeded in every episode and took the optimal path in each case (perfect performance).
- SPL = 0.0: The agent failed every episode, or succeeded but took infinitely long paths.
- SPL = Success Rate: If all successful agents took the optimal path, SPL equals the simple success rate.
- SPL < Success Rate: This indicates successful agents are taking sub-optimal, longer paths. The magnitude of the difference quantifies the average efficiency penalty.
Advantages Over Simple Success Rate
SPL was introduced to address critical flaws in using success rate alone for navigation:
- Penalizes Inefficiency: An agent that wanders randomly until eventually stumbling upon the goal would score a 1.0 in success rate. SPL heavily penalizes this behavior.
- Encourages Optimality: It provides a direct training signal or evaluation criterion that rewards finding shorter paths.
- Real-World Relevance: For physical robots, path length correlates with time, energy consumption, and operational cost. SPL measures practical utility.
- Granular Differentiation: It allows for ranking agents with identical success rates based on their average path efficiency.
Limitations and Criticisms
While standard, SPL has known limitations that researchers account for:
- Dependence on Optimal Path: Requires a pre-computed shortest path (l_i), which can be ambiguous in continuous spaces or complex environments.
- No Partial Credit: An agent that stops 1cm from the goal scores the same (S_i=0) as one that gets completely lost. Metrics like Success weighted by Distance (SD) or Normalized Inverse Path Length (NIPL) offer alternatives.
- Ignores Execution Dynamics: Does not consider smoothness of motion, collisions, or time taken (only path length).
- Sensitive to Stop Condition: The definition of 'success' (e.g., proximity threshold) directly impacts the score. Results are only comparable under identical thresholds.
Calculation in Practice
Implementing SPL evaluation involves specific steps:
- Episode Definition: Each test case is a tuple: (Start Pose, Goal Specification, Instruction).
- Optimal Path Pre-computation: Using a planner (e.g., Dijkstra's algorithm) on a known environment graph to find l_i.
- Agent Execution: Run the agent's policy to produce its trajectory, recording the path length p_i.
- Success Determination: Check if the agent's final position is within a threshold distance (e.g., 3 meters) of the goal.
- Aggregation: Calculate the mean SPL across all episodes in the validation or test set (e.g., on the Room-to-Room (R2R) dataset).
Related Evaluation Metrics
SPL is often reported alongside other metrics to give a fuller performance picture:
- Success Rate (SR): The fraction of episodes where the goal was reached. Provides the upper bound for SPL.
- Oracle Success Rate: The fraction of episodes where the agent ever passed within the success threshold during its trajectory, measuring navigation potential.
- Path Length (PL): The average length of trajectories, reported separately for successful episodes.
- Normalized Dynamic Time Warping (NDTW): Measures the spatial similarity of the agent's path to the reference path, offering partial credit for getting close.
- Goal Progress (GP): Measures the average reduction in distance to the goal over the trajectory.
SPL vs. Other Navigation Metrics
A comparison of Success weighted by Path Length (SPL) against other common metrics used to evaluate language-guided navigation agents, highlighting their formulas, primary uses, and key limitations.
| Metric | Formula / Definition | Primary Use | Key Limitation |
|---|---|---|---|
Success weighted by Path Length (SPL) | S × (L* / max(P, L*)) | Primary benchmark for instruction-following. Balances success (S) with path efficiency. | Requires a known, shortest-path length (L*), which can be expensive to compute for all scenarios. |
Success Rate (SR) | S (1 for success, 0 for failure) | Measures raw task completion. Simple and intuitive. | Ignores path efficiency; an agent that wanders excessively receives the same score as one that takes the optimal path. |
Path Length (PL) | P (total distance traveled) | Measures efficiency of the taken trajectory. Lower is better. | Meaningless without success context; a short path to failure is not useful. |
Normalized Dynamic Time Warping (nDTW) | exp( -DTW(P, L*) / (α × |L*|) ) | Measures the spatial similarity of the taken path to the reference path, forgiving minor deviations. | Computationally intensive. Can be less intuitive than SPL for penalizing clear inefficiencies. |
Goal Progress (GP) | (D_start - D_end) / D_start | Measures how much closer the agent got to the goal, even on failed trajectories. Useful for partial credit. | Does not penalize backtracking or circuitous routes that still end closer to the goal. |
Oracle Success Rate (OSR) | Success if agent ever gets within a threshold of the goal. | Measures navigability of the environment/instruction, independent of the agent's final stopping policy. | Not a measure of agent performance; used for dataset analysis and upper-bound estimation. |
Collision Rate | Number of collisions / Total steps | Evaluates safety and smoothness of navigation in physical or simulated deployments. | Does not measure task success; an agent can be perfectly safe but fail to navigate. |
Where is SPL Used?
Success weighted by Path Length (SPL) is the definitive quantitative benchmark for evaluating autonomous navigation agents. It is the standard metric across major academic and industry benchmarks where an agent must reach a goal.
Benchmarking Multi-Modal Models
SPL is used to evaluate the navigation performance of Cross-Modal Transformer architectures and Vision-Language-Action Models. It provides a single, comparable figure that reflects how well the model's integrated visual and linguistic understanding translates into effective physical (or simulated) movement. It answers: 'Does better cross-modal alignment lead to more efficient action?'
Evaluating Planning & Generalization
Researchers use SPL to measure an agent's ability in zero-shot navigation and instruction decomposition. A high SPL on unseen environments or novel instructions indicates strong generalization. It also helps evaluate hierarchical planners: a low SPL may indicate failures in waypoint prediction or high-level planning, even if the low-level control is competent.
Frequently Asked Questions
Success weighted by Path Length (SPL) is the primary metric for evaluating performance in language-guided navigation and other embodied AI tasks. These questions address its calculation, purpose, and role in benchmarking.
Success weighted by Path Length (SPL) is a composite evaluation metric for navigation tasks that balances the binary success of reaching a goal with the efficiency of the path taken. It is defined as SPL = (1/N) * Σ_i^N S_i * (l_i / max(p_i, l_i)), where S_i is a binary success indicator, l_i is the optimal path length, and p_i is the agent's actual path length for the i-th episode. This formula penalizes agents that succeed but take unnecessarily long routes, providing a more holistic measure of navigation performance than success rate alone.
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
SPL is the primary metric for evaluating language-guided navigation agents. These related concepts define the tasks, environments, and methodologies that SPL is designed to measure.
Vision-and-Language Navigation (VLN)
Vision-and-Language Navigation (VLN) is the core task that SPL evaluates. An embodied agent must follow a natural language instruction to navigate through a real or simulated 3D environment, using only egocentric visual perception. SPL directly measures the efficiency and success of an agent's performance on this task.
- Primary Benchmark: The Room-to-Room (R2R) dataset is the foundational VLN benchmark.
- Agent Input: A natural language instruction and a stream of first-person visual observations.
- Agent Output: A sequence of low-level navigation actions (e.g.,
move_forward,turn_left).
Room-to-Room (R2R) Dataset
The Room-to-Room (R2R) dataset is the standard benchmark environment for evaluating VLN agents and calculating SPL. It provides the ground-truth data necessary for the metric.
- Environment: Uses Matterport3D 3D reconstructions of real building interiors.
- Data Structure: Contains human-annotated trajectory-instruction pairs.
- SPL Calculation: For each instruction, the dataset provides the expert's shortest path length, which is the
L*in the SPL formula, against which the agent's actual path length (L) is compared.
Embodied Instruction Following
Embodied Instruction Following is a broader category of tasks that includes VLN but extends to interactive object manipulation. SPL is specifically designed for the navigation component of these tasks.
- Scope: Includes navigation-to-and-interaction, as seen in benchmarks like ALFRED.
- Task Complexity: Instructions are often long-horizon and compositional (e.g., 'Go to the kitchen, pick up the mug, and place it on the table').
- Metric Adaptation: While SPL measures navigation efficiency, success in these tasks may require additional metrics for interaction success.
Success Rate (SR)
Success Rate (SR) is the foundational component of the SPL metric. It is a binary measure of whether an agent successfully completed its navigation task within a specified distance of the goal.
- Calculation:
SR = (Number of Successful Episodes) / (Total Episodes). - Relationship to SPL: SPL refines SR by incorporating path efficiency. An agent with a high SR but inefficient paths will have a significantly lower SPL.
- Limitation: SR alone does not penalize meandering, long paths that eventually reach the goal, which is why SPL was introduced.
Normalized Dynamic Time Warping (nDTW)
Normalized Dynamic Time Warping (nDTW) is an alternative or complementary metric to SPL that measures the similarity of the agent's path to the optimal path, rather than just its final success and length.
- Core Idea: Measures the spatial alignment between two paths over time, forgiving small temporal deviations.
- Advantage over SPL: Can assign partial credit for paths that come close to the goal or follow the general route but fail to stop exactly at the target.
- Use Case: Often reported alongside SPL to provide a more nuanced view of path quality, especially in REVERIE-style tasks where the goal is an object, not a point.
Path Length (L) & Shortest Path Length (L*)
Path Length (L) and Shortest Path Length (L)* are the two geometric variables in the SPL formula. L is the agent's actual traveled distance, while L* is the length of the optimal path, as determined by an oracle or planner.
- L (Agent Path Length): The cumulative distance of all steps taken by the agent during an episode.
- *L (Shortest Path Length)**: The minimum feasible distance between the start and goal points in the environment. This is a property of the environment and instruction, not the agent.
- SPL Formula:
SPL = S * (L* / max(L, L*)). The ratioL*/Lis the path efficiency penalty, which reduces the success creditSfor suboptimal paths.

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