Papers › Putting People in their Place: Monocular Regression of 3D People in Depth

Putting People in their Place: Monocular Regression of 3D People in Depth

15 Dec 2021CVPR 2022 1arXiv:2112.08274archive 2025-07-28

Yu Sun, Wu Liu, Qian Bao, Yili Fu, Tao Mei, Michael J. Black

Given an image with multiple people, our goal is to directly regress the pose and shape of all the people as well as their relative depth. Inferring the depth of a person in an image, however, is fundamentally ambiguous without knowing their height. This is particularly problematic when the scene contains people of very different sizes, e.g. from infants to adults. To solve this, we need several things. First, we develop a novel method to infer the poses and depth of multiple people in a single image. While previous work that estimates multiple people does so by reasoning in the image plane, our method, called BEV, adds an additional imaginary Bird's-Eye-View representation to explicitly reason about depth. BEV reasons simultaneously about body centers in the image and in depth and, by combing these, estimates 3D body position. Unlike prior work, BEV is a single-shot method that is end-to-end differentiable. Second, height varies with age, making it impossible to resolve depth without also estimating the age of people in the image. To do so, we exploit a 3D body model space that lets BEV infer shapes from infants to adults. Third, to train BEV, we need a new dataset. Specifically, we create a "Relative Human" (RH) dataset that includes age labels and relative depth relationships between the people in the images. Extensive experiments on RH and AGORA demonstrate the effectiveness of the model and training scheme. BEV outperforms existing methods on depth reasoning, child shape estimation, and robustness to occlusion. The code and dataset are released for research purposes.

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

By repository: official repository: 3 samples from 1 repository, 2 ran (1 with no instrument failure; 1 where Syntology's instrument failed); community (archive-listed): 5 samples from 1 repository, 2 ran (2 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.

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

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

Arthur151/ROMP officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to TRACE: 5D Temporal Regression of Avatars with Dynamic Cameras in 3D Environments (arXiv:2306.02850; that paper's own run record: 15 ran (of which 0 constructed an object rather than computing a result; 13 with no instrument failure: 0 honoured, 0 violated, 13 with no contract checked; 2 where Syntology's instrument failed) · 5 unverified); nothing checks that they implement this paper's method. report
Arthur151/Relative_Human officialmentioned in papermentioned on GitHubpytorchSyntology: 3 samples, 2 ran (1 instrument-failed) · 1 unverified report
Arthur151/CenterHMR mentioned on GitHubpytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to TRACE: 5D Temporal Regression of Avatars with Dynamic Cameras in 3D Environments (arXiv:2306.02850; that paper's own run record: 15 ran (of which 0 constructed an object rather than computing a result; 13 with no instrument failure: 0 honoured, 0 violated, 13 with no contract checked; 2 where Syntology's instrument failed) · 5 unverified); nothing checks that they implement this paper's method. report
cai-jianfeng/ROMP_mindspore mentioned on GitHubmindsporeApache-2.0Syntology: 5 samples, 2 ran (0 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.

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

8 samples harvested: 4 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 0 violated, 2 with no contract checked; 1 where Syntology's instrument failed) · 4 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
1ran; the contract check could not run
2ran
4unverified

Licence: 4 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. For 1 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 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.

Arthur151/Relative_Human official repository 3 samples, 2 ran (1 instrument-failed) · 1 unverified
compute_prf1 RH_evaluation/evaluation.py ran · honoured contract fingerprinted no licence file found · pointer only · 77840d506f4c57cf · report fixture: signature count:int/0/int, miss:int/0/int, fp:int/0/int · returned tuple · level recorded 2026-09-22
get_results in 29 papers RH_evaluation/evaluation.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic no licence file found · pointer only · bad47202c970ebbf · report fixture: signature depth_relative:dict/0/?, missed_age_ids:Tensor/1/int, dr_thresh:float/0/float, miss_fine:float/0/float · returned dict · level recorded 2026-09-22
joint_mapping RH_evaluation/evaluation.py unverified no licence file found · pointer only · 491106b5da444b53 · report
cai-jianfeng/ROMP_mindspore community (archive-listed) 5 samples, 2 ran (0 instrument-failed) · 3 unverified
BHWC_to_BCHW simple_romp/romp/model.py ran fingerprinted Apache-2.0 (permissive) · eeaac5bd5e411a86 · report fixture: signature x:Tensor/4/float · returned Tensor · level recorded 2026-09-26
cam2pixel in 8 papers romp/lib/dataset/MuPoTS.py ran fingerprinted Apache-2.0 (permissive) here; the stored copy is pointer only · 5bbf1999f902db71 · report fixture: signature cam_coord:ndarray/2/float, f:ndarray/1/float, c:ndarray/1/float · returned ndarray · level recorded 2026-09-24
get_cam3dmap_anchor romp/lib/constants.py unverified Apache-2.0 (permissive) · cc1a3cf9d8e4ab4f · report
parse_args in 355 papers romp/lib/config.py unverified Apache-2.0 (permissive) · a656a9f06447e9fe · report
read_calibration romp/lib/dataset/MuCo.py unverified Apache-2.0 (permissive) · 42b00d7c582e6acd · report

Tasks

3D Depth Estimationregression

Datasets

Introduced by this paper, per the archive.

Relative Human

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Depth Estimation Relative Human BEV PCDR 68.27 #1 of 3 Archive leaderboard report
3D Depth Estimation Relative Human BEV PCDR-Adult 69.71 #1 of 3 Archive leaderboard report
3D Depth Estimation Relative Human BEV PCDR-Baby 60.77 #1 of 3 Archive leaderboard report
3D Depth Estimation Relative Human BEV PCDR-Kid 67.09 #1 of 3 Archive leaderboard report
3D Depth Estimation Relative Human BEV PCDR-Teen 66.07 #1 of 3 Archive leaderboard report
3D Depth Estimation Relative Human BEV mPCDK 0.884 #1 of 3 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