Papers › Towards Real-World Prohibited Item Detection: A Large-Scale X-ray Benchmark

Towards Real-World Prohibited Item Detection: A Large-Scale X-ray Benchmark

16 Aug 2021ICCV 2021 10arXiv:2108.07020archive 2025-07-28

Boying Wang, Libo Zhang, Longyin Wen, Xianglong Liu, Yanjun Wu

Automatic security inspection using computer vision technology is a challenging task in real-world scenarios due to various factors, including intra-class variance, class imbalance, and occlusion. Most of the previous methods rarely solve the cases that the prohibited items are deliberately hidden in messy objects due to the lack of large-scale datasets, restricted their applications in real-world scenarios. Towards real-world prohibited item detection, we collect a large-scale dataset, named as PIDray, which covers various cases in real-world scenarios for prohibited item detection, especially for deliberately hidden items. With an intensive amount of effort, our dataset contains 12 categories of prohibited items in 47,677 X-ray images with high-quality annotated segmentation masks and bounding boxes. To the best of our knowledge, it is the largest prohibited items detection dataset to date. Meanwhile, we design the selective dense attention network (SDANet) to construct a strong baseline, which consists of the dense attention module and the dependency refinement module. The dense attention module formed by the spatial and channel-wise dense attentions, is designed to learn the discriminative features to boost the performance. The dependency refinement module is used to exploit the dependencies of multi-scale features. Extensive experiments conducted on the collected PIDray dataset demonstrate that the proposed method performs favorably against the state-of-the-art methods, especially for detecting the deliberately hidden items.

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: 3 ran (of which 0 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) · 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: 9 samples from 1 repository, 3 ran (3 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-25 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

bywang2018/security-dataset officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 9 samples, 3 ran (0 instrument-failed) · 6 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: 3 ran (of which 0 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) · 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.

3ran
6unverified

Licence: 0 of the 9 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 bywang2018/security-dataset. “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.

bywang2018/security-dataset official repository 9 samples, 3 ran (0 instrument-failed) · 6 unverified
ga_loc_target in 5 papers mmdet/core/anchor/guided_anchor_target.py ran Apache-2.0 (permissive) · 2440313353f0c835 · report fixture: signature gt_bboxes_list:list/1/Tensor, featmap_sizes:list/1/tuple, anchor_scale:int/0/int, anchor_strides:list/1/int, center_ratio:float/0/float, ignore_ratio:float/0/float · returned tuple · level recorded 2026-09-25
images_to_levels in 11 papers mmdet/core/anchor/anchor_target.py ran Apache-2.0 (permissive) · 8fa249eba3a0ce57 · report fixture: returned list · level recorded 2026-09-26
images_to_levels in 11 papers mmdet/core/anchor/point_target.py ran Apache-2.0 (permissive) · 99bbbfc95abdc86a · report fixture: signature target:list/1/Tensor, num_level_grids:list/1/int · returned list · level recorded 2026-09-25
anchor_target in 6 papers mmdet/core/anchor/anchor_target.py unverified Apache-2.0 (permissive) · 6a7ed994a87db611 · report
anchor_target_single in 7 papers mmdet/core/anchor/anchor_target.py unverified Apache-2.0 (permissive) · 1dd00ccb42e850dc · report
calc_region in 8 papers mmdet/core/anchor/guided_anchor_target.py unverified Apache-2.0 (permissive) · 736c7ce8a0faa02a · report
ga_shape_target in 5 papers mmdet/core/anchor/guided_anchor_target.py unverified Apache-2.0 (permissive) · e3463fa8772a18a9 · report
point_target in 5 papers mmdet/core/anchor/point_target.py unverified Apache-2.0 (permissive) · a08ee98e88ad24e7 · report
point_target_single in 5 papers mmdet/core/anchor/point_target.py unverified Apache-2.0 (permissive) · b660461f38b4382b · report

Datasets

Introduced by this paper, per the archive.

PIDray

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