Papers › Can Language Beat Numerical Regression? Language-Based Multimodal Trajectory Prediction

Can Language Beat Numerical Regression? Language-Based Multimodal Trajectory Prediction

27 Mar 2024CVPR 2024 1arXiv:2403.18447archive 2025-07-28

Inhwan Bae, Junoh Lee, Hae-Gon Jeon

Language models have demonstrated impressive ability in context understanding and generative performance. Inspired by the recent success of language foundation models, in this paper, we propose LMTraj (Language-based Multimodal Trajectory predictor), which recasts the trajectory prediction task into a sort of question-answering problem. Departing from traditional numerical regression models, which treat the trajectory coordinate sequence as continuous signals, we consider them as discrete signals like text prompts. Specially, we first transform an input space for the trajectory coordinate into the natural language space. Here, the entire time-series trajectories of pedestrians are converted into a text prompt, and scene images are described as text information through image captioning. The transformed numerical and image data are then wrapped into the question-answering template for use in a language model. Next, to guide the language model in understanding and reasoning high-level knowledge, such as scene context and social relationships between pedestrians, we introduce an auxiliary multi-task question and answering. We then train a numerical tokenizer with the prompt data. We encourage the tokenizer to separate the integer and decimal parts well, and leverage it to capture correlations between the consecutive numbers in the language model. Lastly, we train the language model using the numerical tokenizer and all of the question-answer prompts. Here, we propose a beam-search-based most-likely prediction and a temperature-based multimodal prediction to implement both deterministic and stochastic inferences. Applying our LMTraj, we show that the language-based model can be a powerful pedestrian trajectory predictor, and outperforms existing numerical-based predictor methods. Code is publicly available at https://github.com/inhwanbae/LMTrajectory .

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 13 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 0 violated, 5 with no contract checked; 4 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 13 samples from 1 repository, 10 ran (6 with no instrument failure; 4 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 on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

inhwanbae/lmtrajectory officialmentioned in papermentioned on GitHubpytorchNOASSERTIONSyntology: 13 samples, 10 ran (4 instrument-failed) · 3 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

13 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 0 violated, 5 with no contract checked; 4 where Syntology's instrument failed) · 3 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.

1ran · honoured contract
2ran · our draft was wrong
2ran; the contract check could not run
5ran
3unverified

Licence: 13 of the 13 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 inhwanbae/lmtrajectory. “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.

inhwanbae/lmtrajectory official repository 13 samples, 10 ran (4 instrument-failed) · 3 unverified
batch_traj2txt utils/converter.py ran licence not identified · pointer only · b54533a035f69b78 · report fixture: signature traj_list:list/1/ndarray, prefix:str/0/str, suffix:str/0/str · returned list · level recorded 2026-09-24
generate_homography utils/homography.py ran fingerprinted licence not identified · pointer only · 6c9d8e97f8976cab · report fixture: signature shift_w:float/0/float, shift_h:float/0/float, rotate:float/0/float, scale:float/0/float · returned ndarray · level recorded 2026-09-24
get_exp_config utils/config.py ran · our draft was wrong licence not identified · pointer only · 2612d67abdd01825 · report fixture: signature file:str/0/str · returned DotDict · level recorded 2026-09-24
image2world utils/homography.py ran; the contract check could not run (RAISES) fingerprinted licence not identified · pointer only · 35ea3f457179e4fd · report fixture: signature coord:ndarray/3/float, H:ndarray/2/float · returned ndarray · level recorded 2026-09-24
preprocess_function in 29 papers model/nltoolkit.py ran licence not identified · pointer only · f65d09762517789d · report fixture: signature examples:dict/0/?, cfg:Config/0/?, history_column:str/0/str, future_column:str/0/str, tokenizer:callable/0/?, padding:str/0/str · returned dict · level recorded 2026-09-24
read_file in 112 papers utils/dataloader.py ran · honoured contract licence not identified · pointer only · 123c2031d3127cc9 · report fixture: signature _path:str/0/str, delim:str/0/str · returned ndarray · level recorded 2026-09-24
text2traj utils/converter.py ran licence not identified · pointer only · 0553d4e98692f456 · report fixture: signature description:str/0/str, frame:int/0/int, dim:int/0/int · returned ndarray · level recorded 2026-09-24
traj2text utils/converter.py ran licence not identified · pointer only · f1fee667db180729 · report fixture: signature trajectory:ndarray/2/float, prefix:str/0/str, suffix:str/0/str · returned str · level recorded 2026-09-24
traj_collate_fn utils/dataloader.py ran · our draft was wrong licence not identified · pointer only · 131c4aa12088ef21 · report fixture: signature data:list/1/dict · returned dict · level recorded 2026-09-24
world2image utils/homography.py ran; the contract check could not run (RAISES) licence not identified · pointer only · c73cb6c875b73dca · report fixture: signature coord:ndarray/2/float, H:ndarray/2/float, transpose:bool/0/bool · returned ndarray · level recorded 2026-09-24
get_dataloader in 111 papers utils/dataloader.py unverified licence not identified · pointer only · 38b6b384edfe5cc7 · report
image_description_generator model/imagemodel.py unverified licence not identified · pointer only · e2522a4d74f0b769 · report
postprocess_text in 21 papers model/nltoolkit.py unverified licence not identified · pointer only · eff19094fe0ec70e · report

Tasks

Image CaptioningLanguage ModelingLanguage ModellingQuestion AnsweringTrajectory Predictionregression

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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