Papers › A simple yet effective baseline for 3d human pose estimation

A simple yet effective baseline for 3d human pose estimation

8 May 2017ICCV 2017 10arXiv:1705.03098archive 2025-07-28

Julieta Martinez, Rayat Hossain, Javier Romero, James J. Little

Following the success of deep convolutional networks, state-of-the-art methods for 3d human pose estimation have focused on deep end-to-end systems that predict 3d joint locations given raw image pixels. Despite their excellent performance, it is often not easy to understand whether their remaining error stems from a limited 2d pose (visual) understanding, or from a failure to map 2d poses into 3-dimensional positions. With the goal of understanding these sources of error, we set out to build a system that given 2d joint locations predicts 3d positions. Much to our surprise, we have found that, with current technology, "lifting" ground truth 2d joint locations to 3d space is a task that can be solved with a remarkably low error rate: a relatively simple deep feed-forward network outperforms the best reported result by about 30% on Human3.6M, the largest publicly available 3d pose estimation benchmark. Furthermore, training our system on the output of an off-the-shelf state-of-the-art 2d detector (i.e., using images as input) yields state of the art results -- this includes an array of systems that have been trained end-to-end specifically for this task. Our results indicate that a large portion of the error of modern deep 3d pose estimation systems stems from their visual analysis, and suggests directions to further advance the state of the art in 3d human pose estimation.

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

The archive's official repository (una-dinosauria/3d-pose-baseline) was not harvested; the 7 samples below come from 3 community repositories.

Syntology 7 code samples harvested from 3 repositories linked to this paper: 5 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 4 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 4 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 7 samples from 3 repositories, 5 ran (1 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.

No sample is linked to this paper from 3 of its repositories that Syntology harvested for other papers:

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

14 repositories listed; official and paper-mentioned ones first.

una-dinosauria/3d-pose-baseline officialmentioned in papermentioned on GitHubtfSyntology: not harvested report
SJTU-DL-lab/3d-pose-baseline mentioned on GitHubtfSyntology: 1 sample, 0 ran · 1 unverified report
ZHONGCHUYUN/3d_pose_baseline_tf mentioned on GitHubtfSyntology: 2 samples, 1 ran (1 instrument-failed) · 1 unverified report
ailingzengzzz/Split-and-Recombine-Net mentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to SRNet: Improving Generalization in 3D Human Pose Estimation with a Split-and-Recombine Approach (arXiv:2007.09389; that paper's own run record: 6 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 3 unverified); nothing checks that they implement this paper's method. report
denilson020898/baseline_3d_pose mentioned on GitHubpytorchSyntology: not harvested report
garyzhao/SemGCN mentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Semantic Graph Convolutional Networks for 3D Human Pose Regression (arXiv:1904.03345; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 5 unverified); nothing checks that they implement this paper's method. report
happyvictor008/High-order-GNN-LF-iter mentioned on GitHubpytorchSyntology: not harvested report
jaroslaw1007/Pose_Baseline_3D_PyTorch mentioned on GitHubpytorchSyntology: not harvested report
llSourcell/3D_Pose_Estimation mentioned on GitHubtfSyntology: not harvested report
serviceberry3/3d-pose-baseline_android mentioned on GitHubtfSyntology: not harvested report
sidify/3d-pose-estimation mentioned on GitHubtfSyntology: 4 samples, 4 ran (3 instrument-failed) · 0 unverified report
sidsunny/human-pose-estimation-mlsp mentioned on GitHubtfSyntology: not harvested report
zhimingzo/modulated-gcn mentioned on GitHubpytorchSyntology: not harvested report
open-mmlab/mmpose pytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to RTMO: Towards High-Performance One-Stage Real-Time Multi-Person Pose Estimation (arXiv:2312.07526; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

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

Licence: 0 of the 7 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.

SJTU-DL-lab/3d-pose-baseline community (archive-listed) 1 sample, 0 ran · 1 unverified
normalization_stats src/data_utils.py unverified MIT (permissive) · 9088d315ea27a453 · report
ZHONGCHUYUN/3d_pose_baseline_tf community (archive-listed) 2 samples, 1 ran (1 instrument-failed) · 1 unverified
show_anim_curves src/openpose_3dpose_sandbox.py ran · our draft was wrong MIT (permissive) · a5dc69f01bac53c1 · report fixture: signature anim_dict:dict/0/?, _plt:module/0/? · returned module · level recorded 2026-09-22
read_openpose_json src/openpose_3dpose_sandbox.py unverified MIT (permissive) · 6bbbd96794d5994d · report
sidify/3d-pose-estimation community (archive-listed) 4 samples, 4 ran (3 instrument-failed) · 0 unverified
angle_between src/kinematics.py ran · our draft was wrong fingerprinted MIT (permissive) · c9e9ff520e9b4533 · report fixture: signature v1:list/1/float, v2:list/1/float · returned float · level recorded 2026-09-22
dotproduct src/kinematics.py ran · violated contract fingerprinted MIT (permissive) · 2b344ab200743c2d · report fixture: signature v1:list/1/float, v2:list/1/float · returned float · level recorded 2026-09-22
get_action_subset src/predict_3dpose.py ran · our draft was wrong MIT (permissive) · f5eee6f4a7a2d3ce · report fixture: signature poses_set:dict/0/?, action:str/0/str · returned dict · level recorded 2026-09-22
length in 22 papers src/kinematics.py ran · our draft was wrong fingerprinted MIT (permissive) · c98211090c8cd833 · report fixture: signature v:list/1/float · returned float · level recorded 2026-09-22

Tasks

3D Human Pose Estimation3D Pose EstimationMonocular 3D Human Pose EstimationPose Estimation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Human Pose Estimation 3DPW Simple-baseline PA-MPJPE 157.0 #113 of 119 Archive leaderboard report
3D Human Pose Estimation Human3.6M SIM (SH detections FT) (MA) Average MPJPE (mm) 62.9 #85 of 88 Archive leaderboard report
3D Human Pose Estimation Human3.6M SIM (SH detections FT) (MA) Multi-View or Monocular Monocular #85 of 88 Archive leaderboard report
3D Human Pose Estimation Human3.6M SIM (SH detections FT) (MA) Using 2D ground-truth joints No #85 of 88 Archive leaderboard report
3D Human Pose Estimation HumanEva-I SIM (SH detections) Mean Reconstruction Error (mm) 24.6 #20 of 31 Archive leaderboard report
Monocular 3D Human Pose Estimation Human3.6M SIM (SH detections FT) (MA) Average MPJPE (mm) 62.9 #31 of 52 Archive leaderboard report
Monocular 3D Human Pose Estimation Human3.6M SIM (SH detections FT) (MA) Frames Needed 1 #31 of 52 Archive leaderboard report
Monocular 3D Human Pose Estimation Human3.6M SIM (SH detections FT) (MA) Need Ground Truth 2D Pose No #31 of 52 Archive leaderboard report
Monocular 3D Human Pose Estimation Human3.6M SIM (SH detections FT) (MA) Use Video Sequence No #31 of 52 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