[Feature] Refactor Waymo dataset_converter/dataset/evaluator#2836
[Feature] Refactor Waymo dataset_converter/dataset/evaluator#2836Tai-Wang merged 5 commits intoopen-mmlab:dev-1.xfrom
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2836 +/- ##
==========================================
+ Coverage 46.70% 47.24% +0.53%
==========================================
Files 277 277
Lines 23635 23417 -218
Branches 3704 3658 -46
==========================================
+ Hits 11039 11063 +24
+ Misses 11892 11640 -252
- Partials 704 714 +10
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Tai-Wang
left a comment
There was a problem hiding this comment.
Please also update the dataset and compatibility documentation
mmdet3d/evaluation/functional/waymo_utils/prediction_to_waymo.py
Outdated
Show resolved
Hide resolved
|
sjh seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
| - info\['instances'\]: It is a list of dict. Each dict contains all annotation information of single instance. For the i-th instance: | ||
| - info\['instances'\]\[i\]\['bbox_3d'\]: List of 7 numbers representing the 3D bounding box of the instance, in (x, y, z, l, w, h, yaw) order. | ||
| - info\['instances'\]\[i\]\['bbox'\]: List of 4 numbers representing the 2D bounding box of the instance, in (x1, y1, x2, y2) order. (some instances may not have a corresponding 2D bounding box) | ||
| - info\['instances'\]\[i\]\['bbox_label_3d'\]: A int indicate the label of instance and the -1 indicate ignore. |
There was a problem hiding this comment.
An int indicating the label of instance and the -1 indicating ignore.
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
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
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