tensorflow / tensorflow/models

Support for per-class NMS score thresholds.

Open
#9,429 0 comments 0 reactions 3 assignees View on GitHub

@pkulzc is already working on this.

Since Oct 29, 2020.

models:research:odapi type:feature
Dominant language
Python
Stars
77.7k
Forks
44.8k
PR merge metrics
No merged PRs in 30d

Description

Files

https://github.com/tensorflow/models/blob/master/research/object_detection/protos/post_processing.proto
https://github.com/tensorflow/models/blob/master/research/object_detection/export_tflite_ssd_graph.py
https://github.com/tensorflow/models/blob/master/research/object_detection/export_tflite_graph_tf2.py

Feature Request

Ability to specify a separate NMS score threshold for each class when exporting a model to TFlite.

Context

In multi-class detection tasks, the optimal score threshold may vary significantly between classes (i.e. one may require a threshold of 0.4 for stop signs and 0.6 for vehicles). Currently, post-processing (batch NMS) only allows the user to specify one universal threshold for all detections. This leaves the user with only 2 options: either compromise on overall accuracy, or to write & optimize code to handle per-class post-processsing.

Are you willing to contribute?

Yes (though may not have the expertise)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.