-
Notifications
You must be signed in to change notification settings - Fork 241
Issues: NVIDIA-AI-IOT/Lidar_AI_Solution
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
When kernel_size = (1,1,1) for SparseConv3d, the onnx inference result is different from the torch
#302
opened Dec 18, 2024 by
Icecream-blue-sky
use myself camera ,lidar calibration parameters and data, use public models,can use cuda-bevfusion?
#301
opened Dec 17, 2024 by
sen9910
How to get 80 in geometry.geometry_dim = nvtype::Int3(360, 360, 80)?
#298
opened Dec 11, 2024 by
Jayden9912
the sparse convolution to onnx inference output does not match the torch output
#297
opened Nov 25, 2024 by
Xiao-Hu-Z
Why does Building CUDA_BEVFusion asks for libcublas.so.12, and not 11?
#293
opened Nov 1, 2024 by
Tony-syr
I have one former camera and lidar, which model should I choose
#292
opened Oct 31, 2024 by
Zhao-Qihao
What version of protobuf has been used to build CUDA_BEVfusion ?
#291
opened Oct 17, 2024 by
Tony-syr
AttributeError: 'torch._C.TensorType' object has no attribute 'with_sizes'
#290
opened Oct 16, 2024 by
Gj-master
why not use TensorRT for LidarBackbone model in CUDA-BEVFusion?
#285
opened Sep 26, 2024 by
fsi-kawatawa
CUDA-BEVFusion: difference in the result of onnx and pytorch model
#283
opened Sep 12, 2024 by
Jayden9912
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.