Methods › General › Interpretability › Network Dissection

Network Dissection

11 papers tagged archive 2025-07-28

Introduced by Bolei Zhou et al. in Interpreting Deep Visual Representations via Network Dissection

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

Network Dissection is an interpretability method for CNNs that evaluates the alignment between individual hidden units and a set of visual semantic concepts. By identifying the best alignments, units are given human interpretable labels across a range of objects, parts, scenes, textures, materials, and colors.

The measurement of interpretability proceeds in three steps:

PaperSource

In Syntology about another paper, arXiv:1704.05796: repository known, no verified implementation (declared_code; repositories: 1 listed of 1 in the graph, strongest link: official). The lookup matched a paper by its title, arXiv:1704.05796, not a method entry. About another paper: this answer is about arXiv:1704.05796, while the archive credits arXiv:1711.05611.

Origin paper of this answer, arXiv:1704.05796 (its page on this site · its page on Syntology).

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: 11 · with a code link: 8 · where Syntology ran a sample: 3 (2 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (3 of 11 tagged: 2 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument)

Page 1 of 1: papers 1 to 11 of 11, 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.

Tasks archive 2025-07-28

16 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Adversarial Defense1
Adversarial Robustness1
Attribute1
Classification1
Decision Making1
General Classification1
Image Classification1
Image Generation1
Image Retrieval1
Knowledge Distillation1
Object1
Object Detection1
Retrieval1
Segmentation1
image-classification1
object-detection1

Usage over time archive 2025-07-28

Papers per year tagged with Network Dissection: 2017 to 2023, peak 3 3 0 2017: 1 paper 2017 2018: 2 papers 2018 2019: 3 papers 2019 2020: 0 papers 2020 2021: 2 papers 2021 2022: 0 papers 2022 2023: 3 papers 2023
Papers per year the archive tags with this method, by the paper's archive date (11 dated). Bars are counts, not a trend claim.

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

Interpretability

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