GitHub - Rtwotwo/DriveTTO: DriveTTO: Understanding Search and Selection in Test-Time Trajectory Optimization · GitHub
Skip to content
RtwotwoPublic

About

DriveTTO: Understanding Search and Selection in Test-Time Trajectory Optimization

Topics

Resources

Stars

9 stars

Watchers

0 watching

Forks

Latest commit

 

History

24 Commits

Folders and files

Repository files navigation

🚗 DriveTTO: Understanding Search and Selection in Test-Time Trajectory Optimization

arXiv GitHub repository GitHub Pages project website

📰 News

  • 2026.10.22 — Project page and visualization videos released.
  • 2026.09.25 — DriveTTO reaches state-of-the-art PDMS/EPDMS on the NAVTEST benchmark.

🔍 Overview

DriveTTO overview

DriveTTO is a training-free framework for test-time trajectory optimization that connects structured search with reference-relative selection. A driving planner may generate a good trajectory yet fail to select it. Adding more candidates therefore makes both trajectory quality and selection quality central to the value of search. DriveTTO explores alternatives around a retained complete plan and compares each proposed update with that reference, while keeping the driving models frozen throughout inference. Across the corresponding benchmark settings, DriveTTO achieves 95.5 PDMS and 92.3 EPDMS on NAVTEST, 57.1 EPDMS on NAVHARD, and 54.5 route completion (RC) with 40.1 HD-Score on 345 HUGSIM scenarios. The single-scorer variant, DriveTTO-S, is also evaluated across six base planners against their native outputs and ToAD. Full results. The animation below illustrates how DriveTTO searches and selects around a retained complete plan at test time.

DriveTTO algorithm animation

Concretely, endpoint feedback associates the predicted utility of a complete trajectory with its achieved terminal state, guiding further search through the planner's native path geometry. Geometric refinement, cross-model proposals and bounded control residuals produce alternative motions around the retained plan. Frozen scorers evaluate gains over the reference in a shared scoring context, and temporal fusion combines proposal and control trajectories along the prediction horizon. Each accepted update becomes the reference for later decisions. By separating the best trajectory available in a candidate pool from the trajectory actually returned, DriveTTO examines how candidate construction, filtering and ranking contribute to the final driving result.

🎬 Visualizations

Play the DriveTTO project video with its animated logo opening

1 min 59 s · Method · Planning · Closed-loop driving — open the full gallery

🛣️ HUGSIM closed-loop rollouts

Video thumbnail
Through the city blocks
nuScenes · hard · RC 100.0 · HD 100.0
Video thumbnail
Between parked vehicles
Waymo · hard · RC 100.0 · HD 97.2
Video thumbnail
Following along a residential street
PandaSet · medium · RC 100.0 · HD 92.9
Video thumbnail
From curbside parking to a crossing
KITTI-360 · easy · RC 95.9 · HD 92.1
Video thumbnail
Across a broad intersection
nuScenes · extreme · RC 100.0 · HD 98.0
Video thumbnail
An uphill urban corridor
Waymo · extreme · RC 100.0 · HD 95.4

🧭 NAVSIM planning animations

Video thumbnail
Urban bend
PDMS 100 · 4 s prediction horizon
Video thumbnail
Narrow street
PDMS 100 · 4 s prediction horizon
Video thumbnail
Junction
PDMS 100 · 4 s prediction horizon
Video thumbnail
Bridge curve
PDMS 100 · 4 s prediction horizon

🙏 Acknowledgements

We thank the authors of ToAD for demonstrating that DrivoR's scorer can be used as a reward to search for better trajectories at test time, DrivoR for the end-to-end driving model by driving on registers, our own ChainFlow planning and evaluation pipeline built on NAVSIM, and the GETok-DSR-NAVSIM-v1 driving model weights and resources, all of which supported this project.

About

DriveTTO: Understanding Search and Selection in Test-Time Trajectory Optimization

Topics

Resources

Stars

9 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages