Papers › Tutorial on Variational Autoencoders

Tutorial on Variational Autoencoders

19 Jun 2016arXiv:1606.05908archive 2025-07-28

Carl Doersch

In just three years, Variational Autoencoders (VAEs) have emerged as one of the most popular approaches to unsupervised learning of complicated distributions. VAEs are appealing because they are built on top of standard function approximators (neural networks), and can be trained with stochastic gradient descent. VAEs have already shown promise in generating many kinds of complicated data, including handwritten digits, faces, house numbers, CIFAR images, physical models of scenes, segmentation, and predicting the future from static images. This tutorial introduces the intuitions behind VAEs, explains the mathematics behind them, and describes some empirical behavior. No prior knowledge of variational Bayesian methods is assumed.

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 3 code samples harvested from 3 repositories linked to this paper: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 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, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 2 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 5 of its repositories that Syntology harvested for other papers:

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

27 repositories listed; official and paper-mentioned ones first.

cdoersch/vae_tutorial officialmentioned in papermentioned on GitHubcaffe2MITSyntology: 1 sample, 0 ran · 1 unverified report
Aditya-Ramesh-10/VAE-MNIST mentioned on GitHubtfSyntology: not harvested report
LeenaShekhar/NLP-Linguistics-ML-Resources mentioned on GitHubtfSyntology: not harvested report
LeenaShekhar/NLP-ML-Resources mentioned on GitHubtfSyntology: not harvested report
MINGUKKANG/CVAE mentioned on GitHubtfSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Auto-Encoding Variational Bayes (arXiv:1312.6114; that paper's own run record: 140 ran (of which 52 constructed an object rather than computing a result; 120 with no instrument failure: 4 honoured, 2 violated, 114 with no contract checked; 20 where Syntology's instrument failed) · 59 unverified); nothing checks that they implement this paper's method. report
abhinavnagpal/Papers-reading-list mentioned on GitHubtfSyntology: not harvested report
adityabingi/Beta-VAE mentioned on GitHubtfSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
adityakumarakash/VariationalAutoEncoders mentioned on GitHubpytorchSyntology: not harvested report
arogers1/VAE_LSTM_Text_Encoding mentioned on GitHubSyntology: not harvested report
bogedy/intro_dfc mentioned on GitHubtfSyntology: not harvested report
danyleb/variational-lstm-autoencoder mentioned on GitHubtfMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to A Multimodal Anomaly Detector for Robot-Assisted Feeding Using an LSTM-based... (arXiv:1711.00614; that paper's own run record: 9 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
dariocazzani/pytorch-ae mentioned on GitHubpytorchSyntology: not harvested report
dutxiaoli/Vae_for_Photon-counting mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
ethanluoyc/pytorch-vae mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Auto-Encoding Variational Bayes (arXiv:1312.6114; that paper's own run record: 140 ran (of which 52 constructed an object rather than computing a result; 120 with no instrument failure: 4 honoured, 2 violated, 114 with no contract checked; 20 where Syntology's instrument failed) · 59 unverified); nothing checks that they implement this paper's method. report
kris-singh/ReadingList mentioned on GitHubpytorchSyntology: not harvested report
psanch21/VAE-GMVAE mentioned on GitHubtfApache-2.0Syntology: not harvested report
richardrl/vae-pytorch mentioned on GitHubpytorchSyntology: not harvested report
seohuibae/VAE_DRAW mentioned on GitHubpytorchSyntology: not harvested report
shib0li/VAE-PyTorch mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Auto-Encoding Variational Bayes (arXiv:1312.6114; that paper's own run record: 140 ran (of which 52 constructed an object rather than computing a result; 120 with no instrument failure: 4 honoured, 2 violated, 114 with no contract checked; 20 where Syntology's instrument failed) · 59 unverified); nothing checks that they implement this paper's method. report
shib0li/VAE-torch mentioned on GitHubpytorchSyntology: not harvested report
sidwa/ae_thesis mentioned on GitHubpytorchSyntology: not harvested report
simonamtoft/ml-library mentioned on GitHubpytorchSyntology: not harvested report
snakers4/playing_with_vae mentioned on GitHubpytorchSyntology: not harvested report
susanwe/ope_worldmodels mentioned on GitHubSyntology: not harvested report
tegg89/VAE-Tensorflow mentioned on GitHubtfSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Auto-Encoding Variational Bayes (arXiv:1312.6114; that paper's own run record: 140 ran (of which 52 constructed an object rather than computing a result; 120 with no instrument failure: 4 honoured, 2 violated, 114 with no contract checked; 20 where Syntology's instrument failed) · 59 unverified); nothing checks that they implement this paper's method. report
timyadnyda/variational-lstm-autoencoder mentioned on GitHubtfMITSyntology: not harvested 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

3 samples harvested: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 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
1unverified

Licence: 1 of the 3 samples is 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. 1 sample whose link to this paper records no repository is listed under one of this paper's own repositories, because identical code was harvested from it for another 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.

cdoersch/vae_tutorial official repository 1 sample, 0 ran · 1 unverified
imtile utils.py unverified MIT (permissive) · 3d1fb4117db70d38 · report
adityabingi/Beta-VAE community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
lr_schedule in 30 papers vae.py identical code Syntology harvested from this repository for another paper; this paper's link records no repository, path or licence of its own ran · honoured contract fingerprinted licence of this copy not recorded · 2dbc820f27054078 · report fixture: signature epoch:int/0/int, previous_lr:float/0/float · returned float · level recorded 2026-09-22
dutxiaoli/Vae_for_Photon-counting community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
latent_loss vae.py ran · our draft was wrong fingerprinted BSD-3-Clause (permissive) · 05efbba9a563b140 · report fixture: signature z_mean:Tensor/2/float, z_stddev:Tensor/2/float · returned Tensor · level recorded 2026-09-22

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