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 |
One cause is using one of the older, buggy time parameterization algorithms in your MoveIt setup. To fix this, you can grep in your "moveit_config" package and find some text like this:
default_planner_request_adapers/terativeParabolicTimeParameterization (or) default_planner_request_adapters/AddTimeParameterization
Replace it with the newest and best time parameterization algorithm, which is: default_planner_request_adapters/AddTimeOptimalParameterization
| | 2 | No.2 Revision |
One cause is using This can be caused by one of the older, buggy time parameterization algorithms in your MoveIt setup. To fix this, you can grep in your "moveit_config" package and find some text like this:
default_planner_request_adapers/terativeParabolicTimeParameterization (or) default_planner_request_adapters/AddTimeParameterization
Replace it with the newest and best time parameterization algorithm, which is: default_planner_request_adapters/AddTimeOptimalParameterization
| | 3 | No.3 Revision |
This can be caused by one of the older, buggy time parameterization algorithms in your MoveIt setup. To fix this, you can grep in your "moveit_config" package and find some text like this:
default_planner_request_adapers/terativeParabolicTimeParameterizationdefault_planner_request_adapers/IterativeParabolicTimeParameterizationdefault_planner_request_adapters/AddTimeParameterization
Replace it with the newest and best time parameterization algorithm, which is: default_planner_request_adapters/AddTimeOptimalParameterization
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.
