The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Can someone please help me where the jerk limits are used in the planning pipeline ??
If with "planning pipeline" you are referring to MoveIt using the default OMPL planner, then the jerk limits are not used at all there. In fact, no limits other than position limits are used, as OMPL purely plans in joint space and MoveIt setups the planning (ie: search) space for OMPL using the joint limits.
Limits on the dynamics are only taken into account at the end of planning pipeline, namely the "time-parameterisation". OMPL delivers a path, time-parameterisation turns it into a trajectory.
There are currently three options for time-parameterisation provided with MoveIt:
There is some discussion on the various options on the Time Parameterization page in the MoveIt tutorials.
Afaik, none of those take jerk limits into account.
I tried incorporating jerk limits in my config file but didn't see much change in the trajectory.
Afaik, that is to be expected. See my earlier comments.
Note that there are planners that could take dynamics into account while planning (something like STOMP or CHOMP, optimisation based) but those are by default not used and they might require some additional setup and configuration.
| | 2 | No.2 Revision |
Can someone please help me where the jerk limits are used in the planning pipeline ??
If with "planning pipeline" you are referring to MoveIt using the default OMPL planner, then the jerk limits are not used at all there. In fact, no limits other than position limits are used, as OMPL purely plans in joint space is a kinematic planner only and does not take dynamics into account (at least: not as it's used by MoveIt) and MoveIt setups the planning (ie: search) space for OMPL using the joint limits.
Limits on the dynamics are only taken into account at the end of planning pipeline, namely the "time-parameterisation". OMPL delivers a path, time-parameterisation turns it into a trajectory.
There are currently three options for time-parameterisation provided with MoveIt:
There is some discussion on the various options on the Time Parameterization page in the MoveIt tutorials.
Afaik, none of those take jerk limits into account.
I tried incorporating jerk limits in my config file but didn't see much change in the trajectory.
Afaik, that is to be expected. See my earlier comments.
Note that there are planners that could take dynamics into account while planning (something like STOMP or CHOMP, optimisation based) but those are by default not used and they might require some additional setup and configuration.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
