-
Notifications
You must be signed in to change notification settings - Fork 423
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
Refactor panoptic quality #1596
Refactor panoptic quality #1596
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #1596 +/- ##
========================================
- Coverage 88% 38% -51%
========================================
Files 225 226 +1
Lines 11938 11952 +14
========================================
- Hits 10555 4510 -6045
- Misses 1383 7442 +6059 |
Not sure how to interpret the codecov failure, the PR doesn't add any "new" code. Is it a CI glitch? Should I do something about it? |
let's just stay with this one commit pls 🦦 |
it is a sanity check that the new code is covered, but it also has some false negative alarms when the coverage change is almost zero... |
What does this PR do?
Preparation work for #1591: breaks apart the big messy update() function, and moves all the helper functions to a new
src/torchmetrics/functional/detection/_panoptic_quality_common.py
file.To make the review a lot simpler, the PR contains 2 commits: I suggest to look at the first commit 7cbf54b which contains all the new code and it can be
diff
'd againstmaster
, whereas the 2nd commit d873aab is doing nothing else than moving code around (edit, there'll be a 3rd because I initially borked the type annotations and found out that mypy doesn't run on pre-commit).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 🙃