Papers › Predicting 3D Human Dynamics from Video

Predicting 3D Human Dynamics from Video

13 Aug 2019ICCV 2019 10arXiv:1908.04781archive 2025-07-28

Jason Y. Zhang, Panna Felsen, Angjoo Kanazawa, Jitendra Malik

Given a video of a person in action, we can easily guess the 3D future motion of the person. In this work, we present perhaps the first approach for predicting a future 3D mesh model sequence of a person from past video input. We do this for periodic motions such as walking and also actions like bowling and squatting seen in sports or workout videos. While there has been a surge of future prediction problems in computer vision, most approaches predict 3D future from 3D past or 2D future from 2D past inputs. In this work, we focus on the problem of predicting 3D future motion from past image sequences, which has a plethora of practical applications in autonomous systems that must operate safely around people from visual inputs. Inspired by the success of autoregressive models in language modeling tasks, we learn an intermediate latent space on which we predict the future. This effectively facilitates autoregressive predictions when the input differs from the output domain. Our approach can be trained on video sequences obtained in-the-wild without 3D ground truth labels. The project website with videos can be found at https://jasonyzhang.com/phd.

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

By repository: official repository: 17 samples from 1 repository, 7 ran (7 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 on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

jasonyzhang/phd officialtfBSD-2-ClauseSyntology: 17 samples, 7 ran (0 instrument-failed) · 10 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

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

7ran
10unverified

Licence: 0 of the 17 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 jasonyzhang/phd. “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.

jasonyzhang/phd official repository 17 samples, 7 ran (0 instrument-failed) · 10 unverified
get_dims src/renderer.py ran fingerprinted BSD-2-Clause (permissive) · 695ee32917b465d7 · report fixture: signature x:Tensor/2/float · returned int · level recorded 2026-09-25
get_labels_poseflow src/extract_tracks.py ran BSD-2-Clause (permissive) · 3a63d35b434d3196 · report fixture: signature json_path:str/0/str, num_frames:int/0/int, min_kp_count:int/0/int · returned list · level recorded 2026-09-25
process_videos src/evaluation/run_video.py ran BSD-2-Clause (permissive) · 2cde9da4227a4934 · report fixture: signature config:Config/0/?, images:list/1/ndarray, T:int/0/int, suffix:str/0/str · returned tuple · level recorded 2026-09-25
tf_pad src/ops.py ran BSD-2-Clause (permissive) · 05191822268f47e6 · report fixture: signature tensor:EagerTensor/2/float, paddings:list/1/list, mode:str/0/str · returned EagerTensor · level recorded 2026-09-25
to_float_tensor src/renderer.py ran BSD-2-Clause (permissive) · e5f55a88efd3909d · report fixture: signature x:ndarray/2/float · returned Tensor · level recorded 2026-09-25
to_variable in 6 papers src/renderer.py ran fingerprinted BSD-2-Clause (permissive) · 2e0b2d1dc17197f6 · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-25
undo_chumpy src/tf_smpl/batch_smpl.py ran fingerprinted BSD-2-Clause (permissive) · e24744b154d5aa09 · report fixture: signature x:ndarray/2/int · returned ndarray · level recorded 2026-09-25
batch_orth_proj_idrot src/tf_smpl/projection.py unverified BSD-2-Clause (permissive) · 74c9b49c72a62f9d · report
batch_orth_proj_optcam src/tf_smpl/projection.py unverified BSD-2-Clause (permissive) · c7079337574a09d2 · report
batch_rodrigues in 15 papers src/tf_smpl/batch_lbs.py unverified BSD-2-Clause (permissive) · 785c66706574bea1 · report
batch_rot2aa src/tf_smpl/batch_lbs.py unverified BSD-2-Clause (permissive) · 5b19861e6645f0be · report
batch_skew src/tf_smpl/batch_lbs.py unverified BSD-2-Clause (permissive) · fca9ceed95411f50 · report
compute_tracks src/extract_tracks.py unverified BSD-2-Clause (permissive) · b29fcb58b1cffa5f · report
get_output_path_name src/evaluation/run_video.py unverified BSD-2-Clause (permissive) · 59c1352c7c8f0c7b · report
procrustes2d_vis src/tf_smpl/projection.py unverified BSD-2-Clause (permissive) · 8a9b610b726cca33 · report
resize_img in 31 papers src/util/common.py unverified BSD-2-Clause (permissive) · ab7d47670a4b49ba · report
run_poseflow src/extract_tracks.py unverified BSD-2-Clause (permissive) · 0b220a0d1abc1008 · report

Tasks

3D Human Dynamics3D Human Pose EstimationFuture predictionHuman DynamicsLanguage ModelingLanguage Modelling

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