-
Notifications
You must be signed in to change notification settings - Fork 323
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
Intersection over Union Metric/Loss #469
Conversation
Codecov Report
@@ Coverage Diff @@
## master #469 +/- ##
==========================================
+ Coverage 80.52% 80.57% +0.04%
==========================================
Files 103 103
Lines 5710 5724 +14
==========================================
+ Hits 4598 4612 +14
Misses 1112 1112
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
But IoU and gIoU are available in torchvision. Thoughts? cc @akihironitta maybe we are reimplementing these in bolts to avoid dependency? |
The conversation regarding |
Hmm, not an issue then but we would need to test to match torchvision's implementation exactly. It can be nice to have drop-in replacement for consistency. Thoughts ? |
So IoU and GIoU in |
Oh yes, it returns Tensor[N, M] Yes, we can even test on same values as we did in torchvision. It would nice to demonstrate with docstring as well. Maybe just say
Like in torchvision |
Great suggestion @oke-aditya! How should I go about changing the description for gIoU? Do I create a separate PR? |
I'm Not sure about that. cc @akihironitta 😄 |
Since Bolts already (heavily?) depends on
@briankosw Let's improve the description of the loss in the docs. Could you work on this in another PR? |
I'll pause work on this PR then. I already updated the docs for IoU metric as @oke-aditya suggested, so what description should I improve? @akihironitta |
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.
@briankosw I left a suggestion. Would you mind considering it?
Right, let's wait for what other members have to say about #469 (comment). |
Also a small point, If we had to add say CIoU and DIoU (yeah IoUs are so many)
|
@akihironitta mind re-review? 🐰 |
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.
LGTM!
What does this PR do?
Implements IoU metric and IoU loss
Fixes #370. Related to #347 and #251.
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃