Datasets › S3DIS › Papers, page 2

S3DIS (Stanford 3D Indoor Scene Dataset (S3DIS))

Papers archive 2025-07-28

papers with a benchmark row: 108 · with a code link: 88 · where Syntology ran a sample: 32 (28 with a run with no instrument failure, 4 where every run was a failure of Syntology's instrument) Syntology

Show: all papers with a benchmark rowonly where code ran (32 of 108 with a benchmark row: 28 with a run with no instrument failure, 4 where every run was a failure of Syntology's instrument)

Page 2 of 2: papers 101 to 108 of 108 with a leaderboard row on this dataset's benchmarks, newest first by the archive's date (ties by slug; undated papers last).

The archive's own "papers using this dataset" list was never published, so this is the benchmark-backed subset, not that list; the archive's count for this dataset is 488. The Syntology column is from Syntology's graph, stated per sample; it is not part of any archive number. A line reads “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” (C is a part of N, never taken away from it); the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced. When the archive marks a repository official for the paper, the cell 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. Syntology's record for this page has not changed since 2026-09-28, the first build that kept a record date for it; when this build read Syntology's graph is in the build record.