Papers › Adversarially Learned Inference

Adversarially Learned Inference

2 Jun 2016arXiv:1606.00704archive 2025-07-28

Vincent Dumoulin, Ishmael Belghazi, Ben Poole, Olivier Mastropietro, Alex Lamb, Martin Arjovsky, Aaron Courville

We introduce the adversarially learned inference (ALI) model, which jointly learns a generation network and an inference network using an adversarial process. The generation network maps samples from stochastic latent variables to the data space while the inference network maps training examples in data space to the space of latent variables. An adversarial game is cast between these two networks and a discriminative network is trained to distinguish between joint latent/data-space samples from the generative network and joint samples from the inference network. We illustrate the ability of the model to learn mutually coherent inference and generation networks through the inspections of model samples and reconstructions and confirm the usefulness of the learned representations by obtaining a performance competitive with state-of-the-art on the semi-supervised SVHN and CIFAR10 tasks.

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

By repository: official repository: 1 sample from 1 repository, 1 ran (1 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 3 samples from 2 repositories, 2 ran (1 with no instrument failure; 1 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

IshmaelBelghazi/ALI officialmentioned in paperMITSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
9310gaurav/ali-pytorch mentioned on GitHubpytorchSyntology: 2 samples, 1 ran (1 instrument-failed) · 1 unverified report
caotians1/OD-test-master mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to A Benchmark of Medical Out of Distribution Detection (arXiv:2007.04250; that paper's own run record: 7 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; 1 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
kryvosheyev/xray-anomaly-detection mentioned on GitHubpytorchSyntology: not harvested report
lkhphuc/Anomaly-BiGAN mentioned on GitHubpytorchSyntology: not harvested report
lkhphuc/Anomaly-XRay-GANs mentioned on GitHubpytorchSyntology: not harvested report
pavasgdb/Anomaly-detector-using-GAN mentioned on GitHubpytorchSyntology: not harvested report
zhenxuan00/graphical-gan mentioned on GitHubtfSyntology: not harvested report
MaximeVandegar/Papers-in-100-Lines-of-Code pytorchSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

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

Licence: 2 of the 4 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 3 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.

IshmaelBelghazi/ALI official repository 1 sample, 1 ran (0 instrument-failed) · 0 unverified
get_key_from_val ali/mixture_viz.py ran MIT (permissive) · c9895e295f5b3d66 · report fixture: signature dictionary:dict/0/?, target_val:str/0/str · returned str · level recorded 2026-09-25
9310gaurav/ali-pytorch community (archive-listed) 2 samples, 1 ran (1 instrument-failed) · 1 unverified
get_random_uniform_batch test_semisup.py ran · our draft was wrong no licence file found · pointer only · 0fb3b06d95c005bf · report fixture: signature data:ndarray/2/float, targets:ndarray/1/int, num_classes:int/0/int, samples_per_class:int/0/int · returned tuple · level recorded 2026-09-22
tocuda in 6 papers test_semisup.py unverified no licence file found · pointer only · c59ce90932b89fbe · report
MaximeVandegar/Papers-in-100-Lines-of-Code community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
sample_latent in 5 papers Adversarially_Learned_Inference/ali.py ran · honoured contract MIT (permissive) · 1422451452fe36c8 · report fixture: signature batch_size:int/0/int, device:str/0/str · returned Tensor · level recorded 2026-09-22

Tasks

Image GenerationImage-to-Image Translation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Image-to-Image Translation Cityscapes Labels-to-Photo BiGAN Class IOU 0.02 #20 of 21 Archive leaderboard report
Image-to-Image Translation Cityscapes Labels-to-Photo BiGAN Per-class Accuracy 6% #20 of 21 Archive leaderboard report
Image-to-Image Translation Cityscapes Labels-to-Photo BiGAN Per-pixel Accuracy 19% #20 of 21 Archive leaderboard report
Image-to-Image Translation Cityscapes Photo-to-Labels BiGAN Class IOU 0.07 #4 of 5 Archive leaderboard report
Image-to-Image Translation Cityscapes Photo-to-Labels BiGAN Per-class Accuracy 13% #4 of 5 Archive leaderboard report
Image-to-Image Translation Cityscapes Photo-to-Labels BiGAN Per-pixel Accuracy 41% #4 of 5 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

1x1 ConvolutionALIAdamConvolutionMaxoutSVMSigmoid Activation

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