Revision history [back]

OMPL is a planning library that includes only planning algorithms. There is no collision checking, nothing that maintains a map or that interacts with controllers. The ROS navigation stack includes planning, map representation, collision checking, and components for executing the computed plans. I guess it depends on what problem you are trying to solve. If you have a map representation and a means to implement collision checking, OMPL can be your solution. If you want to use more components from ROS, the navigation stack would be better suited. Another detail to consider is that the navigation stack is geared for 2d planning and uses search-based algorithms (sbpl library) to compute optimized solutions. OMPL includes sampling based algorithms which will produce different solutions for every execution, but the space in which the motion plan is computed is easily changed. (see http://ompl.kavrakilab.org/planners.html for the different algorithms included in OMPL)