-
Notifications
You must be signed in to change notification settings - Fork 68
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
AMBF simulator window shuts down upon boot (ambf-2.0 branch) #187
Comments
Hi Melody, Please don't apologize for creating new issues, as a matter of fact, thank you for contributing this way. The message The second warning The core infrastructure of AMBF-2.0 is entirely different (better) than AMBF-1.0 and these warnings (/ errors) are part of that. For this comment:
Can you elaborate on what exactly is the issue as these two issues seem to be unrelated? Please feel free to open a new issue, or reopen the existing issues. |
Thanks for the quick reply! The two previous issues #155 and #159 were ones that I found to have mentioned the same error message, but I see now that those messages are probably not the cause of the simulator shutting down immediately upon starting. Thanks again! Let me know if there’s anything you suggest that I try. |
No problem. Are you running the |
I am not running it with any arguments. Here are the outputs I get on the terminal:
Also here is a quick video showing what I'm seeing (with the simulator window shutting down upon boot). In the video, I also tried loading specific robots with the -l flag, and a similar problem occurred. |
Thanks for the video, and I can see that it's a segfault. We shall need to compile Install
Then build AMBF in debug mode. Assuming that cd ~/ambf
mkdir build-debug && cd build-debug
cmake .. -DCMAKE_BUILD_TYPE=Debug
make -j4 After a successful build, head over to the
This would launch the We might also want to try checking the stack trace with sudo apt install valgrind And then run cd ~/ambf/bin-debug/lin-x86_64
valgrind ./ambf_simulator Valgrind may produce a lot of output but I would be interested in the last part where |
Hi Adnan,
And these are outputs from valgrind:
Finally, the following link shows a quick video demo: in case it helps :) |
Awesome, great to have the valgrind output. Can you test something, if you modify this line https://github.com/WPI-AIM/ambf/blob/ambf-2.0/ambf_simulator/src/ambf_simulator.cpp#L343 and change: glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3);
glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 1); to glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 2);
glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 1); and then recompile |
Wow that fixed it! Thank you so much. |
Happy to hear that. It is probably not an issue with the OpenGL version itself as version 3.3 and greater have be supported on machines from many years ago.While reading the output from |
Ah, I see! Yes, the computers in my lab are all 18.04, but I'm currently using my ancient 16.04 laptop. I've renamed the issue title so it's not misleading and will close the comment now. Thanks again for all your help. |
Hi Adnan,
Sorry for opening another issue so quickly, but I have a quick question. I have not made modifications to any file after a fresh pull from the
ambf-2.0
branch. Upon successfully building the code and sourcing thesetup.bash
file, I ran into the "JOINT NOT IMPLEMENTED YET" error message whenever I import a multibody object (that contains joints) to the ambf_simulator.The following is the output I get when typing the bare minimum command:
./ambf_simulator
(similar errors show up when I try importing raven or dvrk using the -l flag)I feel like I must have missed something. Do you have any suggestions?
Thanks a lot!
PS1: There were similar error messages as posed in prior Issues #155 and #159, but the solutions didn't seem to apply in my case.
PS2: I also noticed the warning messages that says "ADF version not defined thus assuming VERSION_1_0". Is that anticipated? Or, should I specify the ADF version in the yaml files somehow. Thanks!
The text was updated successfully, but these errors were encountered: