Papers › PointOdyssey: A Large-Scale Synthetic Dataset for Long-Term Point Tracking

PointOdyssey: A Large-Scale Synthetic Dataset for Long-Term Point Tracking

27 Jul 2023ICCV 2023 1arXiv:2307.15055archive 2025-07-28

Yang Zheng, Adam W. Harley, Bokui Shen, Gordon Wetzstein, Leonidas J. Guibas

We introduce PointOdyssey, a large-scale synthetic dataset, and data generation framework, for the training and evaluation of long-term fine-grained tracking algorithms. Our goal is to advance the state-of-the-art by placing emphasis on long videos with naturalistic motion. Toward the goal of naturalism, we animate deformable characters using real-world motion capture data, we build 3D scenes to match the motion capture environments, and we render camera viewpoints using trajectories mined via structure-from-motion on real videos. We create combinatorial diversity by randomizing character appearance, motion profiles, materials, lighting, 3D assets, and atmospheric effects. Our dataset currently includes 104 videos, averaging 2,000 frames long, with orders of magnitude more correspondence annotations than prior work. We show that existing methods can be trained from scratch in our dataset and outperform the published variants. Finally, we introduce modifications to the PIPs point tracking method, greatly widening its temporal receptive field, which improves its performance on PointOdyssey as well as on two real-world benchmarks. Our data and code are publicly available at: https://pointodyssey.com

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 3 repositories linked to this paper: 12 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 1 honoured, 0 violated, 11 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: official repository: 8 samples from 1 repository, 8 ran (8 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 5 samples from 2 repositories, 4 ran (4 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-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

y-zheng18/point_odyssey officialmentioned on GitHubNOASSERTIONSyntology: 8 samples, 8 ran (0 instrument-failed) · 0 unverified report
aharley/pips2 mentioned on GitHubpytorchMITSyntology: 3 samples, 3 ran (0 instrument-failed) · 0 unverified report
aliciachenw/PIPsUS mentioned on GitHubpytorchSyntology: 2 samples, 1 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

13 samples harvested: 12 ran (of which 0 constructed an object rather than computing a result; 12 with no instrument failure: 1 honoured, 0 violated, 11 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.

1ran · honoured contract
11ran
1unverified

Licence: 8 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 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

y-zheng18/point_odyssey official repository 8 samples, 8 ran (0 instrument-failed) · 0 unverified
as_path utils/file_io.py ran licence not identified · pointer only · 2cb7740d09d1d57c · report fixture: signature path:str/0/str · returned PosixGPath · level recorded 2026-09-24
farthest_point_sampling utils/gen_tracking.py ran fingerprinted licence not identified · pointer only · b360fe44d7520e4a · report fixture: signature p:ndarray/2/float, K:int/0/int · returned tuple · level recorded 2026-09-24
get_calibration_matrix_K_from_blender render_animal.py ran licence not identified · pointer only · 4f778b5ed0da9d1f · report fixture: signature scene:MockScene/0/?, mode:str/0/str · returned ndarray · level recorded 2026-09-24
get_intrinsics render_single.py ran licence not identified · pointer only · 0bc392e72f43660f · report fixture: signature scene:MockScene/0/? · returned ndarray · level recorded 2026-09-24
read_json in 250 papers utils/file_io.py ran licence not identified · pointer only · 21dd9ba5d9e47a8f · report fixture: signature filename:str/0/str · returned dict · level recorded 2026-09-24
read_obj_file render_animal.py ran licence not identified · pointer only · ba4494dbb46634a4 · report fixture: signature obj_file_path:str/0/str · returned tuple · level recorded 2026-09-24
read_obj_file utils/gen_tracking.py ran licence not identified · pointer only · cf0f39e1349d5322 · report fixture: signature obj_path:str/0/str · returned tuple · level recorded 2026-09-24
reprojection utils/gen_tracking.py ran licence not identified · pointer only · 5bdab6524d5a227a · report fixture: signature points:ndarray/2/float, K:ndarray/2/float, RT:ndarray/2/float, h:int/0/int, w:int/0/int · returned tuple · level recorded 2026-09-24
aharley/pips2 community (archive-listed) 3 samples, 3 ran (0 instrument-failed) · 0 unverified
fetch_optimizer in 8 papers finetune_highres.py ran MIT (permissive) · 257df3eb14fc528b · report fixture: signature lr:float/0/float, wdecay:float/0/float, epsilon:float/0/float, num_steps:int/0/int, params:generator/0/? · returned tuple · level recorded 2026-09-24
load in 392 papers saverloader.py ran MIT (permissive) · 7cc0ed613ecce873 · report fixture: signature ckpt_dir:str/0/str, model:callable/0/?, optimizer:SGD/0/?, scheduler:StepLR/0/?, step:int/0/int, model_name:str/0/str, ignore_load:NoneType/0/? · returned int · level recorded 2026-09-24
read_mp4 datasets/exportdataset.py ran fingerprinted MIT (permissive) · 7617204334d1d459 · report fixture: signature fn:str/0/str · returned list · level recorded 2026-09-24
aliciachenw/PIPsUS community (archive-listed) 2 samples, 1 ran (0 instrument-failed) · 1 unverified
coords_grid in 24 papers nets/pipsUS.py ran · honoured contract fingerprinted MIT (permissive) · ea43be6c224959b1 · report fixture: signature batch:int/0/int, ht:int/0/int, wd:int/0/int · returned Tensor · level recorded 2026-09-22
bilinear_sampler in 23 papers nets/pipsUS.py unverified MIT (permissive) · 1ac8cce613d98769 · report

Tasks

DiversityPoint Tracking

Datasets

Introduced by this paper, per the archive.

PointOdyssey

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Point Tracking PointOdyssey PIPs++ MTE 26.95 #1 of 2 Archive leaderboard report
Point Tracking PointOdyssey PIPs++ Survival 50.47 #1 of 2 Archive leaderboard report
Point Tracking PointOdyssey PIPs++ δ 33.64 #1 of 2 Archive leaderboard report
Point Tracking PointOdyssey PIPs+ Survival 49.88 #2 of 2 Archive leaderboard report
Point Tracking PointOdyssey PIPs+ δ 32.41 #2 of 2 Archive leaderboard report
Point Tracking TAP-Vid PIPs++ MTE 4.6 #1 of 1 Archive leaderboard report
Point Tracking TAP-Vid PIPs++ Survival 88.42 #1 of 1 Archive leaderboard report
Point Tracking TAP-Vid PIPs++ δ 63.45 #1 of 1 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