-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Frontend][TFLite] fix detection_postprocess's non_max_suppression_attrs["force_suppress"] #12593
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix @czh978.
Do you mind providing some context on why force_supress
needs to be set this way? Can you give one example of something that wasn't working before this change, and works after the change?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any publicly available network that we can observe this behaviour and create a test case?
b5f7a47
to
90b0c88
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding a test case @czh978. I'm happy for this to be merged once CI is green.
The last thing we need is for the PR description to be improved with a description of your findings that as use_regular_nms
is set as False
in TVM, we need to have force_supress
to be True
, to avoid all detections to be suppressed.
Please expand that with the reasoning why this change is needed and point out that it reproduces on networks like ssd_mobilenet_v2 and other examples if you know any.
…rs["force_suppress"] Since tvm only supports operators detection_postprocess use_regular_nms is false, which will suppress boxes that exceed the threshold regardless of the class when implementing NMS in tflite, in order for the results of tvm and tflite to be consistent, we need to set force_suppress to True.
…rs[force_suppress] Added a test case that reproduces inconsistent results between tvm and tflite When the force_suppress is false,it will get a good result if you set the force_suppress as true
I've modified the commit message to meet the requirements of the new RFC, could you review it if you're available?Thanks. |
…trs["force_suppress"] (apache#12593) * [Frontend][TFLite]fix detection_postprocess's non_max_suppression_attrs["force_suppress"] Since tvm only supports operators detection_postprocess use_regular_nms is false, which will suppress boxes that exceed the threshold regardless of the class when implementing NMS in tflite, in order for the results of tvm and tflite to be consistent, we need to set force_suppress to True. * [Frontend][TFLite]fix detection_postprocess's non_max_suppression_attrs[force_suppress] Added a test case that reproduces inconsistent results between tvm and tflite When the force_suppress is false,it will get a good result if you set the force_suppress as true
I found the value should be "True"