-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Feature] Panoptic segmentation metric #2230
Conversation
Please fix the lint |
I've fixed them. Please check. |
The code LGTM. Please pull the latest code which has fixed the lint about isort. @xizaoqu |
@sunjiahao1999 Please review this PR. |
Fix lint error. |
Codecov ReportBase: 46.39% // Head: 47.04% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## dev-1.x #2230 +/- ##
===========================================
+ Coverage 46.39% 47.04% +0.64%
===========================================
Files 259 261 +2
Lines 21401 21635 +234
Branches 3379 3417 +38
===========================================
+ Hits 9930 10178 +248
+ Misses 10827 10807 -20
- Partials 644 650 +6
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
last round, the overall LGTM |
I've fixed the problems. |
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
Add 3D panoptic segmentation metric for semanticKITTI.
Modification
Add 3D panoptic segmentation metric. NOTE: To verify the metric, this PR also includes the corresponding utils, but there are not merged into the repo yet.
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
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