Papers › Total3DUnderstanding: Joint Layout, Object Pose and Mesh Reconstruction for Indoor...

Total3DUnderstanding: Joint Layout, Object Pose and Mesh Reconstruction for Indoor Scenes from a Single Image

27 Feb 2020CVPR 2020 6arXiv:2002.12212archive 2025-07-28

Yinyu Nie, Xiaoguang Han, Shihui Guo, Yujian Zheng, Jian Chang, Jian Jun Zhang

Semantic reconstruction of indoor scenes refers to both scene understanding and object reconstruction. Existing works either address one part of this problem or focus on independent objects. In this paper, we bridge the gap between understanding and reconstruction, and propose an end-to-end solution to jointly reconstruct room layout, object bounding boxes and meshes from a single image. Instead of separately resolving scene understanding and object reconstruction, our method builds upon a holistic scene context and proposes a coarse-to-fine hierarchy with three components: 1. room layout with camera pose; 2. 3D object bounding boxes; 3. object meshes. We argue that understanding the context of each component can assist the task of parsing the others, which enables joint understanding and reconstruction. The experiments on the SUN RGB-D and Pix3D datasets demonstrate that our method consistently outperforms existing methods in indoor layout estimation, 3D object detection and mesh reconstruction.

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 9 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) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 9 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 between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

yinyunie/Total3DUnderstanding officialmentioned on GitHubpytorchMITSyntology: 9 samples, 7 ran (0 instrument-failed) · 2 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

9 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) · 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.

7ran
2unverified

Licence: 0 of the 9 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 yinyunie/Total3DUnderstanding. “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.

yinyunie/Total3DUnderstanding official repository 9 samples, 7 ran (0 instrument-failed) · 2 unverified
find_optim_module models/optimizers.py ran MIT (permissive) · 7c5097f4707309ec · report fixture: signature net:callable/0/? · returned tuple · level recorded 2026-09-24
has_optim_in_children models/optimizers.py ran MIT (permissive) · 6456fb43944fedf5 · report fixture: signature subnet:callable/0/? · returned bool · level recorded 2026-09-24
load_device net_utils/utils.py ran MIT (permissive) · b0cbe76658e8cbd9 · report fixture: signature cfg:MockConfig/0/? · returned device · level recorded 2026-09-25
load_scheduler models/optimizers.py ran MIT (permissive) · 6993951c91b8384b · report fixture: signature config:dict/0/?, optimizer:SGD/0/? · returned ReduceLROnPlateau · level recorded 2026-09-25
num_from_bins net_utils/libs.py ran MIT (permissive) · 511b658275852213 · report fixture: signature bins:Tensor/2/float, cls:Tensor/1/int, reg:Tensor/1/float · returned Tensor · level recorded 2026-09-25
sample_points_on_edges net_utils/misc.py ran MIT (permissive) · 67a1fe9a74ab3c9e · report fixture: signature points:Tensor/3/float, edges:Tensor/3/int, quantity:int/0/int, mode:str/0/str · returned Tensor · level recorded 2026-09-25
to_dict_tensor net_utils/libs.py ran MIT (permissive) · ea8d8ed9d5ec6bb2 · report fixture: signature dicts:dict/0/?, if_cuda:bool/0/bool · returned dict · level recorded 2026-09-25
R_from_yaw_pitch_roll net_utils/libs.py unverified MIT (permissive) · 584839f99e9b512b · report
load_template in 8 papers net_utils/misc.py unverified MIT (permissive) · 23eae901d43d45b9 · report

Tasks

3D Object Detection3D Shape ReconstructionMonocular 3D Object DetectionObjectObject DetectionObject ReconstructionRoom Layout EstimationScene Understandingobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Shape Reconstruction Pix3D MGN CD 0.0836 #2 of 5 Archive leaderboard report
3D Shape Reconstruction Pix3D MGN EMD N/A #2 of 5 Archive leaderboard report
3D Shape Reconstruction Pix3D MGN IoU N/A #2 of 5 Archive leaderboard report
Monocular 3D Object Detection SUN RGB-D Total3D joint AP@0.15 (10 / NYU-37) 26.38 #3 of 7 Archive leaderboard report
Monocular 3D Object Detection SUN RGB-D Total3D joint AP@0.15 (NYU-37) 14.28 #3 of 7 Archive leaderboard report
Monocular 3D Object Detection SUN RGB-D Total3D w/o. joint AP@0.15 (10 / NYU-37) 23.32 #4 of 7 Archive leaderboard report
Monocular 3D Object Detection SUN RGB-D Total3D w/o. joint AP@0.15 (NYU-37) 13.25 #4 of 7 Archive leaderboard report
Room Layout Estimation SUN RGB-D Total3D joint Camera Pitch 3.15 #3 of 7 Archive leaderboard report
Room Layout Estimation SUN RGB-D Total3D joint Camera Roll 2.09 #3 of 7 Archive leaderboard report
Room Layout Estimation SUN RGB-D Total3D joint IoU 59.2 #3 of 7 Archive leaderboard report
Room Layout Estimation SUN RGB-D Total w/o. joint Camera Pitch 3.68 #4 of 7 Archive leaderboard report
Room Layout Estimation SUN RGB-D Total w/o. joint Camera Roll 2.59 #4 of 7 Archive leaderboard report
Room Layout Estimation SUN RGB-D Total w/o. joint IoU 57.6 #4 of 7 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