Methods › Computer Vision › Semantic Segmentation Models › PSPNet › Papers where code ran, page 1
PSPNet
Papers archive 2025-07-28
archive papers tagged: 47 · with a code link: 21 · where Syntology ran a sample: 2 (2 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 (2 of 47 tagged: 2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Syntology We ran code from the paper's repository; we did not isolate this method inside it.
Page 1 of 1: papers 1 to 2 of the 2 tagged papers where Syntology ran at least one harvested sample (2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument), newest first by the archive's date (ties by arXiv id). This is a filter on Syntology's record ordered by date only, not a ranking; a run is not a correctness claim. A paper missing from this list is not a recorded non-run: it may have no arXiv id, no harvested code, or only samples that have not run yet.
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.
-
Learning What Not to Segment: A New Perspective on Few-Shot Segmentation 15 Mar 2022 · 1 repository · arXiv:2203.07615Syntology official (archive's flag): 16 ran · 16 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 7 where Syntology's instrument failed) · 1 unverified (of 17 harvested samples) · 11 pointer-only (licence)
-
Pyramid Scene Parsing Network 4 Dec 2016 · 67 repositories · arXiv:1612.01105Syntology community repositories only · 21 ran (of which 0 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 0 violated, 14 with no contract checked; 7 where Syntology's instrument failed) · 8 unverified (of 29 harvested samples) · 5 pointer-only (licence)