-
Notifications
You must be signed in to change notification settings - Fork 411
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
Better support for classwise logging #832
Conversation
Codecov Report
@@ Coverage Diff @@
## master #832 +/- ##
=====================================
- Coverage 95% 95% -0%
=====================================
Files 166 167 +1
Lines 6864 6896 +32
=====================================
+ Hits 6522 6552 +30
- Misses 342 344 +2 |
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.
Thank is soo COOL!!!
Co-authored-by: Jirka Borovec <[email protected]>
"""Test wrapper in combination with metric collection.""" | ||
labels = ["horse", "fish", "cat"] | ||
metric = MetricCollection( | ||
{ |
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.
but here it won't share states, right?
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.
You are right. That is common problem for all the wrappers because we assume that states are not nested when trying to figure out the compute groups.
I can try to come up with a general solution for this problem
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.
Can we maybe have a property that kind of forwards the states of the wrapped metrics?
What does this PR do?
Fixes #815
Implement a
ClasswiseWrapper
that makes it easier to log classification metrics that return multiple values.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 🙃