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
moveitcpp vs movegroup #2581
Comments
One advantage is decreased latency. Some disadvantages are:
I'd be interested to hear more pros/cons, too! |
If you want detailed control over the C++ datastructures that do the actual planning, you need MoveItCpp instead or have to do the whole class setup that MoveItCpp does for you by yourself. That's pretty much the whole story. As this is no issue at all, I'll close it now (sorry Andy ;)). Feel free to discuss such question at https://answers.ros.org |
Well, you have reminded me of another advantage of moveit_cpp: You can do things like combine trajectories more easily, or run your own post-processign with |
Thanks for your response |
This is out of curiosity. When is important to use moveitcpp instead of movegroup(advantages and inconvenience). If the goal was a commercial application, would moveitcpp be better and why.
Thank you very much for your response
The text was updated successfully, but these errors were encountered: