| luna-systemui |
2.0.1-2+git |
WebOS user interface support module |
meta-luneos |
| lvr2 |
20.11.3-4 |
The Las Vegas Surface Reconstruction Toolkit is an Open Source toolkit to reconstruct triangle meshes from unordered point clouds. It supports the generation of textured models either using colored point clouds or point clouds plus images and according calibration matrices. The LVR toolkit provides an Open Source C++ API for meshing and texture generation as well as an I/O interface to store the generated meshes in different exchange formats including Stanford PLY, Wavefront OBJ and Collada. In contrast to other meshing software, it focuses on reconstruction of large scale environments on city scale from high resolution point clouds. |
meta-ros1-noetic |
| lvr2 |
25.2.2-1 |
The Las Vegas Surface Reconstruction Toolkit is an Open Source toolkit to reconstruct triangle meshes from unordered point clouds. It supports the generation of textured models either using colored point clouds or point clouds plus images and according calibration matrices. The LVR toolkit provides an Open Source C++ API for meshing and texture generation as well as an I/O interface to store the generated meshes in different exchange formats including Stanford PLY, Wavefront OBJ and Collada. In contrast to other meshing software, it focuses on reconstruction of large scale environments on city scale from high resolution point clouds. |
meta-ros2-humble |
| lvr2 |
25.2.2-1 |
The Las Vegas Surface Reconstruction Toolkit is an Open Source toolkit to reconstruct triangle meshes from unordered point clouds. It supports the generation of textured models either using colored point clouds or point clouds plus images and according calibration matrices. The LVR toolkit provides an Open Source C++ API for meshing and texture generation as well as an I/O interface to store the generated meshes in different exchange formats including Stanford PLY, Wavefront OBJ and Collada. In contrast to other meshing software, it focuses on reconstruction of large scale environments on city scale from high resolution point clouds. |
meta-ros2-jazzy |
| lxc |
5.0.3+git |
lxc aims to use these new functionnalities to provide an userspace container object |
meta-virtualization |
| lxc |
4.0.6 |
lxc aims to use these new functionnalities to provide an userspace container object |
meta-luneos |
| lxcfs |
5.0.4 |
LXCFS is a userspace filesystem created to avoid kernel limitations |
meta-virtualization |
| lzip |
1.24 |
Lossless data compressor based on the LZMA algorithm |
openembedded-core |
| macchanger |
1.7.0 |
Tool to view/change network interface MAC addresses |
meta-networking |
| makedumpfile |
1.7.5 |
VMcore extraction tool |
meta-oe |
| maliit-framework-qt5 |
0.99.0+gitX |
A virtual keyboard for touch-screen based user interfaces |
meta-qt5 |
| maliit-plugins-qt5 |
0.99.0+gitX |
Plugins for a virtual keyboard for touch-screen based user interfaces |
meta-qt5 |
| man-db |
2.12.0 |
An implementation of the standard Unix documentation system accessed using the man command |
openembedded-core |
| man-pages |
6.06 |
Linux man-pages |
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-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-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-noetic |
| 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-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 |
| mbw |
2.0 |
MBW determines the copy memory bandwidth available to userspace programs |
meta-oe |
| media-export |
0.3.0-1 |
Placeholder package enabling generic export of media paths. |
meta-ros1-noetic |
| meson |
1.3.1 |
A high performance build system |
openembedded-core |
| meson |
1.5.1 |
A high performance build system |
meta-webos-backports-5.1 |
| metee |
3.2.4 |
Intel(R) METEE Library |
meta-intel |
| metrics-discovery |
1.12.171 |
Intel Metrics Discovery Application Programming Interface |
meta-intel |
| metro-benchmark-msgs |
0.1.1-1 |
ROS interfaces for recording compute time and other related benchmarking concepts |
meta-ros2-humble |
| minio |
01b87ecc02ffad47dfe13c2154ac31db3e3115df |
MinIO Client is a replacement for ls, cp, mkdir, diff and rsync commands for filesystems and object storage. |
meta-oe |
| mixlib-shellout |
2.1.0 |
Provides a simplified interface to shelling |
meta-openstack |
| mmc-utils |
0.1+git |
Userspace tools for MMC/SD devices |
openembedded-core |
| mocap4r2-msgs |
0.0.6-2 |
Interfaces for Mocap4ROS2 project |
meta-ros2-humble |
| mocap4r2-msgs |
0.1.0-1 |
Interfaces for Mocap4ROS2 project |
meta-ros2-jazzy |
| mocap4r2-msgs |
0.2.0-1 |
Interfaces for Mocap4ROS2 project |
meta-ros2-kilted |
| mod-wsgi |
4.9.1+gitX |
Supports the Python WSGI interface |
meta-openstack |
| mola-kernel |
2.7.0-1 |
Fundamental C++ virtual interfaces and data types for the rest of MOLA modules |
meta-ros2-rolling |
| mola-kernel |
2.9.0-1 |
Fundamental C++ virtual interfaces and data types for the rest of MOLA modules |
meta-ros2-humble |
| mola-kernel |
2.9.0-1 |
Fundamental C++ virtual interfaces and data types for the rest of MOLA modules |
meta-ros2-jazzy |
| mola-kernel |
2.9.0-1 |
Fundamental C++ virtual interfaces and data types for the rest of MOLA modules |
meta-ros2-kilted |
| mola-metric-maps |
2.7.0-1 |
Advanced metric map classes, using the generic `mrpt::maps::CMetricMap` interface, for use in other MOLA odometry and SLAM modules. |
meta-ros2-rolling |
| mola-metric-maps |
2.9.0-1 |
Advanced metric map classes, using the generic `mrpt::maps::CMetricMap` interface, for use in other MOLA odometry and SLAM modules. |
meta-ros2-humble |
| mola-metric-maps |
2.9.0-1 |
Advanced metric map classes, using the generic `mrpt::maps::CMetricMap` interface, for use in other MOLA odometry and SLAM modules. |
meta-ros2-jazzy |
| mola-metric-maps |
2.9.0-1 |
Advanced metric map classes, using the generic `mrpt::maps::CMetricMap` interface, for use in other MOLA odometry and SLAM modules. |
meta-ros2-kilted |
| mosh |
1.4.0 |
Remote shell supporting roaming and high-latency connections |
meta-oe |
| move-base |
1.17.3-1 |
The move_base package provides an implementation of an action (see the <a href="http://www.ros.org/wiki/actionlib">actionlib</a> package) that, given a goal in the world, will attempt to reach it with a mobile base. The move_base node links together a global and local planner to accomplish its global navigation task. It supports any global planner adhering to the nav_core::BaseGlobalPlanner interface specified in the <a href="http://www.ros.org/wiki/nav_core">nav_core</a> package and any local planner adhering to the nav_core::BaseLocalPlanner interface specified in the <a href="http://www.ros.org/wiki/nav_core">nav_core</a> package. The move_base node also maintains two costmaps, one for the global planner, and one for a local planner (see the <a href="http://www.ros.org/wiki/costmap_2d">costmap_2d</a> package) that are used to accomplish navigation tasks. |
meta-ros1-noetic |
| move-base-flex |
0.4.0-1 |
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 plugin’s 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 <a href="http://wiki.ros.org/mbf_abstract_nav">mbf_abstract_nav</a> and the <a href="http://wiki.ros.org/mbf_abstract_core">mbf_abstract_core</a>. For navigation on costmaps see <a href="http://wiki.ros.org/mbf_costmap_nav">mbf_costmap_nav</a> and <a href="http://wiki.ros.org/mbf_costmap_core">mbf_costmap_core</a>. |
meta-ros1-noetic |
| move-base-flex |
1.0.5-1 |
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 plugin’s 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 <a href="http://github.com/naturerobots/move_base_flex">mbf_abstract_nav</a> and the <a href="http://github.com/naturerobots/move_base_flex">mbf_abstract_core</a>. For navigation on costmaps see <a href="http://github.com/naturerobots/move_base_flex">mbf_costmap_nav</a> and <a href="http://github.com/naturerobots/move_base_flex">mbf_costmap_core</a>. |
meta-ros2-humble |