Skip to content

Commit 199fd65

Browse files
committed
Add reference for MBF and entry in navigation.yml
1 parent ca36f0e commit 199fd65

2 files changed

Lines changed: 3 additions & 1 deletion

File tree

_data/navigation.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -309,6 +309,8 @@ wiki:
309309
url: /wiki/planning/multi-robot-planning/
310310
- title: Motion Planning in frenet frame
311311
url: /wiki/planning/frenet-frame-planning.md/
312+
- title: Move Base Flex
313+
url: /wiki/planning/move-base-flex/
312314
# Main links appear in the header.
313315
main:
314316
- title: Wiki

wiki/planning/move_base_flex.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ In both cases, tell them what you're going to say, use the sections below to say
1919

2020
## Introduction
2121

22-
MBF is a navigation stack that is an extension of the Move Base navigation stack, with many great features. The package allows us to load/unload planners and controllers on the fly easily and even run multiple planning algorithms concurrently. The code base is highly flexible and modular. It is an improvement over the original move base navigation package, which only allows 2D costmaps and does not allow easy modification of the execution behavior of the navigation stack.
22+
[MBF](http://wiki.ros.org/move_base_flex) is a navigation stack that is an extension of the Move Base navigation stack, with many great features. The package allows us to load/unload planners and controllers on the fly easily and even run multiple planning algorithms concurrently. The code base is highly flexible and modular. It is an improvement over the original move base navigation package, which only allows 2D costmaps and does not allow easy modification of the execution behavior of the navigation stack.
2323

2424
This package handles all the interactions between the planner, the controller (what they call their local planner), and recovery behaviors. Also, it provides action servers for sending and keeping track of goals. These are supposed to be implemented as classes and are dynamically loaded/unloaded in the memory using the ROS plugin library [1].
2525

0 commit comments

Comments
 (0)