doc

Author: pliablepixels

mlapiconfig.ini

@@ -76,13 +76,29 @@ model_sequence=object,face,alpr
 # was detected by ZM. Default no
 #only_triggered_zm_zones=no
 
-
-# If specified, will limit detected object size to this amount of
-# the total image size passed. Can help avoiding weird detections
-# You can specify as % or px. Default is px
-# Remember the image is resized to 416x416 internally. better
-# to keep in %
-max_detection_size=70%
+# if yes, last detection will be stored for monitors
+# and bounding boxes that match, along with labels
+# will be discarded for new detections. This may be helpful
+# in getting rid of static objects that get detected
+# due to some motion. 
+match_past_detections=no
+
+# The max difference in area between the objects if match_past_detection is on
+# can also be specified in px like 300px. Default is 5%. Basically, bounding boxes of the same
+# object can slightly differ ever so slightly between detection. Contributor @neillbell put in this PR
+# to calculate the difference in areas and based on his tests, 5% worked well. YMMV. Change it if needed.
+# Note: You can specify label/object specific max_diff_areas as well. If present, they override this value
+# example: 
+# person_past_det_max_diff_area=5%
+# car_past_det_max_diff_area=5000px
+past_det_max_diff_area=5%
+
+# this is the maximum size a detected object can have. You can specify it in px or % just like past_det_max_diff_area 
+# This is pretty useful to eliminate bogus detection. In my case, depending on shadows and other lighting conditions, 
+# I sometimes see "car" or "person" detected that covers most of my driveway view. That is practically impossible 
+# and therefore I set mine to 70% because I know any valid detected objected cannot be larger than that area
+
+max_detection_size=90%
 
 # config for object
 [object]