Methods › Computer Vision › Semantic Segmentation Modules › Bilateral Guided Aggregation Layer
Bilateral Guided Aggregation Layer
Introduced by Changqian Yu et al. in BiSeNet V2: Bilateral Network with Guided Aggregation for Real-time Semantic Segmentation
archive 2025-07-28 Description, source and code snippet are the archive's method entry.
Bilateral Guided Aggregation Layer is a feature fusion layer for semantic segmentation that aims to enhance mutual connections and fuse different types of feature representation. It was used in the BiSeNet V2 architecture. Specifically, within the BiSeNet implementation, the layer was used to employ the contextual information of the Semantic Branch to guide the feature response of Detail Branch. With different scale guidance, different scale feature representations can be captured, which inherently encodes the multi-scale information.
In Syntology name not resolved (unknown_name). The lookup matched no method, paper or venue by this name; that asserts nothing about whether code exists.
Near matches the lookup lists, each a different name: GUIDED; GUIDED; Guided-CoT; Guided-TTS; TopK-Guided; Guided Loss; Guided-ReST; Guided-Retry.
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: 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 2 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 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.
-
Exploring Lip Segmentation Techniques in Computer Vision: A Comparative Analysis 20 Nov 2023 · 0 repositories · arXiv:2311.11992
-
BiSeNet V2: Bilateral Network with Guided Aggregation for Real-time Semantic Segmentation 5 Apr 2020 · 7 repositories · arXiv:2004.02147Syntology 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 2 honoured, 3 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 3 unverified (of 10 harvested samples) · 5 pointer-only (licence)
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.
| Task | Papers |
|---|---|
| Segmentation | 2 |
| Edge-computing | 1 |
| Lip Reading | 1 |
| Real-Time Semantic Segmentation | 1 |
| Semantic Segmentation | 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