-
Notifications
You must be signed in to change notification settings - Fork 206
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
Different semantic results of suma++ #6
Comments
Hey, Thanks for using our code. It looks like a problem of the semantic segmentation part, and the SLAM part works. You could visualize the semantic segmentation results by checking the box of "Show semantic map" Several reasons may cause this problem.
|
This comment has been minimized.
This comment has been minimized.
The problem should come from the rangenet_lib, since the semantic segmentation input of SuMa++ is not correct. Have you already tried the example demo of rangenet_lib? The semantic segmentation result visualized in the "Show semantic map" should be the same as that of rangenet_lib. You may test and make sure the rangnet_lib works first. If the example demo of rangenet_lib works well, SuMa++ should also work, and vice versa. |
This comment has been minimized.
This comment has been minimized.
Hi @TT22TY, |
Hi @TT22TY The problem seems caused by the incompatibility of our code with TensorRT version 6. For more details please find here: PRBonn/rangenet_lib#9. |
This comment has been minimized.
This comment has been minimized.
Hi @TT22TY , I've listed the tested setups in PRBonn/rangenet_lib#9. To keep this issue in one track, I am going to close this one again. |
Hi, |
Hello,
Thanks for your work! After I build the suma++, I just obtain the result like this, I use the pretrained model provided on the webpage, however, it seems that the semantic result is quite different from the picture you provided. I am wondering why it happened( Is it due to the pretrained model used?). I try to use the trained model which is trained from scratch by myself, it works well using the infer.py of RangeNet++, the result is also strange. Besides, the result of RangeLib are also different from the picture you provided.
Looking forward to your reply. :) Thanks!
The text was updated successfully, but these errors were encountered: