Papers › Trajectory-guided Control Prediction for End-to-end Autonomous Driving: A Simple yet...
Trajectory-guided Control Prediction for End-to-end Autonomous Driving: A Simple yet Strong Baseline
Penghao Wu, Xiaosong Jia, Li Chen, Junchi Yan, Hongyang Li, Yu Qiao
Current end-to-end autonomous driving methods either run a controller based on a planned trajectory or perform control prediction directly, which have spanned two separately studied lines of research. Seeing their potential mutual benefits to each other, this paper takes the initiative to explore the combination of these two well-developed worlds. Specifically, our integrated approach has two branches for trajectory planning and direct control, respectively. The trajectory branch predicts the future trajectory, while the control branch involves a novel multi-step prediction scheme such that the relationship between current actions and future states can be reasoned. The two branches are connected so that the control branch receives corresponding guidance from the trajectory branch at each time step. The outputs from two branches are then fused to achieve complementary advantages. Our results are evaluated in the closed-loop urban driving setting with challenging scenarios using the CARLA simulator. Even with a monocular camera input, the proposed approach ranks first on the official CARLA Leaderboard, outperforming other complex candidates with multiple sensors or fusion mechanisms by a large margin. The source code is publicly available at https://github.com/OpenPerceptionX/TCP
In Syntology View this paper on Syntology, its page in Syntology's graph. That page lists the repositories linked to the paper, the abstract and the calls for agents.
Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
Syntology holds a reference implementation of Trajectory-guided Control Prediction, generated from the paper text (not the authors' code), at level 3 on Syntology's ladder: V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” (quoted from Syntology's server card). For this implementation, level 3 is recorded, but its report lists no property test that passed on both. No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='Trajectory-guided Control Prediction') (how to connect); the free check have('2206.08129') needs no token.
For agents, on Syntology's MCP service (how to connect):
get_citation_path(paper_1="2206.08129", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2206.08129")
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.
1 assembly on this paper: 0 harvested, 1 generated.
generated Assembly for Trajectory-guided Control Prediction (graph method: Trajectory-guided Control Prediction), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer; level 3 is recorded, but its report lists no property test that passed on both.
label matches by construction: the code was generated for this method (not judged by a model)
- situation_based_fusion entry · level 3 · ran · violated contract ·
a9ed703a08168774ccedf86ea59bbb437d7142cc00be71575d7687a188a1be39
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2206.08129") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Autonomous Driving | CARLA Leaderboard | TCP | Driving Score | 75.14 | #3 of 18 | Archive leaderboard | report |
| Autonomous Driving | CARLA Leaderboard | TCP | Infraction penalty | 0.87 | #3 of 18 | Archive leaderboard | report |
| Autonomous Driving | CARLA Leaderboard | TCP | Route Completion | 85.63 | #3 of 18 | Archive leaderboard | report |
| Autonomous Driving | CARLA Leaderboard | TCP (Reproduced) | Driving Score | 47.91 | #8 of 18 | Archive leaderboard | report |
| Autonomous Driving | CARLA Leaderboard | TCP (Reproduced) | Infraction penalty | 0.77 | #8 of 18 | Archive leaderboard | report |
| Autonomous Driving | CARLA Leaderboard | TCP (Reproduced) | Route Completion | 65.73 | #8 of 18 | Archive leaderboard | report |
| Bench2Drive | Bench2Drive | TCP-traj | Driving Score | 59.90 | #20 of 35 | Archive leaderboard | report |
| Bench2Drive | Bench2Drive | TCP-traj w/o distillation | Driving Score | 49.30 | #23 of 35 | Archive leaderboard | report |
| Bench2Drive | Bench2Drive | TCP | Driving Score | 40.70 | #32 of 35 | Archive leaderboard | report |
| Bench2Drive | Bench2Drive | TCP-ctrl | Driving Score | 30.47 | #34 of 35 | Archive leaderboard | report |
| CARLA longest6 | CARLA | Trajectory-guided Control Prediction (TCP) | Driving Score | 48 | #13 of 21 | Archive leaderboard | report |
| CARLA longest6 | CARLA | Trajectory-guided Control Prediction (TCP) | Infraction Score | 0.65 | #13 of 21 | Archive leaderboard | report |
| CARLA longest6 | CARLA | Trajectory-guided Control Prediction (TCP) | Route Completion | 72 | #13 of 21 | Archive leaderboard | report |
Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.
Methods
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections