Papers › Human Trajectory Forecasting in Crowds: A Deep Learning Perspective

Human Trajectory Forecasting in Crowds: A Deep Learning Perspective

7 Jul 2020arXiv:2007.03639archive 2025-07-28

Parth Kothari, Sven Kreiss, Alexandre Alahi

Since the past few decades, human trajectory forecasting has been a field of active research owing to its numerous real-world applications: evacuation situation analysis, deployment of intelligent transport systems, traffic operations, to name a few. Early works handcrafted this representation based on domain knowledge. However, social interactions in crowded environments are not only diverse but often subtle. Recently, deep learning methods have outperformed their handcrafted counterparts, as they learned about human-human interactions in a more generic data-driven fashion. In this work, we present an in-depth analysis of existing deep learning-based methods for modelling social interactions. We propose two knowledge-based data-driven methods to effectively capture these social interactions. To objectively compare the performance of these interaction-based forecasting models, we develop a large scale interaction-centric benchmark TrajNet++, a significant yet missing component in the field of human trajectory forecasting. We propose novel performance metrics that evaluate the ability of a model to output socially acceptable trajectories. Experiments on TrajNet++ validate the need for our proposed metrics, and our method outperforms competitive baselines on both real-world and synthetic datasets.

PaperPDFCodeCode 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 10 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 10 samples from 1 repository, 9 ran (9 with no instrument failure; 0 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.

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

vita-epfl/trajnetplusplusbaselines mentioned on GitHubpytorchMITSyntology: 10 samples, 9 ran (0 instrument-failed) · 1 unverified 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.

Code Syntology ran Syntology

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

9ran
1unverified

Licence: 0 of the 10 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 vita-epfl/trajnetplusplusbaselines. “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.

vita-epfl/trajnetplusplusbaselines community (archive-listed) 10 samples, 9 ran (0 instrument-failed) · 1 unverified
add_gt_observation_to_prediction evaluator/visualize_prediction_as_gif.py ran MIT (permissive) · f9747c27eac2f941 · report fixture: returned list · level recorded 2026-09-26
ade evaluator/eval_utils.py ran fingerprinted MIT (permissive) · 5ec1c642602bf41e · report fixture: signature pred:ndarray/3/float, gt:ndarray/3/float · returned float32 · level recorded 2026-09-24
collision evaluator/eval_utils.py ran MIT (permissive) · 23245e535f55c843 · report fixture: signature path1:ndarray/2/float, path2:ndarray/2/float, person_radius:float/0/float, inter_parts:int/0/int · returned bool · level recorded 2026-09-24
fde in 5 papers evaluator/eval_utils.py ran fingerprinted MIT (permissive) · 7f58d71fa664e242 · report fixture: signature pred:ndarray/3/float, gt:ndarray/3/float · returned float32 · level recorded 2026-09-24
get_dest get_dest.py ran MIT (permissive) · d07b9469e61a255f · report fixture: signature rows:MockRows/0/? · returned dict · level recorded 2026-09-24
preprocess_test evaluator/write_utils.py ran MIT (permissive) · 4350795c816c54d7 · report fixture: signature scene:list/1/list, obs_len:int/0/int · returned list · level recorded 2026-09-24
random_rotation in 15 papers trajnetbaselines/augmentation.py ran MIT (permissive) · a15d7a55c30696de · report fixture: signature xy:ndarray/3/float · returned ndarray · level recorded 2026-09-24
trackrows get_dest.py ran MIT (permissive) · 347bcda0c1310dd0 · report fixture: signature line:str/0/str · returned list · level recorded 2026-09-24
update_lines evaluator/visualize_prediction_as_gif.py ran MIT (permissive) · cd91bf4e42e6a862 · report fixture: signature num:int/0/int, dataLines:list/1/ndarray, lines:list/1/MockLine · returned list · level recorded 2026-09-25
add_gt_observation_to_prediction evaluator/visualize_predictions.py unverified MIT (permissive) · df36c6556782b4b9 · report

Tasks

Deep LearningTrajectory ForecastingTrajectory Prediction

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Trajectory Forecasting TrajNet++ Social LSTM COL 7.59 #3 of 3 Archive leaderboard report
Trajectory Forecasting TrajNet++ Social LSTM FDE 1.17 #3 of 3 Archive leaderboard report
Trajectory Prediction TrajNet++ Social LSTM COL 7.59 #3 of 3 Archive leaderboard report
Trajectory Prediction TrajNet++ Social LSTM FDE 1.17 #3 of 3 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