Papers › A Simple Pooling-Based Design for Real-Time Salient Object Detection

A Simple Pooling-Based Design for Real-Time Salient Object Detection

21 Apr 2019CVPR 2019 6arXiv:1904.09569archive 2025-07-28

Jiang-Jiang Liu, Qibin Hou, Ming-Ming Cheng, Jiashi Feng, Jianmin Jiang

We solve the problem of salient object detection by investigating how to expand the role of pooling in convolutional neural networks. Based on the U-shape architecture, we first build a global guidance module (GGM) upon the bottom-up pathway, aiming at providing layers at different feature levels the location information of potential salient objects. We further design a feature aggregation module (FAM) to make the coarse-level semantic information well fused with the fine-level features from the top-down pathway. By adding FAMs after the fusion operations in the top-down pathway, coarse-level features from the GGM can be seamlessly merged with features at various scales. These two pooling-based modules allow the high-level semantic features to be progressively refined, yielding detail enriched saliency maps. Experiment results show that our proposed approach can more accurately locate the salient objects with sharpened details and hence substantially improve the performance compared to the previous state-of-the-arts. Our approach is fast as well and can run at a speed of more than 30 FPS when processing a 300 ×400 image. Code can be found at http://mmcheng.net/poolnet/.

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

By repository: community (archive-listed): 3 samples from 2 repositories, 1 ran (0 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.

Res2Net/Res2Net-PoolNet mentioned on GitHubpytorchSyntology: 2 samples, 0 ran · 2 unverified report
backseason/PoolNet mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
balast/saliency_detector mentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
hualuluu/--every-day-paper-- mentioned on GitHubSyntology: not harvested report
chouxianyu/Boundary-Aware-PoolNet pytorchnot reachable when probed 2026-09-17 — repositories for recent papers often appear after camera-readySyntology: not harvested 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

3 samples harvested: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure 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 · our draft was wrong
2unverified

Licence: 0 of the 3 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 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.

Res2Net/Res2Net-PoolNet community (archive-listed) 2 samples, 0 ran · 2 unverified
build_model in 469 papers networks/joint_poolnet_res2net.py unverified MIT (permissive) · 36614cc6a0cacb48 · report
extra_layer networks/joint_poolnet_res2net.py unverified MIT (permissive) · 6507dcc5439172d6 · report
backseason/PoolNet community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
get_test_info joint_main.py ran · our draft was wrong MIT (permissive) · 3af29617906f453d · report fixture: signature sal_mode:str/0/str · returned tuple · level recorded 2026-09-22

Tasks

Object DetectionRGB Salient Object DetectionSalient Object Detectionobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
RGB Salient Object Detection DUT-OMRON PoolNet (VGG-16) F-measure 0.833 #12 of 18 Archive leaderboard report
RGB Salient Object Detection DUT-OMRON PoolNet (VGG-16) MAE 0.053 #12 of 18 Archive leaderboard report
RGB Salient Object Detection DUTS-TE PoolNet (VGG-16) MAE 0.036 #19 of 31 Archive leaderboard report
RGB Salient Object Detection DUTS-TE PoolNet (VGG-16) max F-measure 0.892 #19 of 31 Archive leaderboard report
RGB Salient Object Detection ECSSD PoolNet (VGG-16) F-measure 0.945 #8 of 14 Archive leaderboard report
RGB Salient Object Detection ECSSD PoolNet (VGG-16) MAE 0.038 #8 of 14 Archive leaderboard report
RGB Salient Object Detection HKU-IS PoolNet (VGG-16) F-measure 0.935 #8 of 14 Archive leaderboard report
RGB Salient Object Detection HKU-IS PoolNet (VGG-16) MAE 0.03 #8 of 14 Archive leaderboard report
RGB Salient Object Detection PASCAL-S PoolNet (VGG-16) F-measure 0.88 #7 of 13 Archive leaderboard report
RGB Salient Object Detection PASCAL-S PoolNet (VGG-16) MAE 0.065 #7 of 13 Archive leaderboard report
RGB Salient Object Detection SOD PoolNet (VGG-16) F-measure 0.882 #1 of 3 Archive leaderboard report
RGB Salient Object Detection SOD PoolNet (VGG-16) MAE 0.102 #1 of 3 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

SPEED

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