Real-Time GPU-Accelerated Monte Carlo Evaluation of Safety-Critical AEB Systems Under Uncertainty

arXiv:2604.27193 · cs.RO, cs.CE, cs.DC, cs.SY, eess.SY · Submitted 2026-04-29 · Read on arXiv

Listen

Radio episode about this paper

Transcript

Introduction to the show: ident: Robotics Radio. Generated commentary on the latest robotics and control papers.

Rosa: Today's paper: "Real-Time GPU-Accelerated Monte Carlo Evaluation of Safety-Critical AEB Systems Under Uncertainty".

Dev: The gist The framework demonstrates that GPU-accelerated Monte Carlo simulation can provide a deployable runtime component for uncertainty-aware Automatic Emergency Braking (AEB) evaluation,

Rosa: First, who's behind it and why it matters.

Paper summary: Rosa: We just talked about how this paper is tackling a safety issue that regulators are really focused on.

Dev: Yeah, specifically AEB systems under FMVSS No. one hundred twenty-seven and the core problem is that current methods rely on deterministic thresholds that don't capture real-world uncertainty in sensing or dynamics <ref:2604.27193#pg1>.

Rosa: The paper claims they’ve presented a GPU-accelerated Monte Carlo framework to evaluate emergency braking performance stochastically, using a high-fidelity model that includes aerodynamics and actuator lag.

Dev: Their main claim is providing a scalable computational foundation for real-time uncertainty-aware AEB decision making and probabilistic braking risk estimation.

Taro: It matters because it allows engineers to select AEB thresholds based on quantitative risk curves rather than just fixed numbers, which helps with compliance verification.

Rosa: So, the framework handles parameter uncertainty by treating things like initial speed and road grade as random variables within the simulation.

Dev: They integrate these uncertain parameters into a single stopping distance sample D(i)stop for each realization ξ(i), which is what generates the stopping distance distribution they analyze.

Taro: The system state x(t) equals position, velocity, brake actuator status, and actual braking deceleration, all governed by drag and gravity effects from the road grade.

Rosa: They then use a Monte Carlo approach to propagate this uncertainty through those nonlinear dynamics until the vehicle stops to produce those stopping distance samples.

Dev: The implementation is designed for parallel execution on GPUs using a one-thread-per-sample strategy, which ensures bit-exact numerical correspondence between the CPU and GPU implementations.

Taro: That deterministic sampling approach is important because it’s what allows them to ensure that the GPU implementation uses the same parameter samples generated deterministically on the CPU.

Rosa: The performance results show significant speedups, achieving peaks up to fifty-four point five seven times across different hardware platforms, including both laptop GPUs and automotive-grade embedded systems <ref:2604.27193#pg2>.

Dev: They also proved real-time feasibility by showing that the Jetson AGX Orin can run about twenty-five point zero thousand samples within a budget of five hundred thirty milliseconds.

Taro: That speedup and the timing analysis together establish that this is a viable component for an embedded pipeline, not just some slow offline validation tool.

Rosa: This work shows how they are providing quantitative guidance for risk-aware AEB threshold selection under the NHTSA final rule by deriving collision probability curves P(Dstop > H0) from those distributions.

Conclusion: Rosa: Looking at the paper, "Real-Time GPU-Accelerated Monte Carlo Evaluation of Safety-Critical AEB Systems Under Uncertainty," the authors Akshay Karjol and Shadi Alawneh have built something that moves this evaluation into a practical domain.

Dev: They’ve created a way to provide quantitative guidance for selecting AEB thresholds under the NHTSA final rule by moving beyond simple deterministic calculations.

Rosa: In simple terms, they’ve shown that you can use this framework to evaluate risk-aware AEB decisions under parameter uncertainty in real-time.

Dev: It establishes a scalable computational foundation for probabilistic braking risk estimation, which means developers can now use this tool to verify their systems against the final rule.

Taro: So for anyone listening, the implication is that this capability simplifies regression testing and certification documentation because it provides verifiable metrics for compliance verification.

Rosa: The paper separates the dynamics model from the simulation backend while enforcing consistency between CPU and GPU, which makes it a deployable runtime component rather than just an offline validation tool.

Dev: That means we’re looking at a system where uncertainty-aware AEB threshold calibration can happen directly in the running application.

Taro: The future work they suggest involves incorporating things like sensing latency and measurement noise to enhance realism, which is a natural next step for improving how much the simulation matches reality.

Rosa: So, overall, this paper demonstrates that Monte Carlo–based uncertainty evaluation can be a deployable runtime component for AEB evaluation under parameter uncertainty.

Oakland University

cs.RO, cs.CE, cs.DC, cs.SY, eess.SY

Submitted: 2026-04-29

Updated: 2026-10-14

Comments: 11 pages, 8 figures. Submitted to IEEE journal for possible publication; under review

License: http://arxiv.org/licenses/nonexclusive-distrib/1.0/

Importance score: 88/100

The gist: The gist The framework demonstrates that GPU-accelerated Monte Carlo simulation can provide a deployable runtime component for uncertainty-aware Automatic Emergency Braking (AEB) evaluation,

Key concepts

Monte Carlo Framework
This simulation method is used to explore the range of possible outcomes when model parameters are uncertain. Instead of using single fixed values, it runs many simulations by randomly sampling input variables (like initial speed or friction) from probability distributions. This generates a distribution of stopping distances rather than just one number.
Longitudinal Vehicle Model
This is the mathematical equation that describes how a car's state changes while it is braking. It accounts for real-world physics, including aerodynamic drag (air resistance), the effect of road grade (hills or slopes), and how quickly the brake system responds to driver input, which affects deceleration.
GPU Acceleration and Parallelization
The simulation is designed to run on a Graphics Processing Unit (GPU) for speed. Because each simulation run is independent, the framework uses a 'one-thread-per-sample' strategy, allowing many scenarios to be calculated simultaneously. This parallel approach significantly speeds up the process compared to running them sequentially on a standard CPU.
Risk-Aware Threshold Selection
This involves setting a specific stopping distance threshold (H0) for the AEB system based on an acceptable risk level. By analyzing the distribution of possible stopping distances, researchers can determine what headway distance is required to keep the collision probability below a certain percentage, such as 1%.

Terminology

Summary

The gist The framework demonstrates that GPU-accelerated Monte Carlo simulation can provide a deployable runtime component for uncertainty-aware Automatic Emergency Braking (AEB) evaluation, establishing a scalable computational foundation for risk-aware AEB threshold selection under NHTSA regulations.

Problem Formulation and Model Fidelity

The work evaluates the stopping-distance distribution of a passenger vehicle undergoing emergency braking under uncertainty through Monte Carlo simulation The point-mass longitudinal model employed in this work provides an appropriate abstraction for braking-distance evaluation This model captures dominant stopping-distance variability sources: aerodynamic drag, road grade, actuator lag, and weight transfer The system state is defined as x(t) = [x(t), v(t), abrake,actual(t)] The longitudinal acceleration during braking is governed by aerodynamic drag, gravitational effects due to road grade, and the realized braking deceleration The complete system evolves according to dx/dt = v, dv/dt = atotal(v, θ), dabrake,actual = 1/τ(abrake,cmd - abrake,actual)

Monte Carlo Framework and Uncertainty Representation

The Monte Carlo framework is used to propagate parameter uncertainty through the nonlinear braking dynamics Several model parameters are treated as random variables, including initial speed, road grade, aerodynamic drag coefficient, vehicle mass, tire-road friction coefficient, and actuator time constant For each realization ξ(i), the system dynamics are integrated from the initial state until the vehicle stops to produce an independent stopping-distance sample D(i)stop The simulation parameters include a fixed integration time step ∆t = 0.001 s, maximum simulation horizon Tmax = 10 s, and commanded braking deceleration abrake,cmd = −6.0 m/s2 Uncertainty is modeled using independent normal random variables for parameters such as v0 ∼ N (30.0, 2.0 2) m/s

GPU Implementation and Parallelization Strategy

The GPU implementation is suited for parallel execution because each rollout is independent The parallelization strategy employs a one-thread-per-sample strategy, where each Monte Carlo rollout is assigned to a single GPU thread The GPU kernel proceeds through the sequence of loading the sampled parameter vector ξ(i) from global memory, initializing the state vector x(0), integrating the nonlinear dynamics using a fixed-step fourth-order Runge-Kutta (RK4) integrator until zero speed is reached, and writing the resulting stopping distance to an output array indexed by the thread identifier This design ensures that the GPU implementation uses: the same parameter samples generated deterministically on the CPU, achieving bit-exact numerical correspondence

Performance and Real-Time Feasibility Analysis

The computational complexity for both CPU and GPU implementations is O(N), where N is the number of Monte Carlo samples The speedup factor S = TCPU/TGPU depends on parallelism, overhead amortization, memory bandwidth, and occupancy Performance scaling exhibits three characteristic regimes: kernel-overhead dominance at N ≤ 10,000, linear scaling between 10,000 155k The framework's real-time feasibility analysis uses a timing budget where the Monte Carlo budget is set to 530 ms after accounting for perception processing (120 ms) and decision logic (50 ms) overhead With this budget, the Jetson AGX Orin can execute up to N ≈ 25,000 samples within the 530 ms Monte Carlo budget

Risk-Aware Decision Making and Conclusion

The collision probability is defined as P(collision H0) = P(Dstop > H0), representing the fraction of uncertain scenarios in which the ego vehicle cannot stop before reaching the lead vehicle Evaluating this over a range of headway distances yields a collision-risk curve that informs AEB threshold selection For the simulated braking scenario, minimum safe headways are determined, such as 5% risk requiring H0 = 100.6 m The demonstrated acceleration and cross-platform consistency establish a computational foundation for NHTSA-compliant AEB evaluation This capability simplifies regression testing, certification documentation, and compliance verification under the NHTSA AEB final rule The framework separates the dynamics model from the simulation backend and enforces deterministic CPU-GPU consistency This enables uncertainty-aware AEB threshold calibration and probabilistic braking risk estimation under parameter uncertainty. The results establish Monte Carlo–based uncertainty evaluation as a deployable runtime component rather than an offline validation tool.

Future Work

A next step is incorporation of dynamic leadvehicle motion and time-varying headway within the Monte Carlo simulation loop to enable closed-loop evaluation Incorporating perception effects such as sensing latency, measurement noise, dropout, and occlusion would enhance realism Kernel-level optimizations may reduce execution time without compromising numerical fidelity The framework can be extended to broader probabilistic safety-evaluation tasks including closed-loop AEB controller assessment and rare-event simulation.

References

[1] National Highway Traffic Safety Administration, “Federal motor vehicle safety standards; automatic emergency braking systems for light vehicles: Final rule,” Federal Register, 89 FR 40118, 2024, fMVSS No. 127, published May 9, 2024

[3] R. van der Horst and J. Hogema, “Time-to-collision and collision avoidance systems,” Accident Analysis & Prevention, vol. 45, pp. 507–517, 2012

[4] International Organization for Standardization, “Iso 22737: Intelligent transport systems — pedestrian automatic emergency braking systems — performance requirements and test procedures,” 2021, standard

[5] A. Berthelot, A. Tamke, T. Dang, and G. Breuel, “Stochastic situation assessment in advanced driver assistance system for complex multiobjects traffic situations,” in 2012 IEEE/RSJ International Conference on Intelligent Robots and Systems

[6] C. Stockle, W. Utschick, S. Herrmann, and T. Dirndorfer, “Robust design ¨ of an automatic emergency braking system considering sensor measurement errors,” in 2018 21st International Conference on Intelligent Transportation Systems (ITSC)

[7] J. Dahl, G. R. de Campos, and J. Fredriksson, “Prediction-uncertaintyaware threat detection for adas: A case study on lane-keeping assistance,” IEEE Transactions on Intelligent Vehicles, vol. 8, no. 4, pp. 2914–2925

[8] C. Stockle, S. Herrmann, T. Dirndorfer, and W. Utschick, “Automated ¨ vehicular safety systems: Robust function and sensor design,” IEEE Signal Processing Magazine, vol. 37, no. 4, pp. 24–35

[9] C. P. Robert and G. Casella, Monte Carlo Statistical Methods, 2nd ed., New York: Springer, 2004

[10] K. Esler, J. Kim, D. Ceperley, and L.

Improvements for AI systems

  1. Bold header: Develop a risk-aware AEB threshold selection mechanism based on collision probability curves. This allows for quantitative risk-aware AEB threshold selection for multiple safety margins by deriving P(Dstop > H0) from stopping-distance distributions, enabling engineers to set headways based on desired risk tolerance (e.g., 5% risk (aggressive)).

  2. Bold header: Implement a unified, bit-exact validation workflow across development and deployment environments. The framework ensures this by achieving exact numerical agreement between CPU and GPU outputs across all hardware platforms, simplifying regression testing for NHTSA compliance.

  3. Bold header: Enable real-time probabilistic AEB evaluation within the embedded pipeline. The system can execute approximately 25,000 Monte Carlo samples within a 530 ms budget on automotive-grade platforms like the Jetson AGX Orin, making uncertainty quantification a deployable runtime component.

  4. Bold header: Enhance perception robustness by incorporating stochastic sensing uncertainties. By including sensing latency, measurement noise, dropout, and occlusion, the system can evaluate AEB behavior under these conditions to improve performance beyond deterministic TTC thresholds.

  5. Bold header: Provide closed-loop uncertainty evaluation for lead-vehicle dynamics. Extending the framework to incorporate dynamic leadvehicle motion and time-varying headway would allow for closedloop evaluation where uncertainty in lead-vehicle behavior propagates through the braking trajectory.

Related papers