ros-noetic/actionlib::ros-overlay
- Ebuilds: 1, Testing: 1.13.2-r1 Description:
The actionlib stack provides a standardized interface for
interfacing with preemptable tasks. Examples of this include moving
the base to a target location, performing a laser scan and returning
the resulting point cloud, detecting the handle of a door, etc.
Homepage:http://www.ros.org/wiki/actionlib License: BSD
ros-noetic/actionlib_msgs::ros-overlay
- Ebuilds: 1, Testing: 1.13.1-r1 Description:
actionlib_msgs defines the common messages to interact with an
action server and an action client. For full documentation of
the actionlib API see
the <a href="http://wiki.ros.org/actionlib">actionlib</a>
package.
Homepage:http://wiki.ros.org/actionlib_msgs License: BSD
ros-noetic/agni_tf_tools::ros-overlay
- Ebuilds: 1, Testing: 0.1.6-r1 Description:
This package provides a gui program as well as a rviz plugin to publish static transforms.
Both support the transformation between various Euler angle representations.
The rviz plugin also allows to configure the transform with an interactive marker.
Homepage:http://wiki.ros.org/agni_tf_tools License: BSD
ros-noetic/amcl::ros-overlay
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
<p>
amcl is a probabilistic localization system for a robot moving in
2D. It implements the adaptive (or KLD-sampling) Monte Carlo
localization approach (as described by Dieter Fox), which uses a
particle filter to track the pose of a robot against a known map.
</p>
<p>
This node is derived, with thanks, from Andrew Howard's excellent
'amcl' Player driver.
</p>
Homepage:http://wiki.ros.org/amcl License: LGPL-2
ros-noetic/angles::ros-overlay
- Ebuilds: 1, Testing: 1.9.13-r1 Description:
This package provides a set of simple math utilities to work
with angles. The utilities cover simple things like
normalizing an angle and conversion between degrees and
radians. But even if you're trying to calculate things like
the shortest angular distance between two joint space
positions of your robot, but the joint motion is constrained
by joint limits, this package is what you need. The code in
this package is stable and well tested. There are no plans for
major changes in the near future.
Homepage:http://wiki.ros.org/angles License: BSD
ros-noetic/apriltag_ros::ros-overlay
- Ebuilds: 1, Testing: 3.1.2-r1 Description:
A ROS wrapper of the AprilTag 3 visual fiducial detection
algorithm. Provides full access to the core AprilTag 3 algorithm's
customizations and makes the tag detection image and detected tags' poses
available over ROS topics (including tf). The core AprilTag 3 algorithm is
extended to allow the detection of tag bundles and a bundle calibration
script is provided (bundle detection is more accurate than single tag
detection). Continuous (camera image stream) and single image detector nodes
are available.
Homepage:http://www.ros.org/wiki/apriltag_ros License: BSD
ros-noetic/assisted_teleop::ros-overlay
- Ebuilds: 1, Testing: 0.3.4-r1 Description:
The assisted_teleop node subscribes to a desired trajectory topic
(geometry_msgs/Twist) and uses TrajectoryPlannerROS to find a valid
trajectory close to the desired trajectory before republishing. Useful for
filtering teleop commands while avoiding obstacles. This package also
contains LaserScanMaxRangeFilter, which is a LaserScan filter plugin that
takes max range values in a scan and turns them into valid values that are
slightly less than max range.
Homepage:http://wiki.ros.org/assisted_teleop License: BSD
ros-noetic/base_local_planner::ros-overlay
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
This package provides implementations of the Trajectory Rollout and Dynamic Window approaches to local robot navigation on a plane. Given a plan to follow and a costmap, the controller produces velocity commands to send to a mobile base. This package supports both holonomic and non-holonomic robots, any robot footprint that can be represented as a convex polygon or circle, and exposes its configuration as ROS parameters that can be set in a launch file. This package's ROS wrapper adheres to the BaseLocalPlanner interface specified in the <a href="http://wiki.ros.org/nav_core">nav_core</a> package.
Homepage:http://wiki.ros.org/base_local_planner License: BSD
ros-noetic/bond::ros-overlay
- Ebuilds: 1, Testing: 1.8.6-r1 Description:
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
Homepage:http://www.ros.org/wiki/bond License: BSD
ros-noetic/bond_core::ros-overlay
- Ebuilds: 1, Testing: 1.8.6-r1 Description:
A bond allows two processes, A and B, to know when the other has
terminated, either cleanly or by crashing. The bond remains
connected until it is either broken explicitly or until a
heartbeat times out.
Homepage:http://www.ros.org/wiki/bond_core License: BSD
ros-noetic/checkerboard_detector::ros-overlay
- Ebuilds: 1, Testing: 1.2.15-r1 Description:
Uses opencv to find checkboards and compute their 6D poses with respect to the image. Requires the image to be calibrated.<br/>
Parameters:<br/>
<ul>
<li>display - show the checkerboard detection</li>
<li>rect%d_size_x - size of checker in x direction</li>
<li>rect%d_size_y - size of checker in y direction</li>
<li>grid%d_size_x - number of checkers in x direction</li>
<li>grid%d_size_y - number of checkers in y direction</li>
</ul><br/>
There can be more than one grid%d declared, the numbers should grow consecutively starting at 0.
Homepage:https://jsk-docs.readthedocs.io/projects/jsk_recognition/en/latest/checkerboard_detector License: BSD
ros-noetic/class_loader::ros-overlay
- Ebuilds: 1, Testing: 0.5.0-r1 Description:
The class_loader package is a ROS-independent package for loading plugins during runtime and the foundation of the higher level ROS "pluginlib" library. class_loader utilizes the host operating system's runtime loader to open runtime libraries (e.g. .so/.dll files), introspect the library for exported plugin classes, and allows users to instantiate objects of said exported classes without the explicit declaration (i.e. header file) for those classes.
Homepage:http://ros.org/wiki/class_loader License: BSD
ros-noetic/cob_base_drive_chain::ros-overlay
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
This package contains classes that are able to control the platform of the Care-O-Bot. This means to establish a CAN communication to drive and steering motors of the platform and later send motion commands and receive motor information.
Homepage:http://ros.org/wiki/cob_base_drive_chain License: Apache-2.0
ros-noetic/cob_canopen_motor::ros-overlay
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
The package cob_canopen_motor implements a controller-drive component which is connected to a can-bus and works with a canopen-interface. "CanDriveItf" provides a - more or less - generic interface to the controller-drive components. "CanDrvie..." then implements a specific setup, e.g. an ELMO Harmonica Controller in case of the "CanDriveHarmonica".
Homepage:http://ros.org/wiki/cob_canopen_motor License: Apache-2.0
ros-noetic/cob_cartesian_controller::ros-overlay
- Ebuilds: 1, Testing: 0.8.13-r1 Description:
This package provides nodes that broadcast tf-frames along various (model-based) Cartesian paths (e.g. Linear, Circular).
The tf-frames are interpolated using a given velocity profile (e.g. Ramp, Sinoid) and can be used as targets for the cob_frame_tracker/cob_twist_controller.
Homepage:https://wiki.ros.org License: Apache-2.0
ros-noetic/cob_collision_monitor::ros-overlay
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
The collision monitor uses the planning scene monitor to read the state of the robot and check it for collision with itselt or the environment. It addition a ground plane is added in any case. Can be used as a stand-aloan node or a move_group capability.
Homepage:http://wiki.ros.org/cob_collision_monitor License: Apache-2.0
ros-noetic/cob_common::ros-overlay
- Ebuilds: 1, Testing: 0.7.4-r1 Description:
The cob_common stack hosts common packages that are used within the Care-O-bot repository. E.g. utility packages or common message and service definitions etc. Also the urdf desciption of the robot is located in this stack.
Homepage:http://ros.org/wiki/cob_common License: Apache-2.0
ros-noetic/cob_description::ros-overlay
- Ebuilds: 1, Testing: 0.7.4-r1 Description:
This package contains the description (mechanical, kinematic, visual,
etc.) of the Care-O-bot robot. The files in this package are parsed and used by
a variety of other components. Most users will not interact directly
with this package.
Homepage:http://ros.org/wiki/cob_description License: Apache-2.0
ros-noetic/cob_driver::ros-overlay
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
The cob_driver stack includes packages that provide access to the Care-O-bot hardware through ROS messages, services and actions. E.g. for mobile base, arm, camera sensors, laser scanners, etc...
Homepage:http://ros.org/wiki/cob_driver License: Apache-2.0
ros-noetic/cob_extern::ros-overlay
- Ebuilds: 1, Testing: 0.6.17-r1 Description:
The cob_extern stack contains third party libraries needed for operating Care-O-bot. The packages are downloaded from the manufactorers website and not changed in any way.
Homepage:http://ros.org/wiki/cob_extern License: ( LGPL-2 proprietary )
ros-noetic/cob_generic_can::ros-overlay
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
The package cob_generic_can provides an interface for nodes on a can-bus and examplary wrappers for two PeakSys-can-libs. When a can-bus-device is generated (for an example see base_dirve_chain) you can use generic_can to create as many itfs as there will be components communicating via this can-bus. Assign type of the can communication device (e.g. usb-to-can or can-card of a specific vendor) and can-address of the target device. This package comes with wrappers for PeakSys and PeakSysUSB adapters.
Homepage:http://ros.org/wiki/cob_generic_can License: Apache-2.0
ros-noetic/cob_linear_nav::ros-overlay
- Ebuilds: 1, Testing: 0.6.11-r1 Description:
cob_linear_nav provides a simple navigation instrument driving on a linear path from current position to goal without any planning or obstacle avoidance capabilites.
Obstacle avoidance should be carried out in other package, e.g. <a href="http://ros.org/wiki/cob_collision_velocity_filter">cob_collision_velocity_filter</a>.
Homepage:http://ros.org/wiki/cob_linear_nav License: Apache-2.0
ros-noetic/cob_map_accessibility_analysis::ros-overlay
- Ebuilds: 1, Testing: 0.6.11-r1 Description:
cob_map_accessibility_analysis receives the map from navigation as well as obstacles and inflates_obstacles topics to assemble a common obstacle map. Upon request, this node checks the accessibility of poses within thin map by (i) checking whether the pose itself is free and by (ii) checking whether there is a closed path from robot to the goal pose.
Homepage:http://ros.org/wiki/cob_map_accessibility_analysis License: Apache-2.0
ros-noetic/cob_mecanum_controller::ros-overlay
- Ebuilds: 1, Testing: 0.8.13-r1 Description:
The cob_mecanum_controller_node provides a lightweight base controller for mecanum drive robots.
The out/input for the wheel command/state are wheel velocities in rad/s for the wheels
[front left, front right, rear left, rear right]
Homepage:https://wiki.ros.org License: Apache-2.0
ros-noetic/cob_navigation_config::ros-overlay
- Ebuilds: 1, Testing: 0.6.11-r1 Description:
This package holds common configuration files for running the <a href="http://ros.org/wiki/move_base">move_base</a> node and other navigation related nodes on the <a href="http://ros.org/wiki/care-o-bot">Care-O-bot</a>.
Homepage:http://ros.org/wiki/cob_navigation_config License: Apache-2.0
ros-noetic/cob_navigation_global::ros-overlay
- Ebuilds: 1, Testing: 0.6.11-r1 Description:
This package holds config and launch files for running the <a href="http://ros.org/wiki/move_base">move_base</a> node on the <a href="http://ros.org/wiki/care-o-bot">Care-O-bot</a>.
The move_base node is configured to run over a pre-specified static map.
Homepage:http://ros.org/wiki/cob_navigation_global License: Apache-2.0
ros-noetic/cob_navigation_local::ros-overlay
- Ebuilds: 1, Testing: 0.6.11-r1 Description:
This package holds config and launch files for running the <a href="http://ros.org/wiki/move_base">move_base</a> node on the <a href="http://ros.org/wiki/care-o-bot">Care-O-bot</a> in an odometric frame.
No static map is needed for the move_base node in this configuration.
Homepage:http://ros.org/wiki/cob_navigation_local License: Apache-2.0
ros-noetic/cob_navigation_slam::ros-overlay
- Ebuilds: 1, Testing: 0.6.11-r1 Description:
This package provides launch files for running <a href="http://ros.org/wiki/care-o-bot">Care-O-bot</a> with the <a href="http://ros.org/wiki/gmapping">gmapping</a> slam package of ROS. It further provides the usual navigation functionalities as provided by the <a href="http://ros.org/wiki/move_base">move_base</a> node.
Homepage:http://ros.org/wiki/cob_navigation_slam License: Apache-2.0
ros-noetic/cob_reflector_referencing::ros-overlay
- Ebuilds: 1, Testing: 0.6.10-r1 Description:
This package provides a node broadcasting a tf frame based on reflector markers detected within sensor_msgs::LaserScan messages.
It can be used to position/reference a robot wrt to the reflektor markers.
Homepage:https://wiki.ros.org License: Apache-2.0
ros-noetic/cob_sick_lms1xx::ros-overlay
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
This package published a laser scan message out of a Sick LMS1xx laser scanner.
This version is made by fusion of ipa320/RCPRG_laser_drivers and ipa320/libLMS1xx repository. This package shuld have clearer structure and be easier to install.
Homepage:http://ros.org/wiki/cob_sick_lms1xx License: Apache-2.0
ros-noetic/cob_undercarriage_ctrl::ros-overlay
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
cob_undercarriage_ctrl implements a controller for the omnidirectional base of Care-O-bot 3 on joint level. For a given Pltf-Twist the according wheel steering angles and linear wheel velocities are calculated based on the principle of rigid body motion. Each joint is than controlled individually to achieve the computed position and velocity
Homepage:http://ros.org/wiki/cob_undercarriage_ctrl License: Apache-2.0
ros-noetic/cob_utilities::ros-overlay
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
Deprecated
"cob_utilities" subsumes a number of classes, which are used in the original COb3 software. E.g. "IniFile.h" supports the original inifile structure of Care-O-bot 3. "MathSup.h" provides some basic functions like conversion from degree to radion or norming of angles within +/- PI. The package is currently used while the drivers are ported to ROS and Orocos respectively. Midterm it shall be removed and the ROS structures shall be used for reading parameters during initialization. So, don't use this package in new code!
Homepage:http://ros.org/wiki/cob_utilities License: Apache-2.0
ros-noetic/collada_parser::ros-overlay
- Ebuilds: 1, Testing: 1.12.13-r1 Description:
This package contains a C++ parser for the Collada robot
description format. The parser reads a Collada XML robot
description, and creates a C++ URDF model. Although it is possible
to directly use this parser when working with Collada robot
descriptions, the preferred user API is found in the urdf package.
Homepage:http://ros.org/wiki/collada_parser License: BSD
ros-noetic/collada_urdf::ros-overlay
- Ebuilds: 1, Testing: 1.12.13-r1 Description:
This package contains a tool to convert Unified Robot Description Format (URDF) documents into COLLAborative Design Activity (COLLADA) documents.
Implements robot-specific COLLADA extensions as defined by
http://openrave.programmingvision.com/index.php/Started:COLLADA
Homepage:http://ros.org/wiki/collada_urdf License: BSD
ros-noetic/common_msgs::ros-overlay
- Ebuilds: 1, Testing: 1.13.1-r1 Description:
common_msgs contains messages that are widely used by other ROS packages.
These includes messages for
actions (<a href="http://wiki.ros.org/actionlib_msgs">actionlib_msgs</a>),
diagnostics (<a href="http://wiki.ros.org/diagnostic_msgs">diagnostic_msgs</a>),
geometric primitives (<a href="http://wiki.ros.org/geometry_msgs">geometry_msgs</a>),
robot navigation (<a href="http://wiki.ros.org/nav_msgs">nav_msgs</a>),
and common sensors (<a href="http://wiki.ros.org/sensor_msgs">sensor_msgs</a>), such as laser range finders, cameras, point clouds.
Homepage:http://wiki.ros.org/common_msgs License: BSD
ros-noetic/computer_status_msgs::ros-overlay
- Ebuilds: 1, Testing: 2.1.0-r1 Description:
Messages definitions for representing computer's hardware state, such as battery information, GPU, some miscellaneous sensors. Format is in ROS. Originally developed at <a href="https://github.com/PR2/pr2_common/tree/e64f0362b7bff0f4d1d9916f805cf91ad561b439/pr2_msgs">pr2_common repository</a>
Homepage:http://ros.org/wiki/computer_status_msgs License: BSD
ros-noetic/control_msgs::ros-overlay
- Ebuilds: 1, Testing: 1.5.2-r1 Description:
control_msgs contains base messages and actions useful for
controlling robots. It provides representations for controller
setpoints and joint and cartesian trajectories.
Homepage:http://ros.org/wiki/control_msgs License: BSD
ros-noetic/costmap_2d::ros-overlay
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
This package provides an implementation of a 2D costmap that takes in sensor
data from the world, builds a 2D or 3D occupancy grid of the data (depending
on whether a voxel based implementation is used), and inflates costs in a
2D costmap based on the occupancy grid and a user specified inflation radius.
This package also provides support for map_server based initialization of a
costmap, rolling window based costmaps, and parameter based subscription to
and configuration of sensor topics.
Homepage:http://wiki.ros.org/costmap_2d License: BSD
ros-noetic/cpp_common::ros-overlay
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
cpp_common contains C++ code for doing things that are not necessarily ROS
related, but are useful for multiple packages. This includes things like
the ROS_DEPRECATED and ROS_FORCE_INLINE macros, as well as code for getting
backtraces.
This package is a component of <a href="http://www.ros.org/wiki/roscpp">roscpp</a>.
Homepage:http://www.ros.org/wiki/cpp_common License: BSD
ros-noetic/csm::ros-overlay
- Ebuilds: 1, Testing: 1.0.2-r2 Description:
This is a ROS 3rd-party wrapper <a href="http://www.ros.org/reps/rep-0136.html">(see REP-136 for more detail)</a> of Andrea Censi's CSM package.
From <a href="http://censi.mit.edu/software/csm/">the official website</a>:
<ul>
The C(anonical) Scan Matcher (CSM) is a pure C implementation of a very fast variation of ICP using a point-to-line metric optimized for range-finder scan matching.
It is robust enough to be used in industrial prototypes of autonomous mobile robotics, for example at Kuka. CSM is used by a variety of people, though it is hard to keep track because of the open source distribution, especially as packaged in ROS. If you use this software for something cool, let me know.
</ul>
Homepage:http://censi.mit.edu/software/csm License: LGPL-2
ros-noetic/depth_image_proc::ros-overlay
- Ebuilds: 1, Testing: 1.16.0-r1 Description:
Contains nodelets for processing depth images such as those
produced by OpenNI camera. Functions include creating disparity
images and point clouds, as well as registering (reprojecting)
a depth image into another camera frame.
Homepage:http://ros.org/wiki/depth_image_proc License: BSD
ros-noetic/diagnostic_msgs::ros-overlay
- Ebuilds: 1, Testing: 1.13.1-r1 Description:
This package holds the diagnostic messages which provide the
standardized interface for the diagnostic and runtime monitoring
systems in ROS. These messages are currently used by
the <a href="http://wiki.ros.org/diagnostics">diagnostics</a>
Stack, which provides libraries for simple ways to set and access
the messages, as well as automated ways to process the diagnostic
data.
These messages are used for long term logging and will not be
changed unless there is a very important reason.
Homepage:http://wiki.ros.org/diagnostic_msgs License: BSD
ros-noetic/driver_common::ros-overlay
- Ebuilds: 1, Testing: 1.6.9-r1 Description:
The driver_common stack contains classes and tools that are useful
throughout the driver stacks. It currently contains:
driver_base: A base class for sensors to provide a consistent state machine
(retries, error handling, etc.) and interface
timestamp_tools: Classes to help timestamp hardware events
Homepage:http://www.ros.org/wiki/driver_common License: BSD
ros-noetic/dwa_local_planner::ros-overlay
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
This package provides an implementation of the Dynamic Window Approach to
local robot navigation on a plane. Given a global plan to follow and a
costmap, the local planner produces velocity commands to send to a mobile
base. This package supports any robot who's footprint can be represented as
a convex polygon or cicrle, and exposes its configuration as ROS parameters
that can be set in a launch file. The parameters for this planner are also
dynamically reconfigurable. This package's ROS wrapper adheres to the
BaseLocalPlanner interface specified in the <a href="http://wiki.ros.org/nav_core">nav_core</a> package.
Homepage:http://wiki.ros.org/dwa_local_planner License: BSD
ros-noetic/dynamixel_sdk::ros-overlay
- Ebuilds: 1, Testing: 3.7.51-r4 Description:
This package is wrapping version of ROBOTIS Dynamixel SDK for ROS. The ROBOTIS Dynamixel SDK, or SDK, is a software development library that provides Dynamixel control functions for packet communication. The API is designed for Dynamixel actuators and Dynamixel-based platforms.
Homepage:http://wiki.ros.org/dynamixel_sdk License: Apache-2.0
ros-noetic/dynamixel_workbench::ros-overlay
- Ebuilds: 1, Testing: 2.2.1-r1 Description:
Dynamixel-Workbench is dynamixel solution for ROS.
This metapackage allows you to easily change the ID, baudrate and operating mode of the Dynamixel.
Furthermore, it supports various controllers based on operating mode and Dynamixel SDK.
These controllers are commanded by operators.
Homepage:http://wiki.ros.org/dynamixel_workbench License: Apache-2.0
ros-noetic/dynamixel_workbench_toolbox::ros-overlay
- Ebuilds: 1, Testing: 2.2.1-r1 Description:
This package is composed of 'dynamixel_item', 'dynamixel_tool', 'dynamixel_driver' and 'dynamixel_workbench' class.
The 'dynamixel_item' is saved as control table item and information of Dynamixels.
The 'dynamixel_tool' class loads its by model number of Dynamixels.
The 'dynamixel_driver' class includes wraped function used in DYNAMIXEL SDK.
The 'dynamixel_workbench' class make simple to use Dynamixels
Homepage:http://wiki.ros.org/dynamixel_workbench_toolbox License: Apache-2.0
ros-noetic/ecl_containers::ros-overlay
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
The containers included here are intended to extend the stl containers.
In all cases, these implementations are designed to implement
c++ conveniences and safety where speed is not sacrificed.
Also includes techniques for memory debugging of common problems such
as buffer overruns.
Homepage:http://wiki.ros.org/ecl_containers License: BSD
ros-noetic/ecl_converters::ros-overlay
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Some fast/convenient type converters, mostly for char strings or strings.
These are not really fully fleshed out, alot of them could use the addition for
the whole range of fundamental types (e.g. all integers, not just int, unsigned int).
They will come as the need arises.
Homepage:http://wiki.ros.org/ecl_converters License: BSD
ros-noetic/ecl_errors::ros-overlay
- Ebuilds: 1, Testing: 0.61.6-r1 Description:
This library provides lean and mean error mechanisms.
It includes c style error functions as well as a few
useful macros. For higher level mechanisms,
refer to ecl_exceptions.
Homepage:http://wiki.ros.org/ecl_errors License: BSD
ros-noetic/ecl_exceptions::ros-overlay
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Template based exceptions - these are simple and practical
and avoid the proliferation of exception types. Although not
syntatactically ideal, it is convenient and eminently practical.
Homepage:http://wiki.ros.org/ecl_exceptions License: BSD
ros-noetic/ecl_io::ros-overlay
- Ebuilds: 1, Testing: 0.61.6-r1 Description:
Most implementations (windows, posix, ...) have slightly different api for
low level input-output functions. These are gathered here and re-represented
with a cross platform set of functions.
Homepage:http://wiki.ros.org/ecl_io License: BSD
ros-noetic/ecl_ipc::ros-overlay
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Interprocess mechanisms vary greatly across platforms - sysv, posix, win32, there
are more than a few. This package provides an infrastructure to allow for developing
cross platform c++ wrappers around the lower level c api's that handle these
mechanisms. These make it not only easier to utilise such mechanisms, but allow it
to be done consistently across platforms.
Homepage:http://wiki.ros.org/ecl_ipc License: BSD
ros-noetic/ecl_mpl::ros-overlay
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Metaprogramming tools move alot of runtime calculations to be shifted to
compile time. This has only very elementary structures at this stage.
Homepage:http://wiki.ros.org/ecl_mpl License: BSD
ros-noetic/ecl_navigation::ros-overlay
- Ebuilds: 1, Testing: 0.60.3-r2 Description:
This stack aims to bring the common tools and algorithms needed to
develop navigation algorithms, in particular slam. It does not focus on
the end-point solution, rather the tools needed to create a variety of
end-point solutions.
Homepage:http://www.ros.org/wiki/ecl_navigation License: BSD
ros-noetic/ecl_sigslots::ros-overlay
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Provides a signal/slot mechanism (in the same vein as qt sigslots,
boost::signals etc for intra-process communication. These include
some improvements - they do not need a preprocessor, are fully type safe,
allow for simple connections via a posix style string identifier
and are multithread-safe.
Homepage:http://ros.org/wiki/ecl_sigslots License: BSD
ros-noetic/ecl_threads::ros-overlay
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
This package provides the c++ extensions for a variety of threaded
programming tools. These are usually different on different
platforms, so the architecture for a cross-platform framework
is also implemented.
Homepage:http://wiki.ros.org/ecl_threads License: BSD
ros-noetic/ecl_time::ros-overlay
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Timing utilities are very dependent on the system api provided for their use.
This package provides a means for handling different timing models. Current support
- posix rt : complete.
- macosx : posix timers only, missing absolute timers.
- win : none.
Homepage:http://wiki.ros.org/ecl_time License: BSD
ros-noetic/eml::ros-overlay
- Ebuilds: 1, Testing: 1.8.15-r7 Description:
This is an implementation of the EtherCAT master protocol for the PR2 robot based on the work done at Flanders' Mechatronics Technology Centre.
Homepage:https://wiki.ros.org License: Binary Only
ros-noetic/exotica::ros-overlay
- Ebuilds: 1, Testing: 6.2.0-r1 Description:
The Extensible Optimization Toolset (EXOTica) is a library for defining problems for robot motion planning. This package serves similar to a metapackage and contains dependencies onto all core-released exotica packages. It also builds the documentation.
Homepage:https://github.com/ipab-slmc/exotica License: BSD
ros-noetic/exotica_val_description::ros-overlay
- Ebuilds: 1, Testing: 1.0.0-r1 Description:
val_description version including our updated meshes for unit testing and visualisation. Based on the OpenHumanoids fork of the val_description package by NASA JSC. The most current version of the original package can be found at http://gitlab.com/nasa-jsc-robotics/val_description
Homepage:https://wiki.ros.org License: NASA-1.3
ros-noetic/fetch_drivers::ros-overlay
- Ebuilds: 1, Testing: 0.9.3-r1 Description:
The public fetch_drivers package is a binary only release.
fetch_drivers contains both the drivers and firmware for the fetch and freight research robots.
There should be no reason to use these drivers unless you're running on a fetch or a freight research robot.
This package, is a cmake/make only package which installs the binaries for the drivers and firmware.
Homepage:https://wiki.ros.org/fetch_drivers License: Proprietary
ros-noetic/filters::ros-overlay
- Ebuilds: 1, Testing: 1.9.1-r1 Description:
This library provides a standardized interface for processing data as a sequence
of filters. This package contains a base class upon which to build specific implementations
as well as an interface which dynamically loads filters based on runtime parameters.
Homepage:http://ros.org/wiki/filters License: BSD
ros-noetic/fkie_master_discovery::ros-overlay
- Ebuilds: 1, Testing: 1.2.7-r1 Description:
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.
Homepage:http://ros.org/wiki/master_discovery_fkie License: BSD
ros-noetic/fkie_multimaster::ros-overlay
- Ebuilds: 1, Testing: 1.2.7-r1 Description:
The metapackage to combine the nodes required to establish and manage a multimaster network.
This requires no or minimal configuration. The changes are automatically detected and synchronized.
Homepage:http://ros.org/wiki/fkie_multimaster License: BSD
ros-noetic/fuse_core::ros-overlay
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
The fuse_core package provides the base class interfaces for the various fuse components. Concrete implementations of these
interfaces are provided in other packages.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/fuse_optimizers::ros-overlay
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
The fuse_optimizers package provides a set of optimizer implementations. An optimizer is the object responsible
for coordinating the sensors and motion model inputs, computing the optimal state values, and providing access to
to the optimal state via the publishers.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/fuse_variables::ros-overlay
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
The fuse_variables package provides a set of commonly used variable types, such as 2D and 3D positions,
orientations, velocities, and accelerations.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/gazebo_video_monitor_plugins::ros-overlay
- Ebuilds: 1, Testing: 0.7.0-r1 Description:
gazebo_video_monitor_plugins is a package that lets the user record videos of a <a href="http://gazebosim.org/">Gazebo</a> simulation. It provides a multicamera sensor that can be used for creating different types of videos with multiple views from inside the gazebo world. There is a number of plugins already available in the package, but more can be developed by the user, with minimal effort, to fit arbitrary use cases.
Homepage:https://wiki.ros.org License: GPL-3
ros-noetic/geometry::ros-overlay
- Ebuilds: 1, Testing: 1.13.2-r1 Description:
<p>A metapackage for geometry library suite.</p>
<p><b>Migration</b>: Since ROS Hydro, tf has been "deprecated" in favor of <a href="http://wiki.ros.org/tf2">tf2</a>. tf2 is an iteration on tf providing generally the same feature set more efficiently. As well as adding a few new features.<br/>
As tf2 is a major change the tf API has been maintained in its current form. Since tf2 has a superset of the tf features with a subset of the dependencies the tf implementation has been removed and replaced with calls to tf2 under the hood. This will mean that all users will be compatible with tf2. It is recommended for new work to use tf2 directly as it has a cleaner interface. However tf will continue to be supported for through at least J Turtle.
</p>
Homepage:http://www.ros.org/wiki/geometry License: BSD
ros-noetic/geometry_msgs::ros-overlay
- Ebuilds: 1, Testing: 1.13.1-r1 Description:
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.
Homepage:http://wiki.ros.org/geometry_msgs License: BSD
ros-noetic/gmapping::ros-overlay
- Ebuilds: 1, Testing: 1.4.2-r1 Description:
This package contains a ROS wrapper for OpenSlam's Gmapping.
The gmapping package provides laser-based SLAM (Simultaneous Localization and Mapping),
as a ROS node called slam_gmapping. Using slam_gmapping, you can create a 2-D occupancy
grid map (like a building floorplan) from laser and pose data collected by a mobile robot.
Homepage:http://ros.org/wiki/gmapping License: ( BSD Apache-2.0 )
ros-noetic/gmcl::ros-overlay
- Ebuilds: 1, Testing: 1.0.1-r3 Description:
<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>
Homepage:https://wiki.ros.org License: LGPL-2
ros-noetic/gpp_plugin::ros-overlay
- Ebuilds: 1, Testing: 0.1.0-r1 Description:
The gpp_plugin package offers a pipeline for running global
planners together with auxiliary pre- and post-processing functions
Homepage:https://wiki.ros.org License: MIT
ros-noetic/graft::ros-overlay
- Ebuilds: 1, Testing: 0.2.3-r1 Description:
Graft is not yet finished. It's intended to be a full replacement to
robot_pose_ekf, including native absolute references, and arbitrary
topic configuration.
If you try to use Graft now, please note that not all parameters are
configured and you will not always see a change in behavior by
modifying the parameters.
Homepage:http://ros.org/wiki/graft License: BSD
ros-noetic/hector_gazebo_plugins::ros-overlay
- Ebuilds: 1, Testing: 0.5.4-r1 Description:
hector_gazebo_plugins provides gazebo plugins from Team Hector.
Currently it contains a 6wd differential drive plugin, an IMU sensor plugin,
an earth magnetic field sensor plugin, a GPS sensor plugin and a
sonar ranger plugin.
Homepage:http://ros.org/wiki/hector_gazebo_plugins License: BSD
ros-noetic/hector_localization::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
The hector_localization stack is a collection of packages, that provide the full 6DOF pose of a robot or platform.
It uses various sensor sources, which are fused using an Extended Kalman filter.
Acceleration and angular rates from an inertial measurement unit (IMU) serve as primary measurements.
The usage of other sensors is application-dependent. The hector_localization stack currently supports
GPS, magnetometer, barometric pressure sensors and other external sources that provide a geometry_msgs/PoseWithCovariance
message via the poseupdate topic.
Homepage:http://ros.org/wiki/hector_localization License: BSD
ros-noetic/hector_mapping::ros-overlay
- Ebuilds: 1, Testing: 0.5.2-r4 Description:
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.
Homepage:http://ros.org/wiki/hector_mapping License: BSD
ros-noetic/hector_pose_estimation_core::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
hector_pose_estimation_core is the core package of the hector_localization stack. It contains the Extended Kalman Filter (EKF)
that estimates the 6DOF pose of the robot. hector_pose_estimation can be used either as a library, as a nodelet or as a standalone node.
Homepage:http://ros.org/wiki/hector_pose_estimation_core License: BSD
ros-noetic/hls_lfcd_lds_driver::ros-overlay
- Ebuilds: 1, Testing: 1.1.2-r1 Description:
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.
Homepage:http://wiki.ros.org/hls_lfcd_lds_driver License: BSD
ros-noetic/image_geometry::ros-overlay
- Ebuilds: 1, Testing: 1.15.0-r1 Description:
`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.
Homepage:http://www.ros.org/wiki/image_geometry License: BSD
ros-noetic/image_rotate::ros-overlay
- Ebuilds: 1, Testing: 1.16.0-r1 Description:
<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>
Homepage:http://ros.org/wiki/image_rotate License: BSD
ros-noetic/image_transport::ros-overlay
- Ebuilds: 1, Testing: 1.12.0-r1 Description:
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.
Homepage:http://ros.org/wiki/image_transport License: BSD
ros-noetic/image_transport_plugins::ros-overlay
- Ebuilds: 1, Testing: 1.14.0-r1 Description:
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.
Homepage:http://www.ros.org/wiki/image_transport_plugins License: BSD
ros-noetic/imu_complementary_filter::ros-overlay
- Ebuilds: 1, Testing: 1.2.3-r1 Description:
Filter which fuses angular velocities, accelerations, and (optionally) magnetic readings from a generic IMU device into a quaternion to represent the orientation of the device wrt the global frame. Based on the algorithm by Roberto G. Valenti etal. described in the paper "Keeping a Good Attitude: A Quaternion-Based Orientation Filter for IMUs and MARGs" available at http://www.mdpi.com/1424-8220/15/8/19302 .
Homepage:http://www.mdpi.com/1424-8220/15/8/19302 License: BSD
ros-noetic/imu_filter_madgwick::ros-overlay
- Ebuilds: 1, Testing: 1.2.3-r1 Description:
Filter which fuses angular velocities, accelerations, and (optionally) magnetic readings from a generic IMU device into an orientation. Based on code by Sebastian Madgwick, http://www.x-io.co.uk/node/8#open_source_ahrs_and_imu_algorithms.
Homepage:http://ros.org/wiki/imu_filter_madgwick License: GPL-1
ros-noetic/industrial_deprecated::ros-overlay
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
The Industrial deprecated package contains nodes, launch files, etc... that are slated for
deprecation. This package is the last place something will end up before being deleted.
If you are missing a package/node and find it's contents here, then you should consider
a replacement.
Homepage:http://ros.org/wiki/industrial_deprecated License: BSD
ros-noetic/ira_laser_tools::ros-overlay
- Ebuilds: 1, Testing: 1.0.7-r1 Description:
The ira_laser_tools package. These nodes are meant to provide some utils for lasers, like listen to different laser scan sources and merge them in a single scan or generate virtual laser scans from a pointcloud.
Homepage:http://www.ros.org/wiki/ira_laser_tools License: BSD
ros-noetic/iris_lama::ros-overlay
- Ebuilds: 1, Testing: 1.2.0-r1 Description:
IRIS package for Localization and Mapping (LaMa).
This packages includes the sparse-dense library for grid mapping,
a 2D localization algorithm based on scan matching, an online SLAM solution
with a dynamic likelihood field and a 2D RB Particle Filter SLAM solution
with multithreading.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/ivcon::ros-overlay
- Ebuilds: 1, Testing: 0.1.7-r1 Description:
Mesh Conversion Utility
Used to generate '.iv' files from '.stl' files. This package has not
been changed since 2001 and appears to be very stable. We plan on
keeping this package in this revision for mesh conversions. This
package is only available as a single source file for download. There
are no local modifications to this package.
Homepage:https://sourceforge.net/projects/ivcon/ License: GPL-1
ros-noetic/joint_states_settler::ros-overlay
- Ebuilds: 1, Testing: 0.10.15-r1 Description:
Provides a node that reports how long a subset of joints has been
settled. That is, it calculates how long a set of joints has remained
within a specified threshold. This package is experimental and unstable.
Expect its APIs to change.
Homepage:http://www.ros.org/wiki/joint_states_settler License: BSD
ros-noetic/joy::ros-overlay
- Ebuilds: 1, Testing: 1.15.1-r1 Description:
ROS driver for a generic Linux joystick.
The joy package contains joy_node, a node that interfaces a
generic Linux joystick to ROS. This node publishes a "Joy"
message, which contains the current state of each one of the
joystick's buttons and axes.
Homepage:http://www.ros.org/wiki/joy License: BSD
ros-noetic/kdl_parser::ros-overlay
- Ebuilds: 1, Testing: 1.14.1-r1 Description:
The Kinematics and Dynamics Library (KDL) defines a tree structure
to represent the kinematic and dynamic parameters of a robot
mechanism. <tt>kdl_parser</tt> provides tools to construct a KDL
tree from an XML robot representation in URDF.
Homepage:http://ros.org/wiki/kdl_parser License: BSD
ros-noetic/kdl_parser_py::ros-overlay
- Ebuilds: 1, Testing: 1.14.1-r1 Description:
The Kinematics and Dynamics Library (KDL) defines a tree structure
to represent the kinematic and dynamic parameters of a robot
mechanism. <tt>kdl_parser_py</tt> provides Python tools to construct a KDL
tree from an XML robot representation in URDF.
Homepage:http://ros.org/wiki/kdl_parser_py License: BSD
ros-noetic/kobuki_ftdi::ros-overlay
- Ebuilds: 1, Testing: 0.7.12-r1 Description:
Utilities for flashing and enabling Kobuki's USB connection.
This package contains tools for flashing the Kobuki's FTDI chip (usually done at the factory).
The special firmware for the FTDI chip (USB to serial converter) enables it to appear as
/dev/kobuki on the user's PC.
Homepage:http://ros.org/wiki/kobuki_ftdi License: BSD
ros-noetic/laser_geometry::ros-overlay
- Ebuilds: 1, Testing: 1.6.7-r1 Description:
This package contains a class for converting from a 2D laser scan as defined by
sensor_msgs/LaserScan into a point cloud as defined by sensor_msgs/PointCloud
or sensor_msgs/PointCloud2. In particular, it contains functionality to account
for the skew resulting from moving robots or tilting laser scanners.
Homepage:http://ros.org/wiki/laser_geometry License: BSD
ros-noetic/laser_scan_densifier::ros-overlay
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
The laser_scan_densifier takes in a LaserScan message and densifies it.
Node is inspired by laser_scan_sparsifier (http://wiki.ros.org/laser_scan_sparsifier).
Homepage:https://wiki.ros.org License: BSD
ros-noetic/laser_scan_matcher::ros-overlay
- Ebuilds: 1, Testing: 0.3.3-r1 Description:
<p>
An incremental laser scan matcher, using Andrea Censi's Canonical Scan Matcher (CSM) implementation. See <a href="http://censi.mit.edu/software/csm/">the web site</a> for more about CSM. NOTE the CSM library is licensed under the GNU Lesser General Public License v3, whereas the rest of the code is released under the BSD license.
</p>
Homepage:http://wiki.ros.org/laser_scan_matcher License: ( BSD LGPL-2 )
ros-noetic/laser_scan_splitter::ros-overlay
- Ebuilds: 1, Testing: 0.3.3-r1 Description:
The laser_scan_splitter takes in a LaserScan message and splits it into a number of other LaserScan messages. Each of the resulting laser scans can be assigned an arbitrary coordinate frame, and is published on a separate topic.
Homepage:http://wiki.ros.org/laser_scan_splitter License: BSD
ros-noetic/libdlib::ros-overlay
- Ebuilds: 1, Testing: 0.6.17-r1 Description:
This package wraps the external c++ library dlib (http://dlib.net/) in a ROS package, so other packages can use it. The code was obtained from https://github.com/davisking/dlib . For further descriptions and tutorials see the Makefile.tarball and http://dlib.net/ .
Homepage:http://dlib.net/ License: Boost-1.0
ros-noetic/libmavconn::ros-overlay
- Ebuilds: 1, Testing: 1.10.0-r1 Description:
MAVLink communication library.
This library provide unified connection handling classes
and URL to connection object mapper.
This library can be used in standalone programs.
Homepage:http://wiki.ros.org/mavros License: ( GPL-3 LGPL-2 BSD )
ros-noetic/librealsense2::ros-overlay
- Ebuilds: 1, Testing: 2.50.0-r1 Description:
Library for capturing data from the Intel(R) RealSense(TM) SR300, D400, L500 Depth cameras and T2xx Tracking devices. This effort was initiated to better support researchers, creative coders, and app developers in domains such as robotics, virtual reality, and the internet of things. Several often-requested features of RealSense(TM); devices are implemented in this project.
Homepage:https://github.com/IntelRealSense/librealsense/ License: Apache-2.0
ros-noetic/lockfree::ros-overlay
- Ebuilds: 1, Testing: 1.0.25-r1 Description:
The lockfree package contains lock-free data structures for use in multithreaded programming. These
kinds of data structures are generally not as easy to use as single-threaded equivalents, and are not
always faster. If you don't know you need to use one, try another structure with a lock around it
first.
Homepage:http://ros.org/wiki/lockfree License: BSD
ros-noetic/locomotor::ros-overlay
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Locomotor is an extensible path planning coordination engine that replaces move_base. The goal is to provide a mechanism for controlling what happens when the global and local planners succeed and fail. It leverages ROS callback queues to coordinate multiple threads.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/log_view::ros-overlay
- Ebuilds: 1, Testing: 0.1.3-r1 Description:
The log_view package provides a ncurses based terminal GUI for
viewing and filtering published ROS log messages.
This is an alternative to rqt_console and swri_console that doesn't depend
on qt and can be run directly in a terminal.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/map_server::ros-overlay
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
map_server provides the <tt>map_server</tt> ROS <a href="http://www.ros.org/wiki/Nodes">Node</a>, which offers map data as a ROS <a href="http://www.ros.org/wiki/Services">Service</a>. It also provides the <tt>map_saver</tt> command-line utility, which allows dynamically generated maps to be saved to file.
Homepage:http://wiki.ros.org/map_server License: BSD
ros-noetic/marker_msgs::ros-overlay
- Ebuilds: 1, Testing: 0.0.6-r7 Description:
The marker_msgs package contains messages usable to setup a marker/fiducial system.
The package distinguishes between two types of messages.
First messages to describe the properties of a marker/fiducial detection system and the detected markers.
Secondly messages used to represent a map of markers/features with covariances as it would be produced by a SLAM system or published by a map server for self-localization.
Homepage:http://wiki.ros.org/marker_msgs License: BSD
ros-noetic/mbf_abstract_core::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
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.
Homepage:http://wiki.ros.org/mbf_abstract_core License: BSD
ros-noetic/mbf_abstract_nav::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
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.
Homepage:http://wiki.ros.org/move_base_flex License: BSD
ros-noetic/mbf_costmap_core::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
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.
Homepage:http://wiki.ros.org/move_base_flex/mbf_costmap_core License: BSD
ros-noetic/mbf_costmap_nav::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
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.
Homepage:http://wiki.ros.org/move_base_flex License: BSD
ros-noetic/mbf_msgs::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
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>.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/mbf_simple_nav::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
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>.
Homepage:http://wiki.ros.org/move_base_flex License: BSD
ros-noetic/mesh_navigation::ros-overlay
- Ebuilds: 1, Testing: 1.0.1-r2 Description:
The mesh_navigation package provides a layered mesh_map implementation, a Move Base Flex mesh navigation server, as well as mesh navigation plugins for path planning and navigation control.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/message_to_tf::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
message_to_tf translates pose information from different kind of common_msgs message types to tf. Currently the node supports nav_msgs/Odometry, geometry_msgs/PoseStamped and sensor_msgs/Imu messages as input.
The resulting transform is divided into three subtransforms with intermediate frames for the footprint and the stabilized base frame (without roll and pitch).
Homepage:http://ros.org/wiki/message_to_tf License: BSD
ros-noetic/mk::ros-overlay
- Ebuilds: 1, Testing: 1.15.8-r1 Description:
A collection of .mk include files for building ROS architectural elements.
Most package authors should use cmake .mk, which calls CMake for the build of the package.
The other files in this package are intended for use in exotic situations that mostly arise when importing 3rdparty code.
Homepage:http://www.ros.org/wiki/ROS License: BSD
ros-noetic/mocap_optitrack::ros-overlay
- Ebuilds: 1, Testing: 0.1.3-r1 Description:
Streaming of OptiTrack mocap data to tf
<p>
This package contains a node that translates motion capture data from an
OptiTrack rig to tf transforms, poses and 2D poses. The node receives
packets that are streamed by a NatNet compliant source, decodes them and
broadcasts the poses of configured rigid bodies as tf transforms, poses,
and/or 2D poses.
</p>
<p>
Currently, this node supports the NatNet streaming protocol v3.0
</p>
<p>
Copyright (c) 2013, Clearpath Robotics<br/>
Copyright (c) 2010, University of Bonn, Computer Science Institute VI<br/>
All rights reserved.
</p>
Homepage:http://ros.org/wiki/mocap_optitrack License: BSD
ros-noetic/move_base::ros-overlay
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
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.
Homepage:http://wiki.ros.org/move_base License: BSD
ros-noetic/move_base_flex::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
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>.
Homepage:http://wiki.ros.org/move_base_flex License: BSD
ros-noetic/moveit::ros-overlay
- Ebuilds: 1, Testing: 1.1.6-r1 Description:
Meta package that contains all essential package of MoveIt. Until Summer 2016 MoveIt had been developed over multiple repositories, where developers' usability and maintenance effort was non-trivial. See <a href="http://discourse.ros.org/t/migration-to-one-github-repo-for-moveit/266/34">the detailed discussion for the merge of several repositories</a>.
Homepage:http://moveit.ros.org License: BSD
ros-noetic/moveit_opw_kinematics_plugin::ros-overlay
- Ebuilds: 1, Testing: 0.3.1-r2 Description:
<p>
MoveIt kinematics plugin for industrial robots.
</p>
<p>
This plugin uses an analytical inverse kinematic library, opw_kinematics,
to calculate the inverse kinematics for industrial robots with 6 degrees of freedom,
two parallel joints, and a spherical wrist.
</p>
Homepage:https://wiki.ros.org License: Apache-2.0
ros-noetic/mpc_local_planner::ros-overlay
- Ebuilds: 1, Testing: 0.0.3-r1 Description:
The mpc_local_planner package implements a plugin
to the base_local_planner of the 2D navigation stack.
It provides a generic and versatile model predictive control implementation
with minimum-time and quadratic-form receding-horizon configurations.
Homepage:http://wiki.ros.org/mpc_local_planner License: GPL-3
ros-noetic/nav_core::ros-overlay
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
This package provides common interfaces for navigation specific robot actions. Currently, this package provides the BaseGlobalPlanner, BaseLocalPlanner, and RecoveryBehavior interfaces, which can be used to build actions that can easily swap their planner, local controller, or recovery behavior for new versions adhering to the same interface.
Homepage:http://wiki.ros.org/nav_core License: BSD
ros-noetic/nav_core_adapter::ros-overlay
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
This package contains adapters for using `nav_core` plugins as `nav_core2` plugins and vice versa (more or less).
See README.md for more information.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/navfn::ros-overlay
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
navfn provides a fast interpolated navigation function that can be used to create plans for
a mobile base. The planner assumes a circular robot and operates on a costmap to find a
minimum cost plan from a start point to an end point in a grid. The navigation function is
computed with Dijkstra's algorithm, but support for an A* heuristic may also be added in the
near future. navfn also provides a ROS wrapper for the navfn planner that adheres to the
nav_core::BaseGlobalPlanner interface specified in <a href="http://wiki.ros.org/nav_core">nav_core</a>.
Homepage:http://wiki.ros.org/navfn License: BSD
ros-noetic/navigation::ros-overlay
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
A 2D navigation stack that takes in information from odometry, sensor
streams, and a goal pose and outputs safe velocity commands that are sent
to a mobile base.
Homepage:http://wiki.ros.org/navigation License: ( BSD LGPL-2 LGPL-2 )
ros-noetic/neo_local_planner::ros-overlay
- Ebuilds: 1, Testing: 1.0.1-r1 Description:
This package provides a spline based implementation to local robot navigation on a plane.
This package's ROS wrapper adheres to the
BaseLocalPlanner interface specified in the <a href="http://wiki.ros.org/nav_core">nav_core</a> package.
Homepage:http://wiki.ros.org/base_local_planner License: BSD
ros-noetic/nodelet::ros-overlay
- Ebuilds: 1, Testing: 1.10.2-r1 Description:
The nodelet package is designed to provide a way to run multiple
algorithms in the same process with zero copy transport between
algorithms.
This package provides both the nodelet base class needed for
implementing a nodelet, as well as the NodeletLoader class used
for instantiating nodelets.
Homepage:http://ros.org/wiki/nodelet License: BSD
ros-noetic/octomap_server::ros-overlay
- Ebuilds: 1, Testing: 0.6.6-r1 Description:
octomap_server loads a 3D map (as Octree-based OctoMap) and distributes it to other nodes in a compact binary format. It also allows to incrementally build 3D OctoMaps, and provides map saving in the node octomap_saver.
Homepage:http://www.ros.org/wiki/octomap_server License: BSD
ros-noetic/opencv_apps::ros-overlay
- Ebuilds: 1, Testing: 2.0.2-r1 Description:
<p>opencv_apps provides various nodes that run internally OpenCV's functionalities and publish the result as ROS topics. With opencv_apps, you can skip writing OpenCV application codes for a lot of its functionalities by simply running a launch file that corresponds to OpenCV's functionality you want.</p>
<ul>
<li>You can have a look at all launch files provided here (be sure to choose the correct branch. As of Sept. 2016 indigo branch is used for ROS Indigo, Jade, and Kinetic distros).</li>
<li>Some of the features covered by opencv_apps are explained in <a href="http://wiki.ros.org/opencv_apps">the wiki</a>.</li>
</ul>
<p>The most of code is originally taken from https://github.com/Itseez/opencv/tree/master/samples/cpp</p>
Homepage:https://wiki.ros.org License: BSD
ros-noetic/opengm::ros-overlay
- Ebuilds: 1, Testing: 0.6.17-r1 Description:
This package wraps the external c++ library opengm in a ROS package, so other packages can use it. It downloads the source code of it and then unzips it. The library is a header-only library with command line interfaces, which aren't used, so it doesn't gets build. For further descriptions and tutorials see the Makefile.tarball and https://github.com/opengm/opengm .
Copyright (C) 2013 Bjoern Andres, Thorsten Beier and Joerg H.~Kappes.
Homepage:http://hciweb2.iwr.uni-heidelberg.de/opengm/ License: MIT
ros-noetic/openni2_camera::ros-overlay
- Ebuilds: 1, Testing: 1.5.1-r1 Description:
Drivers for the Asus Xtion and Primesense Devices. For using a kinect
with ROS, try the <a href="http://wiki.ros.org/freenect_stack">freenect stack</a>
Homepage:https://wiki.ros.org License: BSD
ros-noetic/opw_kinematics::ros-overlay
- Ebuilds: 1, Testing: 0.4.4-r1 Description:
A simple, analytical inverse kinematic library for industrial robots with parallel bases and
spherical wrists. Based on the paper "An Analytical Solution of the Inverse Kinematics Problem
of Industrial Serial Manipulators with an Ortho-parallel Basis and a Spherical Wrist" by
Mathias Brandstötter, Arthur Angerer, and Michael Hofbaur.
Homepage:https://wiki.ros.org License: Apache-2.0
ros-noetic/pass_through_controllers::ros-overlay
- Ebuilds: 1, Testing: 0.1.0-r1 Description:
Trajectory controllers (joint-based and Cartesian) that forward trajectories
directly to a robot controller and let it handle trajectory interpolation and execution.
Homepage:https://wiki.ros.org License: Apache-2.0
ros-noetic/pcl_ros::ros-overlay
- Ebuilds: 1, Testing: 1.7.3-r1 Description:
PCL (Point Cloud Library) ROS interface stack. PCL-ROS is the preferred
bridge for 3D applications involving n-D Point Clouds and 3D geometry
processing in ROS.
Homepage:http://ros.org/wiki/perception_pcl License: BSD
ros-noetic/pilz_control::ros-overlay
- Ebuilds: 1, Testing: 0.6.0-r1 Description:
This package provides a specialized joint_trajectory_controller that can be moved into holding state via service call.
No further trajectories will be accepted/followed in this state.
Homepage:http://ros.org/wiki/pilz_control License: Apache-2.0
ros-noetic/pluginlib::ros-overlay
- Ebuilds: 1, Testing: 1.13.0-r1 Description:
The pluginlib package provides tools for writing and dynamically loading plugins using the ROS build infrastructure.
To work, these tools require plugin providers to register their plugins in the package.xml of their package.
Homepage:http://www.ros.org/wiki/pluginlib License: BSD
ros-noetic/polled_camera::ros-overlay
- Ebuilds: 1, Testing: 1.12.0-r1 Description:
polled_camera contains a service and C++ helper classes for implementing a polled
camera driver node and requesting images from it. The package is currently for
internal use as the API is still under development.
Homepage:http://ros.org/wiki/polled_camera License: BSD
ros-noetic/pr2_camera_synchronizer::ros-overlay
- Ebuilds: 1, Testing: 1.6.32-r1 Description:
<p>
The PR2 is equipped with a texture projector that can be used to
project a texture onto featureless surfaces, allowing their
three-dimensional structure to be determined using stereoscopy. The
projector operates in a pulsed mode, producing brief (2ms) pulses of
light. Cameras that want to see the texture must expose during the
projector pulse; other cameras should be expose while the projector is
off.
</p>
<p>
This package contains the pr2_projector_synchronizer node. Based on its dynamically reconfigurable parameters, this node controls the projector pulsing, and sets up triggering of the WGE100 cameras.
</p>
Homepage:http://pr.willowgarage.com/wiki/pr2_camera_synchronizer License: BSD
ros-noetic/pr2_common::ros-overlay
- Ebuilds: 1, Testing: 1.13.0-r1 Description:
URDF description of the robot kinematics and dynamics, 3D models of robot components, information required for gazebo to simulate the PR2, and messages specific to the PR2 such as detailed information about its power board and fingertip pressure sensors.
Homepage:http://ros.org/wiki/pr2_common License: BSD
ros-noetic/pr2_controller_interface::ros-overlay
- Ebuilds: 1, Testing: 1.8.18-r1 Description:
This package specifies the interface to a realtime controller. A
controller that implements this interface can be executed by the
<a href="http://www.ros.org/wiki/pr2_controller_manager">controller
manager</a> in the real time control loop. The package basically
contains the C++ controller base class that all controllers need to
inherit from.
Homepage:http://ros.org/wiki/pr2_controller_interface License: BSD
ros-noetic/pr2_description::ros-overlay
- Ebuilds: 1, Testing: 1.13.0-r1 Description:
This package contains the description (mechanical, kinematic, visual,
etc.) of the PR2 robot. The files in this package are parsed and used by
a variety of other components. Most users will not interact directly
with this package.
Homepage:http://ros.org/wiki/pr2_description License: BSD
ros-noetic/pr2_gripper_action::ros-overlay
- Ebuilds: 1, Testing: 1.10.18-r1 Description:
The pr2_gripper_action provides an action interface for using the
gripper. Users can specify what position to move to (while limiting the
force) and the action will report success when the position is reached or
failure when the gripper cannot move any longer.
Homepage:http://ros.org/wiki/pr2_gripper_action License: BSD
ros-noetic/pr2_hardware_interface::ros-overlay
- Ebuilds: 1, Testing: 1.8.18-r1 Description:
This package contains the C++ interfaces to the PR2 hardware
components that are controlled over EtherCAT. This includes the
motors and encoders needed to control the PR2 mechanism, as well as
components like the pressure sensors in the fingertips, camera
triggers, etc... All of the hardware components in this interface are
directly available to the controllers inside the hard realtime
control loop.
Homepage:http://ros.org/wiki/pr2_hardware_interface License: BSD
ros-noetic/pr2_machine::ros-overlay
- Ebuilds: 1, Testing: 1.13.0-r1 Description:
This package contains the xxx.machine files that describe the different hosts a node can be spawned on. Currently there is one machine file for the pr2 robot, and one for the simulated pr2 robot.
Homepage:http://ros.org/wiki/pr2_machine License: BSD
ros-noetic/pr2_mechanism_model::ros-overlay
- Ebuilds: 1, Testing: 1.8.18-r1 Description:
<p>
This package contains the robot model that is used by the realtime
controllers
inside <a href="http://www.ros.org/wiki/pr2_controller_manager">controller
manager</a>. This robot model focuses on controlling the robot
mechanism in a realtime control loop, and therefore it only contains
the components of a robot that are relevant in realtime: the robot
joints (with encoders, transmisisons and actuators) and the
kinematic/dynamic model of the robot.
</p>
<p>
The pr2_mechanism_model package is well tested and is released with a stable API.
</p>
Homepage:http://ros.org/wiki/pr2_mechanism_model License: BSD
ros-noetic/pr2_run_stop_auto_restart::ros-overlay
- Ebuilds: 1, Testing: 1.6.32-r1 Description:
This package provides a node that monitors the state of the run stops of the pr2_robot. When the state of the
run stop changes from off to on, this node will automatically enable the power to the motors, and reset
the motors. This allows you to use the run stop as a 'pause' button. By using the run stop as a tool to
power up the robot, the run stop is also in reach of the user once the robot starts moving.
Homepage:http://ros.org/wiki/pr2_run_stop_auto_restart License: BSD
ros-noetic/pr2_tilt_laser_interface::ros-overlay
- Ebuilds: 1, Testing: 0.0.12-r1 Description:
Provides a set of tools/actions for manipulating the pr2's tilting
laser. Simplifies previously complex tasks, such as fetching
a single sweep, given a set of desired parameters for both the laser
driver and tilting platform.
Homepage:http://ros.org/wiki/pr2_tilt_laser License: BSD
ros-noetic/pr2_tuckarm::ros-overlay
- Ebuilds: 1, Testing: 0.6.2-r1 Description:
Tucks the arms of the PR2 robot into a safe position for moving the base of the robot.
This also moves the arms out of the view of the tilting laser scanner, as much as possible.
Homepage:http://ros.org/wiki/pr2_tuckarm License: BSD
ros-noetic/ps3joy::ros-overlay
- Ebuilds: 1, Testing: 1.15.0-r1 Description:
Playstation 3 SIXAXIS or DUAL SHOCK 3 joystick driver.
Driver for the Sony PlayStation 3 SIXAXIS or DUAL SHOCK 3
joysticks. In its current state, this driver is not compatible
with the use of other Bluetooth HID devices. The driver listens
for a connection on the HID ports, starts the joystick
streaming data, and passes the data to the Linux uinput device
so that it shows up as a normal joystick.
Homepage:http://www.ros.org/wiki/ps3joy License: BSD
ros-noetic/python_qt_binding::ros-overlay
- Ebuilds: 1, Testing: 0.4.4-r1 Description:
This stack provides Python bindings for Qt.
There are two providers: pyside and pyqt. PySide is released under
the LGPL. PyQt is released under the GPL.
Both the bindings and tools to build bindings are included from each
available provider. For PySide, it is called "Shiboken". For PyQt,
this is called "SIP".
Also provided is adapter code to make the user's Python code
independent of which binding provider was actually used which makes
it very easy to switch between these.
Homepage:http://ros.org/wiki/python_qt_binding License: BSD
ros-noetic/qt_gui::ros-overlay
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
qt_gui provides the infrastructure for an integrated graphical user interface based on Qt.
It is extensible with Python- and C++-based plugins (implemented in separate packages) which can contribute arbitrary widgets.
It requires either PyQt or PySide bindings.
Homepage:http://ros.org/wiki/qt_gui License: BSD
ros-noetic/qt_gui_cpp::ros-overlay
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
qt_gui_cpp provides the foundation for C++-bindings for qt_gui and creates bindings for every generator available.
At least one specific binding must be available in order to use C++-plugins.
Homepage:http://ros.org/wiki/qt_gui_cpp License: BSD
ros-noetic/random_numbers::ros-overlay
- Ebuilds: 1, Testing: 0.3.2-r1 Description:
This library contains wrappers for generating floating point values, integers, quaternions using boost libraries.
The constructor of the wrapper is guaranteed to be thread safe and initialize its random number generator to a random seed.
Seeds are obtained using a separate and different random number generator.
Homepage:http://ros.org/wiki/random_numbers License: BSD
ros-noetic/raw_description::ros-overlay
- Ebuilds: 1, Testing: 0.7.4-r1 Description:
This package contains the description (mechanical, kinematic, visual,
etc.) of the Care-O-bot robot. The files in this package are parsed and used by
a variety of other components. Most users will not interact directly
with this package.
Homepage:http://ros.org/wiki/cob_description License: Apache-2.0
ros-noetic/rc_dynamics_api::ros-overlay
- Ebuilds: 1, Testing: 0.10.1-r1 Description:
The rc_dynamics_api provides an API for easy handling of the dynamic-state data
streams provided by Roboception's stereo camera with self-localization.
See http://rc-visard.com
Dynamic-state estimates of the rc_visard relate to its self-localization and
ego-motion estimation. These states refer to rc_visard's current pose,
velocity, or acceleration and are published on demand via several data streams.
For a complete list and descriptions of these dynamics states and the
respective data streams please refer to rc_visard's user manual.
Homepage:http://rc-visard.com License: BSD
ros-noetic/rc_genicam_api::ros-overlay
- Ebuilds: 1, Testing: 2.5.12-r1 Description:
GenICam/GigE Vision Convenience Layer.
This package combines the Roboception convenience layer for images with the
GenICam reference implementation and a GigE Vision transport layer. It is a
self contained package that permits configuration and image streaming of
GenICam / GigE Vision 2.0 compatible cameras like the Roboception rc_visard.
This package also provides some tools that can be called from the command line
for discovering cameras, changing their configuration and streaming images.
Although the tools are meant to be useful when working in a shell or in a
script, their main purpose is to serve as example on how to use the API for
reading and setting parameters, streaming and synchronizing images.
See LICENSE.md for licensing terms of the different parts.
Homepage:http://wiki.ros.org/rc_genicam_api License: BSD
ros-noetic/resource_retriever::ros-overlay
- Ebuilds: 1, Testing: 1.12.6-r1 Description:
This package retrieves data from url-format files such as http://,
ftp://, package:// file://, etc., and loads the data into memory.
The package:// url for ros packages is translated into a local
file:// url. The resourse retriever was initially designed to load
mesh files into memory, but it can be used for any type of
data. The resource retriever is based on the the libcurl library.
Homepage:http://ros.org/wiki/resource_retriever License: BSD
ros-noetic/robot_state_publisher::ros-overlay
- Ebuilds: 1, Testing: 1.15.2-r1 Description:
This package allows you to publish the state of a robot to
<a href="http://ros.org/wiki/tf2">tf2</a>. Once the state gets published, it is
available to all components in the system that also use <tt>tf2</tt>.
The package takes the joint angles of the robot as input
and publishes the 3D poses of the robot links, using a kinematic
tree model of the robot. The package can both be used as a library
and as a ROS node. This package has been well tested and the code
is stable. No major changes are planned in the near future.
Homepage:http://wiki.ros.org/robot_state_publisher License: BSD
ros-noetic/robot_upstart::ros-overlay
- Ebuilds: 1, Testing: 0.4.1-r1 Description:
The robot_upstart package provides scripts which may be used to install
and uninstall Ubuntu Linux upstart jobs which launch groups of roslaunch files.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/rosatomic::ros-overlay
- Ebuilds: 1, Testing: 1.0.25-r1 Description:
rosatomic provides the C++11-style atomic operations by pulling symbols from the proposed Boost.Atomic
package into the ros namespace. Once C++11-style atomics (std::atomic) are available from compilers, rosatomic will
conditionally use those instead.
Homepage:http://ros.org/wiki/rosatomic License: ( BSD Boost-1.0 )
ros-noetic/rosbag::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
This is a set of tools for recording from and playing back to ROS
topics. It is intended to be high performance and avoids
deserialization and reserialization of the messages.
Homepage:http://wiki.ros.org/rosbag License: BSD
ros-noetic/rosbridge_suite::ros-overlay
- Ebuilds: 1, Testing: 0.11.13-r1 Description:
Rosbridge provides a JSON API to ROS functionality for non-ROS programs.
There are a variety of front ends that interface with rosbridge, including
a WebSocket server for web browsers to interact with.
Rosbridge_suite is a meta-package containing rosbridge, various front end
packages for rosbridge like a WebSocket package, and helper packages.
Homepage:http://ros.org/wiki/rosbridge_suite License: BSD
ros-noetic/roscpp::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
roscpp is a C++ implementation of ROS. It provides
a <a href="http://wiki.ros.org/Client%20Libraries">client
library</a> that enables C++ programmers to quickly interface with
ROS <a href="http://ros.org/wiki/Topics">Topics</a>,
<a href="http://ros.org/wiki/Services">Services</a>,
and <a href="http://ros.org/wiki/Parameter Server">Parameters</a>.
roscpp is the most widely used ROS client library and is designed to
be the high-performance library for ROS.
Homepage:http://ros.org/wiki/roscpp License: BSD
ros-noetic/roscpp_serialization::ros-overlay
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
roscpp_serialization contains the code for serialization as described in
<a href="http://www.ros.org/wiki/roscpp/Overview/MessagesSerializationAndAdaptingTypes">MessagesSerializationAndAdaptingTypes</a>.
This package is a component of <a href="http://www.ros.org/wiki/roscpp">roscpp</a>.
Homepage:http://ros.org/wiki/roscpp_serialization License: BSD
ros-noetic/roscpp_traits::ros-overlay
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
roscpp_traits contains the message traits code as described in
<a href="http://www.ros.org/wiki/roscpp/Overview/MessagesTraits">MessagesTraits</a>.
This package is a component of <a href="http://www.ros.org/wiki/roscpp">roscpp</a>.
Homepage:http://ros.org/wiki/roscpp_traits License: BSD
ros-noetic/roscreate::ros-overlay
- Ebuilds: 1, Testing: 1.15.8-r1 Description:
roscreate contains a tool that assists in the creation of ROS filesystem resources.
It provides: <tt>roscreate-pkg</tt>, which creates a new package directory,
including the appropriate build and manifest files.
Homepage:http://wiki.ros.org/roscreate License: BSD
ros-noetic/rosfmt::ros-overlay
- Ebuilds: 1, Testing: 7.0.0-r1 Description:
fmt is an open-source formatting library for C++.
It can be used as a safe and fast alternative to (s)printf and IOStreams.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/rosgraph::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
rosgraph contains the rosgraph command-line tool, which prints
information about the ROS Computation Graph. It also provides an
internal library that can be used by graphical tools.
Homepage:http://wiki.ros.org/rosgraph License: BSD
ros-noetic/roslang::ros-overlay
- Ebuilds: 1, Testing: 1.15.8-r1 Description:
roslang is a common package that all <a href="http://www.ros.org/wiki/Client%20Libraries">ROS client libraries</a> depend on.
This is mainly used to find client libraries (via 'rospack depends-on1 roslang').
Homepage:http://ros.org/wiki/roslang License: BSD
ros-noetic/roslaunch::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
roslaunch is a tool for easily launching multiple ROS <a href="http://ros.org/wiki/Nodes">nodes</a> locally and remotely
via SSH, as well as setting parameters on the <a href="http://ros.org/wiki/Parameter Server">Parameter
Server</a>. It includes options to automatically respawn processes
that have already died. roslaunch takes in one or more XML
configuration files (with the <tt>.launch</tt> extension) that
specify the parameters to set and nodes to launch, as well as the
machines that they should be run on.
Homepage:http://wiki.ros.org/roslaunch License: BSD
ros-noetic/roslib::ros-overlay
- Ebuilds: 1, Testing: 1.15.8-r1 Description:
Base dependencies and support libraries for ROS.
roslib contains many of the common data structures and tools that are shared across ROS client library implementations.
Homepage:http://wiki.ros.org/roslib License: BSD
ros-noetic/roslint::ros-overlay
- Ebuilds: 1, Testing: 0.12.0-r1 Description:
CMake lint commands for ROS packages.
The lint commands perform static checking of Python or C++ source
code for errors and standards compliance.
Homepage:http://ros.org/wiki/roslint License: BSD
ros-noetic/roslz4::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
A Python and C++ implementation of the LZ4 streaming format. Large data
streams are split into blocks which are compressed using the very fast LZ4
compression algorithm.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/rosmon::ros-overlay
- Ebuilds: 1, Testing: 2.4.0-r1 Description:
Node launcher and monitor for ROS. rosmon is a replacement
for the roslaunch tool, focused on performance, remote
monitoring, and usability.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/rosmon_core::ros-overlay
- Ebuilds: 1, Testing: 2.4.0-r1 Description:
Node launcher and monitor for ROS. rosmon is a replacement
for the roslaunch tool, focused on performance, remote
monitoring, and usability.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/rosmon_msgs::ros-overlay
- Ebuilds: 1, Testing: 2.4.0-r1 Description:
Messages for rosmon, the node launcher and monitor for ROS.
rosmon is a replacement for the roslaunch tool, focused on performance,
remote monitoring, and usability.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/rosmsg::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
rosmsg contains two command-line tools: <tt>rosmsg</tt> and
<tt>rossrv</tt>. <tt>rosmsg</tt> is a command-line tool for
displaying information about <a href="http://wiki.ros.org/msg">ROS Message
types</a>. <tt>rossrv</tt> is a command-line tool for displaying
information about <a href="http://wiki.ros.org/srv">ROS
Service types</a>.
Homepage:http://wiki.ros.org/rosmsg License: BSD
ros-noetic/rosnode::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
rosnode is a command-line tool for displaying debug information
about ROS <a href="http://wiki.ros.org/Nodes">Nodes</a>,
including publications, subscriptions and connections. It also
contains an experimental library for retrieving node
information. This library is intended for internal use only.
Homepage:http://ros.org/wiki/rosnode License: BSD
ros-noetic/rosparam::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
rosparam contains the rosparam command-line tool for getting and
setting ROS Parameters on the <a href="http://wiki.ros.org/Parameter%20Server">Parameter
Server</a> using YAML-encoded files. It also contains an
experimental library for using YAML with the Parameter
Server. This library is intended for internal use only.
rosparam can be invoked within a <a href="http://wiki.ros.org/roslaunch">roslaunch</a> file.
Homepage:http://wiki.ros.org/rosparam License: BSD
ros-noetic/rosping::ros-overlay
- Ebuilds: 1, Testing: 2.1.21-r2 Description:
rosping is the tool to send ICMP ECHO_REQUEST to network hosts where roscore is running, and send back to you as rostopic message. <br/>
For echoing ROS node, use <a href="http://wiki.ros.org/rosnode">rosnode</a>.
Homepage:http://ros.org/wiki/rosping License: Boost-1.0
ros-noetic/rospy::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
rospy is a pure Python client library for ROS. The rospy client
API enables Python programmers to quickly interface with ROS <a href="http://ros.org/wiki/Topics">Topics</a>, <a href="http://ros.org/wiki/Services">Services</a>, and <a href="http://ros.org/wiki/Parameter Server">Parameters</a>. The
design of rospy favors implementation speed (i.e. developer
time) over runtime performance so that algorithms can be quickly
prototyped and tested within ROS. It is also ideal for
non-critical-path code, such as configuration and initialization
code. Many of the ROS tools are written in rospy to take
advantage of the type introspection capabilities.
Many of the ROS tools, such
as <a href="http://ros.org/wiki/rostopic">rostopic</a>
and <a href="http://ros.org/wiki/rosservice">rosservice</a>, are
built on top of rospy.
Homepage:http://wiki.ros.org/rospy License: BSD
ros-noetic/rosrt::ros-overlay
- Ebuilds: 1, Testing: 1.0.25-r1 Description:
rosrt provides classes for interfacing with ROS from within realtime systems, such as realtime-safe Publisher and Subscriber classes.
Homepage:http://ros.org/wiki/rosrt License: BSD
ros-noetic/rosservice::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
rosservice contains the rosservice command-line tool for listing
and querying ROS <a href="http://wiki.ros.org/Services">Services</a>. It also
contains a Python library for retrieving information about
Services and dynamically invoking them. The Python library is
experimental and is for internal-use only.
Homepage:http://ros.org/wiki/rosservice License: BSD
ros-noetic/rostopic::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
rostopic contains the rostopic command-line tool for displaying
debug information about
ROS <a href="http://wiki.ros.org/Topics">Topics</a>, including
publishers, subscribers, publishing rate,
and ROS <a href="http://wiki.ros.org/Messages">Messages</a>. It also
contains an experimental Python library for getting information about
and interacting with topics dynamically. This library is for
internal-use only as the code API may change, though it does provide
examples of how to implement dynamic subscription and publication
behaviors in ROS.
Homepage:http://ros.org/wiki/rostopic License: BSD
ros-noetic/rqt::ros-overlay
- Ebuilds: 1, Testing: 0.5.2-r1 Description:
rqt is a Qt-based framework for GUI development for ROS. It consists of three parts/metapackages<br/>
<ul>
<li>rqt (you're here)</li>
<li><a href="http://ros.org/wiki/rqt_common_plugins">rqt_common_plugins</a> - ROS backend tools suite that can be used on/off of robot runtime.</li>
<li><a href="http://ros.org/wiki/rqt_robot_plugins">rqt_robot_plugins</a> - Tools for interacting with robots during their runtime.</li>
</ul>
rqt metapackage provides a widget <a href="http://ros.org/wiki/rqt_gui">rqt_gui</a> that enables multiple `rqt` widgets to be docked in a single window.
Homepage:http://ros.org/wiki/rqt License: BSD
ros-noetic/rqt_action::ros-overlay
- Ebuilds: 1, Testing: 0.4.9-r1 Description:
rqt_action provides a feature to introspect all available ROS
action (from actionlib) types. By utilizing rqt_msg, the output format is
unified with it and rqt_srv. Note that the actions shown on this plugin
is the ones that are stored on your machine, not on the ROS core your rqt
instance connects to.
Homepage:http://wiki.ros.org/rqt_action License: BSD
ros-noetic/rqt_common_plugins::ros-overlay
- Ebuilds: 1, Testing: 0.4.9-r1 Description:
rqt_common_plugins metapackage provides ROS backend graphical tools suite that can be used on/off of robot runtime.<br/>
<br/>
To run any rqt plugins, just type in a single command "rqt", then select any plugins you want from the GUI that launches afterwards.<br/>
<br/>
rqt consists of three following metapackages:<br/>
<ul>
<li><a href="http://ros.org/wiki/rqt">rqt</a> - core modules of rqt (ROS GUI) framework. rqt plugin developers barely needs to pay attention to this metapackage.</li>
<li>rqt_common_plugins (you're here!)</li>
<li><a href="http://ros.org/wiki/rqt_robot_plugins">rqt_robot_plugins</a> - rqt plugins that are particularly used with robots during their runtime.</li><br/>
</ul>
<br/>
Homepage:http://ros.org/wiki/rqt_common_plugins License: BSD
ros-noetic/rqt_graph::ros-overlay
- Ebuilds: 1, Testing: 0.4.14-r1 Description:
rqt_graph provides a GUI plugin for visualizing the ROS
computation graph.<br/>
Its components are made generic so that other packages
where you want to achieve graph representation can depend upon this pkg
(use <a href="http://www.ros.org/wiki/rqt_dep">rqt_dep</a> to find out
the pkgs that depend. rqt_dep itself depends on rqt_graph too).
Homepage:http://wiki.ros.org/rqt_graph License: BSD
ros-noetic/rqt_moveit::ros-overlay
- Ebuilds: 1, Testing: 0.5.10-r1 Description:
An rqt-based tool that assists monitoring tasks
for <a href="http://ros.org/wiki/moveit">MoveIt!</a> motion planner
developers and users. Currently the following items are monitored if they
are either running, existing or published:
<ul>
<li>Node: /move_group</li>
<li>Parameter: [/robot_description, /robot_description_semantic]</li>
<li>Topic: Following types are monitored. Published "names" are ignored.<br/>
[sensor_msgs/PointCloud, sensor_msgs/PointCloud2,
sensor_msgs/Image, sensor_msgs/CameraInfo]</li>
</ul>
Since this package is not made by the MoveIt! development team (although with
assistance from the them), please post issue reports to the designated
tracker (not MoveIt!'s main tracker).
Homepage:http://wiki.ros.org/rqt_moveit License: BSD
ros-noetic/rqt_msg::ros-overlay
- Ebuilds: 1, Testing: 0.4.10-r1 Description:
A Python GUI plugin for introspecting available ROS message types.
Note that the msgs available through this plugin is the ones that are stored
on your machine, not on the ROS core your rqt instance connects to.
Homepage:http://wiki.ros.org/rqt_msg License: BSD
ros-noetic/rqt_pr2_dashboard::ros-overlay
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
rqt_pr2_dashboard is a GUI for debugging and controlling low-level state of the PR2. It shows things like battery status and breaker states, as well as integrating tools like rqt_console and robot_monitor.
Homepage:http://ros.org/wiki/rqt_pr2_dashboard License: BSD
ros-noetic/rqt_py_common::ros-overlay
- Ebuilds: 1, Testing: 0.5.2-r1 Description:
rqt_py_common provides common functionality for rqt plugins written in Python.
Despite no plugin is provided, this package is part of the rqt_common_plugins
repository to keep refactoring generic functionality from these common plugins
into this package as easy as possible.
Functionality included in this package should cover generic ROS concepts and
should not introduce any special dependencies beside "ros_base".
Homepage:http://ros.org/wiki/rqt_py_common License: BSD
ros-noetic/rqt_reconfigure::ros-overlay
- Ebuilds: 1, Testing: 0.5.4-r1 Description:
This rqt plugin succeeds former dynamic_reconfigure's GUI
(reconfigure_gui), and provides the way to view and edit the parameters
that are accessible via dynamic_reconfigure.<br/>
<br/>
(12/27/2012) In the future, arbitrary parameters that are not associated
with any nodes (which are not handled by dynamic_reconfigure) might
become handled.
However, currently as the name indicates, this pkg solely is dependent
on dynamic_reconfigure that allows access to only those params latched
to nodes.
Homepage:http://wiki.ros.org/rqt_reconfigure License: BSD
ros-noetic/rqt_robot_monitor::ros-overlay
- Ebuilds: 1, Testing: 0.5.13-r1 Description:
rqt_robot_monitor displays diagnostics_agg topics messages that
are published by <a href="http://www.ros.org/wiki/diagnostic_aggregator">diagnostic_aggregator</a>.
rqt_robot_monitor is a direct port to rqt of
<a href="http://www.ros.org/wiki/robot_monitor">robot_monitor</a>. All
diagnostics are fall into one of three tree panes depending on the status of
diagnostics (normal, warning, error/stale). Status are shown in trees to
represent their hierarchy. Worse status dominates the higher level status.<br/>
<ul>
Ex. 'Computer' category has 3 sub devices. 2 are green but 1 is error. Then
'Computer' becomes error.
</ul>
You can look at the detail of each status by double-clicking the tree nodes.<br/>
Currently re-usable API to other pkgs are not explicitly provided.
Homepage:http://wiki.ros.org/rqt_robot_monitor License: BSD
ros-noetic/rqt_robot_plugins::ros-overlay
- Ebuilds: 1, Testing: 0.5.8-r1 Description:
Metapackage of rqt plugins that are particularly used with robots
during its operation.<br/>
<br/>
To run any rqt plugins, just type in a single command "rqt", then select any plugins you want from the GUI that launches afterwards.<br/>
<br/>
rqt consists of three following metapackages:<br/>
<ul>
<li><a href="http://ros.org/wiki/rqt">rqt</a> - provides a container window
where all rqt tools can be docked at. rqt plugin developers barely
needs to pay attention.</li>
<li><a href="http://ros.org/wiki/rqt_common_plugins">rqt_common_plugins</a> -
ROS backend tools suite that can be used on/off of robot runtime.</li>
<li>rqt_robot_plugins (You're here!)</li>
</ul>
Homepage:http://ros.org/wiki/rqt_robot_plugins License: BSD
ros-noetic/rqt_rosmon::ros-overlay
- Ebuilds: 1, Testing: 2.4.0-r1 Description:
rqt GUI for rosmon, the node launcher and monitor for ROS.
rosmon is a replacement for the roslaunch tool, focused on performance,
remote monitoring, and usability.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/rqt_rviz::ros-overlay
- Ebuilds: 1, Testing: 0.7.0-r1 Description:
rqt_rviz provides a GUI plugin embedding <a href="http://www.ros.org/wiki/rviz">RViz</a>.
Note that this rqt plugin does NOT supersede RViz but depends on it.
Homepage:http://wiki.ros.org/rqt_rviz License: BSD
ros-noetic/rqt_srv::ros-overlay
- Ebuilds: 1, Testing: 0.4.9-r1 Description:
A Python GUI plugin for introspecting available ROS message types.
Note that the srvs available through this plugin is the ones that are stored
on your machine, not on the ROS core your rqt instance connects to.
Homepage:http://wiki.ros.org/rqt_srv License: BSD
ros-noetic/scenario_test_tools::ros-overlay
- Ebuilds: 1, Testing: 0.6.21-r1 Description:
The scenario_test_tools package implements helpers for scriptable scenario testing.
It allows to set up a test harness for eg. a state machine or other high level behavior by
providing mocked implementations for various action servers and services that work together
Homepage:https://wiki.ros.org License: Apache-2.0
ros-noetic/schunk_description::ros-overlay
- Ebuilds: 1, Testing: 0.6.14-r1 Description:
This package contains the description (mechanical, kinematic, visual,
etc.) of different schunk components. The files in this package are parsed and used by
a variety of other components. Most users will not interact directly
with this package.
Homepage:http://ros.org/wiki/schunk_description License: Apache-2.0
ros-noetic/schunk_libm5api::ros-overlay
- Ebuilds: 1, Testing: 0.6.14-r1 Description:
This package wraps the libm5api to use it as a ros dependency. Original sources from http://www.schunk-modular-robotics.com/fileadmin/user_upload/software/schunk_libm5api_source.zip.
Homepage:http://ros.org/wiki/schunk_libm5api License: Apache-2.0
ros-noetic/schunk_powercube_chain::ros-overlay
- Ebuilds: 1, Testing: 0.6.14-r1 Description:
This packages provides a configurable driver of a chain
of Schunk powercubes. The powercube chain is configured
through parameters. Most users will not directly interact
with this package but with the corresponding launch files
in other packages, e.g. schunk_bringup, cob_bringup, ...
Homepage:http://ros.org/wiki/schunk_powercube_chain License: Apache-2.0
ros-noetic/schunk_simulated_tactile_sensors::ros-overlay
- Ebuilds: 1, Testing: 0.6.14-r1 Description:
This package provides simulated tactile sensors for the Schunk Dextrous
Hand (SDH) which is mounted on the Care-O-bot arm. The node subscribes to
the Gazebo bumper topics of the SDH. It transforms the Gazebo feedback to
the "tactile_data" topic to provide the same tactile sensor interface as
the schunk_sdh package.
The following parameters can be set:
* cells_x: The number of patches on the tactile sensor in the direction
perpendicular to the finger. Defaults to 6.
* cells_y: The number of patches on the tactile sensor along the direction
of the finger. Defaults to 14.
* output_range: The maximum output value of one patch. Defaults to 3500.
* sensitivity: The change of output in one patch per Newton. Defaults to
350. The sensitivity can be approximated by the following
formula: S = output_range / (measurement_range * cell_area)
- The measurement range of the tactile pads is 250 kPa (from
the data sheet).
- The output range can be determined by experiment from the
real SDH. It is about 3500.
- The cell area is the size of one patch. Length and width
of the area are determined by dividing the length/width
of the collision surface by the number of cells in the
respective direction.
Important: In most cases this is NOT the cell area that is
given in the data sheet!
* filter_length: The length of the moving average filter which smoothes
the values from simulation. Defaults to 10.
The node subscribes to the following topics to receive data from the
simulation:
* thumb_2/state
* thumb_3/state
* finger_12/state
* finger_13/state
* finger_22/state
* finger_23/state
The node publishes the processed data on the following topic:
* tactile_data
The simulated bumper must obtain the collision data in the link that the
sensor is attached to. This is achieved by setting the "frameName" property
in the gazebo_ros_bumper controller.
Homepage:http://ros.org/wiki/schunk_simulated_tactile_sensors License: Apache-2.0
ros-noetic/settlerlib::ros-overlay
- Ebuilds: 1, Testing: 0.10.15-r1 Description:
Defines helper functions and routines that greatly help when trying to create a settler
for a specific sensor channel. This package is experimental and unstable.
Expect its APIs to change.
Homepage:http://www.ros.org/wiki/settlerlib License: BSD
ros-noetic/simple_message::ros-overlay
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
simple_message defines a simple messaging connection and protocol for communicating
with an industrial robot controller. Additional handler and manager classes are
included for handling connection limited systems. This package is part of the ROS-Industrial
program.
Homepage:http://ros.org/wiki/simple_message License: BSD
ros-noetic/slic::ros-overlay
- Ebuilds: 1, Testing: 2.1.21-r2 Description:
SLIC-Superpizel ROS Wrapper
This file contains the class elements of the class Slic. This class is an
implementation of the SLIC Superpixel algorithm by Achanta et al. [PAMI'12,
vol. 34, num. 11, pp. 2274-2282].
This implementation is created for the specific purpose of creating
over-segmentations in an OpenCV-based environment.
Homepage:https://wiki.ros.org License: N/A
ros-noetic/smach::ros-overlay
- Ebuilds: 1, Testing: 2.5.0-r1 Description:
SMACH is a task-level architecture for rapidly creating complex robot
behavior. At its core, SMACH is a ROS-independent Python library to build
hierarchical state machines. SMACH is a new library that takes advantage of
very old concepts in order to quickly create robust robot behavior with
maintainable and modular code.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/smach_ros::ros-overlay
- Ebuilds: 1, Testing: 2.5.0-r1 Description:
The smach_ros package contains extensions for the SMACH library to
integrate it tightly with ROS. For example, SMACH-ROS can call
ROS services, listen to ROS topics, and integrate
with <a href="http://www.ros.org/wiki/actionlib">actionlib</a>
both as a client, and a provider of action servers. SMACH is a
new library that takes advantage of very old concepts in order to
quickly create robust robot behavior with maintainable and modular
code.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/smach_viewer::ros-overlay
- Ebuilds: 1, Testing: 3.0.1-r1 Description:
The smach viewer is a GUI that shows the state of hierarchical
SMACH state machines. It can visualize the possible transitions
between states, as well as the currently active state and the
values of user data that is passed around between states. The
smach viewer uses the SMACH debugging interface based on
the <a href="http://www.ros.org/wiki/smach_msgs">smach
messages</a> to gather information from running state machines.
Homepage:http://ros.org/wiki/smach_viewer License: BSD
ros-noetic/smclib::ros-overlay
- Ebuilds: 1, Testing: 1.8.6-r1 Description:
The State Machine Compiler (SMC) from http://smc.sourceforge.net/
converts a language-independent description of a state machine
into the source code to support that state machine.
This package contains the libraries that a compiled state machine
depends on, but it does not contain the compiler itself.
Homepage:http://smc.sourceforge.net/ License: MPL-1.1
ros-noetic/soem::ros-overlay
- Ebuilds: 1, Testing: 1.4.1003-r1 Description:
ROS wrapper for the Simple Open EtherCAT Master SOEM.
This is an updated version of the original SOEM wrapper released into ROS now including
the upstream Repo as a git subtree.
Homepage:http://openethercatsociety.github.io/ License: GPL-2
ros-noetic/std_msgs::ros-overlay
- Ebuilds: 1, Testing: 0.5.13-r1 Description:
Standard ROS Messages including common message types representing primitive data types and other basic message constructs, such as multiarrays.
For common, generic robot-specific message types, please see <a href="http://www.ros.org/wiki/common_msgs">common_msgs</a>.
Homepage:http://www.ros.org/wiki/std_msgs License: BSD
ros-noetic/swri_nodelet::ros-overlay
- Ebuilds: 1, Testing: 2.14.2-r1 Description:
This package provides a simple script to write simple launch files
that can easily switch between running nodelets together or as
standalone nodes.
Homepage:https://wiki.ros.org License: BSD
ros-noetic/teb_local_planner::ros-overlay
- Ebuilds: 1, Testing: 0.9.1-r1 Description:
The teb_local_planner package implements a plugin
to the base_local_planner of the 2D navigation stack.
The underlying method called Timed Elastic Band locally optimizes
the robot's trajectory with respect to trajectory execution time,
separation from obstacles and compliance with kinodynamic constraints at runtime.
Homepage:http://wiki.ros.org/teb_local_planner License: BSD
ros-noetic/test_osm::ros-overlay
- Ebuilds: 1, Testing: 0.3.0-r1 Description:
These are regression tests for the osm_cartography and
route_network packages. They are packaged separately to avoid
unnecessary implementation dependencies.
Homepage:http://ros.org/wiki/test_osm License: BSD
ros-noetic/tf::ros-overlay
- Ebuilds: 1, Testing: 1.13.2-r1 Description:
tf is a package that lets the user keep track of multiple coordinate
frames over time. tf maintains the relationship between coordinate
frames in a tree structure buffered in time, and lets the user
transform points, vectors, etc between any two coordinate frames at
any desired point in time.
<p><b>Migration</b>: Since ROS Hydro, tf has been "deprecated" in favor of <a href="http://wiki.ros.org/tf2">tf2</a>. tf2 is an iteration on tf providing generally the same feature set more efficiently. As well as adding a few new features.<br/>
As tf2 is a major change the tf API has been maintained in its current form. Since tf2 has a superset of the tf features with a subset of the dependencies the tf implementation has been removed and replaced with calls to tf2 under the hood. This will mean that all users will be compatible with tf2. It is recommended for new work to use tf2 directly as it has a cleaner interface. However tf will continue to be supported for through at least J Turtle.
</p>
Homepage:http://www.ros.org/wiki/tf License: BSD
ros-noetic/tf2::ros-overlay
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
tf2 is the second generation of the transform library, which lets
the user keep track of multiple coordinate frames over time. tf2
maintains the relationship between coordinate frames in a tree
structure buffered in time, and lets the user transform points,
vectors, etc between any two coordinate frames at any desired
point in time.
Homepage:http://www.ros.org/wiki/tf2 License: BSD
ros-noetic/tf_conversions::ros-overlay
- Ebuilds: 1, Testing: 1.13.2-r1 Description:
This package contains a set of conversion functions to convert
common tf datatypes (point, vector, pose, etc) into semantically
identical datatypes used by other libraries. The conversion functions
make it easier for users of the transform library (tf) to work with
the datatype of their choice. Currently this package has support for
the Kinematics and Dynamics Library (KDL) and the Eigen matrix
library. This package is stable, and will get integrated into tf in
the next major release cycle (see roadmap).
Homepage:http://www.ros.org/wiki/tf_conversions License: BSD
ros-noetic/topic_tools::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
Tools for directing, throttling, selecting, and otherwise messing with
ROS topics at a meta level. None of the programs in this package actually
know about the topics whose streams they are altering; instead, these
tools deal with messages as generic binary blobs. This means they can be
applied to any ROS topic.
Homepage:http://ros.org/wiki/topic_tools License: BSD
ros-noetic/trac_ik::ros-overlay
- Ebuilds: 1, Testing: 1.6.6-r1 Description:
The ROS packages in this repository were created to provide an improved
alternative Inverse Kinematics solver to the popular inverse Jacobian
methods in KDL. TRAC-IK handles joint-limited chains better than KDL
without increasing solve time.
Homepage:http://wiki.ros.org/trac_ik License: BSD
ros-noetic/trac_ik_lib::ros-overlay
- Ebuilds: 1, Testing: 1.6.6-r1 Description:
TRAC-IK is a faster, significantly more reliable drop-in replacement for
KDL's pseudoinverse Jacobian solver.
The TRAC-IK library has a very similar API to KDL's IK solver calls,
except that the user passes a maximum time instead of a maximum number of
search iterations. Additionally, TRAC-IK allows for error tolerances to
be set independently for each Cartesian dimension (x,y,z,roll,pitch.yaw).
Homepage:https://wiki.ros.org License: BSD
ros-noetic/trajectory_msgs::ros-overlay
- Ebuilds: 1, Testing: 1.13.1-r1 Description:
This package defines messages for defining robot trajectories. These messages are
also the building blocks of most of the
<a href="http://wiki.ros.org/control_msgs">control_msgs</a> actions.
Homepage:http://wiki.ros.org/trajectory_msgs License: BSD
ros-noetic/turtle_tf::ros-overlay
- Ebuilds: 1, Testing: 0.2.3-r1 Description:
turtle_tf demonstrates how to write a tf broadcaster and listener with the turtlesim. The tutle_tf_listener commands turtle2 to follow turtle1 around as you drive turtle1 using the keyboard.
Homepage:http://ros.org/wiki/turtle_tf License: BSD
ros-noetic/turtle_tf2::ros-overlay
- Ebuilds: 1, Testing: 0.2.3-r1 Description:
turtle_tf2 demonstrates how to write a tf2 broadcaster and listener with the turtlesim. The tutle_tf2_listener commands turtle2 to follow turtle1 around as you drive turtle1 using the keyboard.
Homepage:https://github.com/ros/geometry_tutorials License: BSD
ros-noetic/turtlebot3_example::ros-overlay
- Ebuilds: 1, Testing: 1.2.5-r1 Description:
This package provides four TurtleBot3 basic example include move using interactive marker, move and stop using LDS, move to goal position, move to custom routes. The interactions node is that you can control the TurtleBot3 front and back side or rotate to goal position. The obstacle node is that when the robot meets an obstacle, it stops. The patrol node is that TurtleBot3 move to custom route. There are 3 route(square, triangle, circle) in this package. You can add your route and move the TurtleBot3. The pointop node is that you can insert goal position include distance x-axis, y-axis and angluar z-axis.
Homepage:http://wiki.ros.org/turtlebot3_example License: Apache-2.0
ros-noetic/twist_controller::ros-overlay
- Ebuilds: 1, Testing: 0.1.4-r1 Description:
A ros_control controller accepting Cartesian twist messages in order to move a robot manipulator.
It uses a Cartesian interface to the robot, so that the robot hardware takes care about
doing the inverse kinematics. This could be used e.g. for visual servoing applications.
Homepage:http://wiki.ros.org/twist_controller License: Apache-2.0
ros-noetic/twist_mux::ros-overlay
- Ebuilds: 1, Testing: 3.1.1-r1 Description:
Twist multiplexer, which multiplex several velocity commands (topics) and
allows to priorize or disable them (locks).
Homepage:https://wiki.ros.org License: CC-BY-NC-SA-4.0
ros-noetic/urdf::ros-overlay
- Ebuilds: 1, Testing: 1.13.2-r1 Description:
This package contains a C++ parser for the Unified Robot Description
Format (URDF), which is an XML format for representing a robot model.
The code API of the parser has been through our review process and will remain
backwards compatible in future releases.
Homepage:http://ros.org/wiki/urdf License: BSD
ros-noetic/variant_msgs::ros-overlay
- Ebuilds: 1, Testing: 0.1.6-r1 Description:
Variant messages are designed to accommodate the information content of any invariant message. They are truly generic and can freely be converted to and from specific message objects.
Homepage:http://github.com/anybotics/variant License: LGPL-2
ros-noetic/video_stream_opencv::ros-overlay
- Ebuilds: 1, Testing: 1.1.6-r1 Description:
The video_stream_opencv package contains a node to publish a video stream (the protocols that
opencv supports are supported, including rtsp, webcams on /dev/video and video files) in ROS image topics, it supports camera info and basic image flipping (horizontal, vertical or both) capabilities, also adjusting publishing rate.
Homepage:http://www.ros.org/wiki/video_stream_opencv License: BSD
ros-noetic/visp_auto_tracker::ros-overlay
- Ebuilds: 1, Testing: 0.12.1-r1 Description:
Online automated pattern-based object tracker relying on visual servoing.
visp_auto_tracker wraps model-based trackers provided by ViSP visual
servoing library into a ROS package. The tracked object should have a
QRcode of Flash code pattern. Based on the pattern, the object is
automaticaly detected. The detection allows then to initialise the
model-based trackers. When lost of tracking achieves a new detection
is performed that will be used to re-initialize the tracker.
This computer vision algorithm computes the pose (i.e. position and
orientation) of an object in an image. It is fast enough to allow
object online tracking using a camera.
Homepage:http://wiki.ros.org/visp_auto_tracker License: GPL-2
ros-noetic/visp_tracker::ros-overlay
- Ebuilds: 1, Testing: 0.12.1-r1 Description:
Wraps the ViSP moving edge tracker provided by the ViSP visual
servoing library into a ROS package.
This computer vision algorithm computes the pose (i.e. position
and orientation) of an object in an image. It is fast enough to
allow object online tracking using a camera.
Homepage:http://wiki.ros.org/wiki/visp_tracker License: BSD
ros-noetic/visualization_msgs::ros-overlay
- Ebuilds: 1, Testing: 1.13.1-r1 Description:
visualization_msgs is a set of messages used by higher level packages, such as <a href="/wiki/rviz">rviz</a>, that deal in visualization-specific data.
The main messages in visualization_msgs is <tt>visualization_msgs/Marker</tt>.
The marker message is used to send visualization "markers" such as boxes, spheres, arrows, lines, etc. to a visualization environment such as <a href="http:///www.ros.org/wiki/rviz">rviz</a>.
See the rviz tutorial <a href="http://www.ros.org/wiki/rviz/Tutorials">rviz tutorials</a> for more information.
Homepage:http://ros.org/wiki/visualization_msgs License: BSD
ros-noetic/voxel_grid::ros-overlay
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
voxel_grid provides an implementation of an efficient 3D voxel grid. The occupancy grid can support 3 different representations for the state of a cell: marked, free, or unknown. Due to the underlying implementation relying on bitwise and and or integer operations, the voxel grid only supports 16 different levels per voxel column. However, this limitation yields raytracing and cell marking performance in the grid comparable to standard 2D structures making it quite fast compared to most 3D structures.
Homepage:http://wiki.ros.org/voxel_grid License: BSD
ros-noetic/wge100_camera_firmware::ros-overlay
- Ebuilds: 1, Testing: 1.8.5-r1 Description:
Source for the WGE100 Ethernet camera: Verilog source for the
FPGA, Forth source for the camera firmware. Intended for camera
developers. Note that a built binary from this package is checked
in under wge100_camera/firmware_images/
Homepage:http://ros.org/wiki/wge100_camera_firmware License: BSD
ros-noetic/wiimote::ros-overlay
- Ebuilds: 1, Testing: 1.15.0-r1 Description:
The wiimote package allows ROS nodes to communicate with a Nintendo Wiimote
and its related peripherals, including the Nunchuk, Motion Plus, and
(experimentally) the Classic. The package implements a ROS node that uses
Bluetooth to communicate with the Wiimote device, obtaining accelerometer
and gyro data, the state of LEDs, the IR camera, rumble (vibrator),
buttons, joystick, and battery state. The node additionally enables ROS
nodes to control the Wiimote's LEDs and vibration for feedback to the human
Wiimote operator. LEDs and vibration may be switched on and off, or made to
operate according to a timed pattern.
Homepage:http://www.ros.org/wiki/wiimote License: GPL-1
ros-noetic/xacro::ros-overlay
- Ebuilds: 1, Testing: 1.14.10-r1 Description:
Xacro (XML Macros)
Xacro is an XML macro language. With xacro, you can construct shorter and more readable XML files by using macros that expand to larger XML expressions.
Homepage:http://ros.org/wiki/xacro License: BSD
ros-noetic/xmlrpcpp::ros-overlay
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
XmlRpc++ is a C++ implementation of the XML-RPC protocol. This version is
heavily modified from the package available on SourceForge in order to
support roscpp's threading model. As such, we are maintaining our
own fork.
Homepage:http://xmlrpcpp.sourceforge.net License: LGPL-2.1
ros-noetic/xpp::ros-overlay
- Ebuilds: 1, Testing: 1.0.10-r1 Description:
Visualization of motion-plans for legged robots. It draws support areas,
contact forces and motion trajectories in RVIZ and displays URDFs for
specific robots, including a one-legged, a two-legged hopper and
<a href="http://dls.iit.it/">HyQ</a>.
Example motions were generated by
<a href="https://github.com/ethz-adrl/towr">towr</a>.
Homepage:http://github.com/leggedrobotics/xpp License: BSD
ros-noetic/xpp_hyq::ros-overlay
- Ebuilds: 1, Testing: 1.0.10-r1 Description:
HyQ-robot specific functions for visualization in the XPP Motion Framework.
These include inverse kinematics as well as urdf files for a one-legged,
two-legged and four legged robot with <a href="http://dls.iit.it/">HyQ</a>
legs.
The dynamic model can be found
<a href="https://github.com/iit-DLSLab/hyq-description">here</a>.
See also <a href="https://dls.iit.it">IIT</a>.
Homepage:http://github.com/leggedrobotics/xpp License: BSD
ros-noetic/xpp_quadrotor::ros-overlay
- Ebuilds: 1, Testing: 1.0.10-r1 Description:
The URDF file for a quadrotor to be used with the xpp packages and a
simple rviz publisher of quadrotor tfs.
Adapted from Daniel Mellinger, Nathan Michael, Vijay Kumar,
"Trajectory Generation and Control for Precise Aggressive Maneuvers
with Quadrotors".
Homepage:http://github.com/leggedrobotics/xpp License: BSD
ros-noetic/xpp_states::ros-overlay
- Ebuilds: 1, Testing: 1.0.10-r1 Description:
Common definitions (positions, velocities, angular angles,
angular rates) and robot definitions in Cartesian and joint state
used in the Xpp Motion Framework, as well as conversions to/from
xpp_msgs.
Homepage:http://github.com/leggedrobotics/xpp License: BSD