Megvii-BaseDetection / Megvii-BaseDetection/BEVDepth
How to deal with camera pixels without lidar point?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 881
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
Thanks for your great work! Your work has been very inspiring to me!
I have a little confusion. For example, in the following figure, the camera pixel indicated by the arrow cannot match any lidar point. In this case, how to provide depth supervision? Another question is: if a camera pixel cannot match any lidar, how to get the "ground truth" in Table 1 in your paper "BEVDepth"?
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a source file, test, or entry point to inspect. First trace how camera pixels without matching lidar points are handled and how Table 1 ground truth is produced; the work is done when the repository or documentation clearly answers both questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, machine-learning
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100