Methods › Computer Vision › Generative Models › IAN
Introspective Adversarial Network
IAN
archive 2025-07-28 Description, source and code snippet are the archive's method entry.
The Introspective Adversarial Network (IAN) is a hybridization of GANs and VAEs that leverages the power of the adversarial objective while maintaining the VAE’s efficient inference mechanism. It uses the discriminator of the GAN, D, as a feature extractor for an inference subnetwork, E, which is implemented as a fully-connected layer on top of the final convolutional layer of the discriminator. We infer latent values Z ∼E(X) = q(Z|X) for reconstruction and sample random values Z ∼p(Z) from a standard normal for random image generation using the generator network, G.
Three distinct loss functions are used:
- ℒ_(img), the L1 pixel-wise reconstruction loss, which is preferred to the L2 reconstruction loss for its higher average gradient.
- ℒ_(𝒻ℯ𝒶𝓉𝓊𝓇ℯ), the feature-wise reconstruction loss, evaluated as the L2 difference between the original and reconstruction in the space of the hidden layers of the discriminator.
- ℒ_(adv), the ternary adversarial loss, a modification of the adversarial loss that forces the discriminator to label a sample as real, generated, or reconstructed (as opposed to a binary real vs. generated label).
Including the VAE’s KL divergence between the inferred latents E(X) and the prior p(Z), the loss function for the generator and encoder network is thus:
ℒ_(E, G) = λ_(adv)ℒ_(G_(adv)) + λ_(img)ℒ_(img) + λ_(feature)ℒ_(feature) + D_(KL)(E(X) || p(Z))
Where the λ terms weight the relative importance of each loss. We set λ_(img) to 3 and leave the other terms at 1. The discriminator is updated solely using the ternary adversarial loss. During each training step, the generator produces reconstructions G(E(X)) (using the standard VAE reparameterization trick) from data X and random samples G(Z), while the discriminator observes X as well as the reconstructions and random samples, and both networks are simultaneously updated.
In Syntology name not resolved (unknown_name). Other entries in Syntology's graph carry this name; the lookup's note below says what that means for this name.
From the lookup's note on this name: Nothing resolved to this name, but 2 entries in Syntology's graph carry it; the most cited is the paper “IAN: The Individual Aggregation Network for Person Search” (arXiv:1705.05552, 160 citations). The lookup reads this as a miss of its own name matching, not a gap in coverage: the graph holds the name under a spelling the lookup did not reach. For arXiv:1705.05552: ask the lookup about it.
Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.
Papers archive 2025-07-28
archive papers tagged: 4 · with a code link: 3 · where Syntology ran a sample: 1 (1 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (1 of 4 tagged: 1 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Page 1 of 1: papers 1 to 4 of 4, newest first by the archive's date (ties by slug), in archive order.
Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.
-
Cross-View Geolocalization and Disaster Mapping with Street-View and VHR Satellite Imagery: A Case Study of Hurricane IAN 13 Aug 2024 · 1 repository · arXiv:2408.06761
-
Inferior Alveolar Nerve Segmentation in CBCT images using Connectivity-Based Selective Re-training 18 Aug 2023 · 1 repository · arXiv:2308.09298
-
Arabic aspect based sentiment analysis using bidirectional GRU based models 23 Jan 2021 · 0 repositories · arXiv:2101.10539
-
Neural Photo Editing with Introspective Adversarial Networks 22 Sep 2016 · 2 repositories · arXiv:1609.07093Syntology official (archive's flag): 2 ran · 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 2 honoured, 0 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified (of 2 harvested samples)
Tasks archive 2025-07-28
7 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.
| Task | Papers |
|---|---|
| Aspect-Based Sentiment Analysis | 1 |
| Aspect-Based Sentiment Analysis (ABSA) | 1 |
| Contrastive Learning | 1 |
| Disaster Response | 1 |
| Image Generation | 1 |
| Sentence | 1 |
| Sentiment Analysis | 1 |
Usage over time archive 2025-07-28
Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).
Categories archive 2025-07-28
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