| hpp-fcl |
2.4.5-1 |
An extension of the Flexible Collision Library. |
meta-ros1-noetic |
| hpp-fcl |
2.4.5-1 |
An extension of the Flexible Collision Library. |
meta-ros2-humble |
| hpp-fcl |
2.4.5-1 |
An extension of the Flexible Collision Library. |
meta-ros2-jazzy |
| hpp-fcl |
2.4.5-2 |
An extension of the Flexible Collision Library. |
meta-ros2-kilted |
| ipr-extern |
0.8.8-1 |
Package with external libraries used in Industrial and Service workspaces. Currentlly supported Libraries: Reflexxes, Libmodbus. |
meta-ros1-melodic |
| jq |
1.8.1 |
Lightweight and flexible command-line JSON processor |
meta-oe |
| jq |
jq-1.5 |
JQ |
meta-luv |
| jq |
1.8.1 |
Lightweight and flexible command-line JSON processor |
meta-voltumna |
| kconfiglib |
14.1.0 |
kconfiglib |
meta-buildutils |
| kernel-module-imx-gpu-viv |
6.4.11.p4.4 |
Kernel loadable module for Vivante GPU |
meta-freescale |
| kwin |
6.5.2 |
KWin |
meta-kde |
| kwin |
6.6.0 |
KWin is an easy to use, but flexible, compositor for Wayland on Linux |
meta-wayland |
| libcsv |
3.0.3 |
Fast and flexible CSV library written in pure ANSI C that can read and write CSV data. |
meta-parallel-php |
| liblogging |
1.0.8 |
An easy to use logging library |
meta-oe |
| liblogging |
1.0.8 |
An easy to use logging library |
meta-voltumna |
| libmaxminddb |
1.4.3 |
C library for the MaxMind DB file format |
meta-networking |
| libpam |
1.7.2 |
Linux-PAM (Pluggable Authentication Modules) |
openembedded-core |
| libpam |
1.7.2 |
Linux-PAM (Pluggable Authentication Modules) |
meta-voltumna |
| libtest-deep-perl |
1.205 |
Test::Deep - Extremely flexible deep comparison |
meta-perl |
| libtest-deep-perl |
1.205 |
Test::Deep - Extremely flexible deep comparison |
meta-voltumna |
| libtest-fatal-perl |
0.018 |
Incredibly simple helpers for testing code with exceptions |
openembedded-core |
| libtest-fatal-perl |
0.018 |
Incredibly simple helpers for testing code with exceptions |
meta-voltumna |
| log-any-adapter-daemontools-perl |
0.102 |
In the daemontools way of thinking, a daemon writes all its logging output to STDOUT (or STDERR), which is a pipe to a logger process. Doing this instead of other logging alternatives keeps your program simple and allows you to capture errors generated by deeper libraries (like libc) which aren't aware of your logging API. If you want complicated logging you can keep those details in the logging process and not bloat each daemon you write. This module aims to be the easiest, simplest, most efficent way to get Log::Any messages to a file handle while still being flexible enough for the needs of the typical unix daemon or utility script. |
meta-cpan |
| log4c |
1.2.4 |
Log4c is a C library for flexible logging to files, syslog and other destinations |
meta-oe |
| log4cplus |
2.1.2 |
log4cplus provides a simple C++ logging API for log management |
openembedded-core |
| log4cpp |
1.1.4 |
A library of C++ classes for flexible logging to files, syslog, IDSA and other destinations. |
meta-oe |
| matchbox-panel-2 |
2.12 |
Simple GTK+ based panel for handheld devices |
openembedded-core |
| mbf-abstract-core |
0.4.0-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-core |
0.4.0-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-noetic |
| mbf-abstract-core |
1.0.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-ros2-humble |
| mbf-abstract-core |
1.0.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-ros2-jazzy |
| mbf-abstract-nav |
0.4.0-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-abstract-nav |
0.4.0-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-noetic |
| mbf-abstract-nav |
1.0.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-ros2-humble |
| mbf-abstract-nav |
1.0.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-ros2-jazzy |
| mbf-costmap-core |
0.4.0-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-core |
0.4.0-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-noetic |
| mbf-costmap-nav |
0.4.0-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-costmap-nav |
0.4.0-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-noetic |
| mbf-msgs |
0.4.0-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-msgs |
0.4.0-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-noetic |
| mbf-msgs |
1.0.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-ros2-humble |
| mbf-msgs |
1.0.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-ros2-jazzy |
| mbf-simple-core |
1.0.5-1 |
This package provides common interfaces for navigation specific robot actions. It contains the SimplePlanner, SimpleController and SimpleRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_simple_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and there is no binding to a map representation. |
meta-ros2-humble |
| mbf-simple-core |
1.0.5-1 |
This package provides common interfaces for navigation specific robot actions. It contains the SimplePlanner, SimpleController and SimpleRecovery interfaces. The interfaces have to be implemented by the plugins to make them available for Move Base Flex using the mbf_simple_nav navigation implementation. That implementation inherits the mbf_abstract_nav implementation and there is no binding to a map representation. |
meta-ros2-jazzy |
| mbf-simple-nav |
0.4.0-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-simple-nav |
0.4.0-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-noetic |
| mbf-simple-nav |
1.0.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-ros2-humble |
| mbf-simple-nav |
1.0.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-ros2-jazzy |
| mbf-test-utility |
1.0.5-1 |
Contains tools that help with testing move base flex modules. This package should only be used as a test dependency. If some tool shall be used in production, move it into mbf_utility for example. |
meta-ros2-humble |