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

terminate when running SurfelMap.cpp #19

Closed
qiaozhijian opened this issue Nov 25, 2019 · 8 comments
Closed

terminate when running SurfelMap.cpp #19

qiaozhijian opened this issue Nov 25, 2019 · 8 comments

Comments

@qiaozhijian
Copy link

qiaozhijian commented Nov 25, 2019

Hi, Could you help me with this problem? Thank you very much!
I run this command
./bin/visualizer ./SuMa/config/default.xml
Terminal output is following :

OpenGL Context Version 3.3 core profile
GLEW initialized.
OpenGL context version: 3.3
OpenGL vendor string : VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits)
Extracting surfel maps partially.
OpenGL Error: invalid enumerant(1280)
In: /home/Mine/slam/code/catkin_suma/src/SuMa/src/core/SurfelMap.cpp on Line: 298
terminate called after throwing an instance of 'std::runtime_error'
what(): OpenGL error detected.

@qiaozhijian qiaozhijian changed the title OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) terminate when running SurfelMap.cpp Nov 25, 2019
@jbehley
Copy link
Owner

jbehley commented Dec 6, 2019

Hi @qiaozhijian,

sorry for the delay, but I was quite busy with some other stuff.

I would suggest that you run the code without a virtual machine with a real graphics driver. I don't know if the VMWare OpenGL implementation supports all operations needed by our code. It might be that I used some operation that is not strictly supported by OpenGL 3.3 Core Profile. Therefore, I would suggest that you have a real NVIDIA or AMD or Intel GPU driver, since they usally support at least OpenGL 4.0 and usally also more then the Core Profile asks for.

@qiaozhijian
Copy link
Author

Hi @qiaozhijian,

sorry for the delay, but I was quite busy with some other stuff.

I would suggest that you run the code without a virtual machine with a real graphics driver. I don't know if the VMWare OpenGL implementation supports all operations needed by our code. It might be that I used some operation that is not strictly supported by OpenGL 3.3 Core Profile. Therefore, I would suggest that you have a real NVIDIA or AMD or Intel GPU driver, since they usally support at least OpenGL 4.0 and usally also more then the Core Profile asks for.

Thank you. But I don't know why it outputs "OpenGL vendor string : VMware, Inc." while my device is equipped with GTX1070. I will try to work it out again. Maybe there are some problems in my Ubuntu.

@qiaozhijian
Copy link
Author

Hi @qiaozhijian,

sorry for the delay, but I was quite busy with some other stuff.

I would suggest that you run the code without a virtual machine with a real graphics driver. I don't know if the VMWare OpenGL implementation supports all operations needed by our code. It might be that I used some operation that is not strictly supported by OpenGL 3.3 Core Profile. Therefore, I would suggest that you have a real NVIDIA or AMD or Intel GPU driver, since they usally support at least OpenGL 4.0 and usally also more then the Core Profile asks for.

I have solved the problem by reinstall nvidia-drive. Thank you!
But the new problem ocurrs when I open a ".bin" file

OpenGL Context Version 4.6 core profile
GLEW initialized.
OpenGL context version: 4.6
OpenGL vendor string : NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1070/PCIe/SSE2
Extracting surfel maps partially.
Performing frame-to-model matching.
Gtk-Message: 21:24:21.687: GtkDialog mapped without a transient parent. This is discouraged.
calibration filename: /media/qzj/Document/grow/slam/slamDataSet/kitti/data_odometry_velodyne/dataset/00/calib.txt...段错误 (核心已转储)

@qiaozhijian qiaozhijian reopened this Dec 6, 2019
@jbehley
Copy link
Owner

jbehley commented Dec 6, 2019 via email

@qiaozhijian
Copy link
Author

You need to download the extra calibration files containing a line starting withTr that is available as extra download on the odometry benchmark website.

OK, thank you~!

@tym2103
Copy link

tym2103 commented Jun 9, 2020

Hi @qiaozhijian,
sorry for the delay, but I was quite busy with some other stuff.
I would suggest that you run the code without a virtual machine with a real graphics driver. I don't know if the VMWare OpenGL implementation supports all operations needed by our code. It might be that I used some operation that is not strictly supported by OpenGL 3.3 Core Profile. Therefore, I would suggest that you have a real NVIDIA or AMD or Intel GPU driver, since they usally support at least OpenGL 4.0 and usally also more then the Core Profile asks for.

I have solved the problem by reinstall nvidia-drive. Thank you!
But the new problem ocurrs when I open a ".bin" file

OpenGL Context Version 4.6 core profile
GLEW initialized.
OpenGL context version: 4.6
OpenGL vendor string : NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1070/PCIe/SSE2
Extracting surfel maps partially.
Performing frame-to-model matching.
Gtk-Message: 21:24:21.687: GtkDialog mapped without a transient parent. This is discouraged.
calibration filename: /media/qzj/Document/grow/slam/slamDataSet/kitti/data_odometry_velodyne/dataset/00/calib.txt...段错误 (核心已转储)

@tym2103
Copy link

tym2103 commented Jun 9, 2020

How do you solve this problem?Just reinstall nvidia-drive?
I meet the same problem sa you

@jbehley
Copy link
Owner

jbehley commented Jun 9, 2020

Could you please open a new issue. In this issue, three different things are discussed. And its hard to help, when you don't know what's exactly the problem. However, as a summary for troubleshooting :

  1. We mainly tested our approach with Nvidia GPUs and drivers provided by Nvidia under Ubuntu 16.04/18.04. Thus, ensure that you have current Nvidia drivers.
  2. We tried to follow the specification of the OpenGL Core Profile and use only functionality described as required, since we made the experience that Intel, Mesa, and ATI often only support the required specifications. However, sometimes there are driver-specifics that we could not test. Please, report such problems and we try to work this out. (Nvidia has a rather feature complete driver and often implements all texture formats, etc. We even experienced that uncompiled shaders got linked by silently compiling them. Very convenient. ;))
  3. The KITTI calibration file contained with the images misses the line Tr: and must be downloaded separately from the KITTI webpage.

Hope that helps.

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

3 participants