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

Stomp Smoothing Planning Request Adapter #1081

wants to merge 16 commits into
base: kinetic-devel


None yet
4 participants
Copy link

raghavendersahdev commented Oct 9, 2018

Addition of STOMP Smoothing Adapter in MoveIt

This PR is work done by Raghavender as a part of 2018 Google summer of code. As a part of this PR, a STOMP Smoothing adapter has been implemented. This enables the user to use STOMP as an additional post processing motion planning algorithm in a pipeline with another motion planner like CHOMP, OMPL, etc. This then produces smooth motion plans.

For tutorials on how to use this motion planning request adapter, refer to PR for a tutorial on Planning Request Adapters PR#220 . This PR also needs this PR in industrial_moveit package to be merged PR#78 in order for the STOMP smoothing adapter to function properly.
It should be noted this PR overrides an older PR #965 , after this PR gets merged PR #965 can be closed and ignored.
@davetcoleman @mamoll


  • addition of STOMP smoothing adapter into existing MoveIt Planning Request Adapters
  • merging of the STOMP moveit package from industrial moveit into moveit, this PR overrides this PR #965

@raghavendersahdev raghavendersahdev referenced this pull request Oct 9, 2018


STOMP Smoothing Adapter #78

0 of 2 tasks complete
@@ -24,3 +24,7 @@
local-name: srdfdom
version: kinetic-devel
- git:
local-name: industrial_moveit

This comment has been minimized.


davetcoleman Oct 13, 2018


this needs to be switched to the new stomp repo that is suppose to be created. fyi @gavanderhoorn


This comment has been minimized.

Copy link

rhaschke commented Oct 24, 2018

Please revert the last merge-commit and rebase your branch onto the kinetic-devel to resolve conflicts.
Having merge-commits within a PR-branch like this, makes it impossible to squash, or cherry-pick it to another branch later on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment