Papers › Trajectron++: Dynamically-Feasible Trajectory Forecasting With Heterogeneous Data

Trajectron++: Dynamically-Feasible Trajectory Forecasting With Heterogeneous Data

9 Jan 2020ECCV 2020 8arXiv:2001.03093archive 2025-07-28

Tim Salzmann, Boris Ivanovic, Punarjay Chakravarty, Marco Pavone

Reasoning about human motion is an important prerequisite to safe and socially-aware robotic navigation. As a result, multi-agent behavior prediction has become a core component of modern human-robot interactive systems, such as self-driving cars. While there exist many methods for trajectory forecasting, most do not enforce dynamic constraints and do not account for environmental information (e.g., maps). Towards this end, we present Trajectron++, a modular, graph-structured recurrent model that forecasts the trajectories of a general number of diverse agents while incorporating agent dynamics and heterogeneous data (e.g., semantic maps). Trajectron++ is designed to be tightly integrated with robotic planning and control frameworks; for example, it can produce predictions that are optionally conditioned on ego-agent motion plans. We demonstrate its performance on several challenging real-world trajectory forecasting datasets, outperforming a wide array of state-of-the-art deterministic and generative methods.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also 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.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 6 code samples harvested from 1 repository linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 6 samples from 1 repository, 6 ran (4 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

StanfordASL/Trajectron-plus-plus officialmentioned in papermentioned on GitHubpytorchMITSyntology: 6 samples, 6 ran (2 instrument-failed) · 0 unverified report
nvlabs/adaptive-prediction mentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Expanding the Deployment Envelope of Behavior Prediction via Adaptive Meta-Learning (arXiv:2209.11820; that paper's own run record: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
nvr-avg/adaptive-prediction mentioned on GitHubpytorchApache-2.0Syntology: not harvested report

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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

6 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · our draft was wrong
4ran

Licence: 0 of the 6 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from StanfordASL/Trajectron-plus-plus. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

StanfordASL/Trajectron-plus-plus official repository 6 samples, 6 ran (2 instrument-failed) · 0 unverified
cyclical_lr trajectron/model/model_utils.py ran MIT (permissive) · ff1848a826b358a0 · report fixture: signature stepsize:int/0/int, min_lr:float/0/float, max_lr:float/0/float, decay:float/0/float · returned function · level recorded 2026-09-24
derivative_of trajectron/environment/data_utils.py ran MIT (permissive) · db65861280ab2fd8 · report fixture: signature x:ndarray/1/float, dt:float/0/float, radian:bool/0/bool · returned ndarray · level recorded 2026-09-25
exp_anneal trajectron/model/model_utils.py ran · our draft was wrong MIT (permissive) · 6b2d284bebc1dc60 · report fixture: signature anneal_kws:dict/0/? · returned function · level recorded 2026-09-24
get_model_device in 8 papers trajectron/model/model_registrar.py ran · our draft was wrong MIT (permissive) · 5a0beb315ee2d6b3 · report fixture: signature model:callable/0/? · returned device · level recorded 2026-09-24
make_continuous_copy trajectron/environment/data_utils.py ran fingerprinted MIT (permissive) · d8adbba3a0d64563 · report fixture: signature alpha:ndarray/1/float · returned ndarray · level recorded 2026-09-25
to_one_hot in 44 papers
census: 5 implementations from 6 papers, 4 distinct outputs across 2 buckets, one shared input per bucket
trajectron/model/model_utils.py ran MIT (permissive) · 8f0b65c232680906 · report fixture: signature labels:Tensor/1/int, n_labels:int/0/int · returned Tensor · level recorded 2026-09-24

Tasks

Motion ForecastingSelf-Driving CarsTrajectory ForecastingTrajectory Prediction

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Trajectory Prediction ETH Trajectron++ Avg AMD/AMV 8/12 1.01 #2 of 5 Archive leaderboard report
Trajectory Prediction ETH/UCY Trajectron++ ADE-8/12 0.21 #8 of 20 Archive leaderboard report
Trajectory Prediction ETH/UCY Trajectron++ FDE-8/12 0.39 #8 of 20 Archive leaderboard report
Trajectory Prediction nuScenes Trajectron++ MinADE_10 1.51 #22 of 34 Archive leaderboard report
Trajectory Prediction nuScenes Trajectron++ MinADE_5 1.88 #22 of 34 Archive leaderboard report
Trajectory Prediction nuScenes Trajectron++ MinFDE_1 9.52 #22 of 34 Archive leaderboard report
Trajectory Prediction nuScenes Trajectron++ MissRateTopK_2_10 0.57 #22 of 34 Archive leaderboard report
Trajectory Prediction nuScenes Trajectron++ MissRateTopK_2_5 0.7 #22 of 34 Archive leaderboard report
Trajectory Prediction nuScenes Trajectron++ OffRoadRate 0.25 #22 of 34 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.

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