Papers › EPro-PnP: Generalized End-to-End Probabilistic Perspective-n-Points for Monocular...

EPro-PnP: Generalized End-to-End Probabilistic Perspective-n-Points for Monocular Object Pose Estimation

22 Mar 2023arXiv:2303.12787archive 2025-07-28

Hansheng Chen, Wei Tian, Pichao Wang, Fan Wang, Lu Xiong, Hao Li

Locating 3D objects from a single RGB image via Perspective-n-Point (PnP) is a long-standing problem in computer vision. Driven by end-to-end deep learning, recent studies suggest interpreting PnP as a differentiable layer, allowing for partial learning of 2D-3D point correspondences by backpropagating the gradients of pose loss. Yet, learning the entire correspondences from scratch is highly challenging, particularly for ambiguous pose solutions, where the globally optimal pose is theoretically non-differentiable w.r.t. the points. In this paper, we propose the EPro-PnP, a probabilistic PnP layer for general end-to-end pose estimation, which outputs a distribution of pose with differentiable probability density on the SE(3) manifold. The 2D-3D coordinates and corresponding weights are treated as intermediate variables learned by minimizing the KL divergence between the predicted and target pose distribution. The underlying principle generalizes previous approaches, and resembles the attention mechanism. EPro-PnP can enhance existing correspondence networks, closing the gap between PnP-based method and the task-specific leaders on the LineMOD 6DoF pose estimation benchmark. Furthermore, EPro-PnP helps to explore new possibilities of network design, as we demonstrate a novel deformable correspondence network with the state-of-the-art pose accuracy on the nuScenes 3D object detection benchmark. Our code is available at https://github.com/tjiiv-cprg/EPro-PnP-v2.

PaperPDFCodeCode Syntology ran

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 8 code samples harvested from 2 repositories linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 1 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 1 sample from 1 repository, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 7 samples from 1 repository, 6 ran (6 with no instrument failure; 0 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 between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 6 samples that ran has no recorded date.

tjiiv-cprg/epro-pnp-v2 officialmentioned in papermentioned on GitHubpytorchMITSyntology: 1 sample, 0 ran · 1 unverified report
tjiiv-cprg/epro-pnp mentioned on GitHubpytorchApache-2.0Syntology: 7 samples, 6 ran (0 instrument-failed) · 1 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

8 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 1 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 2 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
5ran
2unverified

Licence: 7 of the 8 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

tjiiv-cprg/epro-pnp-v2 official repository 1 sample, 0 ran · 1 unverified
download in 53 papers EPro-PnP-6DoF_v2/lib/utils/fs.py unverified MIT (permissive) · 78300875c6a51f76 · report
tjiiv-cprg/epro-pnp community (archive-listed) 7 samples, 6 ran (0 instrument-failed) · 1 unverified
draw_orient_density EPro-PnP-6DoF/lib/utils/draw_orient_density.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · 5a8477f0b7df5a2a · report fixture: signature pose_opt:Tensor/2/float, pose_samples:Tensor/3/float, pose_sample_logweights:Tensor/2/float, size:int/0/int, saturation:float/0/float, sphere_opacity:float/0/float, sample_kernel:tuple/1/int, intensity_scale:int/0/int · returned ndarray · level recorded 2026-09-24
euler_angles_to_matrix in 5 papers EPro-PnP-6DoF/lib/ops/rotation_conversions.py ran Apache-2.0 recorded; this copy not marked cleared · pointer only · 97dae9745013aa60 · report fixture: signature euler_angles:Tensor/2/float, convention:str/0/str · returned Tensor · level recorded 2026-09-25
matrix_to_quaternion in 11 papers EPro-PnP-6DoF/lib/ops/rotation_conversions.py ran fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · e59f47c519114fa0 · report fixture: signature matrix:Tensor/3/float · returned Tensor · level recorded 2026-09-25
obj2idx EPro-PnP-6DoF/lib/ref.py ran fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · 5253f1ce3347b571 · report fixture: signature obj_name:str/0/str · returned int · level recorded 2026-09-25
quaternion_to_matrix in 10 papers EPro-PnP-6DoF/lib/ops/rotation_conversions.py ran fingerprinted Apache-2.0 recorded; this copy not marked cleared · pointer only · e0238352153c0549 · report fixture: signature quaternions:Tensor/2/float · returned Tensor · level recorded 2026-09-25
str2bool in 533 papers EPro-PnP-6DoF/lib/config.py ran · violated contract Apache-2.0 recorded; this copy not marked cleared · pointer only · f017532fc389cbfe · report fixture: signature v:str/0/str · returned bool · level recorded, date not recorded
set_logger_dir EPro-PnP-6DoF/lib/utils/fancy_logger.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · c4444b8ff1266dfa · report

Tasks

3D Object Detection6D Pose Estimation using RGBObject DetectionPose Estimationobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Object Detection nuScenes EPro-PnP-Det v2 NDS 0.49 #278 of 372 Archive leaderboard report
3D Object Detection nuScenes EPro-PnP-Det v2 mAAE 0.123 #278 of 372 Archive leaderboard report
3D Object Detection nuScenes EPro-PnP-Det v2 mAOE 0.302 #278 of 372 Archive leaderboard report
3D Object Detection nuScenes EPro-PnP-Det v2 mAP 0.423 #278 of 372 Archive leaderboard report
3D Object Detection nuScenes EPro-PnP-Det v2 mASE 0.236 #278 of 372 Archive leaderboard report
3D Object Detection nuScenes EPro-PnP-Det v2 mATE 0.547 #278 of 372 Archive leaderboard report
3D Object Detection nuScenes EPro-PnP-Det v2 mAVE 1.071 #278 of 372 Archive leaderboard report
6D Pose Estimation using RGB LineMOD EPro-PnP-6DoF v2 Mean ADD 96.36 #4 of 22 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.

Methods

PnP

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