atlas

Research map / Detection and segmentation / 3D detection and driving

MonoDGP: Monocular 3D Object Detection with Decoupled-Query and Geometry-Error Priors

CVPR 2025 · Detection and segmentation › 3D detection and driving · approach: Monocular 3D object detection · 25 citations (OpenAlex)

Read the paperCheck your idea against 108,967 papers

AI-extracted summary. Written by AI from the paper's full text. Numbers and claims can be wrong or missing context, so check the paper before you cite or build on it.

Proposes MonoDGP, a DETR-style monocular 3D detector that predicts perspective-invariant geometry (depth) errors to correct geometric depth, decouples a 2D visual decoder for query initialization, and adds a Region Segmentation Head for enhanced features and segment embeddings.

Problem

Monocular 3D object detection relies on perspective projection for geometric depth, but the 2D bounding-box height often fails to represent the actual central height, causing depth errors; multi-depth prediction is complex and under-exploits geometric depth.

Approach

Replace direct depth prediction with a perspective-invariant depth error added to geometric depth computed from the 2D box height, combined with a decoupled 2D visual decoder that initializes object queries and a U-Net-style region segmentation head that enhances foreground features and supplies BERT-like segment embeddings.

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
replace MonoDDE with MonoDGPKITTI test, Car Moderate · KITTI test, Car ModerateAP3D|R40: 17.14 -> 18.72Helped
replace MonoDETR with MonoDGPKITTI val, Car Moderate · KITTI val, Car ModerateAP3D|R40: 20.61 -> 22.34Helped
add decoupled query (ablation)MonoDGP · KITTI val, Car ModerateAP3D: 21.48 -> 22.34Helped
add RSH (ablation)MonoDGP · KITTI val, Car ModerateAP3D: 21.93 -> 22.34Helped
set segment embedding threshold to 0.3 instead of 0.5 (ablation)MonoDGP · KITTI val, Car ModerateAP3D|R40: 21.64 -> 21.51Hurt
set segment embedding threshold to 0.7 instead of 0.5 (ablation)MonoDGP · KITTI val, Car ModerateAP3D|R40: 21.64 -> 21.54Hurt
remove segment embeddings (ablation)MonoDGP · KITTI val, Car ModerateAP3D|R40: 21.43 vs 21.64Hurt
use direct depth prediction instead of the full method (ablation)MonoDGP · KITTI val, Car ModerateAP3D|R40: 19.23 vs 22.34Hurt
use geometric depth from hbbox without error correction (ablation)MonoDGP · KITTI val, Car ModerateAP3D|R40: 7.99 vs 22.34Hurt
use geometric depth from hc instead of the proposed correction (ablation)MonoDGP · KITTI val, Car ModerateAP3D|R40: 20.73 vs 22.34Hurt
fuse depth map, direct depth, and geometric depth instead of using geometric depth error (ablation)MonoDGP · KITTI val, Car ModerateAP3D|R40: 21.64 vs 22.34Hurt
correct geometric depth with bounding box height error instead of depth error (ablation)MonoDGP · KITTI val, Car ModerateAP3D|R40: 21.18 vs 22.34Hurt

Surprising findings

Limitations

Experimental setup

Datasets: KITTI

Benchmarks: KITTI

Metrics: AP3D APBEV AP40

Baselines: MonoDETR MonoCD MonoDDE GUPNet DID-M3D OccupancyM3D MonoDTR CaDDN FD3D

Builds on: MonoDETR DETR Deformable DETR BERT Mixup3D

Closest papers by meaning

Writing a paper in this area? scime draft is a free LaTeX editor with AI included, real-time co-authors and a check of your references and venue rules before you submit. It also imports OpenAI Prism projects.

Open scime draft

Get the next scime Dispatch and a monthly field update

Free. We send a confirmation link first; every email has a one-click unsubscribe. Privacy