You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we want models to be customizable, we may want to allow users to see all generated boxes. Currently some are suppressed during prediction directly inside retinanet. Then more are suppressed in predict_tile for overlapping images. We want to document a way of turning all of these off. I have a suspicion that the nms settings are baked directly into the retinanet architecture and will be pretty specific. I have often noticed that the config["nms_thresh"] argument works best on the predict_tile methods and not the predict_image, meaning that the nms that is happening inside retinanet isn't being respected. I think the same is true for score_threshold arguments.
Document where NMS is being applied.
Show an example of turning off NMS for predict_tile
Show an example of turning off NMS for underling retinanet model for tree release. This may not relate to other architectures.
Its always hard to guess, but I think this issue will take some careful debugging, since its at the interface of deepforest and torchvision, and not wholly about DeepForest code.
The text was updated successfully, but these errors were encountered:
bw4sz
changed the title
How to completely turn off non-max-supression?
How to completely turn off non max suppression?
Feb 20, 2024
If we want models to be customizable, we may want to allow users to see all generated boxes. Currently some are suppressed during prediction directly inside retinanet. Then more are suppressed in predict_tile for overlapping images. We want to document a way of turning all of these off. I have a suspicion that the nms settings are baked directly into the retinanet architecture and will be pretty specific. I have often noticed that the config["nms_thresh"] argument works best on the predict_tile methods and not the predict_image, meaning that the nms that is happening inside retinanet isn't being respected. I think the same is true for score_threshold arguments.
Its always hard to guess, but I think this issue will take some careful debugging, since its at the interface of deepforest and torchvision, and not wholly about DeepForest code.
The text was updated successfully, but these errors were encountered: