-
Notifications
You must be signed in to change notification settings - Fork 159
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
Changing the grid size resulted in incorrect inference results #98
Comments
const float min_x_range = 0.0; const float pillar_x_size = 0.16; This is the point cloud range and pillar size provided by the author. Thank you very much for your answer |
I have the same problem. Have you finally resolved it? If it is resolved, could you please let me know where the problem is? |
1 similar comment
I have the same problem. Have you finally resolved it? If it is resolved, could you please let me know where the problem is? |
I won't modify the parameters of the model right now. Instead, I will crop the range of the point cloud in my own code and select the appropriate point cloud.
护玉者
***@***.***
…------------------ 原始邮件 ------------------
发件人: ***@***.***>;
发送时间: 2023年12月27日(星期三) 中午11:32
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [NVIDIA-AI-IOT/CUDA-PointPillars] Changing the grid size resulted in incorrect inference results (Issue #98)
I have the same problem. Have you finally resolved it? If it is resolved, could you please let me know where the problem is?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
好的,谢谢啦 |
Once I change the ratio of point cloud to pillar size, the inference results are completely inaccurate.
const int grid_x_size = (max_x_range - min_x_range) / pillar_x_size;
const int grid_y_size = (max_y_range - min_y_range) / pillar_y_size;
const int grid_z_size = (max_z_range - min_z_range) / pillar_z_size;
If my own grid size does not match the grid size provided by the CUDA pointpillar author, the reasoning is incorrect.
This issue has caused me to be unable to freely set the point cloud range and pillar size.
The text was updated successfully, but these errors were encountered: