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 |
A couple of related discussions can be found here:
In short, it is a known problem which seem to occur when there are orientation constraints (which I failed to mention in the problem...) and has no proper fix at the moment. The current workaround is to use enforce_joint_model_state_space.
The idea of setting explicit joint jump limits was mentioned in the discussion but due to lack of interface for this on OMPL side, this cannot be implemented for the time being.
| | 2 | No.2 Revision |
A couple of related discussions can be found here:
In short, it is a known problem which seem to occur when there are orientation constraints (which I failed to mention in the problem...) and has no proper fix at the moment. The current workaround is to use enforce_joint_model_state_space.
The idea of setting explicit joint jump limits was mentioned in the discussion but due to lack of the interface for this is not available on OMPL side, this thus cannot be implemented for the time being.
| | 3 | No.3 Revision |
A couple of related discussions can be found here:
In short, it is a known problem which seem to occur when there are orientation constraints (which I failed to mention in the problem...) and has no proper fix at the moment. The current workaround is to use enforce_joint_model_state_space.
The idea of setting explicit joint jump limits was mentioned in the discussion but the interface for this is not available on OMPL side, thus cannot be implemented for the time being.
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.
