Papers › Multi-Anchor Active Domain Adaptation for Semantic Segmentation

Multi-Anchor Active Domain Adaptation for Semantic Segmentation

18 Aug 2021ICCV 2021 10arXiv:2108.08012archive 2025-07-28

Munan Ning, Donghuan Lu, Dong Wei, Cheng Bian, Chenglang Yuan, Shuang Yu, Kai Ma, Yefeng Zheng

Unsupervised domain adaption has proven to be an effective approach for alleviating the intensive workload of manual annotation by aligning the synthetic source-domain data and the real-world target-domain samples. Unfortunately, mapping the target-domain distribution to the source-domain unconditionally may distort the essential structural information of the target-domain data. To this end, we firstly propose to introduce a novel multi-anchor based active learning strategy to assist domain adaptation regarding the semantic segmentation task. By innovatively adopting multiple anchors instead of a single centroid, the source domain can be better characterized as a multimodal distribution, thus more representative and complimentary samples are selected from the target domain. With little workload to manually annotate these active samples, the distortion of the target-domain distribution can be effectively alleviated, resulting in a large performance gain. The multi-anchor strategy is additionally employed to model the target-distribution. By regularizing the latent representation of the target samples compact around multiple anchors through a novel soft alignment loss, more precise segmentation can be achieved. Extensive experiments are conducted on public datasets to demonstrate that the proposed approach outperforms state-of-the-art methods significantly, along with thorough ablation study to verify the effectiveness of each component.

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 12 code samples harvested from 2 repositories linked to this paper: 9 ran (of which 2 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 7 samples from 1 repository, 6 ran (5 with no instrument failure; 1 where Syntology's instrument failed); community (archive-listed): 5 samples from 1 repository, 3 ran (1 with no instrument failure; 2 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 between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

munanning/mada officialmentioned in papermentioned on GitHubpytorchMITSyntology: 7 samples, 6 ran (1 instrument-failed) · 1 unverified report
munanning/madav2 mentioned on GitHubpytorchMITSyntology: 5 samples, 3 ran (2 instrument-failed) · 2 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

12 samples harvested: 9 ran (of which 2 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 3 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.

3ran · our draft was wrong
6ran
3unverified

Licence: 3 of the 12 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

munanning/mada official repository 7 samples, 6 ran (1 instrument-failed) · 1 unverified
Class_Features select_active_samples.py ran MIT (permissive) · f3a6086bb86995ce · report fixture: returned Class_Features · level recorded 2026-09-22
NormalisationPoolingFunction select_active_samples.py ran MIT (permissive) · daf02aef604440a9 · report fixture: returned NormalisationPoolingFunction · level recorded 2026-09-22
bootstrapped_cross_entropy2d loss/loss.py ran MIT (permissive) · dfe03b9cbc5639c5 · report fixture: signature input:Tensor/4/float, target:Tensor/3/int, K:int/0/int, weight:Tensor/1/float, size_average:bool/0/bool · returned Tensor · level recorded 2026-09-26
cross_entropy2d in 12 papers loss/loss.py ran MIT (permissive) · 57b36a6b7f29df1a · report fixture: signature input:Tensor/4/float, target:Tensor/3/int, weight:Tensor/1/float, size_average:bool/0/bool · returned Tensor · level recorded 2026-09-25
get_scheduler in 122 papers models/networks.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 62a8cdfdb51ec275 · report fixture: signature optimizer:Adam/0/?, opt:Options/0/? · returned LambdaLR · level recorded 2026-09-22
normalisation_pooling select_active_samples.py ran fingerprinted MIT (permissive) · 9032dc1e1e618038 · report fixture: signature input:Tensor/2/float, scale_factor:float/0/float · returned Tensor · level recorded 2026-09-24
multi_scale_cross_entropy2d loss/loss.py unverified MIT (permissive) · 6ceebb622653f267 · report
munanning/madav2 community (archive-listed) 5 samples, 3 ran (2 instrument-failed) · 2 unverified
cross_entropy2d in 12 papers loss/loss.py ran MIT (permissive) · 4865609e5a035433 · report fixture: signature input:Tensor/4/float, target:Tensor/3/int, weight:Tensor/1/float, size_average:bool/0/bool · returned Tensor · level recorded 2026-09-24
get_norm_layer in 111 papers models/networks.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 05f3653dd76468d9 · report fixture: signature norm_type:str/0/str · returned partial · level recorded 2026-09-22
init_net in 47 papers models/networks.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · bf329cef80ee24c5 · report fixture: signature net:callable/0/?, init_type:str/0/str, init_gain:float/0/float, gpu_ids:list/1/empty · returned SimpleNet · level recorded 2026-09-22
get_criterion in 15 papers loss/loss.py unverified MIT (permissive) · 8a376f4180e6fb9c · report
multi_scale_cross_entropy2d loss/loss.py unverified MIT (permissive) · 02c66a386abd9218 · 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 Multi-Anchor Active Domain Adaptation (graph method: Multi-Anchor Active Domain Adaptation). 3 bricks; individually on a fixture: 3 ran (of which 2 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

  1. Class_Features entry · level 1 · ran · f3a6086bb86995ce
  2. normalisation_pooling helper · level 1 · ran · 9032dc1e1e618038
  3. NormalisationPoolingFunction helper · level 1 · ran · daf02aef604440a9

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="2108.08012") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Active LearningDomain AdaptationSemantic Segmentation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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