-
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] Support PolarMix
augmentation
#2265
Conversation
Codecov ReportBase: 47.09% // Head: 46.96% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## dev-1.x #2265 +/- ##
===========================================
- Coverage 47.09% 46.96% -0.14%
===========================================
Files 261 262 +1
Lines 21679 21964 +285
Branches 3425 3460 +35
===========================================
+ Hits 10210 10315 +105
- Misses 10816 10987 +171
- Partials 653 662 +9
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. |
f8780dd
to
34ad2a9
Compare
1e67cee
to
07cdbc1
Compare
f55feac
to
51c5b85
Compare
* support polarmix * Update __init__.py * add UT * use `BasePoints` instead of numpy * Update transforms_3d.py * Update transforms_3d.py * Update test_transforms_3d.py * update docs * update polarmix without MultiImageMixDataset * add comments * fix UT * update docstring * fix yaw calculation * fix UT * refactor * update * update docs * fix typo * Update transforms_3d.py * update ut * fix typehint * add prob argument
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
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