Megvii-BaseDetection / Megvii-BaseDetection/BEVDepth
some a fews problem about compute depth details
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 881
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
self.depth_channels = int(
(self.dbound[1] - self.dbound[0]) / self.dbound[2])
- why is depth channels setting 'd_bound': [2.0, 58.0, 0.5] to compute channels is 112 ?
- https://github.com/Megvii-BaseDetection/BEVDepth/blob/main/exps/bev_depth_lss_r50_256x704_128x128_24e.py#L271 Why to multiply 3.0 depth_loss?
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
Start with the self.depth_channels calculation shown in the issue and the linked line 271 in exps/bev_depth_lss_r50_256x704_128x128_24e.py. Trace the d_bound values and depth-loss configuration, then document why they produce 112 channels and why the loss is multiplied by 3.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, machine-learning
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100