Navigation Menu

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

moveitcpp vs movegroup #2581

Closed
stevedanomodolor opened this issue Apr 6, 2021 · 4 comments
Closed

moveitcpp vs movegroup #2581

stevedanomodolor opened this issue Apr 6, 2021 · 4 comments

Comments

@stevedanomodolor
Copy link

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

@AndyZe
Copy link
Contributor

AndyZe commented Apr 6, 2021

One advantage is decreased latency.

Some disadvantages are:

  • Can only be used with C++
  • Less tutorial documentation.

I'd be interested to hear more pros/cons, too!

@v4hn
Copy link
Member

v4hn commented Apr 6, 2021

movegroup does not exist, you are probably talking about the MoveGroupInterface.
This is a very thin class wrapping ROS actions that provides very easy access to MoveIt. Nothing more.

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

@v4hn v4hn closed this as completed Apr 6, 2021
@AndyZe
Copy link
Contributor

AndyZe commented Apr 6, 2021

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 moveit_cpp. That's not really an option with MGI.

@stevedanomodolor
Copy link
Author

Thanks for your response

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