-
Notifications
You must be signed in to change notification settings - Fork 135
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
Support subset for KITTI 3D format #1621
Support subset for KITTI 3D format #1621
Conversation
95a8aff
to
2f49c3d
Compare
I have a quick question. Will it support "train", "val" and "test" folders right? What kind of structure is expected as input? |
|
Ok, I see. Thank you! I will prepare the same structure then. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## releases/1.10.0 #1621 +/- ##
==================================================
Coverage ? 81.12%
==================================================
Files ? 281
Lines ? 32773
Branches ? 6653
==================================================
Hits ? 26587
Misses ? 4723
Partials ? 1463
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
1c5256b
to
e2fa0b2
Compare
@wonjuleee , could you review? |
Hi @wonjuleee @sooahleex is there any reason not to support mmdet's kitty layout?
I think many people'd prefer to use mmdet's data preparation script |
@sovrasov I only considered the structure of the kitti dataset like kitti-3d-object-detection-dataset, and the use case for our product is limited to monocular 3D object detection. So I did not support point clouds from the lidar sensor or any additional information, but I fully agree with our opinion that the public prefers to use the kitti layout of mmdetection. I will consider supporting this structure in the next release. |
Summary
How to test
Checklist
License
Feel free to contact the maintainers if that's a concern.