You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 13, 2017. It is now read-only.
The mechanism for loading parameters from the ROS parameter server of the ompl_interface is a protected function loadPlannerConfigurations() run only on construction.
Many planner parameters drastically change the performance of the planner, and it would be nice to be able to change these on the fly without having to restart the move_group node. For example, the parameter "range" indicates how far toward some random c-space point the random planner will attempt to move to create each waypoint. When this value is small, one tends to get intricate plans closely skirting objects. When it is large, the plans tend to move way out of the way.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The mechanism for loading parameters from the ROS parameter server of the ompl_interface is a protected function loadPlannerConfigurations() run only on construction.
Many planner parameters drastically change the performance of the planner, and it would be nice to be able to change these on the fly without having to restart the move_group node. For example, the parameter "range" indicates how far toward some random c-space point the random planner will attempt to move to create each waypoint. When this value is small, one tends to get intricate plans closely skirting objects. When it is large, the plans tend to move way out of the way.
The text was updated successfully, but these errors were encountered: