-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Fix] Fix potential unexcepted behaviors if metric_options
is not specified in multi-label evaluation.
#647
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.
LGTM
@dreamer121121 Thanks for your contribution. Please sign the CLA and then we can merge your code. |
Codecov Report
@@ Coverage Diff @@
## dev #647 +/- ##
=======================================
Coverage 82.27% 82.27%
=======================================
Files 120 120
Lines 7045 7045
Branches 1228 1228
=======================================
Hits 5796 5796
Misses 1075 1075
Partials 174 174
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
metric_options
is not specified in multi-label evaluation.
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
…pecified in multi-label evaluation. (open-mmlab#647) * Update multi_label.py * Fix lint Co-authored-by: mzr1996 <mzr1996@163.com>
…pecified in multi-label evaluation. (open-mmlab#647) * Update multi_label.py * Fix lint Co-authored-by: mzr1996 <mzr1996@163.com>
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
muti-label test bug, default metric-options is {}.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:
After PR: