Papers › MINE: Towards Continuous Depth MPI with NeRF for Novel View Synthesis

MINE: Towards Continuous Depth MPI with NeRF for Novel View Synthesis

27 Mar 2021ICCV 2021 10arXiv:2103.14910archive 2025-07-28

Jiaxin Li, Zijian Feng, Qi She, Henghui Ding, Changhu Wang, Gim Hee Lee

In this paper, we propose MINE to perform novel view synthesis and depth estimation via dense 3D reconstruction from a single image. Our approach is a continuous depth generalization of the Multiplane Images (MPI) by introducing the NEural radiance fields (NeRF). Given a single image as input, MINE predicts a 4-channel image (RGB and volume density) at arbitrary depth values to jointly reconstruct the camera frustum and fill in occluded contents. The reconstructed and inpainted frustum can then be easily rendered into novel RGB or depth views using differentiable rendering. Extensive experiments on RealEstate10K, KITTI and Flowers Light Fields show that our MINE outperforms state-of-the-art by a large margin in novel view synthesis. We also achieve competitive results in depth estimation on iBims-1 and NYU-v2 without annotated depth supervision. Our source code is available at https://github.com/vincentfung13/MINE

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

By repository: official repository: 7 samples from 1 repository, 5 ran (0 with no instrument failure; 5 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.

vincentfung13/MINE officialmentioned in paperpytorchSyntology: 7 samples, 5 ran (5 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

7 samples harvested: 5 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure 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.

3ran · our draft was wrong
2ran; the contract check could not run
2unverified

Licence: 0 of the 7 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 vincentfung13/MINE. “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.

vincentfung13/MINE official repository 7 samples, 5 ran (5 instrument-failed) · 2 unverified
alpha_composition operations/mpi_rendering.py ran · our draft was wrong MIT (permissive) · 7525a41074955b82 · report fixture: signature alpha_BK1HW:Tensor/5/float, value_BKCHW:Tensor/5/float · returned tuple · level recorded 2026-09-22
inverse in 15 papers operations/mpi_rendering.py ran; the contract check could not run (RAISES) MIT (permissive) · 3c56cc2b3ae0cce5 · report fixture: returned Tensor · level recorded 2026-09-22
plane_volume_rendering operations/mpi_rendering.py ran · our draft was wrong MIT (permissive) · 1c9f33a62f20f378 · report fixture: signature rgb_BS3HW:Tensor/5/float, sigma_BS1HW:Tensor/5/float, xyz_BS3HW:Tensor/5/float, is_bg_depth_inf:bool/0/bool · returned tuple · level recorded 2026-09-22
render in 19 papers operations/mpi_rendering.py ran; the contract check could not run (RAISES) MIT (permissive) · 5ecf76e78c778112 · report fixture: signature rgb_BS3HW:Tensor/5/float, sigma_BS1HW:Tensor/5/float, xyz_BS3HW:Tensor/5/float, use_alpha:bool/0/bool, is_bg_depth_inf:bool/0/bool · returned tuple · level recorded 2026-09-22
weighted_sum_mpi operations/mpi_rendering.py ran · our draft was wrong fingerprinted MIT (permissive) · 9aefbf4f8f6698cd · report fixture: signature rgb_BS3HW:Tensor/5/float, xyz_BS3HW:Tensor/5/float, weights:Tensor/5/float, is_bg_depth_inf:bool/0/bool · returned tuple · level recorded 2026-09-22
HomographySample operations/mpi_rendering.py unverified MIT (permissive) · 896f18a21e472ff2 · report
render_tgt_rgb_depth operations/mpi_rendering.py unverified MIT (permissive) · ff9fe99c79e58e72 · report

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 MINE (graph method: MINE). 7 bricks; individually on a fixture: 5 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. render_tgt_rgb_depth entry · level 0 · unverified · ff9fe99c79e58e72
  2. HomographySample helper · level 0 · unverified · 896f18a21e472ff2
  3. render helper · level 1 · ran; the contract check could not run (RAISES) · 5ecf76e78c778112
  4. inverse helper · level 1 · ran; the contract check could not run (RAISES) · 3c56cc2b3ae0cce5
  5. alpha_composition model · level 1 · ran · our draft was wrong · 7525a41074955b82
  6. plane_volume_rendering model · level 1 · ran · our draft was wrong · 1c9f33a62f20f378
  7. weighted_sum_mpi model · level 1 · ran · our draft was wrong · 9aefbf4f8f6698cd

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="2103.14910") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

3D ReconstructionDepth EstimationNeRFNovel View Synthesis

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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