SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 1903.07933 · 2019

What the Constant Velocity Model Can Teach Us About Pedestrian Motion Prediction

arXiv · PDF · Open in the Atlas

Code that ran

4 of 6 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 3 have no contract verdict; 1 failure of our instrument; 2 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/1903.07933.json · badge: /api/ran/1903.07933.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
cschoeller/constant_velocity_pedestrian_motion canonical (classifier label)
classifier basis: classifier_2025
1 ran · 2 no recorded run
elbuco1/AttentionMechanismsTrajectoryPrediction community (classifier label)
classifier basis not recorded on the link
3 ran · 0 no recorded run
FunctionStatusWhere it lives
constant_velocity_model Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
cschoeller/constant_velocity_pedestrian_motion/evaluate.py
code served (permissive licence) · get_code("e9e82a2209496dde")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned Tensor, ndim 3, dtype family float, shape (12, 2, 2) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import numpy as np

torch.manual_seed(0)

class RunConfig:
    sequence_length = 20
    min_sequence_length = 10
    observed_history = 8
    sample = False
    num_samples = 20
    sample_angle_std = 25
    dataset_paths = ['./data/eth_univ', './data/eth_hotel', './data/ucy_zara01', './data/ucy_zara02', './data/ucy_univ']

# Create a small observed tensor
# Shape: (sequence_length, batch_size, 2) where 2 is x,y coordinates
observed = torch.randn(9, 2, 2)

ARGS = {
    "observed": observed,
    "sample": False
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 3, dtype family float, shape (12, 2, 2) — shape (12, 2, 2) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
find_file_by_extension Ran
ran on a synthesized input
elbuco1/AttentionMechanismsTrajectoryPrediction/src/features/helpers/helpers.py
code served (permissive licence) · get_code("cc4864b0de4744bb")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned list, ndim 1, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import os
import tempfile
import shutil

# Create a temporary directory with test files
temp_dir = tempfile.mkdtemp()

# Create some test files with different extensions
open(os.path.join(temp_dir, 'file1.txt'), 'w').close()
open(os.path.join(temp_dir, 'file2.txt'), 'w').close()
open(os.path.join(temp_dir, 'file3.py'), 'w').close()
open(os.path.join(temp_dir, 'file4.py'), 'w').close()
open(os.path.join(temp_dir, 'file5.json'), 'w').close()

# Create a subdirectory (which should not be included in file_list)
os.makedirs(os.path.join(temp_dir, 'subdir'), exist_ok=True)

ARGS = {
    'root': temp_dir,
    'ext': 'txt'
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
none outside the standard library — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type list, ndim 1, dtype family float — a list output has no array shape of its own; none is stated
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
min_max_scale Ran
ran on a synthesized input
elbuco1/AttentionMechanismsTrajectoryPrediction/src/features/helpers/helpers.py
code served (permissive licence) · get_code("093da9385c920cd8")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 2, dtype family float, shape (2, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import numpy as np

torch.manual_seed(0)

# Analyze the function:
# - x: numeric data (tensor or array) that gets scaled
# - min_: minimum value for normalization
# - max_: maximum value for normalization
# - frange: tuple of (lower_bound, upper_bound) for output range

# Create a small tensor for x
x = torch.tensor([[1.0, 2.0, 3.0, 4.0],
                   [5.0, 6.0, 7.0, 8.0]])

# Define min and max values
min_ = torch.tensor(1.0)
max_ = torch.tensor(8.0)

# Define the feature range (default is (0, 1))
frange = (0, 1)

ARGS = {
    'x': x,
    'min_': min_,
    'max_': max_,
    'frange': frange
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 2, dtype family float, shape (2, 4) — shape (2, 4) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
revert_min_max_scale Ran
ran on a synthesized input
elbuco1/AttentionMechanismsTrajectoryPrediction/src/features/helpers/helpers.py
code served (permissive licence) · get_code("e9c2176deb201fcf")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 2, dtype family float, shape (2, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import numpy as np

torch.manual_seed(0)

# Create simple tensor inputs for the function
x_scaled = torch.tensor([[0.2, 0.4, 0.6, 0.8],
                         [0.1, 0.3, 0.5, 0.7]], dtype=torch.float32)

min_ = torch.tensor([-1.0, -2.0, -3.0, -4.0], dtype=torch.float32)
max_ = torch.tensor([1.0, 2.0, 3.0, 4.0], dtype=torch.float32)

frange = (0, 1)

ARGS = {
    "x_scaled": x_scaled,
    "min_": min_,
    "max_": max_,
    "frange": frange
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 2, dtype family float, shape (2, 4) — shape (2, 4) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
evaluate_testset Not yet run
unverified (harvested, no recorded run)
cschoeller/constant_velocity_pedestrian_motion/evaluate.py
code served (permissive licence) · get_code("682d0b5698dcbcf9")
How it ran

no invocation recorded.

rel_to_abs Not yet run
unverified (harvested, no recorded run)
cschoeller/constant_velocity_pedestrian_motion/evaluate.py
code served (permissive licence) · get_code("f44792f1ecf2dd5e")
How it ran

no invocation recorded.

Also present in other papers' code

Of 6 samples lifted from this paper's linked repositories, 6 carry a function identity and 0 do not. Of the 6 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 6 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Pedestrian motion prediction is a fundamental task for autonomous robots and vehicles to operate safely. In recent years many complex approaches based on neural networks have been proposed to address this problem. In this work we show that - surprisingly - a simple Constant Velocity Model can outperform even state-of-the-art neural models. This indicates that either neural networks are not able to make use of the additional information they are provided with, or that this information is not as relevant as commonly believed. Therefore, we analyze how neural networks process their input and how it impacts their predictions. Our analysis reveals pitfalls in training neural networks for pedestrian motion prediction and clarifies false assumptions about the problem itself. In particular, neural networks implicitly learn environmental priors that negatively impact their generalization capability, the motion history of pedestrians is irrelevant and interactions are too complex to predict. Our work shows how neural networks for pedestrian motion prediction can be thoroughly evaluated and our results indicate which research directions for neural motion prediction are promising in future.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("1903.07933")
get_code_for_paper("1903.07933")
have("1903.07933")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/1903.07933.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/1903.07933.svg)](https://syntology.ai/paper/1903.07933)

Connect an agent — have() is free.