Papers › Prototype as Query for Few Shot Semantic Segmentation
Prototype as Query for Few Shot Semantic Segmentation
Leilei Cao, Yibo Guo, Ye Yuan, Qiangguo Jin
Few-shot Semantic Segmentation (FSS) was proposed to segment unseen classes in a query image, referring to only a few annotated examples named support images. One of the characteristics of FSS is spatial inconsistency between query and support targets, e.g., texture or appearance. This greatly challenges the generalization ability of methods for FSS, which requires to effectively exploit the dependency of the query image and the support examples. Most existing methods abstracted support features into prototype vectors and implemented the interaction with query features using cosine similarity or feature concatenation. However, this simple interaction may not capture spatial details in query features. To alleviate this limitation, a few methods utilized all pixel-wise support information via computing the pixel-wise correlations between paired query and support features implemented with the attention mechanism of Transformer. These approaches suffer from heavy computation on the dot-product attention between all pixels of support and query features. In this paper, we propose a simple yet effective framework built upon Transformer termed as ProtoFormer to fully capture spatial details in query features. It views the abstracted prototype of the target class in support features as Query and the query features as Key and Value embeddings, which are input to the Transformer decoder. In this way, the spatial details can be better captured and the semantic features of target class in the query image can be focused. The output of the Transformer-based module can be viewed as semantic-aware dynamic kernels to filter out the segmentation mask from the enriched query features. Extensive experiments on PASCAL-5ⁱ and COCO-20ⁱ show that our ProtoFormer significantly advances the state-of-the-art methods.
In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.
Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, on Syntology's MCP service (how to connect):
get_harvested_code_for_paper(arxiv_id="2211.14764")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2211.14764", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2211.14764")
Code
The archive's official repository (leileicao/protoformer) was not harvested; the 1 sample below is identical to code Syntology harvested from another paper's repository, and this paper's own copy was not located.
Syntology 1 code sample harvested: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.
By repository: 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
No date is recorded for the sample that ran: its level was written before Syntology's graph kept the date.
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
1 sample harvested: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 1 of the 1 sample is pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.
1 sample is listed last, in a group without a repository. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.
Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
census: 3 implementations from 12 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 4, kind float, dtype float32 · arg 2: rank 4, kind float, dtype float32 repository not located ran · our draft was wrong fingerprinted licence of this copy not recorded ·
df77cb77dfe58d6d · report
fixture: signature supp_feat:Tensor/4/float, mask:Tensor/4/float · returned Tensor · level recorded, date not recorded Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Few-Shot Semantic Segmentation | COCO-20i (1-shot) | ProtoFormer (ResNet-101) | FB-IoU | 70 | #19 of 85 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | COCO-20i (1-shot) | ProtoFormer (ResNet-101) | Mean IoU | 47 | #19 of 85 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | COCO-20i (1-shot) | ProtoFormer (ResNet-50) | FB-IoU | 69.6 | #32 of 85 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | COCO-20i (1-shot) | ProtoFormer (ResNet-50) | Mean IoU | 45.7 | #32 of 85 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | COCO-20i (5-shot) | ProtoFormer (ResNet-101) | FB-IoU | 74.6 | #17 of 81 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | COCO-20i (5-shot) | ProtoFormer (ResNet-101) | Mean IoU | 54.7 | #17 of 81 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | COCO-20i (5-shot) | ProtoFormer (ResNet-50) | FB-IoU | 73.3 | #24 of 81 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | COCO-20i (5-shot) | ProtoFormer (ResNet-50) | Mean IoU | 53.4 | #24 of 81 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | PASCAL-5i (1-Shot) | ProtoFormer (ResNet-101) | FB-IoU | 72.6 | #68 of 105 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | PASCAL-5i (1-Shot) | ProtoFormer (ResNet-101) | Mean IoU | 63.2 | #68 of 105 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | PASCAL-5i (1-Shot) | ProtoFormer (ResNet-50) | FB-IoU | 72.6 | #69 of 105 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | PASCAL-5i (1-Shot) | ProtoFormer (ResNet-50) | Mean IoU | 63.1 | #69 of 105 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | PASCAL-5i (5-Shot) | ProtoFormer (ResNet-50) | FB-IoU | 77.1 | #62 of 96 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | PASCAL-5i (5-Shot) | ProtoFormer (ResNet-50) | Mean IoU | 67.4 | #62 of 96 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | PASCAL-5i (5-Shot) | ProtoFormer (ResNet-101) | FB-IoU | 76.3 | #64 of 96 | Archive leaderboard | report |
| Few-Shot Semantic Segmentation | PASCAL-5i (5-Shot) | ProtoFormer (ResNet-101) | Mean IoU | 67 | #64 of 96 | Archive leaderboard | report |
Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.
Methods
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