Home

Awesome

RepPoints: Point Set Representation for Object Detection

By Ze Yang, Shaohui Liu, and Han Hu.

We provide code support and configuration files to reproduce the results in the paper for "RepPoints: Point Set Representation for Object Detection" on COCO object detection. Our code is based on mmdetection, which is a clean open-sourced project for benchmarking object detection methods.

Introduction

RepPoints, initially described in arXiv, is a new representation method for visual objects, on which visual understanding tasks are typically centered. Visual object representation, aiming at both geometric description and appearance feature extraction, is conventionally achieved by bounding box + RoIPool (RoIAlign). The bounding box representation is convenient to use; however, it provides only a rectangular localization of objects that lacks geometric precision and may consequently degrade feature quality. Our new representation, RepPoints, models objects by a point set instead of a bounding box, which learns to adaptively position themselves over an object in a manner that circumscribes the object’s spatial extent and enables semantically aligned feature extraction. This richer and more flexible representation maintains the convenience of bounding boxes while facilitating various visual understanding applications. This repo demonstrated the effectiveness of RepPoints for COCO object detection.

Another feature of this repo is the demonstration of an anchor-free detector, which can be as effective as state-of-the-art anchor-based detection methods. The anchor-free detector can utilize either bounding box or RepPoints as the basic object representation.

<div align="center"> <img src="demo/reppoints.png" width="400px" /> <p>Learning RepPoints in Object Detection.</p> </div>

Usage

a. Clone the repo:

git clone --recursive https://github.com/microsoft/RepPoints

b. Download the COCO detection dataset, copy RepPoints src into mmdetection and install mmdetection.

sh ./init.sh

c. Run experiments with a speicific configuration file:

./mmdetection/tools/dist_train.sh ${path-to-cfg-file} ${num_gpu} --validate

We give one example here:

./mmdetection/tools/dist_train.sh ./configs/reppoints_moment_r101_fpn_2x_mt.py 8 --validate

Citing RepPoints

@inproceedings{yang2019reppoints,
  title={RepPoints: Point Set Representation for Object Detection},
  author={Yang, Ze and Liu, Shaohui and Hu, Han and Wang, Liwei and Lin, Stephen},
  booktitle={The IEEE International Conference on Computer Vision (ICCV)},
  month={Oct},
  year={2019}
}

Results and models

The results on COCO 2017val are shown in the table below.

MethodBackboneAnchorconvert funcLr schdbox APDownload
BBoxR-50-FPNsingle-1x36.3model
BBoxR-50-FPNnone-1x37.3model
RepPointsR-50-FPNnonepartial MinMax1x38.1model
RepPointsR-50-FPNnoneMinMax1x38.2model
RepPointsR-50-FPNnonemoment1x38.2model
RepPointsR-50-FPNnonemoment2x38.6model
RepPointsR-50-FPNnonemoment2x (ms train)40.8model
RepPointsR-50-FPNnonemoment2x (ms train&ms test)42.2
RepPointsR-101-FPNnonemoment2x40.3model
RepPointsR-101-FPNnonemoment2x (ms train)42.3model
RepPointsR-101-FPNnonemoment2x (ms train&ms test)44.1
RepPointsR-101-FPN-DCNnonemoment2x43.0model
RepPointsR-101-FPN-DCNnonemoment2x (ms train)44.8model
RepPointsR-101-FPN-DCNnonemoment2x (ms train&ms test)46.4
RepPointsX-101-FPN-DCNnonemoment2x44.5model
RepPointsX-101-FPN-DCNnonemoment2x (ms train)45.6model
RepPointsX-101-FPN-DCNnonemoment2x (ms train&ms test)46.8

Notes:

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.