{"id":259,"date":"2023-02-28T19:16:43","date_gmt":"2023-02-28T19:16:43","guid":{"rendered":"https:\/\/mrsdprojects.ri.cmu.edu\/2023teami\/?page_id=259"},"modified":"2023-03-01T21:14:41","modified_gmt":"2023-03-01T21:14:41","slug":"move-base-flex-architecture","status":"publish","type":"page","link":"https:\/\/mrsdprojects.ri.cmu.edu\/2023teami\/move-base-flex-architecture\/","title":{"rendered":"Move Base Flex Architecture"},"content":{"rendered":"\n

What is Move Base Flex<\/strong><\/h2>\n\n\n\n

Move Base Flex is a navigation stack that is an extension of the Move Base navigation stack, with a lot of great features. The package allows us to easily load\/unload planners and controllers on the fly, and even run multiple planning algorithms concurrently. The code base is highly flexible and modular, which makes it perfect for our application.<\/p>\n\n\n\n

\"\"
Move Base Flex Architecture (Reference: move_base_flex ROS Wiki)<\/figcaption><\/figure>\n\n\n\n

In a nutshell, this package handles all the interactions between the planner, the controller (which is what they call their local planner) and recovery behaviors, and also provides action server 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 pluginlib.<\/p>\n\n\n\n

What all do we need to implement<\/strong><\/h2>\n\n\n\n
\"\"<\/figure>
\n

These classes are purely abstract. We need to make our own global planner, local planner and recovery classes that inherit from these classes, and implement the pure virtual functions of these classes. <\/p>\n<\/div><\/div>\n\n\n\n

\n

In addition to this, the abstract_navigation_server is also a pure abstract class. This is the main class that runs the entire navigation stack. We need to make our own navigation server class that inherits from the abstract_navigation_server and implement the pure virtual functions of these classes.<\/p>\n<\/div>

\"\"<\/figure><\/div>\n\n\n\n
\"\"<\/figure>
\n

There are abstract classes for controlling the planner, controller, and recovery execution as well, but these are not pure abstract classes, and their functions have already been implemented by move_base_flex. However, if we want to change the way our planner, controller, and recovery behaviors execute and tie in with our navigation server, we can inherit from these classes and implement those functions that we want to change.<\/p>\n<\/div><\/div>\n\n\n\n

After all this is done, we can write a simple node that instantiates the navigation server class we implemented, and the rest will be taken care of by the package.<\/p>\n\n\n\n

To know more about the blocks that have to be implemented, go to the pages below:<\/p>\n\n\n\n