Methods › Computer Vision › Instance Segmentation Models › SCNet

SCNet

6 papers tagged archive 2025-07-28

Introduced by Thang Vu et al. in SCNet: Training Inference Sample Consistency for Instance Segmentation

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

Sample Consistency Network (SCNet) is a method for instance segmentation which ensures the IoU distribution of the samples at training time are as close to that at inference time. To this end, only the outputs of the last box stage are used for mask predictions at both training and inference. The Figure shows the IoU distribution of the samples going to the mask branch at training time with/without sample consistency compared to that at inference time.

PaperSource

In Syntology name not resolved (unknown_name). Other entries in Syntology's graph carry this name; the lookup's note below says what that means for this name.

From the lookup's note on this name: Nothing resolved to this name, but 3 entries in Syntology's graph carry it; the most cited is the paper “SCNet: Learning Semantic Correspondence” (arXiv:1705.04043, 159 citations). The lookup reads this as a miss of its own name matching, not a gap in coverage: the graph holds the name under a spelling the lookup did not reach. For arXiv:1705.04043: its page on this site · ask the lookup about it.

Near matches the lookup lists, each a different name: Neuro-SCNet.

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: 6 · with a code link: 5 · 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 6 tagged papers has a Syntology run on record

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

14 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
Cloth-Changing Person Re-Identification2
Person Re-Identification2
CPU1
Decoder1
Diversity1
Image Enhancement1
Instance Segmentation1
Music Source Separation1
Object Detection1
Prompt Learning1
Semantic Segmentation1
Vocal Bursts Type Prediction1
compressed sensing1
object-detection1

Usage over time archive 2025-07-28

Papers per year tagged with SCNet: 2020 to 2024, peak 2 2 0 2020: 1 paper 2020 2021: 1 paper 2021 2022: 0 papers 2022 2023: 2 papers 2023 2024: 2 papers 2024
Papers per year the archive tags with this method, by the paper's archive date (6 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

Instance Segmentation Models

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