Papers › Boosting Monocular Depth Estimation Models to High-Resolution via Content-Adaptive...

Boosting Monocular Depth Estimation Models to High-Resolution via Content-Adaptive Multi-Resolution Merging

28 May 2021CVPR 2021 1arXiv:2105.14021archive 2025-07-28

S. Mahdi H. Miangoleh, Sebastian Dille, Long Mai, Sylvain Paris, Yağız Aksoy

Neural networks have shown great abilities in estimating depth from a single image. However, the inferred depth maps are well below one-megapixel resolution and often lack fine-grained details, which limits their practicality. Our method builds on our analysis on how the input resolution and the scene structure affects depth estimation performance. We demonstrate that there is a trade-off between a consistent scene structure and the high-frequency details, and merge low- and high-resolution estimations to take advantage of this duality using a simple depth merging network. We present a double estimation method that improves the whole-image depth estimation and a patch selection method that adds local details to the final result. We demonstrate that by merging estimations at different resolutions with changing context, we can generate multi-megapixel depth maps with a high level of detail using a pre-trained model.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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 2 code samples harvested from 1 repository linked to this paper: 2 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; every one of the 2 samples that ran constructed an object rather than computing a result. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 2 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.

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

compphoto/BoostingMonocularDepth officialpytorchSyntology: 2 samples, 2 ran (0 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

2 samples harvested: 2 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; every one of the 2 samples that ran constructed an object rather than computing a result. “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.

2ran

Licence: 2 of the 2 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 compphoto/BoostingMonocularDepth. “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”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

compphoto/BoostingMonocularDepth official repository 2 samples, 2 ran (0 instrument-failed) · 0 unverified
FFM lib/network_auxi.py ran licence not identified · pointer only · fa52eddca77318d6 · report fixture: returned FFM · level recorded 2026-09-22
FTB lib/network_auxi.py ran fingerprinted licence not identified · pointer only · cb0120387905f7c3 · report fixture: returned FTB · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Content-Adaptive Multi-Resolution Merging (graph method: Content-Adaptive Multi-Resolution Merging). 2 bricks; individually on a fixture: 2 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; every one of the 2 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

  1. FFM entry · level 1 · ran · fa52eddca77318d6
  2. FTB helper · level 1 · ran · cb0120387905f7c3

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2105.14021") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Depth EstimationMonocular Depth Estimation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Monocular Depth Estimation IBims-1 Miangoleh et al. (SGR) D3R 0.3222 #1 of 4 Archive leaderboard report
Monocular Depth Estimation IBims-1 Miangoleh et al. (SGR) ORD 0.3938 #1 of 4 Archive leaderboard report
Monocular Depth Estimation IBims-1 Miangoleh et al. (SGR) RMSE 0.1598 #1 of 4 Archive leaderboard report
Monocular Depth Estimation IBims-1 Miangoleh et al. (SGR) δ1.25 0.6390 #1 of 4 Archive leaderboard report
Monocular Depth Estimation IBims-1 Miangoleh et al. (MiDaS) D3R 0.4671 #2 of 4 Archive leaderboard report
Monocular Depth Estimation IBims-1 Miangoleh et al. (MiDaS) ORD 0.5538 #2 of 4 Archive leaderboard report
Monocular Depth Estimation IBims-1 Miangoleh et al. (MiDaS) RMSE 0.1965 #2 of 4 Archive leaderboard report
Monocular Depth Estimation IBims-1 Miangoleh et al. (MiDaS) δ1.25 0.7460 #2 of 4 Archive leaderboard report
Monocular Depth Estimation Middlebury 2014 Miangoleh et al. (MiDaS) D3R 0.1578 #1 of 2 Archive leaderboard report
Monocular Depth Estimation Middlebury 2014 Miangoleh et al. (MiDaS) ORD 0.3467 #1 of 2 Archive leaderboard report
Monocular Depth Estimation Middlebury 2014 Miangoleh et al. (MiDaS) RMSE 0.1557 #1 of 2 Archive leaderboard report
Monocular Depth Estimation Middlebury 2014 Miangoleh et al. (MiDaS) δ1.25 0.7406 #1 of 2 Archive leaderboard report
Monocular Depth Estimation Middlebury 2014 Miangoleh et al. (SGR) D3R 0.2324 #2 of 2 Archive leaderboard report
Monocular Depth Estimation Middlebury 2014 Miangoleh et al. (SGR) ORD 0.3879 #2 of 2 Archive leaderboard report
Monocular Depth Estimation Middlebury 2014 Miangoleh et al. (SGR) RMSE 0.1973 #2 of 2 Archive leaderboard report
Monocular Depth Estimation Middlebury 2014 Miangoleh et al. (SGR) δ1.25 0.7891 #2 of 2 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