Papers › VS-Net: Voting with Segmentation for Visual Localization

VS-Net: Voting with Segmentation for Visual Localization

23 May 2021CVPR 2021 1arXiv:2105.10886archive 2025-07-28

Zhaoyang Huang, Han Zhou, Yijin Li, Bangbang Yang, Yan Xu, Xiaowei Zhou, Hujun Bao, Guofeng Zhang, Hongsheng Li

Visual localization is of great importance in robotics and computer vision. Recently, scene coordinate regression based methods have shown good performance in visual localization in small static scenes. However, it still estimates camera poses from many inferior scene coordinates. To address this problem, we propose a novel visual localization framework that establishes 2D-to-3D correspondences between the query image and the 3D map with a series of learnable scene-specific landmarks. In the landmark generation stage, the 3D surfaces of the target scene are over-segmented into mosaic patches whose centers are regarded as the scene-specific landmarks. To robustly and accurately recover the scene-specific landmarks, we propose the Voting with Segmentation Network (VS-Net) to segment the pixels into different landmark patches with a segmentation branch and estimate the landmark locations within each patch with a landmark location voting branch. Since the number of landmarks in a scene may reach up to 5000, training a segmentation network with such a large number of classes is both computation and memory costly for the commonly used cross-entropy loss. We propose a novel prototype-based triplet loss with hard negative mining, which is able to train semantic segmentation networks with a large number of labels efficiently. Our proposed VS-Net is extensively tested on multiple public benchmarks and can outperform state-of-the-art visual localization methods. Code and models are available at https://github.com/zju3dv/VS-Net.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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):

Code

Syntology 15 code samples harvested from 1 repository linked to this paper: 8 ran (of which 5 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 1 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 7 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 15 samples from 1 repository, 8 ran (7 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

zju3dv/VS-Net officialmentioned in papermentioned on GitHubpytorchSyntology: 15 samples, 8 ran (1 instrument-failed) · 7 unverified report

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

15 samples harvested: 8 ran (of which 5 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 1 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 7 unverified. “Where Syntology's instrument failed” counts failures 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.

1ran · honoured contract
1ran · violated contract
1ran · our draft was wrong
5ran
7unverified

Licence: 0 of the 15 samples are 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.

Harvested from zju3dv/VS-Net. “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”. For 2 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

zju3dv/VS-Net official repository 15 samples, 8 ran (1 instrument-failed) · 7 unverified
FutureResult models/vs_net.py ran Apache-2.0 (permissive) · 7dc23d18929cb6b1 · report fixture: returned FutureResult · level recorded 2026-09-22
SlavePipe models/vs_net.py ran Apache-2.0 (permissive) · e75aa93b78286d50 · report fixture: returned SlavePipe · level recorded 2026-09-22
SyncMaster models/vs_net.py ran Apache-2.0 (permissive) · 0178fefa2f59ec8a · report fixture: returned SyncMaster · level recorded 2026-09-22
SynchronizedBatchNorm2d in 7 papers models/vs_net.py ran · metamorphic tier: deterministic Apache-2.0 (permissive) · 4aa7bfaba5716143 · report fixture: returned SynchronizedBatchNorm2d · level recorded 2026-09-22
_SynchronizedBatchNorm in 7 papers models/vs_net.py ran · metamorphic tier: deterministic Apache-2.0 (permissive) · 7457f764be2878a2 · report fixture: returned _SynchronizedBatchNorm · level recorded 2026-09-22
_sum_ft models/vs_net.py ran · violated contract fingerprinted Apache-2.0 (permissive) · 3151cee68a1020dc · report fixture: signature tensor:Tensor/3/float · returned Tensor · level recorded 2026-09-22
_unsqueeze_ft models/vs_net.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 1efd43bcf31727c0 · report fixture: signature tensor:Tensor/2/float · returned Tensor · level recorded 2026-09-22
build_aspp in 10 papers models/vs_net.py ran · our draft was wrong Apache-2.0 (permissive) · 5f036accfda6f69c · report fixture: signature backbone:str/0/str, output_stride:int/0/int, BatchNorm:callable/0/? · returned ASPP · level recorded 2026-09-22
ASPP in 23 papers models/vs_net.py unverified Apache-2.0 (permissive) · 27065a228bad5068 · report
VSNet models/vs_net.py unverified Apache-2.0 (permissive) · 45f12adaeae8ff49 · report
_ASPPModule in 7 papers models/vs_net.py unverified Apache-2.0 (permissive) · f3070bb2d0cc1f19 · report
build_backbone in 29 papers models/vs_net.py unverified Apache-2.0 (permissive) · 5c2833e31e74538a · report
build_decoder in 18 papers models/vs_net.py unverified Apache-2.0 (permissive) · 6b32bebbe43bf3a6 · report
decoder_v1 models/vs_net.py unverified Apache-2.0 (permissive) · f77c1e0417e279a4 · report
decoder_v2 models/vs_net.py unverified Apache-2.0 (permissive) · 21f984bcd960f312 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for VS-Net (graph method: VS-Net). 15 bricks; individually on a fixture: 8 ran (of which 5 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 1 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 7 unverified. The assembly has not been run end-to-end.

  1. VSNet entry · level 0 · unverified · 45f12adaeae8ff49
  2. SynchronizedBatchNorm2d helper · level 1 · ran · 4aa7bfaba5716143
  3. build_aspp helper · level 1 · ran · our draft was wrong · 5f036accfda6f69c
  4. build_backbone helper · level 0 · unverified · 5c2833e31e74538a
  5. build_decoder helper · level 0 · unverified · 6b32bebbe43bf3a6
  6. _SynchronizedBatchNorm helper · level 1 · ran · 7457f764be2878a2
  7. ASPP model · level 0 · unverified · 27065a228bad5068
  8. decoder_v1 model · level 0 · unverified · f77c1e0417e279a4
  9. decoder_v2 model · level 0 · unverified · 21f984bcd960f312
  10. SyncMaster helper · level 1 · ran · 0178fefa2f59ec8a
  11. _sum_ft helper · level 1 · ran · violated contract · 3151cee68a1020dc
  12. _unsqueeze_ft helper · level 1 · ran · honoured contract · 1efd43bcf31727c0
  13. _ASPPModule helper · level 0 · unverified · f3070bb2d0cc1f19
  14. FutureResult helper · level 1 · ran · 7dc23d18929cb6b1
  15. SlavePipe helper · level 1 · ran · e75aa93b78286d50

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2105.10886") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

SegmentationSemantic SegmentationVisual Localization

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Triplet Loss

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