Papers › LED2-Net: Monocular 360 Layout Estimation via Differentiable Depth Rendering

LED2-Net: Monocular 360 Layout Estimation via Differentiable Depth Rendering

1 Apr 2021arXiv:2104.00568archive 2025-07-28

Fu-En Wang, Yu-Hsuan Yeh, Min Sun, Wei-Chen Chiu, Yi-Hsuan Tsai

Although significant progress has been made in room layout estimation, most methods aim to reduce the loss in the 2D pixel coordinate rather than exploiting the room structure in the 3D space. Towards reconstructing the room layout in 3D, we formulate the task of 360 layout estimation as a problem of predicting depth on the horizon line of a panorama. Specifically, we propose the Differentiable Depth Rendering procedure to make the conversion from layout to depth prediction differentiable, thus making our proposed model end-to-end trainable while leveraging the 3D geometric information, without the need of providing the ground truth depth. Our method achieves state-of-the-art performance on numerous 360 layout benchmark datasets. Moreover, our formulation enables a pre-training step on the depth dataset, which further improves the generalizability of our layout estimation model.

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

By repository: official repository: 10 samples from 1 repository, 10 ran (9 with no instrument failure; 1 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-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

fuenwang/LED2-Net officialpytorchMITSyntology: 10 samples, 10 ran (1 instrument-failed) · 0 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

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

Licence: 0 of the 10 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 fuenwang/LED2-Net. “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.

fuenwang/LED2-Net official repository 10 samples, 10 ran (1 instrument-failed) · 0 unverified
XY2json LED2Net/IOjson.py ran MIT (permissive) · c8eaa407a1e421f2 · report fixture: signature XY:ndarray/2/float, y:float/0/float, h:float/0/float, dim:int/0/int, meters:float/0/float · returned dict · level recorded 2026-09-25
XY2lonlat LED2Net/Conversion/EquirecCoordinate.py ran MIT (permissive) · ab0422c369265bf8 · report fixture: signature xy:ndarray/2/float, shape:tuple/1/int, mode:str/0/str · returned ndarray · level recorded 2026-09-25
XY2xyz LED2Net/Conversion/EquirecCoordinate.py ran MIT (permissive) · 5907af8147d2f4bc · report fixture: signature xy:ndarray/3/float, shape:tuple/1/int, mode:str/0/str · returned ndarray · level recorded 2026-09-25
errorCalculate LED2Net/PostProcessing.py ran MIT (permissive) · 7e1eba510ae651bd · report fixture: signature ratio:float/0/float, up_norm:ndarray/1/float, down_norm:ndarray/1/float · returned ndarray · level recorded 2026-09-25
homogeneous LED2Net/Conversion/MatrixTools.py ran fingerprinted MIT (permissive) · 4d466189f21b7855 · report fixture: signature tensor:Tensor/2/float · returned Tensor · level recorded 2026-09-25
interpolate in 95 papers LED2Net/IOjson.py ran MIT (permissive) · 5c9b2483d562092d · report fixture: signature a:ndarray/1/float, b:ndarray/1/float, count:int/0/int · returned ndarray · level recorded 2026-09-25
lonlat2xyz LED2Net/Conversion/EquirecCoordinate.py ran MIT (permissive) · 4907f6ce41bc7042 · report fixture: signature lonlat:ndarray/3/float, RADIUS:float/0/float, mode:str/0/str · returned ndarray · level recorded 2026-09-25
lr_pad LED2Net/Network.py ran · our draft was wrong fingerprinted MIT (permissive) · fb884f33b5fda8ea · report fixture: signature x:Tensor/4/float, padding:int/0/int · returned Tensor · level recorded 2026-09-22
normalizeDepth LED2Net/Tools.py ran fingerprinted MIT (permissive) · 9ac2a3c4a05a69ae · report fixture: signature depth:Tensor/4/float · returned Tensor · level recorded 2026-09-25
xyz2json LED2Net/IOjson.py ran MIT (permissive) · e1dc5bd0e4f3f8e9 · report fixture: signature xyz:ndarray/2/float, h:float/0/float · returned dict · level recorded 2026-09-25

Tasks

3D Room Layouts From A Single RGB PanoramaDepth EstimationDepth PredictionRoom Layout Estimation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Room Layouts From A Single RGB Panorama Stanford2D3D Panoramic LED2-Net 3DIoU 83.77 #3 of 9 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