| gazebo-msgs |
2.9.2-1 |
Message and service data structures for interacting with Gazebo from ROS. |
meta-ros1-noetic |
| gazebo-msgs |
3.5.2-5 |
Message and service data structures for interacting with Gazebo from ROS2. |
meta-ros2-galactic |
| gem5-m5ops |
v20.1.0.5 |
m5ops provide pseudo-instructions to trigger gem5 functionality |
meta-gem5 |
| genmsg |
0.6.0-1 |
Standalone Python library for generating ROS message and service data structures for various languages. |
meta-ros1-noetic |
| geometry-msgs |
1.13.1-1 |
geometry_msgs provides messages for common geometric primitives such as points, vectors, and poses. These primitives are designed to provide a common data type and facilitate interoperability throughout the system. |
meta-ros1-noetic |
| gettext |
0.21 |
Utilities and libraries for producing multi-lingual messages |
openembedded-core |
| gflags |
2.2.2 |
The gflags package contains a C++ library that implements commandline flags processing. It includes built-in support for standard types such as string and the ability to define flags in the source file in which they are used |
meta-oe |
| gflags |
2.2.2 |
C++ library that implements commandline flags processing |
meta-gnss-sdr |
| ghostscript |
9.56.1 |
The GPL Ghostscript PostScript/PDF interpreter |
openembedded-core |
| gmcl |
1.0.1-3 |
<p> gmcl, which stands for general monte carlo localization, is a probabilistic-based localization technique for mobile robots in 2D-known map. It integrates the adaptive monte carlo localization - amcl - approach with three different particle filter algorithms (Optimal, Intelligent, Self-adaptive) to improve the performance while working in real time. </p> <p> Main node structure and amcl-algorithms’s code was derived, with thanks, from Brian Gerkey's amcl package. </p> |
meta-ros1-noetic |
| gnome-settings-daemon |
42.1 |
Window navigation construction toolkit |
meta-gnome |
| gnu-efi |
3.0.15 |
Libraries for producing EFI binaries |
openembedded-core |
| gnulib |
2018-03-07.03 |
The GNU portability library |
meta-oe |
| go |
1.19.7 |
Go programming language compiler |
openembedded-core |
| go |
1.20.1 |
Go programming language compiler |
meta-shellhub |
| go-cross-canadian-i686 |
1.19.7 |
Go programming language compiler |
openembedded-core |
| go-cross-canadian-i686 |
1.20.1 |
Go programming language compiler |
meta-shellhub |
| go-cross-core2-32 |
1.19.7 |
Go programming language compiler |
openembedded-core |
| go-cross-core2-32 |
1.20.1 |
Go programming language compiler |
meta-shellhub |
| go-crosssdk-x86_64-oesdk-linux |
1.19.7 |
Go programming language compiler |
openembedded-core |
| go-crosssdk-x86_64-oesdk-linux |
1.20.1 |
Go programming language compiler |
meta-shellhub |
| go-native |
1.19.7 |
Go programming language compiler |
openembedded-core |
| go-native |
1.20.1 |
Go programming language compiler |
meta-shellhub |
| go-runtime |
1.19.7 |
Go programming language compiler |
openembedded-core |
| go-runtime |
1.20.1 |
Go programming language compiler |
meta-shellhub |
| gpp-prune-path |
0.1.0-1 |
The gpp_prune_path plugin will prune the path produced by a global-planner |
meta-ros1-noetic |
| greengrass-bin |
2.9.6 |
AWS IoT Greengrass Nucleus - Binary Distribution |
meta-aws |
| greengrass-bin-demo |
1.0 |
greengrass-bin demo |
meta-aws |
| groff |
1.22.4 |
GNU Troff software |
openembedded-core |
| gtk-doc |
1.33.2 |
Documentation generator for glib-based software |
openembedded-core |
| heaptrack |
1.2.0 |
Heap memory profiler for Linux |
meta-oe |
| hector-gazebo-thermal-camera |
0.5.4-1 |
hector_gazebo_thermal_camera provides a gazebo plugin that produces simulated thermal camera images. The plugin uses modified code from the gazebo_ros_camera plugin. |
meta-ros1-noetic |
| hector-mapping |
0.5.2-4 |
hector_mapping is a SLAM approach that can be used without odometry as well as on platforms that exhibit roll/pitch motion (of the sensor, the platform or both). It leverages the high update rate of modern LIDAR systems like the Hokuyo UTM-30LX and provides 2D pose estimates at scan rate of the sensors (40Hz for the UTM-30LX). While the system does not provide explicit loop closing ability, it is sufficiently accurate for many real world scenarios. The system has successfully been used on Unmanned Ground Robots, Unmanned Surface Vehicles, Handheld Mapping Devices and logged data from quadrotor UAVs. |
meta-ros1-noetic |
| highway |
0.17.0 |
Highway is a C++ library for SIMD (Single Instruction, Multiple Data) |
meta-wayland |
| hls-lfcd-lds-driver |
2.0.3-1 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros2-dashing |
| hls-lfcd-lds-driver |
2.0.1-1 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros2-eloquent |
| hls-lfcd-lds-driver |
2.0.1-1 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros2-foxy |
| hls-lfcd-lds-driver |
2.0.4-4 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros2-rolling |
| hls-lfcd-lds-driver |
1.1.2-1 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros1-noetic |
| hls-lfcd-lds-driver |
2.0.4-1 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros2-galactic |
| ifuse |
1.1.4 |
A fuse filesystem to access the contents of an iPhone or iPod Touch |
meta-filesystems |
| image-geometry |
2.1.4-1 |
`image_geometry` contains C++ and Python libraries for interpreting images geometrically. It interfaces the calibration parameters in sensor_msgs/CameraInfo messages with OpenCV functions such as image rectification, much as cv_bridge interfaces ROS sensor_msgs/Image with OpenCV data types. |
meta-ros2-dashing |
| image-geometry |
2.1.4-1 |
`image_geometry` contains C++ and Python libraries for interpreting images geometrically. It interfaces the calibration parameters in sensor_msgs/CameraInfo messages with OpenCV functions such as image rectification, much as cv_bridge interfaces ROS sensor_msgs/Image with OpenCV data types. |
meta-ros2-eloquent |
| image-geometry |
2.2.1-1 |
`image_geometry` contains C++ and Python libraries for interpreting images geometrically. It interfaces the calibration parameters in sensor_msgs/CameraInfo messages with OpenCV functions such as image rectification, much as cv_bridge interfaces ROS sensor_msgs/Image with OpenCV data types. |
meta-ros2-foxy |
| image-geometry |
3.4.0-2 |
`image_geometry` contains C++ and Python libraries for interpreting images geometrically. It interfaces the calibration parameters in sensor_msgs/CameraInfo messages with OpenCV functions such as image rectification, much as cv_bridge interfaces ROS sensor_msgs/Image with OpenCV data types. |
meta-ros2-rolling |
| image-geometry |
1.16.2-1 |
`image_geometry` contains C++ and Python libraries for interpreting images geometrically. It interfaces the calibration parameters in sensor_msgs/CameraInfo messages with OpenCV functions such as image rectification, much as cv_bridge interfaces ROS sensor_msgs/Image with OpenCV data types. |
meta-ros1-noetic |
| image-geometry |
2.2.1-2 |
`image_geometry` contains C++ and Python libraries for interpreting images geometrically. It interfaces the calibration parameters in sensor_msgs/CameraInfo messages with OpenCV functions such as image rectification, much as cv_bridge interfaces ROS sensor_msgs/Image with OpenCV data types. |
meta-ros2-galactic |
| image-rotate |
2.1.1-1 |
<p> Contains a node that rotates an image stream in a way that minimizes the angle between a vector in some arbitrary frame and a vector in the camera frame. The frame of the outgoing image is published by the node. </p> <p> This node is intended to allow camera images to be visualized in an orientation that is more intuitive than the hardware-constrained orientation of the physical camera. This is particularly helpful, for example, to show images from the PR2's forearm cameras with a consistent up direction, despite the fact that the forearms need to rotate in arbitrary ways during manipulation. </p> <p> It is not recommended to use the output from this node for further computation, as it interpolates the source image, introduces black borders, and does not output a camera_info. </p> |
meta-ros2-dashing |
| image-rotate |
2.2.1-1 |
<p> Contains a node that rotates an image stream in a way that minimizes the angle between a vector in some arbitrary frame and a vector in the camera frame. The frame of the outgoing image is published by the node. </p> <p> This node is intended to allow camera images to be visualized in an orientation that is more intuitive than the hardware-constrained orientation of the physical camera. This is particularly helpful, for example, to show images from the PR2's forearm cameras with a consistent up direction, despite the fact that the forearms need to rotate in arbitrary ways during manipulation. </p> <p> It is not recommended to use the output from this node for further computation, as it interpolates the source image, introduces black borders, and does not output a camera_info. </p> |
meta-ros2-foxy |
| image-rotate |
3.0.1-2 |
<p> Contains a node that rotates an image stream in a way that minimizes the angle between a vector in some arbitrary frame and a vector in the camera frame. The frame of the outgoing image is published by the node. </p> <p> This node is intended to allow camera images to be visualized in an orientation that is more intuitive than the hardware-constrained orientation of the physical camera. This is particularly helpful, for example, to show images from the PR2's forearm cameras with a consistent up direction, despite the fact that the forearms need to rotate in arbitrary ways during manipulation. </p> <p> It is not recommended to use the output from this node for further computation, as it interpolates the source image, introduces black borders, and does not output a camera_info. </p> |
meta-ros2-rolling |