HiPose: Hierarchical Binary Surface Encoding and Correspondence Pruning for RGB-D 6DoF Object Pose Estimation

Yongliang Lin, Yongzhi Su, Praveen Nathan, Sandeep Inuganti, Yan Di +5 more
2/14/2026

No official code found. Best implementation: lyltc1/HiPose (43 stars, MIT, last commit 2025-05-28).

Abstract

In this work, we present a novel dense-correspondence method for 6DoF object pose estimation from a single RGB-D image. While many existing data-driven methods achieve impressive performance, they tend to be time-consuming due to their reliance on rendering-based refinement approaches. To circumvent this limitation, we present HiPose, which establishes 3D-3D correspondences in a coarse-to-fine manner with a hierarchical binary surface encoding. Unlike previous dense-correspondence methods, we estimate the correspondence surface by employing point-to-surface matching and iteratively constricting the surface until it becomes a correspondence point while gradually removing outliers. Extensive experiments on public benchmarks LM-O, YCB-V, and T-Less demonstrate that our method surpasses all refinement-free methods and is even on par with expensive refinement-based approaches. Crucially, our approach is computationally efficient and enables real-time critical applications with high accuracy requirements.

View on arXivView PDF

Code Implementations(1)

lyltc1/HiPoseCommunity100%
MIT
432C, C++Mar 13, 20241 years agoMIT

Similar Papers

Cite this paper

@article{lin2026hipose,
  title  = {HiPose: Hierarchical Binary Surface Encoding and Correspondence Pruning for RGB-D 6DoF Object Pose Estimation},
  author = {Yongliang Lin and Yongzhi Su and Praveen Nathan and Sandeep Inuganti and Yan Di and M. Sundermeyer and Fabian Manhardt and Didier Stricke and J. Rambach and Yu Zhang},
  year   = {2026},
  eprint = {2311.12588},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/pdf/2311.12588},
  journal = {CVPR 2023 2023}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2311.12588.svg)](https://codeofpaper.com/paper/2311.12588)

Discussion