Browse State-of-the-Art › Amodal Instance Segmentation
Amodal Instance Segmentation
15 papers with code · 1 benchmark · 2 datasets archive 2025-07-28
Amodal instance segmentation aims to predict the region encompassing both visible and occluded parts of each object.
Description Credit: Amodal Instance Segmentation, ECCV 2016
Description from the archive archive 2025-07-28.
Benchmarks archive 2025-07-28
1 leaderboard table shown for this task, 1 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| WALT (2 rows) | WALTNET | WALT: Watch and Learn 2D Amodal Representation From Time-Lapse Imagery | code | — | Compare |
Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Libraries
Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.
Datasets archive 2025-07-28
2 datasets whose archive record lists this task, ordered by the archive's paper count.
Subtasks archive 2025-07-28
No subtask under this task in the archive's task tree.
Parent tasks archive 2025-07-28
Papers archive 2025-07-28
archive papers tagged: 24 · with a code link: 15 · where Syntology ran a sample: 3 (3 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (3 of 24 tagged: 3 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Page 1 of 1: papers 1 to 24 of 24, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.
Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.
-
24 Apr 2018 2 repositories listed Syntology 12 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 7 where Syntology's instrument failed) · 5 unverified (of 17 harvested samples) · 10 pointer-only (licence)Semantic amodal segmentation is a recently proposed extension to instance-aware segmentation that includes the prediction of the invisible region of each object instance.
-
21 Sep 2024 1 repository listedThis way, while basing our method on an amodal instance segmentation, we nevertheless obtain video-level amodal instance segmentation results.
-
18 Mar 2024 1 repository listedConsequently, this compromised quality of visible features during the subsequent visible-to-amodal transition.
-
16 Jan 2024 1 repository listedHowever, based on ``segmentation within bounding box'' paradigm, current instance segmentation methods using OBBs are overly dependent on bounding box detection performance.
-
14 Jul 2023 1 repository listedIn this work, we present SynTable, a unified and flexible Python-based dataset generator built using NVIDIA's Isaac Sim Replicator Composer for generating high-quality synthetic datasets for unseen object amodal…
-
12 Mar 2023 1 repository listedImages of realistic scenes often contain intra-class objects that are heavily occluded from each other, making the amodal perception task that requires parsing the occluded parts of the objects challenging.
-
12 Oct 2022 1 repository listedAISFormer explicitly models the complex coherence between occluder, visible, amodal, and invisible masks within an object's regions of interest by treating them as learnable queries.
-
1 Jan 2022 1 repository listedLabeled real data of occlusions is scarce (even in large datasets) and synthetic data leaves a domain gap, making it hard to explicitly model and learn occlusions.
-
23 Sep 2021 1 repository listedInstance-aware segmentation of unseen objects is essential for a robotic system in an unstructured environment.
-
23 Aug 2021 1 repository listedThe resulting predictions on training images are taken as the pseudo-ground truth for the standard training of Mask-RCNN, which we use for amodal instance segmentation of test images.
-
23 Mar 2021 1 repository listed Syntology official (archive's flag): 9 ran · 9 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 0 violated, 3 with no contract checked; 5 where Syntology's instrument failed) · 3 unverified (of 12 harvested samples) · 5 pointer-only (licence)Segmenting highly-overlapping objects is challenging, because typically no distinction is made between real object contours and occlusion boundaries.
-
Amodal Segmentation through Out-of-Task and Out-of-Distribution Generalization with a Bayesian Model25 Oct 2020 1 repository listed Syntology official (archive's flag): 1 ran · 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified (of 2 harvested samples)Moreover, by leveraging an outlier process, Bayesian models can further generalize out-of-distribution to segment partially occluded objects and to predict their amodal object boundaries.
-
14 Feb 2020 1 repository listedThe proposed method extends upon the representational output of semantic instance segmentation by explicitly including both visible and occluded parts.
-
1 Jun 2019 1 repository listedWe propose the network structure to reason invisible parts via a new multi-task framework with Multi-View Coding (MVC), which combines information in various recognition levels.
-
30 May 2019 1 repository listedSpecifically, we first introduce a new representation, namely a semantics-aware distance map (sem-dist map), to serve as our target for amodal segmentation instead of the commonly used masks and heatmaps.
-
Segment Anything, Even Occluded8 Mar 2025 0 repositories listedAmodal instance segmentation, which aims to detect and segment both visible and invisible parts of objects in images, plays a crucial role in various applications including autonomous driving, robotic manipulation, and…
-
Amodal Instance Segmentation with Diffusion Shape Prior Estimation26 Sep 2024 0 repositories listedAmodal Instance Segmentation (AIS) presents an intriguing challenge, including the segmentation prediction of both visible and occluded parts of objects within images.
-
BLADE: Box-Level Supervised Amodal Segmentation through Directed Expansion3 Jan 2024 0 repositories listedPerceiving the complete shape of occluded objects is essential for human and machine intelligence.
-
GIN: Generative INvariant Shape Prior for Amodal Instance Segmentation22 Sep 2023 0 repositories listedAmodal instance segmentation (AIS) predicts the complete shape of the occluded object, including both visible and occluded regions.
-
OAFormer: Learning Occlusion Distinguishable Feature for Amodal Instance Segmentation4 Jun 2023 0 repositories listedThe Amodal Instance Segmentation (AIS) task aims to infer the complete mask of occluded instance.
-
MUVA: A New Large-Scale Benchmark for Multi-View Amodal Instance Segmentation in the Shopping Scenario1 Jan 2023 0 repositories listedAmodal Instance Segmentation (AIS) endeavors to accurately deduce complete object shapes that are partially or fully occluded.
-
2D Amodal Instance Segmentation Guided by 3D Shape Prior1 Jun 2022 0 repositories listedAmodal instance segmentation aims to predict the complete mask of the occluded instance, including both visible and invisible regions.
-
Learning Vector Quantized Shape Code for Amodal Blastomere Instance Segmentation2 Dec 2020 0 repositories listedBlastomere instance segmentation is important for analyzing embryos' abnormality.
-
Amodal Instance Segmentation27 Apr 2016 0 repositories listedWe consider the problem of amodal instance segmentation, the objective of which is to predict the region encompassing both visible and occluded parts of each object.
Syntology lines on 3 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
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