Estimate steering wheel angle, throttle, and brake from how a vehicle moves. Synchronize those controls with video for world-model and driving-policy training.
Video-input evaluation, speed > 5 m/s. Errors measured at the steering wheel; equal-dataset weighting. See evaluation scope ↓
Method
Control labels from driving video.
PACE uses a proprietary physics-based model to estimate control inputs from egocentric driving video. The resulting action labels are synchronized with the video for model training.
01 / Input
Egocentric video
Driving footage with frame timestamps.
02 / Processing
Kosmic PACE
Proprietary physics-based control extraction.
03 / Output
Frame-aligned controls
Steering wheel angle radians
Throttle position 0–100%
Brake position 0–100%
The public overview presents capabilities, validation results, and limitations. Algorithmic details are available to partners under NDA.
Evaluation datasets
Across vehicles and environments.
One representative front-camera frame from each of the eight evaluation datasets, spanning passenger cars, a van, a coach, and a semi-truck.
Steering wheel angle error against CAN ground truth, strictly above 5 m/s. Errors are in degrees.
Dataset
Scored frames
MAE
RMSE
A2D2
32,325
1.99°
3.03°
comma2k19
2,043,677
2.18°
3.11°
Turing Japan
2,354,277
1.97°
2.83°
Yaak L2D
18,873,404
5.70°
12.32°
ZOD
284,532
4.42°
5.93°
Udacity Self-Driving Car Dataset
693,153
1.31°
2.24°
RoboBus
690,225
6.67°
10.46°
VTTI CONOPS
11,959
9.03°
11.02°
Equal-dataset weighting
8 datasets
4.16°
7.50°
All scored frames pooled
24,983,552
4.95°
10.95°
MAE is the mean absolute error. RMSE gives greater weight to large errors. Equal-dataset MAE averages the eight dataset MAEs; equal-dataset RMSE is the square root of the mean dataset MSE. Pooled metrics weight every scored frame equally.
Evaluation scope and calibration notes
One front-camera timeline is counted per dataset: Udacity’s center camera, RoboBus camera 200, and synchronized Yaak state rows counted once. Original finite-value, duplicate, direction, and camera-alignment masks are preserved.
Coverage: above 5 m/s, valid predictions cover 98.66% of eligible RoboBus frames and 99.996% of Udacity frames; the other six datasets have 100% coverage under their eligibility masks.
A2D2 and CONOPS: A2D2 covers the available continuous-motion records. CONOPS covers Port Queuing recordings; its cross-country release has no comparable steering target.
Yaak: steering errors in degrees inherit the adapter’s ±480° conversion from normalized steering.
Turing Japan: the retained effective steering ratio was calibrated previously, and calibration recordings are included in the reported evaluation. This is not a wholly held-out calibration benchmark.
The public steering benchmark scores frames above 5 m/s. Selected demonstration excerpts below have a different scope. Detailed speed breakdowns are available in the full partner report.
Longitudinal controls
Throttle and brake.
Pedal channels are scored only where the recorded signal is comparable to pedal position. The public overview reports all-speed throttle results on seven datasets, and brake results on Yaak L2D.
All speeds · Errors in percentage points of full pedal travel
Dataset
Scored frames
ThrottleMAE
ThrottleRMSE
BrakeMAE
BrakeRMSE
A2D2
65,371
2.51
4.51
—
—
comma2k19
2,360,839
7.21
10.17
—
—
Yaak L2D
24,885,560
5.05
8.37
1.95
5.15
ZOD
351,055
7.71
11.54
—
—
Udacity Self-Driving Car Dataset
976,609
4.36
6.78
—
—
RoboBus
847,852
9.96
17.01
—
—
VTTI CONOPS
39,765
9.10
16.15
—
—
Equal-dataset weighting
7 datasets
6.56
11.48
1.95*
5.15*
Source: public overview, Table 2. These are separate all-speed pedal results, not the steering threshold populations. A dash denotes unavailable comparable ground truth. *Brake averages are Yaak-only. Turing is omitted because it has no usable pedal signal in this evaluation.
Pedal accuracy depends on the vehicle, signal definition, and evaluation setup. These scores do not establish equivalent accuracy on an unseen vehicle.
Frame progression
Controls, frame by frame.
Four sequences compare PACE with recorded controls across Yaak L2D, RoboBus, VTTI CONOPS, and comma2k19. Each row follows one maneuver through four camera frames.
Figure 5 from the public overview. Columns show relative camera-frame offsets T = 0, 50, 100, and 150. Magenta: Actual. Green: PACE. Available controls are shown per dataset; steering paths are approximate projections. Select the image to inspect it at full size.
Selected maneuver
Through a roundabout.
A 15-second RoboBus excerpt shows the entire turn, including the wheel unwinding. Magenta is the recorded steering; green is PACE.
Figure 3 from the public overview · Setra S431DT · 450 frames · All speeds. The recorded peak occurs at 4.6 m/s, below the headline benchmark’s speed threshold. This is a selected example.
Small motion errors are amplified at low speed. A stationary trajectory cannot reveal steering while stopped. Parking and reversing remain important open cases. Detailed lower-speed analysis is available in the full partner report.
Vehicle-specific accuracy
Accuracy varies across vehicles and operating conditions. Results for known evaluation vehicles do not guarantee equivalent performance on an unknown vehicle.
Heavy and articulated vehicles
The current dynamics model treats the vehicle as one rigid body. The coach and truck results do not validate trailer articulation or a general multi-body model.
Demonstration overlays
Steering paths are approximate projections for visualization, not measured future trajectories. Unsupported channels are omitted or marked N/A. The demonstrations use real dataset footage with control overlays.
Documentation
PACE public overview.
October 2026 · 7 pages · PDF
The public overview covers the method, eight-dataset steering evaluation, pedal results, qualitative examples, and limitations.
Dataset attributions and notices are included in the overview. A fuller technical report is available to partners under NDA.
Research and partnerships
Action-conditioned world-model training.
PACE supports our internal preparation of driving data for Kosmic Worlds. Contact us about validation, dataset integration, or world-model design partnerships.