help
Recipe name Version Description Layer
marti-perception-msgs 0.8.0 marti_perception_msgs meta-ros1-melodic
marti-perception-msgs 1.0.0-1 marti_perception_msgs meta-ros2-dashing
marti-perception-msgs 1.1.0-1 marti_perception_msgs meta-ros2-foxy
marti-sensor-msgs 0.8.0 marti_sensor_msgs meta-ros1-melodic
marti-sensor-msgs 1.0.0-1 marti_sensor_msgs meta-ros2-dashing
marti-sensor-msgs 1.1.0-1 marti_sensor_msgs meta-ros2-foxy
marti-status-msgs 0.8.0 marti_status_msgs meta-ros1-melodic
marti-status-msgs 1.0.0-1 marti_status_msgs meta-ros2-dashing
marti-status-msgs 1.1.0-1 marti_status_msgs meta-ros2-foxy
marti-visualization-msgs 0.8.0 marti_visualization_msgs meta-ros1-melodic
marti-visualization-msgs 1.0.0-1 marti_visualization_msgs meta-ros2-dashing
marti-visualization-msgs 1.1.0-1 marti_visualization_msgs meta-ros2-foxy
master-discovery-fkieblacklisted 0.8.12 Discover the running ROS Masters in local network. The discovering is done by sending an echo heartbeat messages to a defined multicast group. The alternative is to use a zeroconf/avahi daemon to register the ROS master as service and discover other ROS masters. meta-ros1-melodic
master-sync-fkieblacklisted 0.8.12 Synchronize the local ROS master to the remote masters discovered by master_discovery_fkie node. The registration of topics and services is only perform by local ROS master. meta-ros1-melodic
mav-comm 3.3.2 Contains messages and services for MAV communication meta-ros1-melodic
mav-msgs 3.3.2 Package containing messages for communicating with rotary wing MAVs meta-ros1-melodic
mav-planning-msgs 3.3.2 Messages specific to MAV planning, especially polynomial planning. meta-ros1-melodic
mavlink 2020.3.3-1 MAVLink message marshaling library. This package provides C-headers and C++11 library for both 1.0 and 2.0 versions of protocol. For pymavlink use separate install via rosdep (python-pymavlink). meta-ros1-melodic
mavlink 2020.2.2-1 MAVLink message marshaling library. This package provides C-headers and C++11 library for both 1.0 and 2.0 versions of protocol. For pymavlink use separate install via rosdep (python-pymavlink). meta-ros2-eloquent
mavros 1.0.0-1 MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station. meta-ros1-melodic
mavros-extras 1.0.0-1 Extra nodes and plugins for <a href="http://wiki.ros.org/mavros">MAVROS</a>. meta-ros1-melodic
mavros-msgs 1.0.0-1 mavros_msgs defines messages for <a href="http://wiki.ros.org/mavros">MAVROS</a>. meta-ros1-melodic
mbedtls 2.16.3 Lightweight crypto and SSL/TLS library meta-networking
mbedtls 2.1.1 An open source, portable, easy to use, readable and flexible SSL library meta-digi-dey
mbf-abstract-core 0.2.5-1 This package provides common interfaces for navigation specific robot actions. It contains the AbstractPlanner, AbstractController and AbstractRecovery plugin interfaces. This interfaces have to be implemented by the plugins to make the plugin available for Move Base Flex. The abstract classes provides a meaningful interface enabling the planners, controllers and recovery behaviors to return information, e.g. why something went wrong. Derivided interfaces can, for example, provide methods to initialize the planner, controller or recovery with map representations like costmap_2d, grid_map or other representations. meta-ros1-melodic
mbf-abstract-nav 0.2.5-1 The mbf_abstract_nav package contains the abstract navigation server implementation of Move Base Flex (MBF). The abstract navigation server is not bound to any map representation. It provides the actions for planning, controlling and recovering. MBF loads all defined plugins at the program start. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. meta-ros1-melodic
mbf-costmap-core 0.2.5-1 This package provides common interfaces for navigation specific robot actions. It contains the CostmapPlanner, CostmapController and CostmapRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_costmap_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and binds the system to a local and a global costmap. meta-ros1-melodic
mbf-costmap-nav 0.2.5-1 The mbf_costmap_nav package contains the costmap navigation server implementation of Move Base Flex (MBF). The costmap navigation server is bound to the <a href="wiki.ros.org/costmap_2d">costmap_2d</a> representation. It provides the Actions for planning, controlling and recovering. At the time of start MBF loads all defined plugins. Therefor, it loads all plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. Additionally the mbf_costmap_nav package comes with a wrapper for the old navigation stack and the plugins which inherits from the <a href="wiki.ros.org/nav_core">nav_core</a> base classes. Preferably it tries to load plugins for the new API. However, plugins could even support both <a href="wiki.ros.org/move_base">move_base</a> and <a href="wiki.ros.org/move_base_flex">move_base_flex</a> by inheriting both base class interfaces located in the <a href="wiki.ros.org/nav_core">nav_core</a> package and in the <a href="mbf_costmap_core">mbf_costmap_core</a> package. meta-ros1-melodic
mbf-msgs 0.2.5-1 The move_base_flex messages package providing the action definition files for the action GetPath, ExePath, Recovery and MoveBase. The action servers providing these action are implemented in <a href="http://wiki.ros.org/mbf_abstract_nav">mbf_abstract_nav</a>. meta-ros1-melodic
mbf-simple-nav 0.2.5-1 The mbf_simple_nav package contains a simple navigation server implementation of Move Base Flex (MBF). The simple navigation server is bound to no map representation. It provides actions for planning, controlling and recovering. MBF loads all defined plugins which are defined in the lists *planners*, *controllers* and *recovery_behaviors*. Each list holds a pair of a *name* and a *type*. The *type* defines which kind of plugin to load. The *name* defines under which name the plugin should be callable by the actions. It tries to load the defined plugins which implements the defined interfaces in <a href="wiki.ros.org/mbf_abstract_core">mbf_abstract_core</a>. meta-ros1-melodic
mbf-utility 0.2.5-1 The mbf_utility package meta-ros1-melodic
mcl-3dl 0.2.1-1 3-D/6-DOF localization for mobile robots with 3-D LIDAR(s) meta-ros1-melodic
mcl-3dl-msgs 0.2.0-1 The mcl_3dl message definition package meta-ros1-melodic
mcmillan-airfieldblacklisted 0.0.1-1 The mcmillan_airfield package meta-ros1-melodic
md-juggler 0.0.0+gitX Qt markdown report generator meta-qt5-extra
md49-base-controller 0.1.4-1 The md49_base_controller package meta-ros1-melodic
md49-messages 0.1.4-1 The md49_messages package meta-ros1-melodic
md49-serialport 0.1.4-1 The md49_serialport package meta-ros1-melodic
mecanum-gazebo-pluginblacklisted 0.1.0-1 Plugin which uses directional friction to simulate mecanum wheels. meta-ros1-melodic
media-export 0.3.0-1 Placeholder package enabling generic export of media paths. meta-ros1-melodic
media-resource-calculator 1.0.0-4 Media Resource Calculator for webOS meta-webosose
message-filters 1.14.5-1 A set of message filters which take in messages and may output those messages at a later time, based on the conditions that filter needs met. meta-ros1-melodic
message-filters 3.1.3-1 A set of ROS2 message filters which take in messages and may output those messages at a later time, based on the conditions that filter needs met. meta-ros2-dashing
message-filters 3.2.3-1 A set of ROS2 message filters which take in messages and may output those messages at a later time, based on the conditions that filter needs met. meta-ros2-eloquent
message-filters 3.2.4-1 A set of ROS2 message filters which take in messages and may output those messages at a later time, based on the conditions that filter needs met. meta-ros2-foxy
message-generation 0.4.1-1 Package modeling the build-time dependencies for generating language bindings of messages. meta-ros1-melodic
message-relay 0.0.2-1 Package to programmatically spawn message, service, and action relays. To add support for a message/service dependency, please add to the build dependencies in package.xml and CMakeLists.txt meta-ros1-melodic
message-runtime 0.4.12 Package modeling the run-time dependencies for language bindings of messages. meta-ros1-melodic
metee 2.1.1 Intel(R) METEE Library meta-intel
metrics-discovery 1.5.108 Intel Metrics Discovery Application Programming Interface meta-intel