Papers › CoordGAN: Self-Supervised Dense Correspondences Emerge from GANs

CoordGAN: Self-Supervised Dense Correspondences Emerge from GANs

30 Mar 2022CVPR 2022 1arXiv:2203.16521archive 2025-07-28

Jiteng Mu, Shalini De Mello, Zhiding Yu, Nuno Vasconcelos, Xiaolong Wang, Jan Kautz, Sifei Liu

Recent advances show that Generative Adversarial Networks (GANs) can synthesize images with smooth variations along semantically meaningful latent directions, such as pose, expression, layout, etc. While this indicates that GANs implicitly learn pixel-level correspondences across images, few studies explored how to extract them explicitly. In this work, we introduce Coordinate GAN (CoordGAN), a structure-texture disentangled GAN that learns a dense correspondence map for each generated image. We represent the correspondence maps of different images as warped coordinate frames transformed from a canonical coordinate frame, i.e., the correspondence map, which describes the structure (e.g., the shape of a face), is controlled via a transformation. Hence, finding correspondences boils down to locating the same coordinate in different correspondence maps. In CoordGAN, we sample a transformation to represent the structure of a synthesized instance, while an independent texture branch is responsible for rendering appearance details orthogonal to the structure. Our approach can also extract dense correspondence maps for real images by adding an encoder on top of the generator. We quantitatively demonstrate the quality of the learned dense correspondences through segmentation mask transfer on multiple datasets. We also show that the proposed generator achieves better structure and texture disentanglement compared to existing approaches. Project page: https://jitengmu.github.io/CoordGAN/

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 16 code samples harvested from 1 repository linked to this paper: 14 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 2 honoured, 1 violated, 8 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 16 samples from 1 repository, 14 ran (11 with no instrument failure; 3 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-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 14 samples that ran has no recorded date.

NVlabs/CoordGAN officialmentioned on GitHubpytorchMITSyntology: 16 samples, 14 ran (3 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

16 samples harvested: 14 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 2 honoured, 1 violated, 8 with no contract checked; 3 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

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

Licence: 3 of the 16 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from NVlabs/CoordGAN. “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.

NVlabs/CoordGAN official repository 16 samples, 14 ran (3 instrument-failed) · 2 unverified
all_gather in 119 papers distributed.py ran MIT (permissive) · ed03ba54397adbe4 · report fixture: signature data:dict/0/? · returned list · level recorded 2026-09-26
apply_random_crop loss/patchgan_loss.py ran MIT (permissive) · 0e2078aff3bb57c9 · report fixture: signature x:Tensor/4/float, target_size:int/0/int, scale_range:tuple/1/float, num_crops:int/0/int, return_rect:bool/0/bool · returned Tensor · level recorded 2026-09-24
d_logistic_loss in 15 papers
census: 2 implementations from 7 papers, 1 distinct output on one shared input
loss/gan_loss.py ran fingerprinted MIT (permissive) · e88ba1e8aa95eea5 · report fixture: signature real_pred:Tensor/2/float, fake_pred:Tensor/2/float · returned Tensor · level recorded 2026-09-24
d_r1_loss in 10 papers loss/gan_loss.py ran; the contract check could not run (RAISES) MIT (permissive) · 0693ac46c6c25e65 · report fixture: signature real_pred:Tensor/2/float, real_img:Tensor/4/float · returned Tensor · level recorded 2026-09-22
default_loader in 66 papers dataset.py ran · honoured contract MIT (permissive) here; the stored copy is pointer only · ac269a0e4b8d946e · report fixture: signature path:str/0/str · returned Image · level recorded 2026-09-24
g_nonsaturating_loss loss/gan_loss.py ran fingerprinted MIT (permissive) · f8b6363145aa25ad · report fixture: signature fake_pred:Tensor/2/float · returned Tensor · level recorded 2026-09-24
get_cor_img loss/warp_loss.py ran MIT (permissive) · 80db4290f1bdf5c9 · report fixture: signature args:Args/0/?, real:Tensor/4/float, warp:Tensor/4/float, temp:float/0/float, mode:str/0/str, down_sample_ratio:int/0/int, num_cls:int/0/int · returned Tensor · level recorded 2026-09-24
get_random_crops loss/patchgan_loss.py ran MIT (permissive) · 89c6b5dda075f671 · report fixture: signature args:Args/0/?, x:Tensor/4/float · returned Tensor · level recorded 2026-09-24
make_dataset in 144 papers dataset.py ran MIT (permissive) · 7a422a9212828aec · report fixture: returned list · level recorded 2026-09-26
normalize_tensor in 47 papers
census: 3 implementations from 5 papers, 2 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 2, kind float, dtype float32
loss/lpips_loss.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 7257fdf155f5ef45 · report fixture: signature x:Tensor/2/float, eps:float/0/float · returned Tensor · level recorded 2026-09-22
reduce_loss_dict in 18 papers distributed.py ran MIT (permissive) · 5144ad456049f8ce · report fixture: signature loss_dict:dict/0/? · returned dict · level recorded 2026-09-26
reduce_sum in 34 papers
census: 4 implementations from 5 papers, 4 distinct outputs across 4 buckets, one shared input per bucket
distributed.py ran · honoured contract fingerprinted MIT (permissive) · 3f0a1105ef251d78 · report fixture: signature tensor:Tensor/2/float · returned Tensor · level recorded 2026-09-24
spatial_average in 34 papers loss/lpips_loss.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · e268053216b1dd62 · report fixture: signature x:Tensor/4/float, keepdim:bool/0/bool · returned Tensor · level recorded 2026-09-22
str2bool in 533 papers eval_corr.py ran · violated contract MIT (permissive) · 7c508037b40522af · report fixture: signature v:str/0/str · returned bool · level recorded, date not recorded
compute_patch_discriminator_losses loss/patchgan_loss.py unverified MIT (permissive) · 484375c2ea0102d8 · report
is_image_file in 157 papers dataset.py unverified MIT (permissive) · 08750a49987bd9a5 · report

Tasks

Disentanglement

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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