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 repositories, every harvested function with whether it ran, its licence and the call to fetch it.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2112.08274")

Code

Syntology Ran 3 of 8 code samples harvested from 2 repositories linked to this paper; 5 have no recorded run. Of those that ran: 1 ran · honoured contract; 1 ran · fixture could not drive it; 1 ran with no contract checked.

By repository: official repository: 3 samples from 1 repository, 2 ran; community (archive-listed): 5 samples from 1 repository, 1 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Arthur151/ROMP officialmentioned in papermentioned on GitHubpytorchApache-2.0 report
Arthur151/Relative_Human officialmentioned in papermentioned on GitHubpytorch report
Arthur151/CenterHMR mentioned on GitHubpytorchApache-2.0 report
cai-jianfeng/ROMP_mindspore mentioned on GitHubmindsporeApache-2.0 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

8 samples harvested; 3 ran; 1 honoured the contract we drafted; 5 have no recorded run. Read from Syntology's graph 2026-09-25; that is when this build read the record, not when the samples ran.

1ran · honoured contract
1ran · fixture could not drive it
1ran
5unverified

Licence: 3 of the 8 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 2 repositories linked to this paper, official or community; each sample names its own and says which. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

compute_prf1 Arthur151/Relative_Human/RH_evaluation/evaluation.py official repository ran · honoured contract no licence file found · pointer only · 77840d506f4c57cf · report
get_results Arthur151/Relative_Human/RH_evaluation/evaluation.py official repository ran · fixture could not drive it no licence file found · pointer only · bad47202c970ebbf · report
joint_mapping Arthur151/Relative_Human/RH_evaluation/evaluation.py official repository unverified no licence file found · pointer only · 491106b5da444b53 · report
cam2pixel cai-jianfeng/ROMP_mindspore/romp/lib/dataset/MuPoTS.py community (archive-listed) ran fingerprinted Apache-2.0 (permissive) · 5bbf1999f902db71 · report
BHWC_to_BCHW cai-jianfeng/ROMP_mindspore/simple_romp/romp/model.py community (archive-listed) unverified Apache-2.0 (permissive) · eeaac5bd5e411a86 · report
get_cam3dmap_anchor cai-jianfeng/ROMP_mindspore/romp/lib/constants.py community (archive-listed) unverified Apache-2.0 (permissive) · cc1a3cf9d8e4ab4f · report
parse_args cai-jianfeng/ROMP_mindspore/romp/lib/config.py community (archive-listed) unverified Apache-2.0 (permissive) · a656a9f06447e9fe · report
read_calibration cai-jianfeng/ROMP_mindspore/romp/lib/dataset/MuCo.py community (archive-listed) 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