Papers › Specificity-preserving RGB-D Saliency Detection
Specificity-preserving RGB-D Saliency Detection
Tao Zhou, Deng-Ping Fan, Geng Chen, Yi Zhou, Huazhu Fu
Salient object detection (SOD) on RGB and depth images has attracted more and more research interests, due to its effectiveness and the fact that depth cues can now be conveniently captured. Existing RGB-D SOD models usually adopt different fusion strategies to learn a shared representation from the two modalities (i.e., RGB and depth), while few methods explicitly consider how to preserve modality-specific characteristics. In this study, we propose a novel framework, termed SPNet} (Specificity-preserving network), which benefits SOD performance by exploring both the shared information and modality-specific properties (e.g., specificity). Specifically, we propose to adopt two modality-specific networks and a shared learning network to generate individual and shared saliency prediction maps, respectively. To effectively fuse cross-modal features in the shared learning network, we propose a cross-enhanced integration module (CIM) and then propagate the fused feature to the next layer for integrating cross-level information. Moreover, to capture rich complementary multi-modal information for boosting the SOD performance, we propose a multi-modal feature aggregation (MFA) module to integrate the modality-specific features from each individual decoder into the shared decoder. By using a skip connection, the hierarchical features between the encoder and decoder layers can be fully combined. Extensive experiments demonstrate that our~\ours outperforms cutting-edge approaches on six popular RGB-D SOD and three camouflaged object detection benchmarks. The project is publicly available at: https://github.com/taozh2017/SPNet.
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):
get_harvested_code_for_paper(arxiv_id="2108.08162")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2108.08162", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2108.08162")
Code
Syntology 14 code samples harvested from 1 repository linked to this paper: 8 ran (of which 5 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.
By repository: official repository: 14 samples from 1 repository, 8 ran (8 with no instrument failure; 0 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
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
14 samples harvested: 8 ran (of which 5 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 0 where Syntology's instrument failed) · 6 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.
Licence: 14 of the 14 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 taozh2017/spnet. “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 5 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.
6f7dc36dfca30bd6 · report
fixture: returned BasicConv2d · level recorded 2026-09-22 3ffcd486629f4a44 · report
fixture: signature rgb:Tensor/4/float, depth:Tensor/4/float, xx:Tensor/4/float · returned Tensor · level recorded 2026-09-24 cdd815c11bc3b308 · report
fixture: returned CIM0 · level recorded 2026-09-22 44339066f845642e · report
fixture: returned GCM · level recorded 2026-09-22 d0645ef0d981f8c6 · report
fixture: signature x_ful:Tensor/4/float, x1:Tensor/4/float, x2:Tensor/4/float · returned Tensor · level recorded 2026-09-24 64042638243b2287 · report
fixture: returned Res2Net · level recorded 2026-09-22 ed2cc280674cf0a0 · report
fixture: returned Res2Net_Ours · level recorded 2026-09-22 1ba84e986e6271da · report
fixture: returned MaxPool2d · level recorded 2026-09-22 80cb9358c3e49eba · report
a6795e469d7d38d1 · report
f87d1c0232c5537b · report
e53b02bcbaa59003 · report
6ed15a5516f3109e · 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 SP-Net (graph method: SP-Net). 15 bricks; individually on a fixture: 9 ran (of which 6 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified. The assembly has not been run end-to-end.
- SPNet entry · level 0 · unverified ·
0f30b631d3500cde - BasicConv2d helper · level 1 · ran ·
6f7dc36dfca30bd6 - CIM model · level 1 · ran ·
3ffcd486629f4a44 - CIM0 model · level 1 · ran ·
cdd815c11bc3b308 - GCM model · level 1 · ran ·
44339066f845642e - MFA model · level 1 · ran ·
d0645ef0d981f8c6 - Res2Net_model helper · level 0 · unverified ·
80cb9358c3e49eba - maxpool helper · level 1 · ran ·
1ba84e986e6271da - res2net101_v1b helper · level 0 · unverified ·
a6795e469d7d38d1 - res2net101_v1b_Ours helper · level 0 · unverified ·
f87d1c0232c5537b - res2net50_v1b helper · level 0 · unverified ·
e53b02bcbaa59003 - res2net50_v1b_Ours helper · level 0 · unverified ·
6ed15a5516f3109e - Bottle2neck helper · level 1 · ran ·
dc89ec9e1ceeaf0e - Res2Net helper · level 1 · ran ·
64042638243b2287 - Res2Net_Ours helper · level 1 · ran ·
ed2cc280674cf0a0
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.08162") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Object Detection | DSEC | SPNet | mAP | 27.7 | #5 of 12 | Archive leaderboard | report |
| Object Detection | PKU-DDD17-Car | SPNet | mAP50 | 84.7 | #2 of 14 | Archive leaderboard | report |
| Thermal Image Segmentation | RGB-T-Glass-Segmentation | SPNet | MAE | 0.041 | #6 of 22 | 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.
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