Revision history [back]

Hi,

The code that generates the number of points along the path is in ompl_ros_interface/src/planners/ompl_ros_joint_planner.cpp and ompl_ros_interface/src/planners/ompl_ros_rpy_task_space_planner.cpp; Each of these files contains a getSolutionPath() method, where you will see path.interpolate() being called. By default, interpolate() will generate points on the path at the resolution that was used for collision checking. However, you can specify the number of points as an argument. So you need to change the code to something like path.interpolate(value); This has no notion of time however, and it depends on your trajectory filtering how long the path takes to execute.

Another thing you can do (not recommended) is to make the collision checking resolution be much smaller, so you get more points. That will however slow down planning significantly. Changing the collision checking resolution can be done by modifying the value of the longest_valid_sement_fraction parameter in the loaded ompl_planning.yaml;