Robots Atlas>ROBOTS ATLAS
Robotics

AV (Autonomous Vehicle)

1988ActivePublished: 31 August 2026Updated: 31 August 2026Published
Key innovation
Integration of multi-modal perception, motion prediction and planning into a single real-time closed-loop control system that lets a vehicle drive without human input within a defined operational design domain (ODD).
Category
Robotics
Abstraction level
System
Operation level
SystemRobot controlInference
Use cases
Robotaxis / autonomous ride-hailingAutonomous trucking (highway freight)Last-mile deliveryAdvanced driver-assistance systems (ADAS)Autonomous shuttles and public transitIndustrial vehicles: mining, agriculture, logistics

How it works

The system runs a continuous real-time sense–plan–act loop. (1) Perception: sensors (cameras, LiDAR, radar, ultrasonics) provide raw data from which modules detect and track objects and build a semantic scene representation. (2) Localization and mapping: fusion of GNSS/IMU with HD maps and SLAM estimates the vehicle pose. (3) Sensor fusion: combines multi-modal readings into a coherent environment state. (4) Prediction: forecasts future trajectories of other road agents. (5) Planning: a behavioral layer selects a maneuver and a motion planner generates a safe, feasible trajectory. (6) Control: a controller (e.g. MPC) turns the trajectory into steering, throttle and brake commands. In the end-to-end approach much of this pipeline is replaced by a single neural network trained via behavior cloning or reinforcement learning.

Problem solved

Automating the driving task to reduce human error — the leading cause of road crashes — while increasing mobility access, optimizing traffic flow, and reducing labor costs in transport.

Components

PerceptionTurns raw sensor data into an understanding of the environment.

Detects and tracks objects and builds a semantic scene representation from raw sensor data (cameras, LiDAR, radar, ultrasonics).

INImage streams, LiDAR point clouds, radar and ultrasonic readings.
OUTList of detected and tracked objects and a semantic scene representation (e.g. BEV).

Official

Localization & MappingPlaces the vehicle in the world with the accuracy required for planning.

Estimates the vehicle pose by fusing GNSS/IMU with high-definition (HD) maps and SLAM.

INGNSS/IMU readings, HD maps and perception data.
OUTVehicle pose estimate (position and orientation).

Official

PredictionProvides the planner with a forecast of environment dynamics.

Forecasts the future trajectories and intentions of other road agents (vehicles, pedestrians, cyclists).

INTracked agents and scene context.
OUTDistributions of future trajectories of road agents.

Official

PlanningDecides what the vehicle should do over the near-term horizon.

Selects a maneuver (behavioral layer) and generates a safe, feasible trajectory (motion planner).

INSemantic scene, predictions and vehicle pose.
OUTPlanned trajectory (path + speed profile).

Official

ControlExecutes the trajectory, closing the control loop.

Turns the planned trajectory into actuator commands (steering, throttle, brake), often using MPC.

INTrajectory from the planning layer.
OUTSteering, acceleration and braking commands.

Official

Implementation

Implementation pitfalls
Long-tail edge casesCritical

Rare, unusual traffic situations under-represented in training data cause perception and decision failures.

Fix:Active data mining, edge-case simulation, out-of-distribution detection and safe fallback strategies.
Sensor degradation in adverse conditionsHigh

Rain, fog, snow, glare and dirt degrade the quality of camera and LiDAR data.

Fix:Multi-modal fusion (weather-robust radar), ODD restriction and sensor-health monitoring.
Sim-to-real gapHigh

Behaviors learned in simulation do not transfer faithfully to the real world.

Fix:Domain randomization, high-fidelity simulation and real-world validation.
Safety validationCritical

Statistically proving safety requires billions of kilometers of driving and coverage of rare events.

Fix:Scenario-based approaches, simulation validation, safety-case argumentation and gradual ODD expansion.
Real-time latency constraintsHigh

The whole perception→control pipeline must complete within tens of milliseconds at high speeds.

Fix:Model optimization and quantization, dedicated accelerators and hard real-time guarantees.

Evolution

Original paper · 1988 · NeurIPS (NIPS) 1988 · Dean A. Pomerleau
ALVINN: An Autonomous Land Vehicle in a Neural Network
Dean A. Pomerleau
1988
ALVINN — first neural network steering a vehicle
Inflection point

Dean Pomerleau (CMU) trains a neural network mapping camera images to steering angle — a precursor of the end-to-end approach.

1994
VaMP/VITA-2 — autonomous highway driving (Dickmanns)

Ernst Dickmanns' team demonstrates high-speed vision-based driving in traffic (PROMETHEUS project).

2005
DARPA Grand Challenge — Stanley (Stanford) wins
Inflection point

Sebastian Thrun's Stanley completes the desert course; the first finished Grand Challenge.

2007
DARPA Urban Challenge — Boss (CMU) wins

CMU's Boss wins the urban race with traffic — a milestone for city driving.

2009
Google self-driving car project launched (later Waymo)

Google launches its self-driving car program, spun out as Waymo in 2016.

2014
SAE J3016 standard published (levels 0–5)
Inflection point

SAE International defines a common taxonomy of six levels of driving automation.

2016
NVIDIA "End to End Learning for Self-Driving Cars" (PilotNet)
Inflection point

A CNN maps raw camera pixels directly to steering commands — reviving the end-to-end approach.

2018
Waymo One — commercial robotaxi service (Phoenix)

Waymo launches a commercial autonomous ride-hailing service in the Phoenix area.

2023
UniAD — unified end-to-end driving framework (CVPR 2023)
Inflection point

The "Planning-oriented Autonomous Driving" framework integrates the full driving-task stack in one network; presented at CVPR 2023.

Hyperparameters (configurable axes)

Automation level (SAE)Critical

SAE J3016 automation level, from 0 (none) to 5 (full).

L2 — częściowa automatyzacjaDriver supervises (e.g. adaptive cruise + lane centering).
L4 — wysoka automatyzacjaDriverless within a defined ODD (e.g. robotaxis).
Operational design domain (ODD)Critical

Range of conditions (area, weather, time of day, speeds) under which the system can operate safely.

Sensor suiteHigh

Sensor modality configuration — from camera-only to camera + LiDAR + radar fusion.

kamery-onlyVision-only approach (e.g. Tesla).
kamera + LiDAR + radarMulti-modal fusion (e.g. Waymo).
Software paradigmHigh

Modular pipeline vs. end-to-end approach (a single neural network from sensors to control).

Redundancy / fail-operationalHigh

Degree of hardware and software redundancy ensuring safe operation after a fault.

Parallelism

Parallelism level
Partially parallel

The stack modules (perception, prediction, planning, control) run partly in parallel in real time, yet the control decision remains a sequential loop dependent on the latest perception.

Scope
Inference

Hardware requirements

Primary

Perception and planning networks run on automotive tensor-core accelerators (e.g. NVIDIA DRIVE, dedicated SoCs), delivering real-time inference within a constrained power budget.