[Enhance] Format semantickitti label mapping#2323
[Enhance] Format semantickitti label mapping#2323ZwwWayne merged 17 commits intoopen-mmlab:dev-1.xfrom
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## dev-1.x #2323 +/- ##
===========================================
+ Coverage 46.86% 46.88% +0.01%
===========================================
Files 264 264
Lines 22173 22175 +2
Branches 3482 3482
===========================================
+ Hits 10392 10396 +4
+ Misses 11118 11116 -2
Partials 663 663
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 1 file with indirect coverage changes 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 in Codecov by Sentry. |
| @@ -2,13 +2,11 @@ | |||
| dataset_type = 'SemanticKITTIDataset' | |||
There was a problem hiding this comment.
Should we rename this file to semantickitti-seg.py?
There was a problem hiding this comment.
I think semantickitti already indicates that is the semantic version of the kitti dataset.
There was a problem hiding this comment.
but we should repalce SemanticKITTIDataset with SemanticKittiDataset
| @@ -2,13 +2,11 @@ | |||
| dataset_type = 'SemanticKITTIDataset' | |||
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
Format semantickitti label mapping and fix some loading bug.
Modification
Please briefly describe what modification is made in this PR.
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