Papers › Path Aggregation Network for Instance Segmentation

Path Aggregation Network for Instance Segmentation

5 Mar 2018CVPR 2018 6arXiv:1803.01534archive 2025-07-28

Shu Liu, Lu Qi, Haifang Qin, Jianping Shi, Jiaya Jia

The way that information propagates in neural networks is of great importance. In this paper, we propose Path Aggregation Network (PANet) aiming at boosting information flow in proposal-based instance segmentation framework. Specifically, we enhance the entire feature hierarchy with accurate localization signals in lower layers by bottom-up path augmentation, which shortens the information path between lower layers and topmost feature. We present adaptive feature pooling, which links feature grid and all feature levels to make useful information in each feature level propagate directly to following proposal subnetworks. A complementary branch capturing different views for each proposal is created to further improve mask prediction. These improvements are simple to implement, with subtle extra computational overhead. Our PANet reaches the 1st place in the COCO 2017 Challenge Instance Segmentation task and the 2nd place in Object Detection task without large-batch training. It is also state-of-the-art on MVD and Cityscapes. Code is available at https://github.com/ShuLiu1993/PANet

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 4 code samples: 3 from 1 repository linked to this paper, 1 identical to code harvested from another paper's repository. Across all 4: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 3 samples from 1 repository, 2 ran (1 with no instrument failure; 1 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 5 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

ShuLiu1993/PANet officialmentioned in papermentioned on GitHubpytorchMITSyntology: 3 samples, 2 ran (1 instrument-failed) · 1 unverified report
CVUsers/Smart-Retail-By-Efficientdet mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Feature Pyramid Networks for Object Detection (arXiv:1612.03144; that paper's own run record: 33 ran (of which 9 constructed an object rather than computing a result; 28 with no instrument failure: 4 honoured, 0 violated, 24 with no contract checked; 5 where Syntology's instrument failed) · 18 unverified); nothing checks that they implement this paper's method. report
YuefeiZ/PANet mentioned on GitHubtfGPL-3.0Syntology: not harvested report
texasinstruments/edgeai-yolov5 mentioned on GitHubpytorchGPL-3.0Syntology: not harvested report
texasinstruments/edgeai-yolox mentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
ultralytics/yolov5 mentioned on GitHubpytorchAGPL-3.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Deep Residual Learning for Image Recognition (arXiv:1512.03385; that paper's own run record: 254 ran (of which 108 constructed an object rather than computing a result; 163 with no instrument failure: 3 honoured, 1 violated, 159 with no contract checked; 91 where Syntology's instrument failed) · 123 unverified); nothing checks that they implement this paper's method. report
wslerry/yolov5 mentioned on GitHubpytorchGPL-3.0Syntology: not harvested report
PaddlePaddle/PaddleDetection paddleSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to PP-YOLOE: An evolved version of YOLO (arXiv:2203.16250; that paper's own run record: 22 ran (of which 0 constructed an object rather than computing a result; 19 with no instrument failure: 2 honoured, 0 violated, 17 with no contract checked; 3 where Syntology's instrument failed) · 5 unverified); nothing checks that they implement this paper's method. report
mindspore-ai/models mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to AdaBin: Improving Binary Neural Networks with Adaptive Binary Sets (arXiv:2208.08084; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
open-mmlab/mmdetection pytorchApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to An Open and Comprehensive Pipeline for Unified Object Grounding and Detection (arXiv:2401.02361; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

4 samples harvested: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
1ran; the contract check could not run
1ran
1unverified

Licence: 2 of the 4 samples are pointer only, meaning Syntology does not serve that copy's text. For 1 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from ShuLiu1993/PANet. 1 sample is listed last, in a group without a repository. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

ShuLiu1993/PANet official repository 3 samples, 2 ran (1 instrument-failed) · 1 unverified
parse_rec in 26 papers lib/datasets/voc_eval.py ran MIT (permissive) · 06e62194f17cd06a · report fixture: signature filename:str/0/str · returned list · level recorded 2026-09-25
voc_ap in 44 papers
census: 5 implementations from 10 papers, 2 distinct outputs on one shared input
lib/datasets/voc_eval.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) here; the stored copy is pointer only · 611c47c44c424dba · report fixture: signature rec:ndarray/1/float, prec:ndarray/1/float, use_07_metric:bool/0/bool · returned float64 · level recorded 2026-09-25
voc_eval in 19 papers lib/datasets/voc_eval.py unverified MIT (permissive) · 7177fe851c20e20e · report
Repository not located 1 sample, 1 ran (1 instrument-failed) · 0 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
compute_backbone_shapes in 12 papers repository not located ran · our draft was wrong licence of this copy not recorded · ae91aee49740c295 · report fixture: signature config:StandInConfig/0/?, image_shape:tuple/1/int · returned ndarray · level recorded 2026-09-22

Tasks

Instance SegmentationObject DetectionSegmentationSemantic Segmentationobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Instance Segmentation COCO minival PANet (ResNet-50) mask AP 37.8 #83 of 93 Archive leaderboard report
Instance Segmentation COCO test-dev PANet mask AP 42.0 #56 of 112 Archive leaderboard report
Instance Segmentation iSAID PANet Average Precision 34.17 #5 of 5 Archive leaderboard report
Object Detection COCO test-dev PANet (ResNeXt-101, multi-scale) AP50 67.2 #118 of 225 Archive leaderboard report
Object Detection COCO test-dev PANet (ResNeXt-101, multi-scale) AP75 51.8 #118 of 225 Archive leaderboard report
Object Detection COCO test-dev PANet (ResNeXt-101, multi-scale) APL 60.0 #118 of 225 Archive leaderboard report
Object Detection COCO test-dev PANet (ResNeXt-101, multi-scale) APM 51.7 #118 of 225 Archive leaderboard report
Object Detection COCO test-dev PANet (ResNeXt-101, multi-scale) APS 30.1 #118 of 225 Archive leaderboard report
Object Detection COCO test-dev PANet (ResNeXt-101, multi-scale) box mAP 47.4 #118 of 225 Archive leaderboard report
Object Detection iSAID PANet Average Precision 41.66 #3 of 5 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.

Methods

Introduced by this paper: Adaptive Feature Pooling, PAFPN, PANet

1x1 ConvolutionAdaptive Feature PoolingAverage PoolingBatch NormalizationBottleneck Residual BlockBottom-up Path AugmentationConvolutionDense ConnectionsFPNGlobal Average PoolingGrouped ConvolutionKaiming InitializationMax PoolingPAFPNPANetRPNReLUResNeXtResNeXt BlockResidual BlockResidual ConnectionRoIAlignSGD with MomentumWeight Decay

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