-
Notifications
You must be signed in to change notification settings - Fork 377
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
Using a single image as input and limiting the field of view of the point cloud (nuScenes) #570
Comments
I am also stuck trying to change configs so that I can do inference without lidar data (lidar failure), but I can give you a little input for the 2. question: I came across this from the transfusion paper: " We set the region-ofinterest (RoI) to [−54.0m, 54.0m] for X and Y axis, and Hope that helps a little |
Hi! I see that your issue is kinda new. When trying to train the nuscenes dataset you encountered an error "no specified protocol"? |
It appears while doing inference too, but thats not an error, just a info |
Hm i get it. Could you tell me did you do anything that is not in the instruction to make this work? |
Hello. I also wanted to use one image and about 60 degrees FOV this time, so I found it while looking for it. Could you please share what you have done about it? |
@J4nekT Have you been able to do it? |
First of all, I would like to thank you for publishing the code and for the great work. I don't have much experience with machine learning so I appreciate any help.
To adapt the pipeline to my system, I would like to make some changes to the input.
Firstly, I would like to use only one image as input instead of six. I would still like to use the nuscene data set, but only the front camera as input. What adjustments do I need to make and where?
Secondly, I would like to limit the point cloud to a FOV of 70 degrees. Do I have to adjust the point_cloud_range and/or the voxel_size? If further adjustments are necessary, please let me know.
Thank you in advance for your comments and suggestions.
The text was updated successfully, but these errors were encountered: