atlas

Research map / Detection and segmentation / CNN features

End-to-End Real-Time Vanishing Point Detection with Transformer

AAAI 2024 · Detection and segmentation › CNN features · approach: Context for hard detection conditions · 4 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 VPTR, a transformer-based end-to-end vanishing point detector that treats VP detection as point object detection on a Gaussian hemisphere with region division and a decoder bridged directly to multi-level CNN features, running at 140 FPS.

Problem

Vanishing point detection is typically line-based or relies on Manhattan assumptions and candidate sampling, which trades accuracy against speed and fails when lines are hard to detect or the number of VPs is unknown.

Approach

Model VP detection as one-stage point object detection on the Gaussian hemisphere: Fibonacci-lattice anchors define overlapping spherical caps, each query predicts a confidence and a VP location, and a deformable decoder attends directly to multi-level backbone features with no encoder.

Key results

Measured effects reported in the paper

What was changedWhereMeasuredEffect
use VPTR instead of NeurVPSvanishing point detection · SU3AA@3°: 94.4 -> 88.5Hurt
use VPTR instead of Lin et al.vanishing point detection · ScanNetAA@5°: 42.0 -> 42.2Helped
use VPTR instead of NeurVPSvanishing point detection · Natural SceneAA@2°: 50.3 -> 52.0Helped
use VPTR instead of NeurVPSvanishing point detection · Natural SceneAA@10°: 85.5 -> 84.3Hurt
use VPTR instead of Lin et al.vanishing point detection · NYUAA@10°: 69.5 -> 69.7Helped
add decoder bridge (ablation)VPTR baseline · SU3AA@3°: 83.4 -> 87.3Helped
add Manhattan loss (ablation)VPTR with decoder bridge · SU3AA@3°: 87.3 -> 88.1Helped
add multi-level features (ablation)VPTR with decoder bridge and Manhattan loss · SU3AA@3°: 88.1 -> 88.5Helped
use 128 anchors instead of 256 (ablation)VPTR · SU3AA@3°: 88.5 -> 87.9Hurt
use 512 anchors instead of 256 (ablation)VPTR · SU3AA@3°: 88.5 -> 88.1Hurt
use 8 referring points instead of 32 (ablation)VPTR · SU3AA@3°: 88.5 -> 88.2Hurt
use 128 referring points instead of 32 (ablation)VPTR · SU3AA@3°: 88.5 -> 88.4No clear effect

Surprising findings

Limitations

Experimental setup

Datasets: SU3 ScanNet Natural Scene dataset NYU

Benchmarks: SU3 ScanNet Natural Scene dataset NYU

Metrics: AA@3° AA@5° AA@10° AA@1° AA@2° FPS

Baselines: J-Linkage Simon et al. Li et al. CONSAC NeurVPS TLC Lin et al. Zhou et al.

Builds on: Deformable DETR NeurVPS DETR YOLO

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