Methods › General › Attention Modules › CAB

Contextual Attention Block

CAB

2 papers tagged archive 2025-07-28

Introduced by Gianluca Carloni et al. in Connectivity-Inspired Network for Context-Aware Recognition

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

The Contextual Attention Block (CAB) is a new plug-and-play module to model context awareness. It is simple and effective and can be integrated with any feed-forward neural network.

CAB infers weights that multiply the feature maps according to their causal influence on the scene, modeling the co-occurrence of different objects in the image.

You can place the CAB module at different bottlenecks to infuse a hierarchical context awareness into the model.

PaperSource

In Syntology about another paper, arXiv:2605.16736: repository known, no verified implementation (declared_code; repositories: 1 listed of 1 in the graph, strongest link: listed only). About another paper: this answer is about arXiv:2605.16736, while the archive credits arXiv:2409.04360.

Origin paper of this answer, arXiv:2605.16736 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 3 honoured, 1 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified (of 7 harvested samples) · 7 pointer-only (licence). The instrument figure counts failures of Syntology's instrument, not of the code. Ran means executed on a synthesized input, not that the code is correct.

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: 2 · with a code link: 1 · where Syntology ran a sample: 0 (0 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: none of the 2 tagged papers has a Syntology run on record

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

5 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
Biologically-plausible Training1
Causal Discovery1
Functional Connectivity1
Image Classification1
image-classification1

Usage over time archive 2025-07-28

Papers per year tagged with CAB: 2024 to 2025, peak 1 1 0 2024: 1 paper 2024 2025: 1 paper 2025
Papers per year the archive tags with this method, by the paper's archive date (2 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

Attention Modules

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