From c142683e55b05e21b6f5b302105e45f133c77190 Mon Sep 17 00:00:00 2001 From: Luke Wood Date: Tue, 11 Apr 2023 02:20:04 -0400 Subject: [PATCH] Update NMS threshold based on anecdotal changes after sigmoid fix (#1702) 0.9 is too high Theres still no reasonable default, but lets try our best --- .../object_detection/multi_class_non_max_suppression.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/keras_cv/layers/object_detection/multi_class_non_max_suppression.py b/keras_cv/layers/object_detection/multi_class_non_max_suppression.py index 02b68f8307..e54399d980 100644 --- a/keras_cv/layers/object_detection/multi_class_non_max_suppression.py +++ b/keras_cv/layers/object_detection/multi_class_non_max_suppression.py @@ -33,7 +33,7 @@ class MultiClassNonMaxSuppression(keras.layers.Layer): IoU threshold for two boxes to be considered same for suppression. Defaults to 0.5. confidence_threshold: a float value in the range [0, 1]. All boxes with - confidence below this value will be discarded, defaults to 0.9. + confidence below this value will be discarded, defaults to 0.5. max_detections: the maximum detections to consider after nms is applied. A large number may trigger significant memory overhead, defaults to 100. max_detections_per_class: the maximum detections to consider per class @@ -45,7 +45,7 @@ def __init__( bounding_box_format, from_logits, iou_threshold=0.5, - confidence_threshold=0.9, + confidence_threshold=0.5, max_detections=100, max_detections_per_class=100, **kwargs,