Papers › Enforcing geometric constraints of virtual normal for depth prediction

Enforcing geometric constraints of virtual normal for depth prediction

29 Jul 2019ICCV 2019 10arXiv:1907.12209archive 2025-07-28

Wei Yin, Yifan Liu, Chunhua Shen, Youliang Yan

Monocular depth prediction plays a crucial role in understanding 3D scene geometry. Although recent methods have achieved impressive progress in evaluation metrics such as the pixel-wise relative error, most methods neglect the geometric constraints in the 3D space. In this work, we show the importance of the high-order 3D geometric constraints for depth prediction. By designing a loss term that enforces one simple type of geometric constraints, namely, virtual normal directions determined by randomly sampled three points in the reconstructed 3D space, we can considerably improve the depth prediction accuracy. Significantly, the byproduct of this predicted depth being sufficiently accurate is that we are now able to recover good 3D structures of the scene such as the point cloud and surface normal directly from the depth, eliminating the necessity of training new sub-models as was previously done. Experiments on two benchmarks: NYU Depth-V2 and KITTI demonstrate the effectiveness of our method and state-of-the-art performance.

PaperPDFConference PDFCode

In Syntology View this paper on Syntology, its page in Syntology's graph. That page 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

YvanYin/VNL_Monocular_Depth_Prediction mentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
aim-uofa/AdelaiDepth mentioned on GitHubpytorchSyntology: not harvested report
aim-uofa/depth mentioned on GitHubpytorchCC0-1.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Towards Accurate Reconstruction of 3D Scene Shape from A Single Monocular Image (arXiv:2208.13241; that paper's own run record: 10 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 6 where Syntology's instrument failed) · 2 unverified); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Tasks

Depth EstimationDepth PredictionMonocular Depth EstimationPrediction

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Depth Estimation NYU-Depth V2 VNL RMS 0.416 #10 of 17 Archive leaderboard report
Monocular Depth Estimation KITTI Eigen split VNL absolute relative error 0.072 #43 of 79 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 VNL Delta < 1.25 0.875 #57 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 VNL Delta < 1.25^2 0.976 #57 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 VNL Delta < 1.25^3 0.989 #57 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 VNL RMSE 0.416 #57 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 VNL absolute relative error 0.111 #57 of 85 Archive leaderboard report
Monocular Depth Estimation NYU-Depth V2 VNL log 10 0.048 #57 of 85 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