Home

Awesome

Proposal Distribution Calibration for Few-Shot Object Detection

<!-- <div align=center><img src="figs/Framework1.png"></div> --> <div align=center><img src="figs/Framework.png"></div> <!-- <div align=center><img src="figs/Framework3.png"></div> -->

Code of Proposal Distribution Calibration for Few-Shot Object Detection.

The code is based on mmdetection and imTED. Thanks a lot to these outstanding work. Please refer to get_started.md and MMDET_README.md to set up the environment and prepare the data.

Data Preparation

For few-shot experiments, please refer to FsDet for data preparation. Remember to modify the path of json in the configuration files, e.g. configs/imted/few_shot_pdc/imted_faster_rcnn_vit_base_2x_base_training_coco.py.

In run_train_pdc_few_shot.sh, you can get the relevant running commands about base training stage and finetune stage for coco dataset.

More detail about experiment for voc dataset and coco dataset will release soon.

Results on VOC Benchmark

MethodSplit-1Split-2Split-3
Shot123510123510123510
YOLO-ft6.610.712.524.838.612.54.211.616.133.913.015.915.032.238.4
FRCN-ft13.819.632.841.545.67.915.326.231.639.19.811.319.135.045.1
FSRW14.815.526.733.947.215.715.222.730.140.521.325.628.442.845.9
TFA39.836.144.755.756.023.526.934.135.139.130.834.842.849.549.8
MPSR41.7-51.455.261.824.4-39.239.947.835.6-42.348.049.7
CME41.547.550.458.260.927.230.241.442.546.834.339.645.148.351.5
FSCE44.243.851.461.963.427.329.543.544.250.237.241.947.554.658.5
imTED-S(Our Implement)43.451.058.167.666.623.226.939.444.252.749.948.856.461.461.1
imTED-S+PDC50.152.360.270.768.423.328.543.248.454.653.050.857.763.862.9
imTED-B(Our Implement)56.864.869.480.176.837.438.159.157.660.960.959.370.073.975.7
imTED-B+PDC61.869.170.278.779.642.941.260.056.365.960.363.170.673.376.7

Results on COCO Benchmark

MethodmAP<sup>novel</sup>
Shot1030
FRCN-ft6.511.1
FSRW5.69.1
MetaDet7.111.3
MetaR-CNN8.712.4
TFA10.013.7
MPSR9.814.1
imTED-S15.021.0
imTED-S+PDC15.722.1
imTED-B22.530.2
imTED-B+PDC23.430.8

If you have any questions with our code/paper, feel free to contact me through issue or e-mail.