[ros-users] [Discourse.ros.org] [Next Generation ROS] ROS2 Navigation - Input requested
ros.discourse at gmail.com
Sat Jun 2 06:29:59 UTC 2018
Not really a navigation stack user myself, so just passing by, but I was surprised `move_base_flex` wasn't / isn't mentioned more. Only @Jeremie mentioned it once earlier in this thread.
>From the [presentation](https://vimeo.com/236174072) at ROSCon and [the docs](http://wiki.ros.org/move_base_flex) it seems it's gone into the direction that @gbiggs, @wdsmart and some others sketch:
> Move Base Flex (MBF) is a backwards-compatible replacement for move_base. MBF can use existing plugins for move_base, and provides an enhanced version of the planner, controller and recovery plugin ROS interfaces. It exposes action servers for planning, controlling and recovering, providing detailed information of the current state and the plugins feedback. An external executive logic can use MBF and its actions to perform smart and flexible navigation strategies. Furthermore, MBF enables the use of other map representations, e.g. meshes or grid_map This package is a meta package and refers to the Move Base Flex stack packages.The abstract core of MBF without any binding to a map representation is represented by the [mbf_abstract_nav](http://wiki.ros.org/mbf_abstract_nav) and the [mbf_abstract_core](http://wiki.ros.org/mbf_abstract_core). For navigation on costmaps see [mbf_costmap_nav](http://wiki.ros.org/mbf_costmap_nav) and [mbf_costmap_core](http://wiki.ros.org/mbf_co
Would seem to be a good idea to get some input from its maintainers (@spuetz et al.).
[Visit Topic](https://discourse.ros.org/t/ros2-navigation-input-requested/4884/17) or reply to this email to respond.
More information about the ros-users