Papers › Multi-view Aggregation Network for Dichotomous Image Segmentation

Multi-view Aggregation Network for Dichotomous Image Segmentation

11 Apr 2024CVPR 2024 1arXiv:2404.07445archive 2025-07-28

Qian Yu, Xiaoqi Zhao, Youwei Pang, Lihe Zhang, Huchuan Lu

Dichotomous Image Segmentation (DIS) has recently emerged towards high-precision object segmentation from high-resolution natural images. When designing an effective DIS model, the main challenge is how to balance the semantic dispersion of high-resolution targets in the small receptive field and the loss of high-precision details in the large receptive field. Existing methods rely on tedious multiple encoder-decoder streams and stages to gradually complete the global localization and local refinement. Human visual system captures regions of interest by observing them from multiple views. Inspired by it, we model DIS as a multi-view object perception problem and provide a parsimonious multi-view aggregation network (MVANet), which unifies the feature fusion of the distant view and close-up view into a single stream with one encoder-decoder structure. With the help of the proposed multi-view complementary localization and refinement modules, our approach established long-range, profound visual interactions across multiple views, allowing the features of the detailed close-up view to focus on highly slender structures.Experiments on the popular DIS-5K dataset show that our MVANet significantly outperforms state-of-the-art methods in both accuracy and speed. The source code and datasets will be publicly available at MVANet (https://github.com/qianyu-dlut/MVANet).

PaperPDFConference PDFCodeCode Syntology ran

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

By repository: official repository: 9 samples from 1 repository, 9 ran (1 with no instrument failure; 8 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 9 samples that ran have no recorded date.

qianyu-dlut/mvanet officialmentioned in papermentioned on GitHubpytorchMITSyntology: 9 samples, 9 ran (8 instrument-failed) · 0 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

9 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 8 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
6ran · our draft was wrong
2ran; the contract check could not run

Licence: 1 of the 9 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, 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 qianyu-dlut/mvanet. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

qianyu-dlut/mvanet official repository 9 samples, 9 ran (8 instrument-failed) · 0 unverified
window_partition in 377 papers
census: 13 implementations from 17 papers, 5 distinct outputs across 3 buckets, one shared input per bucket
model/SwinTransformer.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · 144d10b49baeb8a6 · report fixture: signature x:Tensor/4/float, window_size:int/0/int · returned Tensor · level recorded, date not recorded
cv_random_flip in 14 papers utils/dataset_strategy_fpn.py ran; the contract check could not run (RAISES) · metamorphic tier: well formed MIT (permissive) · 41839b27773cccf7 · report fixture: signature img:Image/0/?, label:Image/0/? · returned tuple · level recorded 2026-09-22
get_activation_fn in 67 papers model/MVANet.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · f2e72d81f39d65cd · report fixture: signature activation:str/0/str · returned function · level recorded 2026-09-25
l2_regularisation in 7 papers utils/misc.py ran · honoured contract MIT (permissive) · c23b05634625d281 · report fixture: signature m:callable/0/? · returned Tensor · level recorded 2026-09-22
make_cbg model/MVANet.py ran · our draft was wrong MIT (permissive) · 78918720bdb361d4 · report fixture: signature in_dim:int/0/int, out_dim:int/0/int · returned Sequential · level recorded 2026-09-24
make_cbr model/MVANet.py ran · our draft was wrong MIT (permissive) · 6ffe5c11970654fa · report fixture: signature in_dim:int/0/int, out_dim:int/0/int · returned Sequential · level recorded 2026-09-24
randomCrop in 16 papers utils/dataset_strategy_fpn.py ran · our draft was wrong MIT (permissive) · b8fc70f2a16b23cc · report fixture: signature image:Image/0/?, label:Image/0/? · returned tuple · level recorded 2026-09-22
randomRotation in 14 papers utils/dataset_strategy_fpn.py ran · our draft was wrong MIT (permissive) · 8d40bcc4f2cf3edb · report fixture: signature image:Image/0/?, label:Image/0/? · returned tuple · level recorded 2026-09-22
window_reverse in 296 papers model/SwinTransformer.py ran · our draft was wrong MIT (permissive) · 61bf152e6a42a184 · report fixture: signature windows:Tensor/4/float, window_size:int/0/int, H:int/0/int, W:int/0/int · returned Tensor · level recorded, date not recorded

Tasks

DecoderDichotomous Image SegmentationImage SegmentationSemantic Segmentation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Dichotomous Image Segmentation DIS-TE1 MVANet E-measure 0.911 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE1 MVANet HCE 104 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE1 MVANet MAE 0.037 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE1 MVANet S-Measure 0.879 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE1 MVANet max F-Measure 0.873 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE1 MVANet weighted F-measure 0.823 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE2 MVANet E-measure 0.944 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE2 MVANet HCE 251 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE2 MVANet MAE 0.030 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE2 MVANet S-Measure 0.915 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE2 MVANet max F-Measure 0.916 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE2 MVANet weighted F-measure 0.874 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE3 MVANet E-measure 0.954 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE3 MVANet HCE 525 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE3 MVANet MAE 0.031 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE3 MVANet S-Measure 0.920 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE3 MVANet max F-Measure 0.929 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE3 MVANet weighted F-measure 0.890 #2 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE4 MVANet E-measure 0.944 #1 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE4 MVANet HCE 2331 #1 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE4 MVANet MAE 0.041 #1 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE4 MVANet S-Measure 0.903 #1 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE4 MVANet max F-Measure 0.912 #1 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-TE4 MVANet weighted F-measure 0.857 #1 of 22 Archive leaderboard report
Dichotomous Image Segmentation DIS-VD MVANet E-measure 0.941 #4 of 24 Archive leaderboard report
Dichotomous Image Segmentation DIS-VD MVANet HCE 893 #4 of 24 Archive leaderboard report
Dichotomous Image Segmentation DIS-VD MVANet MAE 0.034 #4 of 24 Archive leaderboard report
Dichotomous Image Segmentation DIS-VD MVANet S-Measure 0.905 #4 of 24 Archive leaderboard report
Dichotomous Image Segmentation DIS-VD MVANet max F-Measure 0.904 #4 of 24 Archive leaderboard report
Dichotomous Image Segmentation DIS-VD MVANet weighted F-measure 0.863 #4 of 24 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Focus

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