| husky-controlblacklisted |
0.4.2-1 |
Clearpath Husky controller configurations |
meta-ros1-melodic |
| husky-description |
0.4.2-1 |
Clearpath Husky URDF description |
meta-ros1-melodic |
| husky-desktopblacklisted |
0.4.2-1 |
Metapackage for Clearpath Husky visualization software |
meta-ros1-melodic |
| husky-gazeboblacklisted |
0.4.2-1 |
Clearpath Husky Simulator bringup |
meta-ros1-melodic |
| husky-msgs |
0.4.2-1 |
Messages for Clearpath Husky |
meta-ros1-melodic |
| husky-navigation |
0.4.2-1 |
Autonomous mapping and navigation demos for the Clearpath Husky |
meta-ros1-melodic |
| husky-robotblacklisted |
0.4.2-1 |
Metapackage for Clearpath Husky robot software |
meta-ros1-melodic |
| husky-simulatorblacklisted |
0.4.2-1 |
Metapackage for Clearpath Husky simulation software |
meta-ros1-melodic |
| husky-vizblacklisted |
0.4.2-1 |
Visualization configuration for Clearpath Husky |
meta-ros1-melodic |
| hydrogen |
1.0.0~beta1+gitX |
Hydrogen is an advanced drum machine for GNU/Linux |
meta-musicians |
| ibeo-core |
2.0.2 |
The ibeo_core package |
meta-ros1-melodic |
| ibeo-lux |
2.0.1 |
ROS driver for IBEO LUX |
meta-ros1-melodic |
| ibeo-msgs |
3.0.1-1 |
The ibeo_msgs package |
meta-ros1-melodic |
| ibm-iotf-embeddedc |
1.0 |
Embedded C client for interacting with the IBM Watson Internet of Things Platform |
meta-iot-cloud |
| ieee80211-channels |
1.0.16-1 |
This package provides mapping from frequencies to IEEE802.11 channels and vice-versa. |
meta-ros1-melodic |
| ifm3dblacklisted |
0.6.2-2 |
ifm pmd-based 3D ToF Camera ROS package |
meta-ros1-melodic |
| ifm3d-coreblacklisted |
0.17.0-9 |
Library and Utilities for working with ifm pmd-based 3D ToF Cameras |
meta-ros1-melodic |
| ifm3d-core |
0.18.0-4 |
Library and Utilities for working with ifm pmd-based 3D ToF Cameras |
meta-ros2-foxy |
| ifoptblacklisted |
2.0.7-1 |
An <a href="http://eigen.tuxfamily.org">Eigen-</a> based interface to Nonlinear Programming solver <a href="https://projects.coin-or.org/Ipopt">Ipopt</a>. Inuitive and efficient C++ implementation of variables, costs and constraints using Eigen. Easy integration in your projects in catkin or pure cmake. |
meta-ros1-melodic |
| igvc-self-drive-descriptionblacklisted |
0.1.4-1 |
Meshes and URDF descriptions for Gem vehicle |
meta-ros1-melodic |
| igvc-self-drive-gazeboblacklisted |
0.1.4-1 |
Gazebo models and runtime configuration for igvc_self_drive simulator |
meta-ros1-melodic |
| igvc-self-drive-gazebo-pluginsblacklisted |
0.1.4-1 |
Gazebo plugins for IGVC Self-Drive simulator |
meta-ros1-melodic |
| igvc-self-drive-simblacklisted |
0.1.4-1 |
Metapackage for igvc_self_drive_sim |
meta-ros1-melodic |
| iio-oscilloscope |
0.14 |
Analog Devices IIO Oscilloscope app |
meta-gnss-sdr |
| iirob-filters |
0.9.1-1 |
The iirob_filters package implements following filters: 1) Low-Pass 2) Moving Mean 3) Gravity Compensation (used for force-torque sensors) 4) Threshold Filter 5) Kalman Filter |
meta-ros1-melodic |
| image-cb-detector |
0.10.14 |
Provide a node that extracts checkerboard corners from ROS images. This package is still experimental and unstable. Expect its APIs to change. |
meta-ros1-melodic |
| image-common |
1.11.13 |
Common code for working with images in ROS. |
meta-ros1-melodic |
| image-common |
2.2.1-1 |
Common code for working with images in ROS. |
meta-ros2-eloquent |
| image-common |
2.3.0-1 |
Common code for working with images in ROS. |
meta-ros2-foxy |
| image-geometry |
1.13.0 |
`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-melodic |
| 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.0-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-pipeline |
1.14.0-1 |
image_pipeline fills the gap between getting raw images from a camera driver and higher-level vision processing. |
meta-ros1-melodic |
| image-pipeline |
2.1.1-1 |
image_pipeline fills the gap between getting raw images from a camera driver and higher-level vision processing. |
meta-ros2-foxy |
| image-proc |
1.14.0-1 |
Single image rectification and color processing. |
meta-ros1-melodic |
| image-proc |
2.1.1-1 |
Single image rectification and color processing. |
meta-ros2-foxy |
| image-publisher |
1.14.0-1 |
<p> Contains a node publish an image stream from single image file or avi motion file. </p> |
meta-ros1-melodic |
| image-publisher |
2.1.1-1 |
<p> Contains a node publish an image stream from single image file or avi motion file. </p> |
meta-ros2-foxy |
| image-rotate |
1.14.0-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-ros1-melodic |
| 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-foxy |
| image-tools |
0.7.9-1 |
Tools to capture and play back images to and from DDS subscriptions and publications. |
meta-ros2-dashing |
| image-tools |
0.8.4-1 |
Tools to capture and play back images to and from DDS subscriptions and publications. |
meta-ros2-eloquent |
| image-tools |
0.9.3-1 |
Tools to capture and play back images to and from DDS subscriptions and publications. |
meta-ros2-foxy |
| image-transport |
1.11.13 |
image_transport should always be used to subscribe to and publish images. It provides transparent support for transporting images in low-bandwidth compressed formats. Examples (provided by separate plugin packages) include JPEG/PNG compression and Theora streaming video. |
meta-ros1-melodic |
| image-transport |
2.1.1-1 |
image_transport should always be used to subscribe to and publish images. It provides transparent support for transporting images in low-bandwidth compressed formats. Examples (provided by separate plugin packages) include JPEG/PNG compression and Theora streaming video. |
meta-ros2-dashing |
| image-transport |
2.2.1-1 |
image_transport should always be used to subscribe to and publish images. It provides transparent support for transporting images in low-bandwidth compressed formats. Examples (provided by separate plugin packages) include JPEG/PNG compression and Theora streaming video. |
meta-ros2-eloquent |
| image-transport |
2.3.0-1 |
image_transport should always be used to subscribe to and publish images. It provides transparent support for transporting images in low-bandwidth compressed formats. Examples (provided by separate plugin packages) include JPEG/PNG compression and Theora streaming video. |
meta-ros2-foxy |
| image-transport-plugins |
1.9.5 |
A set of plugins for publishing and subscribing to sensor_msgs/Image topics in representations other than raw pixel data. For example, for viewing a stream of images off-robot, a video codec will give much lower bandwidth and latency. For low frame rate tranport of high-definition images, you might prefer sending them as JPEG or PNG-compressed form. |
meta-ros1-melodic |
| image-transport-plugins |
2.1.0-1 |
A set of plugins for publishing and subscribing to sensor_msgs/Image topics in representations other than raw pixel data. For example, for viewing a stream of images off-robot, a video codec will give much lower bandwidth and latency. For low frame rate tranport of high-definition images, you might prefer sending them as JPEG or PNG-compressed form. |
meta-ros2-dashing |