Papers › Pix2Pose: Pixel-Wise Coordinate Regression of Objects for 6D Pose Estimation

Pix2Pose: Pixel-Wise Coordinate Regression of Objects for 6D Pose Estimation

20 Aug 2019ICCV 2019 10arXiv:1908.07433archive 2025-07-28

Kiru Park, Timothy Patten, Markus Vincze

Estimating the 6D pose of objects using only RGB images remains challenging because of problems such as occlusion and symmetries. It is also difficult to construct 3D models with precise texture without expert knowledge or specialized scanning devices. To address these problems, we propose a novel pose estimation method, Pix2Pose, that predicts the 3D coordinates of each object pixel without textured models. An auto-encoder architecture is designed to estimate the 3D coordinates and expected errors per pixel. These pixel-wise predictions are then used in multiple stages to form 2D-3D correspondences to directly compute poses with the PnP algorithm with RANSAC iterations. Our method is robust to occlusion by leveraging recent achievements in generative adversarial training to precisely recover occluded parts. Furthermore, a novel loss function, the transformer loss, is proposed to handle symmetric objects by guiding predictions to the closest symmetric pose. Evaluations on three different benchmark datasets containing symmetric and occluded objects show our method outperforms the state of the art using only RGB images.

PaperPDFConference PDFCodeCode 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: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 8 samples from 2 repositories, 4 ran (4 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.

GH3927/Pix2Pix-applied-to-cranes mentioned on GitHubtfSyntology: not harvested report
hz-ants/Pix2Pose mentioned on GitHubtfMITSyntology: 4 samples, 2 ran (0 instrument-failed) · 2 unverified report
kirumang/Pix2Pose mentioned on GitHubtfMITSyntology: 4 samples, 2 ran (0 instrument-failed) · 2 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: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 4 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.

4ran
4unverified

Licence: 0 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.

hz-ants/Pix2Pose community (archive-listed) 4 samples, 2 ran (0 instrument-failed) · 2 unverified
compute_rotation_from_vertex rendering/utils.py ran fingerprinted MIT (permissive) · f1f755c2a962bfe2 · report fixture: signature vertex:ndarray/1/float · returned ndarray · level recorded 2026-09-24
singleton in 23 papers rendering/renderer.py ran MIT (permissive) · 7688c81b21c2784f · report fixture: signature cls:callable/0/? · returned function · level recorded 2026-09-25
draw_detections_2D rendering/utils.py unverified MIT (permissive) · 58e205d70619d7b4 · report
get_bbox_from_mask in 5 papers pix2pose_util/common_util.py unverified MIT (permissive) · 2a1a7f9181849be6 · report
kirumang/Pix2Pose community (archive-listed) 4 samples, 2 ran (0 instrument-failed) · 2 unverified
conv_block in 95 papers pix2pose_model/resnet50_mod.py ran MIT (permissive) · 0c20710ab8a2abc9 · report fixture: signature input_tensor:KerasTensor/0/float, kernel_size:int/0/int, filters:list/1/int, stage:int/0/int, block:str/0/str, strides:tuple/1/int · returned KerasTensor · level recorded 2026-09-24
getXYZ pix2pose_util/common_util.py ran MIT (permissive) · 56ef64fd9c7a6e8f · report fixture: signature depth:ndarray/2/float, fx:float/0/float, fy:float/0/float, cx:float/0/float, cy:float/0/float, bbox:ndarray/1/int · returned ndarray · level recorded 2026-09-24
get_normal in 5 papers pix2pose_util/common_util.py unverified MIT (permissive) · d73753b0d8a243a5 · report
identity_block in 32 papers pix2pose_model/resnet50_mod.py unverified MIT (permissive) · 4709da86c7cc71fd · report

Tasks

6D Pose Estimation6D Pose Estimation using RGBPose Estimationregression

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
6D Pose Estimation using RGB LineMOD Pix2Pose Mean ADD 32 #20 of 22 Archive leaderboard report
6D Pose Estimation using RGB T-LESS Pix2Pose without ICP Recall (VSD) 29.5 #1 of 2 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

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerReLUResidual ConnectionSoftmaxTransformer

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