Outlier rejection is the algorithmic process of identifying and discarding sensor measurements that are statistically inconsistent with a system's current state estimate or a predefined model. In robotics and autonomous systems, raw sensor data from sources like LiDAR, cameras, or IMUs is often corrupted by noise, multipath reflections, or transient failures. These erroneous readings, called outliers, can severely degrade the performance of downstream estimation algorithms like the Kalman filter or nonlinear optimizers if left unchecked.
Glossary
Outlier Rejection

What is Outlier Rejection?
Outlier rejection is a critical pre-processing step in sensor fusion and state estimation that identifies and discards erroneous data points before they corrupt the system's understanding of its state.
The process typically involves calculating a residual—the difference between an observed measurement and its predicted value from the model. This residual is then compared against a probabilistic threshold, often derived from the covariance matrix of the state estimate. Measurements exceeding this threshold are flagged as outliers and excluded from the update step. Common techniques include chi-squared tests, Mahalanobis distance checks, and robust algorithms like RANSAC. Effective outlier rejection is fundamental to maintaining the robustness and accuracy of embodied intelligence systems operating in unpredictable real-world environments.
Key Outlier Rejection Methods
Outlier rejection is a critical pre-processing and in-process step in sensor fusion pipelines. These methods identify and discard statistically inconsistent measurements to prevent corruption of the state estimate. The choice of method depends on the sensor modality, data distribution, and computational constraints of the real-time system.
Mahalanobis Distance Gating
The Mahalanobis distance is the statistically principled metric for outlier detection within Gaussian estimation frameworks like the Kalman filter. It measures the distance between a new sensor measurement and the filter's predicted measurement, normalized by the innovation covariance.
- Mechanism: A measurement is flagged as an outlier if its squared Mahalanobis distance exceeds a threshold from a chi-squared distribution (e.g., p=0.95).
- Use Case: Standard in Kalman Filters, EKF, and UKF for validating incoming measurements from LiDAR, radar, or GPS before the update step.
- Key Insight: It accounts for the estimated uncertainty and correlations between state variables, making it more robust than simple Euclidean distance.
RANSAC (RANdom SAmple Consensus)
RANSAC is an iterative, hypothesis-and-test algorithm designed to estimate model parameters from a dataset containing a large proportion of outliers.
- Mechanism: It randomly selects minimal subsets of data to form candidate models, then evaluates consensus by counting inliers within a tolerance threshold. The model with the most inliers is selected.
- Use Case: Fundamental in computer vision for tasks like estimating essential matrices in visual odometry or plane fitting in LiDAR point clouds, where many data points may belong to irrelevant objects.
- Limitation: Performance degrades when the inlier ratio is very low (<50%), and it is computationally intensive for large datasets.
Statistical Thresholding (Z-Score / IQR)
These are simple, non-parametric methods that identify outliers based on the distribution of a single scalar measurement stream.
- Z-Score: Assumes a Gaussian distribution. Data points exceeding a threshold (e.g., |Z| > 3) are considered outliers. Sensitive to non-Gaussian data.
- Interquartile Range (IQR): A robust, distribution-agnostic method. Outliers are points below Q1 - 1.5IQR or above Q3 + 1.5IQR, where Q1 and Q3 are the 25th and 75th percentiles.
- Use Case: Pre-processing for individual sensor channels (e.g., filtering obviously erroneous temperature readings from a thermistor or spike noise from a single-axis accelerometer) before fusion.
Dynamic Covariance Scaling (DCS)
DCS is a robust kernel-based method integrated directly into the Kalman filter update. Instead of binary rejection, it gracefully down-weights the influence of potential outliers.
- Mechanism: It scales the measurement covariance matrix inversely based on the Mahalanobis distance. A large innovation leads to an inflated covariance, reducing the Kalman gain and thus the impact of that measurement.
- Advantage over Gating: Avoids the brittle 'accept/reject' decision. A single extreme outlier is heavily discounted without being completely ignored, which can be safer for system stability.
- Use Case: Preferred in safety-critical inertial navigation systems and visual-inertial odometry (VIO) where continuous, smooth correction is required.
Consensus-Based Matching (ICP Variants)
In geometric registration algorithms like Iterative Closest Point (ICP), outlier rejection is built into the correspondence matching step.
- Mechanism: Methods like Trimmed ICP or Threshold Rejection discard point correspondences based on distance. Only the best 80-90% of matches (or those below a distance threshold) are used to compute the alignment transform in each iteration.
- Use Case: Essential for LiDAR scan matching and point cloud registration in dynamic environments, where moving objects (people, cars) generate many spurious point correspondences that would derail alignment.
Temporal Consistency Checks
This method leverages the physical constraints of the system over time to identify implausible measurements.
- Mechanism: It checks if a new measurement violates limits on physically possible rates of change (e.g., maximum acceleration, jerk, or angular velocity). A LiDAR scan placing an object 10 meters away when it was 1 meter away 0.01 seconds prior is physically impossible.
- Implementation: Often uses a simple process model (constant velocity/acceleration) to predict a measurement envelope. Measurements outside this envelope are rejected.
- Use Case: Critical for high-frequency sensors (IMU, radar) and in object tracking pipelines to reject sensor ghosts, multipath reflections, and sporadic noise bursts.
Outlier Rejection vs. Related Concepts
A comparison of outlier rejection with other methods for handling erroneous or anomalous data in state estimation and sensor fusion.
| Feature / Metric | Outlier Rejection | Robust Cost Functions | Sensor Redundancy | RANSAC |
|---|---|---|---|---|
Primary Objective | Identify and discard erroneous measurements before or during state update. | Down-weight the influence of outliers within the optimization objective. | Provide multiple independent measurements to mask or vote out faulty data. | Robustly estimate model parameters from a dataset containing a high proportion of outliers. |
Stage of Application | Pre-processing or within the filter update (e.g., gating). | Within the optimization loop (cost function evaluation). | System design and data pre-fusion. | Model fitting, often as a pre-processing step. |
Mechanism | Statistical tests (e.g., Mahalanobis distance gating), consistency checks. | Non-quadratic cost kernels (e.g., Huber, Cauchy) that penalize large errors less severely. | Hardware/software architecture using voting, averaging, or fault detection across identical sensors. | Iterative hypothesis generation and testing via random sampling of minimal data subsets. |
Handles Inlier Noise | ||||
Requires Probabilistic Model | ||||
Computational Overhead | Low to Moderate | Moderate | Low (hardware cost) | High (scales with iterations and outlier ratio) |
Typical Use Case in State Estimation | Real-time gating of LiDAR points or visual features in a Kalman filter. | Non-linear optimization in graph-based SLAM or bundle adjustment. | Triple-redundant IMUs in aviation; multiple GPS antennas. | Initial motion estimation from feature correspondences; plane fitting in point clouds. |
Effect on State Covariance | Prevents contamination, maintains correct uncertainty. | Implicitly modeled, can lead to larger credible intervals. | Reduces overall measurement uncertainty if sensors agree. | Not directly applicable; produces a parameter estimate. |
Frequently Asked Questions
Outlier rejection is a critical defensive mechanism in sensor fusion and state estimation, protecting algorithms from erroneous data that can corrupt the system's understanding of its state. These questions address its core principles, mechanisms, and role in robust robotics.
Outlier rejection is the algorithmic process of identifying and discarding sensor measurements that are statistically inconsistent with the current state estimate and sensor model. It is critically important because real-world sensors produce erroneous data due to temporary failures, environmental interference (e.g., glare for cameras, multipath for LiDAR), or incorrect data association. Without robust outlier rejection, these spurious measurements are incorporated into the state estimator, causing catastrophic corruption of the estimated position, orientation, and map, leading to system failure. It is a foundational component of a robust perception stack.
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
Outlier rejection is a critical defensive layer within state estimation pipelines. These related concepts define the mathematical frameworks, algorithms, and metrics that enable robust filtering against erroneous data.
Innovation Test
The core statistical gating mechanism within recursive Bayesian filters like the Kalman filter. The test compares the measurement residual (innovation) against its predicted statistical distribution.
Process:
- Predict the next state and its covariance.
- Predict what the measurement should be and its covariance (
S). - When a real measurement arrives, compute the innovation
z - Hx. - Compute the squared Mahalanobis distance of the innovation.
- If the distance exceeds a threshold (e.g., 95% percentile of the χ² distribution), the measurement is rejected as an outlier.
Data Association
The critical preceding step to outlier rejection in many perception tasks. Before a measurement can be tested, it must be assigned to a known landmark, object, or track. Incorrect association is a primary source of outliers.
Methods include:
- Nearest Neighbor with gating.
- Joint Probabilistic Data Association (JPDA) which considers multiple hypotheses.
- Global Nearest Neighbor (GNN) via assignment algorithms.
Failed or low-confidence data association often results in a measurement being treated as a potential outlier or used to initialize a new track.

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