Methods › Computer Vision › Convolutions › SAC

Switchable Atrous Convolution

SAC

168 papers tagged archive 2025-07-28

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

Switchable Atrous Convolution (SAC) softly switches the convolutional computation between different atrous rates and gathers the results using switch functions. The switch functions are spatially dependent, i.e., each location of the feature map might have different switches to control the outputs of SAC. To use SAC in a detector, we convert all the standard 3x3 convolutional layers in the bottom-up backbone to SAC.

Source: DetectoRS: Detecting Objects with Recursive Feature...

In Syntology repository known, no verified implementation (declared_code; repositories: 1 listed of 1 in the graph, strongest link: listed only). The archive credits no paper with an arXiv id for this method, so whether this answer (about arXiv:2601.14039) is about this method is not checked.

From the lookup's note on this name: The same name also belongs to the paper “SAC: Semantic Attention Composition for Text-Conditioned Image Retrieval” (arXiv:2009.01485, 58 citations), which the lookup finds cited far more than the paper this answer is about (0 citations), so this answer may be about a different sense of the name. For arXiv:2009.01485: ask the lookup about it.

Code Syntology holds under other names, as the lookup lists them (code_nearby); not a complete list, and none of them is this method.

Origin paper of this answer, arXiv:2601.14039 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 5 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 4 where Syntology's instrument failed) · 3 unverified (of 8 harvested samples). 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.

What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).

Papers archive 2025-07-28

archive papers tagged: 168 · with a code link: 69 · where Syntology ran a sample: 20 (16 with a run with no instrument failure, 4 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (20 of 168 tagged: 16 with a run with no instrument failure, 4 where every run was a failure of Syntology's instrument)

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

20 shown of 117 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
Reinforcement Learning (RL)86
reinforcement-learning65
Deep Reinforcement Learning59
Reinforcement Learning50
Continuous Control29
continuous-control28
MuJoCo21
Q-Learning12
OpenAI Gym9
Atari Games8
Decision Making8
Autonomous Driving5
ISAC5
Imitation Learning5
Scheduling5
Integrated sensing and communication4
Adversarial Defense3
Benchmarking3
Computational Efficiency3
Continual Learning3

Usage over time archive 2025-07-28

Papers per year tagged with SAC: 2020 to 2025, peak 42 42 0 2020: 17 papers 2020 2021: 41 papers 2021 2022: 28 papers 2022 2023: 25 papers 2023 2024: 42 papers 2024 2025: 15 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (168 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

Convolutions

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