Papers › CheckerPose: Progressive Dense Keypoint Localization for Object Pose Estimation with...

CheckerPose: Progressive Dense Keypoint Localization for Object Pose Estimation with Graph Neural Network

29 Mar 2023ICCV 2023 1arXiv:2303.16874archive 2025-07-28

Ruyi Lian, Haibin Ling

Estimating the 6-DoF pose of a rigid object from a single RGB image is a crucial yet challenging task. Recent studies have shown the great potential of dense correspondence-based solutions, yet improvements are still needed to reach practical deployment. In this paper, we propose a novel pose estimation algorithm named CheckerPose, which improves on three main aspects. Firstly, CheckerPose densely samples 3D keypoints from the surface of the 3D object and finds their 2D correspondences progressively in the 2D image. Compared to previous solutions that conduct dense sampling in the image space, our strategy enables the correspondence searching in a 2D grid (i.e., pixel coordinate). Secondly, for our 3D-to-2D correspondence, we design a compact binary code representation for 2D image locations. This representation not only allows for progressive correspondence refinement but also converts the correspondence regression to a more efficient classification problem. Thirdly, we adopt a graph neural network to explicitly model the interactions among the sampled 3D keypoints, further boosting the reliability and accuracy of the correspondences. Together, these novel components make CheckerPose a strong pose estimation algorithm. When evaluated on the popular Linemod, Linemod-O, and YCB-V object pose estimation benchmarks, CheckerPose clearly boosts the accuracy of correspondence-based methods and achieves state-of-the-art performances. Code is available at https://github.com/RuyiLian/CheckerPose.

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 12 code samples harvested from 1 repository linked to this paper: 9 ran (of which 3 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 1 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 3 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.

By repository: official repository: 12 samples from 1 repository, 9 ran (4 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.

ruyilian/checkerpose officialmentioned in papermentioned on GitHubpytorchSyntology: 12 samples, 9 ran (5 instrument-failed) · 3 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

12 samples harvested: 9 ran (of which 3 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 1 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures 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.

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

Licence: 12 of the 12 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 ruyilian/checkerpose. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

ruyilian/checkerpose official repository 12 samples, 9 ran (5 instrument-failed) · 3 unverified
Index2Feat_module checkerpose/model/pipeline.py ran · metamorphic tier: deterministic no licence file found · pointer only · eb7d2796646a1b58 · report fixture: returned Index2Feat_module · level recorded 2026-09-22
MLP_QueryNet checkerpose/model/pipeline.py ran · metamorphic tier: deterministic no licence file found · pointer only · 867a5d1fd85cb80c · report fixture: returned MLP_QueryNet · level recorded 2026-09-22
StaticGraph_module checkerpose/model/pipeline.py ran · metamorphic tier: deterministic no licence file found · pointer only · 3a4e6e03e31dc6a0 · report fixture: returned StaticGraph_module · level recorded 2026-09-22
from_bit_prob_to_id checkerpose/model/pipeline.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted no licence file found · pointer only · e117f45960a9a457 · report fixture: signature bit_prob:Tensor/3/float · returned Tensor · level recorded 2026-09-22
from_code_prob_to_id checkerpose/model/pipeline.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted no licence file found · pointer only · 97585cf5dbeb1837 · report fixture: signature code_prob:Tensor/3/float, class_base:int/0/int · returned Tensor · level recorded 2026-09-22
from_mask_prob_to_mask checkerpose/model/pipeline.py ran · violated contract no licence file found · pointer only · 3f179262db33b7f1 · report fixture: signature mask_prob:Tensor/3/float · returned Tensor · level recorded 2026-09-22
get_MLP_leakyReLU_layers checkerpose/model/pipeline.py ran · our draft was wrong no licence file found · pointer only · d869bfc65c47e517 · report fixture: signature dims:list/1/int, doLastAct:bool/0/bool, negative_slope:float/0/float · returned Sequential · level recorded 2026-09-22
get_gdrn_upsample_module checkerpose/model/pipeline.py ran · our draft was wrong no licence file found · pointer only · 3d836ca3230417ae · report fixture: signature is_convtrans:bool/0/bool, in_channels:int/0/int, num_filters:int/0/int, kernel_size:int/0/int, padding:int/0/int, output_padding:int/0/int · returned Sequential · level recorded 2026-09-22
get_graph_feature in 51 papers
census: 6 implementations from 5 papers, 4 distinct outputs across 2 buckets, one shared input per bucket
checkerpose/model/pipeline.py ran · our draft was wrong no licence file found · pointer only · a774849fdc6cb021 · report fixture: signature x:Tensor/3/float, knn_idx:Tensor/3/int, batch_indices:Tensor/2/int · returned Tensor · level recorded 2026-09-22
PoseNet_GNNskip checkerpose/model/pipeline.py unverified no licence file found · pointer only · d979eab4f9fcbafe · report
Refine_moduleGNN checkerpose/model/pipeline.py unverified no licence file found · pointer only · 40cab79e9b830452 · report
from_code_to_id checkerpose/model/pipeline.py unverified no licence file found · pointer only · 5935c64a872da27c · 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 CheckerPose (graph method: CheckerPose). 13 bricks; individually on a fixture: 10 ran (of which 3 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 1 violated, 3 with no contract checked; 6 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.

  1. PoseNet_GNNskip entry · level 0 · unverified · d979eab4f9fcbafe
  2. Refine_moduleGNN model · level 0 · unverified · 40cab79e9b830452
  3. from_bit_prob_to_id helper · level 1 · ran; the contract check could not run (RAISES) · e117f45960a9a457
  4. from_code_prob_to_id helper · level 1 · ran; the contract check could not run (RAISES) · 97585cf5dbeb1837
  5. from_mask_prob_to_mask helper · level 1 · ran · violated contract · 3f179262db33b7f1
  6. get_gdrn_upsample_module model · level 1 · ran · our draft was wrong · 3d836ca3230417ae
  7. Index2Feat_module model · level 1 · ran · eb7d2796646a1b58
  8. MLP_QueryNet model · level 1 · ran · 867a5d1fd85cb80c
  9. StaticGraph_module model · level 1 · ran · 3a4e6e03e31dc6a0
  10. get_MLP_leakyReLU_layers helper · level 1 · ran · our draft was wrong · d869bfc65c47e517
  11. knn helper · level 1 · ran; the contract check could not run · cdd0141594039dcb
  12. from_code_to_id helper · level 0 · unverified · 5935c64a872da27c
  13. get_graph_feature helper · level 1 · ran · our draft was wrong · a774849fdc6cb021

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

Tasks

Graph Neural NetworkPose Estimation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Graph Neural Network

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