Papers › Deep Feature Consistent Variational Autoencoder

Deep Feature Consistent Variational Autoencoder

2 Oct 2016arXiv:1610.00291archive 2025-07-28

Xianxu Hou, Linlin Shen, Ke Sun, Guoping Qiu

We present a novel method for constructing Variational Autoencoder (VAE). Instead of using pixel-by-pixel loss, we enforce deep feature consistency between the input and the output of a VAE, which ensures the VAE's output to preserve the spatial correlation characteristics of the input, thus leading the output to have a more natural visual appearance and better perceptual quality. Based on recent deep learning works such as style transfer, we employ a pre-trained deep convolutional neural network (CNN) and use its hidden features to define a feature perceptual loss for VAE training. Evaluated on the CelebA face dataset, we show that our model produces better results than other methods in the literature. We also show that our method can produce latent vectors that can capture the semantic information of face expressions and can be used to achieve state-of-the-art performance in facial attribute prediction.

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

By repository: community (archive-listed): 8 samples from 5 repositories, 4 ran (2 with no instrument failure; 2 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-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

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

AntixK/PyTorch-VAE mentioned on GitHubpytorchApache-2.0Syntology: not harvested report
Nanway/dfc-vae mentioned on GitHubpytorchSyntology: not harvested report
UdbhavPrasad072300/Generate-Fake-Faces-with-CVAE-in-PyTorch mentioned on GitHubpytorchSyntology: not harvested report
bhpfelix/Variational-Autoencoder-PyTorch mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
bogedy/intro_dfc mentioned on GitHubtfSyntology: not harvested report
inkplatform/beta-vae mentioned on GitHubpytorchSyntology: not harvested report
ku2482/vae.pytorch mentioned on GitHubpytorchMITSyntology: 2 samples, 1 ran (0 instrument-failed) · 1 unverified report
lukeditria/cnn-vae mentioned on GitHubpytorchMITSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 unverified report
matthew-liu/beta-vae mentioned on GitHubpytorchSyntology: not harvested report
nmichlo/disent mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Overlooked Implications of the Reconstruction Loss for VAE Disentanglement (arXiv:2202.13341; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
peria1/VAEconvMNIST mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
svenrdz/DFC-VAE mentioned on GitHubpytorchSyntology: not harvested report
vinoth654321/Beta-Vae-face-dataset mentioned on GitHubpytorchSyntology: not harvested report
Dylan-get/Deep-Feature-Consistent-VAE pytorchApache-2.0Syntology: 3 samples, 0 ran · 3 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

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

2ran · our draft was wrong
2ran
4unverified

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

bhpfelix/Variational-Autoencoder-PyTorch community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
loss_function in 62 papers
census: 7 implementations from 6 papers, 7 distinct outputs across 2 buckets, one shared input per bucket
src/vanila_vae.py ran · our draft was wrong no licence file found · pointer only · 151aee3ffaced99a · report fixture: signature recon_x:Tensor/2/float, x:Tensor/2/float, mu:Tensor/2/float, logvar:Tensor/2/float · returned Tensor · level recorded 2026-09-22
ku2482/vae.pytorch community (archive-listed) 2 samples, 1 ran (0 instrument-failed) · 1 unverified
parse_annotation in 7 papers utils/anno.py ran MIT (permissive) · 25aa7d6d0c4aeff8 · report fixture: signature path:str/0/str · returned DataFrame · level recorded 2026-09-26
get_df in 8 papers utils/anno.py unverified MIT (permissive) · b2870cfaccbe1020 · report
lukeditria/cnn-vae community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
get_norm_layer in 111 papers RES_VAE_Dynamic.py ran MIT (permissive) · 6d449298eb9f6365 · report fixture: signature channels:int/0/int, norm_type:str/0/str · returned BatchNorm2d · level recorded 2026-09-26
peria1/VAEconvMNIST community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
loss_function in 62 papers
census: 7 implementations from 6 papers, 7 distinct outputs across 2 buckets, one shared input per bucket
src/vanilla_vae.py ran · our draft was wrong no licence file found · pointer only · 310bb444965578fb · report fixture: signature recon_x:Tensor/2/float, x:Tensor/2/float, mu:Tensor/2/float, logvar:Tensor/2/float · returned Tensor · level recorded 2026-09-22
Dylan-get/Deep-Feature-Consistent-VAE community (archive-listed) 3 samples, 0 ran · 3 unverified
inception_score in 13 papers IS/is_torch.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · 6d3c813b7561493d · report
inception_score in 13 papers IS/is_paddle.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · 537c6692279cb920 · report
inception_score in 13 papers IS/is_source.py unverified Apache-2.0 recorded; this copy not marked cleared · pointer only · f344dca39109fdf5 · report

Tasks

AttributeStyle Transfer

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