Skip to content
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

why smoke predict box3d so good? #84

Open
Kerry678231 opened this issue Dec 21, 2022 · 3 comments
Open

why smoke predict box3d so good? #84

Kerry678231 opened this issue Dec 21, 2022 · 3 comments

Comments

@Kerry678231
Copy link

author, i want to ask a few questions
1、 pred_box3d_locs is from pred_depths_offset * depth_ref 、 pred_proj_offsets and K calculation
2、depth_ref is denormalization values, am i rights, how to get this values? it can also affect box3d accuracy?
3、pred_depths_offset have not target values, it calculate loss through pred_box3d, and pred_box3d's accuracy is depend pred_depths?
4、recently i write a net, just predict orientation of 3d, not box3d,Very much hope to give guidance and help
thanks a lot

@Kerry678231 Kerry678231 changed the title why use smoke predict box3d is good? why smoke predict box3d so good? Dec 22, 2022
@Kerry678231
Copy link
Author

i read paper about it,but i still have above question, please give me some guide, Thanks!

image

@HassanHotait
Copy link

image

@HassanHotait
Copy link

It's hard to predict absolute depth in meters with DNNs', instead it predicts a relative depth [unitless scalar], similar to normalized depth maps obtained from Stereo Vision, then this relative depth is converted to absolute depth in meters by computing an appropriate scale and offset.

In my opinion, this is the limitation of this algorithm, the scale and offset are calculated given the KITTI Official dataset. If you get the mean and std of the objects depth over the complete training dataset, you will get the values mentioned in the paper.

The algorithm uses a fixed scale and offset for all images, naturally this will not generalize to other scenarios with good enough accuracy.

Yes also these values affect the 3D and 2D Box location...

Anyone including the author or people who experimented with this could correct me if I'm wrong, this is my observation after a couple of months investigating SMOKE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants