Papers › Segmenting Transparent Objects in the Wild

Segmenting Transparent Objects in the Wild

31 Mar 2020ECCV 2020 8arXiv:2003.13948archive 2025-07-28

Enze Xie, Wenjia Wang, Wenhai Wang, Mingyu Ding, Chunhua Shen, Ping Luo

Transparent objects such as windows and bottles made by glass widely exist in the real world. Segmenting transparent objects is challenging because these objects have diverse appearance inherited from the image background, making them had similar appearance with their surroundings. Besides the technical difficulty of this task, only a few previous datasets were specially designed and collected to explore this task and most of the existing datasets have major drawbacks. They either possess limited sample size such as merely a thousand of images without manual annotations, or they generate all images by using computer graphics method (i.e. not real image). To address this important problem, this work proposes a large-scale dataset for transparent object segmentation, named Trans10K, consisting of 10,428 images of real scenarios with carefully manual annotations, which are 10 times larger than the existing datasets. The transparent objects in Trans10K are extremely challenging due to high diversity in scale, viewpoint and occlusion as shown in Fig. 1. To evaluate the effectiveness of Trans10K, we propose a novel boundary-aware segmentation method, termed TransLab, which exploits boundary as the clue to improve segmentation of transparent objects. Extensive experiments and ablation studies demonstrate the effectiveness of Trans10K and validate the practicality of learning object boundary in TransLab. For example, TransLab significantly outperforms 20 recent object segmentation methods based on deep learning, showing that this task is largely unsolved. We believe that both Trans10K and TransLab have important contributions to both the academia and industry, facilitating future researches and applications.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2003.13948")

Code

Syntology Ran 3 of 9 code samples harvested from 1 repository linked to this paper; 6 have no recorded run. Of those that ran: 1 ran · violated contract; 2 ran · fixture could not drive it.

By repository: official repository: 9 samples from 1 repository, 3 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

xieenze/Segment_Transparent_Objects officialmentioned in papermentioned on GitHubpytorchApache-2.0 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; 0 honoured the contract we drafted; 6 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

1ran · violated contract
2ran · fixture could not drive it
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 xieenze/Segment_Transparent_Objects. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

iou xieenze/Segment_Transparent_Objects/segmentron/solver/lovasz_losses.py official repository ran · fixture could not drive it fingerprinted Apache-2.0 (permissive) · d94639b28b2134ff · report
iou_binary xieenze/Segment_Transparent_Objects/segmentron/solver/lovasz_losses.py official repository ran · fixture could not drive it fingerprinted Apache-2.0 (permissive) · 1211530cd527bd0b · report
lovasz_grad xieenze/Segment_Transparent_Objects/segmentron/solver/lovasz_losses.py official repository ran · violated contract fingerprinted Apache-2.0 (permissive) · e85b5d21dc5b8382 · report
batch_ber xieenze/Segment_Transparent_Objects/segmentron/utils/score.py official repository unverified Apache-2.0 (permissive) · 33276fb60e28dceb · report
batch_mae xieenze/Segment_Transparent_Objects/segmentron/utils/score.py official repository unverified Apache-2.0 (permissive) · 8eae673295914188 · report
batch_pix_accuracy xieenze/Segment_Transparent_Objects/segmentron/utils/score.py official repository unverified Apache-2.0 (permissive) · a08d84c1264ca07e · report
get_norm xieenze/Segment_Transparent_Objects/segmentron/modules/batch_norm.py official repository unverified Apache-2.0 (permissive) · 7d6250302cdb769d · report
get_segmentation_loss xieenze/Segment_Transparent_Objects/segmentron/solver/loss.py official repository unverified Apache-2.0 (permissive) · 267edfcf2795234f · report
groupNorm xieenze/Segment_Transparent_Objects/segmentron/modules/batch_norm.py official repository unverified Apache-2.0 (permissive) · 644effb1fd52ef7d · report

Tasks

SegmentationSemantic SegmentationTransparent objects

Datasets

Introduced by this paper, per the archive.

Trans10K

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Semantic Segmentation Trans10K Trans2Lab GFLOPs 61.31 #4 of 15 Archive leaderboard report
Semantic Segmentation Trans10K Trans2Lab mIoU 69.00% #4 of 15 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