Papers › TRACER: Extreme Attention Guided Salient Object Tracing Network

TRACER: Extreme Attention Guided Salient Object Tracing Network

14 Dec 2021arXiv:2112.07380archive 2025-07-28

Min Seok Lee, WooSeok Shin, Sung Won Han

Existing studies on salient object detection (SOD) focus on extracting distinct objects with edge information and aggregating multi-level features to improve SOD performance. To achieve satisfactory performance, the methods employ refined edge information and low multi-level discrepancy. However, both performance gain and computational efficiency cannot be attained, which has motivated us to study the inefficiencies in existing encoder-decoder structures to avoid this trade-off. We propose TRACER, which detects salient objects with explicit edges by incorporating attention guided tracing modules. We employ a masked edge attention module at the end of the first encoder using a fast Fourier transform to propagate the refined edge information to the downstream feature extraction. In the multi-level aggregation phase, the union attention module identifies the complementary channel and important spatial information. To improve the decoder performance and computational efficiency, we minimize the decoder block usage with object attention module. This module extracts undetected objects and edge information from refined channels and spatial representations. Subsequently, we propose an adaptive pixel intensity loss function to deal with the relatively important pixels unlike conventional loss functions which treat all pixels equally. A comparison with 13 existing methods reveals that TRACER achieves state-of-the-art performance on five benchmark datasets. We have released TRACER at https://github.com/Karel911/TRACER.

PaperPDFCodeCode 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 6 code samples harvested from 1 repository linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 6 samples from 1 repository, 6 ran (6 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 on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

Karel911/TRACER officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 6 samples, 6 ran (0 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

6 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 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 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.

6ran

Licence: 0 of the 6 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 Karel911/TRACER. “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.

Karel911/TRACER official repository 6 samples, 6 ran (0 instrument-failed) · 0 unverified
Criterion in 6 papers util/losses.py ran Apache-2.0 (permissive) · f5bd6bccbeb5626f · report fixture: signature args:Args/0/? · returned function · level recorded 2026-09-24
Optimizer in 18 papers util/losses.py ran Apache-2.0 (permissive) · e1efea555907f415 · report fixture: signature args:Args/0/?, model:callable/0/? · returned Adam · level recorded 2026-09-24
Scheduler in 12 papers util/losses.py ran Apache-2.0 (permissive) · f79eb9487bb69976 · report fixture: signature args:Args/0/?, optimizer:SGD/0/? · returned ReduceLROnPlateau · level recorded 2026-09-24
get_loader in 62 papers dataloader.py ran Apache-2.0 (permissive) · 48f924316939963f · report fixture: signature img_folder:str/0/str, gt_folder:str/0/str, edge_folder:str/0/str, phase:str/0/str, batch_size:int/0/int, shuffle:bool/0/bool, num_workers:int/0/int, transform:callable/0/?, seed:int/0/int · returned DataLoader · level recorded 2026-09-24
get_test_augmentation dataloader.py ran Apache-2.0 (permissive) · 9495d7c131ec1b70 · report fixture: signature img_size:int/0/int · returned Compose · level recorded 2026-09-24
get_train_augmentation dataloader.py ran Apache-2.0 (permissive) · cc56bda02cebc582 · report fixture: signature img_size:int/0/int, ver:int/0/int · returned Compose · level recorded 2026-09-24

Tasks

Computational EfficiencyDecoderObjectObject DetectionRGB Salient Object DetectionSalient Object Detectionobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
RGB Salient Object Detection DUT-OMRON TRACER-TE7 F-measure 0.849 #8 of 18 Archive leaderboard report
RGB Salient Object Detection DUT-OMRON TRACER-TE7 MAE 0.045 #8 of 18 Archive leaderboard report
RGB Salient Object Detection DUT-OMRON TRACER-TE7 S-Measure 0.855 #8 of 18 Archive leaderboard report
RGB Salient Object Detection DUT-OMRON TRACER-TE7 mean F-Measure 0.798 #8 of 18 Archive leaderboard report
RGB Salient Object Detection DUT-OMRON TRACER-(ResNet50) MAE 0.050 #17 of 18 Archive leaderboard report
RGB Salient Object Detection DUTS-TE TRACER-TE7 MAE 0.022 #8 of 31 Archive leaderboard report
RGB Salient Object Detection DUTS-TE TRACER-TE7 S-Measure 0.919 #8 of 31 Archive leaderboard report
RGB Salient Object Detection DUTS-TE TRACER-TE7 max F-measure 0.932 #8 of 31 Archive leaderboard report
RGB Salient Object Detection DUTS-TE TRACER-TE7 mean F-Measure 0.904 #8 of 31 Archive leaderboard report
RGB Salient Object Detection DUTS-TE TRACER-(ResNet50) MAE 0.035 #31 of 31 Archive leaderboard report
RGB Salient Object Detection ECSSD TRACER-TE7 F-measure 0.961 #3 of 14 Archive leaderboard report
RGB Salient Object Detection ECSSD TRACER-TE7 MAE 0.026 #3 of 14 Archive leaderboard report
RGB Salient Object Detection ECSSD TRACER-TE7 S-Measure 0.935 #3 of 14 Archive leaderboard report
RGB Salient Object Detection ECSSD TRACER-TE7 mean F-Measure 0.940 #3 of 14 Archive leaderboard report
RGB Salient Object Detection ECSSD TRACER-(ResNet50) MAE 0.033 #13 of 14 Archive leaderboard report
RGB Salient Object Detection HKU-IS TRACER-TE7 F-measure 0.954 #3 of 14 Archive leaderboard report
RGB Salient Object Detection HKU-IS TRACER-TE7 MAE 0.020 #3 of 14 Archive leaderboard report
RGB Salient Object Detection HKU-IS TRACER-TE7 S-Measure 0.932 #3 of 14 Archive leaderboard report
RGB Salient Object Detection HKU-IS TRACER-TE7 mean F-Measure 0.934 #3 of 14 Archive leaderboard report
RGB Salient Object Detection HKU-IS TRACER-(ResNet50) MAE 0.028 #13 of 14 Archive leaderboard report
RGB Salient Object Detection PASCAL-S TRACER-TE7 F-measure 0.909 #4 of 13 Archive leaderboard report
RGB Salient Object Detection PASCAL-S TRACER-TE7 MAE 0.047 #4 of 13 Archive leaderboard report
RGB Salient Object Detection PASCAL-S TRACER-TE7 S-Measure 0.882 #4 of 13 Archive leaderboard report
RGB Salient Object Detection PASCAL-S TRACER-TE7 mean F-Measure 0.874 #4 of 13 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