actionlib
- 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
actionlib_msgs
- 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
agni_tf_tools
- 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
allocators
- Ebuilds: 1, Testing: 1.0.25-r1 Description:
Contains aligned allocation functions, as well as an STL-compatible AlignedAllocator class.
Homepage:http://ros.org/wiki/allocators License: BSD
amcl
- 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
angles
- 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
apriltag_ros
- 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
arbotix_sensors
- Ebuilds: 1, Testing: 0.11.0-r1 Description:
Extends the arbotix_node package with a number of more sophisticated ROS wrappers for common devices.
Homepage:http://ros.org/wiki/arbotix_sensors License: BSD
aruco_detect
- Ebuilds: 1, Testing: 0.12.0-r1 Description:
Fiducial detection based on the aruco library
Homepage:https://wiki.ros.org License: BSD
assisted_teleop
- 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
audibot_gazebo
- Ebuilds: 1, Testing: 0.2.1-r1 Description:
Gazebo model plugin to simulate Audibot
Homepage:https://wiki.ros.org License: BSD
audio_capture
- Ebuilds: 1, Testing: 0.3.12-r1 Description:
Transports audio from a source to a destination. Audio sources can come
from a microphone or file. The destination can play the audio or save it
to an mp3 file.
Homepage:http://ros.org/wiki/audio_capture License: BSD
autoware_external_msgs
- Ebuilds: 1, Testing: 1.14.0-r1 Description:
Package to contain an install external message dependencies
Homepage:https://wiki.ros.org License: Apache-2.0
autoware_lanelet2_msgs
- Ebuilds: 1, Testing: 1.14.0-r1 Description:
The autoware_lanelet2_msgs package. Contains messages for lanelet2 maps
Homepage:https://wiki.ros.org License: Apache-2.0
autoware_map_msgs
- Ebuilds: 1, Testing: 1.14.0-r1 Description:
Includes messages to handle each class in Autoware Map Format
Homepage:https://wiki.ros.org License: Apache-2.0
backward_ros
- Ebuilds: 1, Testing: 0.1.7-r1 Description:
The backward_ros package is a ros wrapper of backward-cpp from https://github.com/bombela/backward-cpp
Homepage:https://wiki.ros.org License: MIT
bagger
- Ebuilds: 1, Testing: 0.1.4-r1 Description:
An application used to systematically record rosbags
Homepage:http://www.ros.org/wiki/bagger License: BSD
base_local_planner
- 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
bayesian_belief_networks
- Ebuilds: 1, Testing: 2.1.21-r2 Description:
The bayesian_belief_networks package form https://github.com/eBay/bayesian-belief-networks, Authored by Neville Newey, Anzar Afaq, Copyright 2013 eBay Software Foundation
Homepage:https://github.com/eBay/bayesian-belief-networks License: Apache-2.0
bond
- 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
bond_core
- 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
bondcpp
- Ebuilds: 1, Testing: 1.8.6-r1 Description:
C++ implementation of bond, a mechanism for checking when
another process has terminated.
Homepage:http://www.ros.org/wiki/bondcpp License: BSD
bondpy
- Ebuilds: 1, Testing: 1.8.6-r1 Description:
Python implementation of bond, a mechanism for checking when
another process has terminated.
Homepage:http://www.ros.org/wiki/bondpy License: BSD
calibration
- Ebuilds: 1, Testing: 0.10.15-r1 Description:
Provides a toolchain running through the robot calibration process. This
involves capturing calibration data, estimating parameters, and
then updating the URDF.
Homepage:http://www.ros.org/wiki/ros_comm License: BSD
calibration_launch
- Ebuilds: 1, Testing: 0.10.15-r1 Description:
This package contains a collection of launch files that can be helpful in configuring
the calibration stack to run on your robot.
Homepage:http://ros.org/wiki/calibration_launch License: BSD
calibration_msgs
- Ebuilds: 1, Testing: 0.10.15-r1 Description:
This package defines messages for storing calibration samples
to be used in full robot calibration procedures. This package
is still unstable. Expect the messages to change.
Homepage:http://www.ros.org/wiki/calibration_msgs License: BSD
calibration_setup_helper
- Ebuilds: 1, Testing: 0.10.15-r1 Description:
This package contains a script to generate calibration launch and configurationfiles for your robot.
which is based on Michael Ferguson's calibration code
Homepage:http://ros.org/wiki/calibration_setup_helper License: Apache-2.0
camera_aravis
- Ebuilds: 1, Testing: 4.0.0-r1 Description:
camera_aravis: A complete and comfortable GenICam (USB3Vision and GigEVision) based camera driver for ROS (ethernet and usb).
Homepage:https://github.com/FraunhoferIOSB/camera_aravis License: LGPL-2
camera_calibration
- Ebuilds: 1, Testing: 1.16.0-r1 Description:
camera_calibration allows easy calibration of monocular or stereo
cameras using a checkerboard calibration target.
Homepage:http://www.ros.org/wiki/camera_calibration License: BSD
camera_info_manager
- Ebuilds: 1, Testing: 1.12.0-r1 Description:
This package provides a C++ interface for camera calibration
information. It provides CameraInfo, and handles SetCameraInfo
service requests, saving and restoring the camera calibration
data.
Homepage:http://ros.org/wiki/camera_info_manager License: BSD
can_dbc_parser
- Ebuilds: 1, Testing: 1.0.0-r1 Description:
DBC file interface. Read a DBC file, unpack CAN messages and convert to engineering units, pack values into CAN messages for publishing.
Homepage:https://wiki.ros.org License: BSD
canopen_402
- Ebuilds: 1, Testing: 0.8.5-r1 Description:
This implements the CANopen device profile for drives and motion control. CiA(r) 402
Homepage:http://wiki.ros.org/canopen_402 License: LGPL-2
canopen_chain_node
- Ebuilds: 1, Testing: 0.8.5-r1 Description:
Base implementation for CANopen chains node with support for management services and diagnostics
Homepage:http://wiki.ros.org/canopen_chain_node License: LGPL-2
canopen_master
- Ebuilds: 1, Testing: 0.8.5-r1 Description:
CiA(r) CANopen 301 master implementation with support for interprocess master synchronisation.
Homepage:http://wiki.ros.org/canopen_master License: LGPL-2
canopen_motor_node
- Ebuilds: 1, Testing: 0.8.5-r1 Description:
canopen_chain_node specialization for handling of canopen_402 motor devices. It facilitates interface abstraction with ros_control.
Homepage:http://wiki.ros.org/canopen_motor_node License: LGPL-2
capabilities
- Ebuilds: 1, Testing: 0.3.1-r1 Description:
Package which implements capabilities, including code to parse capability interface specs, to parse capability provider specs, and implement the capability server.
Homepage:http://wiki.ros.org/capabilities License: BSD
carrot_planner
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
This planner attempts to find a legal place to put a carrot for the robot to follow. It does this by moving back along the vector between the robot and the goal point.
Homepage:http://wiki.ros.org/carrot_planner License: BSD
cartesian_interface
- Ebuilds: 1, Testing: 0.1.4-r1 Description:
Defines a hardware interface to send Cartesian commands to a robot hardware and read
Cartesian states.
Homepage:http://wiki.ros.org/cartesian_interface License: Apache-2.0
catch_ros
- Ebuilds: 1, Testing: 0.5.0-r2 Description:
ROS integration for the Catch unit test framework
Homepage:https://wiki.ros.org License: BSD
catkin
- Ebuilds: 1, Testing: 0.8.10-r1 Description:
Low-level build system macros and infrastructure for ROS.
Homepage:http://wiki.ros.org/catkin License: BSD
checkerboard_detector
- 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
class_loader
- 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
clear_costmap_recovery
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
This package provides a recovery behavior for the navigation stack that attempts to clear space by reverting the costmaps used by the navigation stack to the static map outside of a given area.
Homepage:http://wiki.ros.org/clear_costmap_recovery License: BSD
clober_msgs
- Ebuilds: 1, Testing: 1.0.1-r1 Description:
The messages for Clober
Homepage:https://wiki.ros.org License: Apache-2.0
cmake_modules
- Ebuilds: 1, Testing: 0.5.0-r1 Description:
A common repository for CMake Modules which are not distributed with CMake but are commonly used by ROS packages.
Homepage:https://github.com/ros/cmake_modules License: BSD
cmvision
- Ebuilds: 1, Testing: 0.5.0-r2 Description:
Node for the Color Machine Vision Project, used for fast color blob detection
Homepage:http://ros.org/wiki/cmvision License: LGPL-2
cnpy
- Ebuilds: 1, Testing: 0.0.6-r1 Description:
library to read/write .npy and .npz files in C/C++
Homepage:https://wiki.ros.org License: MIT
cob_base_controller_utils
- Ebuilds: 1, Testing: 0.8.13-r1 Description:
The cob_base_controller_utils package contains common utils for various base_controllers.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_base_drive_chain
- 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
cob_base_velocity_smoother
- Ebuilds: 1, Testing: 0.8.13-r1 Description:
The 'cob_base_velocity_smoother' reads velocity messages and publishes messages of the same type for "smoothed" velocity to avoid shaking behavior.
Homepage:http://ros.org/wiki/cob_base_velocity_smoother License: Apache-2.0
cob_bms_driver
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
Driver package for interfacing the battery management system (BMS) on Care-O-bot.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_canopen_motor
- 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
cob_cartesian_controller
- 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
cob_collision_monitor
- 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
cob_common
- 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
cob_control_mode_adapter
- Ebuilds: 1, Testing: 0.8.13-r1 Description:
The cob_control_mode_adapter package provides a node that automatically loads respective ros_controllers depending on required control mode.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_control_msgs
- Ebuilds: 1, Testing: 0.8.13-r1 Description:
Common messages and services used in various packages within cob_control.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_default_robot_behavior
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
The cob_default_robot_behavior package provides helper scripts for standard robot behaviors.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_default_robot_config
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
Default configuration of the different robots supported by the Care-O-bot stacks. Configuration is e.g. preconfigured joint positions.
Homepage:http://ros.org/wiki/cob_default_robot_config License: Apache-2.0
cob_description
- 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
cob_driver
- 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
cob_elmo_homing
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
This packagae implements the special homing procedure that is needed for old cob4/raw bases
Homepage:https://wiki.ros.org License: Apache-2.0
cob_extern
- 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 )
cob_gazebo_ros_control
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
This package contains a specialization of the gazebo_ros_control plugin.
The cob_gazebo_ros_control plugin allows Multi-HardwareInterface-Support.
Homepage:http://ros.org/wiki/cob_gazebo_ros_control License: Apache-2.0
cob_generic_can
- 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
cob_hand
- Ebuilds: 1, Testing: 0.6.9-r1 Description:
The cob_hand stack includes packages that provide access to the Care-O-bot hand through ROS serial.
Homepage:http://ros.org/wiki/cob_hand License: Apache-2.0
cob_hand_bridge
- Ebuilds: 1, Testing: 0.6.9-r1 Description:
The cob_hand_bridge package provides a driver for the gripper of Care-O-bot4.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_hardware_config
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
This package contains configuration for each robot instance (e.g. cob4-X, raw3-X). There is a directory for each robot with configuration about urdf and hardware/device configurations.
Homepage:http://ros.org/wiki/cob_hardware_config License: Apache-2.0
cob_image_flip
- Ebuilds: 1, Testing: 0.6.17-r1 Description:
Flips the image of Care-O-bots kinect in dependence of the viewing direction of the cameras to receive an upright image all the time.
Homepage:http://wiki.ros.org/cob_image_flip License: Apache-2.0
cob_light
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
This package contains scripts to operate the LED lights on Care-O-bot.
Homepage:http://ros.org/wiki/cob_light License: Apache-2.0
cob_linear_nav
- 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
cob_map_accessibility_analysis
- 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
cob_mapping_slam
- Ebuilds: 1, Testing: 0.6.11-r1 Description:
cob_mapping_slam holds launch files for running SLAM using the <a href="http://ros.org/wiki/gmapping">gmapping</a> package.
Homepage:http://ros.org/wiki/cob_mapping_slam License: Apache-2.0
cob_mecanum_controller
- 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
cob_mimic
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
This package implements the Care-O-bot mimic
Homepage:http://ros.org/wiki/cob_mimic License: Apache-2.0
cob_moveit_config
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
MoveIt config files for all cob and raw
Homepage:https://wiki.ros.org License: Apache-2.0
cob_msgs
- Ebuilds: 1, Testing: 0.7.4-r1 Description:
Messages for representing state information, such as battery information and emergency stop status.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_navigation
- Ebuilds: 1, Testing: 0.6.11-r1 Description:
The cob_navigation stack provides different navigation packages for <a href="http://ros.org/wiki/care-o-bot">Care-O-bot</a>.
Homepage:http://ros.org/wiki/cob_navigation License: Apache-2.0
cob_navigation_config
- 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
cob_navigation_global
- 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
cob_navigation_local
- 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
cob_navigation_slam
- 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
cob_object_detection_visualizer
- Ebuilds: 1, Testing: 0.6.17-r1 Description:
The cob_object_detection_visualizer package visualizes the object detection result.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_omni_drive_controller
- Ebuilds: 1, Testing: 0.8.13-r1 Description:
The cob_omni_drive_controller package provides a ros_controller plugin for the Care-O-bot omni-directional base platform.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_phidget_em_state
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
The cob_phidget_em_state package publishes emergency state based on phidgets signals.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_phidget_power_state
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
The cob_phidget_power_state package publishes power state based on phidgets signals.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_reflector_referencing
- 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
cob_safety_controller
- Ebuilds: 1, Testing: 0.6.10-r1 Description:
This package is a substitute for the private implementation of cob_safety_controller package
Homepage:https://wiki.ros.org License: Apache-2.0
cob_scan_unifier
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
The cob_scan_unifier package holds code to unify two or more laser-scans to one unified scan-message
Homepage:https://wiki.ros.org License: Apache-2.0
cob_sick_lms1xx
- 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
cob_sick_s300
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
This package published a laser scan message out of a Sick S300 laser scanner.
Homepage:http://ros.org/wiki/cob_sick_s300 License: Apache-2.0
cob_sound
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
This package implements a sound play module using text2wave and aplay through python.
Homepage:http://ros.org/wiki/cob_sound License: Apache-2.0
cob_srvs
- Ebuilds: 1, Testing: 0.7.4-r1 Description:
This Package contains Care-O-bot specific service definitions.
Homepage:http://ros.org/wiki/cob_srvs License: Apache-2.0
cob_trajectory_controller
- Ebuilds: 1, Testing: 0.8.13-r1 Description:
This package provides a trajectory controller which controlls velocities for a chain of joints. This controller can be used e.g. with [[schunk_powercube_chain]].
Homepage:http://ros.org/wiki/cob_trajectory_controller License: Apache-2.0
cob_tricycle_controller
- Ebuilds: 1, Testing: 0.8.13-r1 Description:
The cob_omni_drive_controller package provides a ros_controller plugin for the Care-O-bot tricycle base platform.
Homepage:https://wiki.ros.org License: Apache-2.0
cob_undercarriage_ctrl
- 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
cob_utilities
- 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
collada_parser
- 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
collada_urdf
- 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
color_util
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
An almost dependency-less library for converting between color spaces
Homepage:https://wiki.ros.org License: BSD
common_msgs
- 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
computer_status_msgs
- 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
control_box_rst
- Ebuilds: 1, Testing: 0.0.7-r1 Description:
The control_box_rst package provides C++ libraries for predictive control,
direct optimal control, optimization and simulation.
Homepage:http://wiki.ros.org/control_box_rst License: GPL-3
control_msgs
- 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
costmap_2d
- 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
costmap_converter
- Ebuilds: 1, Testing: 0.0.13-r1 Description:
A ros package that includes plugins and nodes to convert occupied costmap2d cells to primitive types.
Homepage:http://wiki.ros.org/costmap_converter License: BSD
costmap_queue
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Tool for iterating through the cells of a costmap to find the closest distance to a subset of cells.
Homepage:https://wiki.ros.org License: BSD
cpp_common
- 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
csm
- 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
cv_bridge
- Ebuilds: 1, Testing: 1.15.0-r1 Description:
This contains CvBridge, which converts between ROS
Image messages and OpenCV images.
Homepage:http://www.ros.org/wiki/cv_bridge License: BSD
cv_camera
- Ebuilds: 1, Testing: 0.6.0-r1 Description:
cv_camera uses OpenCV capture object to capture camera image.
This supports camera_image and nodelet.
Homepage:http://wiki.ros.org/cv_camera License: BSD
cvp_mesh_planner
- Ebuilds: 1, Testing: 1.0.1-r2 Description:
The Continuous Vector Field Planner (CVP) mesh planner package
Homepage:https://wiki.ros.org License: BSD
darknet_ros
- Ebuilds: 1, Testing: 1.1.5-r1 Description:
Darknet is an open source neural network framework that runs on CPU and GPU. You only look once (YOLO) is a state-of-the-art, real-time object detection system.
Homepage:https://github.com/leggedrobotics/darknet_ros License: BSD
darknet_ros_msgs
- Ebuilds: 1, Testing: 1.1.5-r1 Description:
Darknet is an open source neural network framework that runs on CPU and GPU. You only look once (YOLO) is a state-of-the-art, real-time object detection system.
Homepage:https://github.com/leggedrobotics/darknet_ros License: BSD
dataspeed_can
- Ebuilds: 1, Testing: 1.0.16-r1 Description:
CAN bus tools using Dataspeed hardware
Homepage:http://dataspeedinc.com License: BSD
dataspeed_can_usb
- Ebuilds: 1, Testing: 1.0.16-r1 Description:
Driver to interface with the Dataspeed Inc. USB CAN Tool
Homepage:http://dataspeedinc.com License: BSD
dataspeed_pds
- Ebuilds: 1, Testing: 1.0.6-r1 Description:
Interface to the Dataspeed Inc. Intelligent Power Distribution System (iPDS)
Homepage:http://dataspeedinc.com License: BSD
dataspeed_pds_can
- Ebuilds: 1, Testing: 1.0.6-r1 Description:
Interface to the Dataspeed Inc. Intelligent Power Distribution System (iPDS) via CAN
Homepage:http://dataspeedinc.com License: BSD
dataspeed_pds_msgs
- Ebuilds: 1, Testing: 1.0.6-r1 Description:
Messages for the Dataspeed Inc. Intelligent Power Distribution System (iPDS)
Homepage:http://dataspeedinc.com License: BSD
dataspeed_pds_rqt
- Ebuilds: 1, Testing: 1.0.6-r1 Description:
ROS rqt GUI for the Dataspeed Inc. Intelligent Power Distribution System (iPDS)
Homepage:http://dataspeedinc.com License: BSD
dataspeed_pds_scripts
- Ebuilds: 1, Testing: 1.0.6-r1 Description:
Test scripts to interface to the Dataspeed Inc. Intelligent Power Distribution System (iPDS)
Homepage:http://dataspeedinc.com License: BSD
dbw_fca
- Ebuilds: 1, Testing: 1.2.1-r1 Description:
Drive-by-wire interface to the Dataspeed Inc. Chrysler Pacifica DBW kit
Homepage:http://dataspeedinc.com License: BSD
dbw_fca_can
- Ebuilds: 1, Testing: 1.2.1-r1 Description:
Drive-by-wire interface to the Dataspeed Inc. Chrysler Pacifica DBW kit
Homepage:http://dataspeedinc.com License: BSD
dbw_fca_msgs
- Ebuilds: 1, Testing: 1.2.1-r1 Description:
Drive-by-wire messages for the Chrysler Pacifica
Homepage:http://dataspeedinc.com License: BSD
dbw_mkz
- Ebuilds: 1, Testing: 1.4.1-r1 Description:
Drive-by-wire interface to the Dataspeed Inc. Lincoln MKZ DBW kit
Homepage:http://dataspeedinc.com License: BSD
dbw_mkz_can
- Ebuilds: 1, Testing: 1.4.1-r1 Description:
Drive-by-wire interface to the Dataspeed Inc. Lincoln MKZ DBW kit
Homepage:http://dataspeedinc.com License: BSD
ddynamic_reconfigure_python
- Ebuilds: 1, Testing: 0.0.1-r1 Description:
The ddynamic_reconfigure_python package contains
a class to instantiate dynamic reconfigure servers on the fly
registering variables
Homepage:https://wiki.ros.org License: BSD
depth_image_proc
- 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
diagnostic_analysis
- Ebuilds: 1, Testing: 1.10.4-r1 Description:
The diagnostic_analysis package can convert a log of diagnostics data
into a series of CSV files. Robot logs are recorded with rosbag, and
can be processed offline using the scripts in this package.
Homepage:http://www.ros.org/wiki/diagnostics_analysis License: BSD
diagnostic_msgs
- 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
diagnostic_updater
- Ebuilds: 1, Testing: 1.10.4-r1 Description:
diagnostic_updater contains tools for easily updating diagnostics. it is commonly used in device drivers to keep track of the status of output topics, device status, etc.
Homepage:http://www.ros.org/wiki/diagnostic_updater License: BSD
driver_base
- Ebuilds: 1, Testing: 1.6.9-r1 Description:
A framework for writing drivers that helps with runtime reconfiguration, diagnostics and self-test.
This package is deprecated.
Homepage:http://www.ros.org/wiki/driver_base License: BSD
driver_common
- 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
dwa_local_planner
- 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
dwb_local_planner
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Plugin based local planner implementing the nav_core2::LocalPlanner interface.
Homepage:https://wiki.ros.org License: BSD
dwb_msgs
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Message/Service definitions specifically for the dwb_local_planner
Homepage:https://wiki.ros.org License: BSD
dwb_plugins
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Standard implementations of the GoalChecker
and TrajectoryGenerators for dwb_local_planner
Homepage:https://wiki.ros.org License: BSD
dynamic_reconfigure
- Ebuilds: 1, Testing: 1.7.1-r1 Description:
The dynamic_reconfigure package provides a means to update parameters
at runtime without having to restart the node.
Homepage:http://ros.org/wiki/dynamic_reconfigure License: BSD
dynamixel_sdk
- 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
dynamixel_workbench
- 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
dynamixel_workbench_toolbox
- 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
ecl_build
- Ebuilds: 1, Testing: 0.61.8-r1 Description:
Collection of cmake/make build tools primarily for ecl development itself, but also
contains a few cmake modules useful outside of the ecl.
Homepage:http://wiki.ros.org/ecl_build License: BSD
ecl_command_line
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Embeds the TCLAP library inside the ecl. This is a very convenient
command line parser in templatised c++.
Homepage:http://wiki.ros.org/ecl_command_line License: BSD
ecl_concepts
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Introduces a compile time concept checking mechanism that can be used
most commonly to check for required functionality when passing
template arguments.
Homepage:http://wiki.ros.org/ecl_concepts License: BSD
ecl_config
- Ebuilds: 1, Testing: 0.61.6-r1 Description:
These tools inspect and describe your system with macros, types
and functions.
Homepage:http://wiki.ros.org/ecl_config License: BSD
ecl_containers
- 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
ecl_converters
- 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
ecl_converters_lite
- Ebuilds: 1, Testing: 0.61.6-r1 Description:
These are a very simple version of some of the functions in ecl_converters
suitable for firmware development. That is, there is no use of new,
templates or exceptions.
Homepage:http://wiki.ros.org/ecl_converters_lite License: BSD
ecl_core
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
A set of tools and interfaces extending the capabilities of c++ to
provide a lightweight, consistent interface with a focus for control
programming.
Homepage:http://www.ros.org/wiki/ecl_core License: BSD
ecl_core_apps
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
This includes a suite of programs demo'ing various aspects of the
ecl_core. It also includes various benchmarking and utility programs for
use primarily with embedded systems.
Homepage:http://wiki.ros.org/ecl_core_apps License: BSD
ecl_devices
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Provides an extensible and standardised framework for input-output devices.
Homepage:http://wiki.ros.org/ecl_devices License: BSD
ecl_eigen
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
This provides an Eigen implementation for ecl's linear algebra.
Homepage:http://wiki.ros.org/ecl_eigen License: BSD
ecl_errors
- 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
ecl_exceptions
- 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
ecl_formatters
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
The formatters here simply format various input types to a specified
text format. They can be used with most streaming types (including both
ecl and stl streams).
Homepage:http://wiki.ros.org/ecl_formatters License: BSD
ecl_geometry
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Any tools relating to mathematical geometry.
Primarily featuring polynomials and interpolations.
Homepage:http://wiki.ros.org/ecl_geometry License: BSD
ecl_io
- 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
ecl_ipc
- 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
ecl_license
- Ebuilds: 1, Testing: 0.61.8-r1 Description:
Maintains the ecl licenses and also provides an install
target for deploying licenses with the ecl libraries.
Homepage:http://wiki.ros.org/ecl_license License: BSD
ecl_lite
- Ebuilds: 1, Testing: 0.61.6-r1 Description:
Libraries and utilities for embedded and low-level linux development.
Homepage:http://www.ros.org/wiki/ecl_lite License: BSD
ecl_math
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
This package provides simple support to cmath, filling in holes
or redefining in a c++ formulation where desirable.
Homepage:http://wiki.ros.org/ecl_math License: BSD
ecl_mobile_robot
- Ebuilds: 1, Testing: 0.60.3-r2 Description:
Contains transforms (e.g. differential drive inverse kinematics)
for the various types of mobile robot platforms.
Homepage:http://wiki.ros.org/ecl_mobile_robot License: BSD
ecl_mpl
- 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
ecl_navigation
- 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
ecl_sigslots
- 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
ecl_sigslots_lite
- Ebuilds: 1, Testing: 0.61.6-r1 Description:
This avoids use of dynamic storage (malloc/new) and thread safety (mutexes) to
provide a very simple sigslots implementation that can be used for *very*
embedded development.
Homepage:http://wiki.ros.org/ecl_sigslots_lite License: BSD
ecl_streams
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
These are lightweight text streaming classes that connect to standardised
ecl type devices.
Homepage:http://wiki.ros.org/ecl_streams License: BSD
ecl_threads
- 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
ecl_time
- 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
ecl_time_lite
- Ebuilds: 1, Testing: 0.61.6-r1 Description:
Provides a portable set of time functions that are especially useful for
porting other code or being wrapped by higher level c++ classes.
Homepage:http://wiki.ros.org/ecl_time_lite License: BSD
ecl_utilities
- Ebuilds: 1, Testing: 0.62.3-r1 Description:
Includes various supporting tools and utilities for c++ programming.
Homepage:http://wiki.ros.org/ecl_utilities License: BSD
eml
- 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
ethercat_grant
- Ebuilds: 1, Testing: 0.2.5-r8 Description:
Makes it possible to run the ros_ethercat_loop without using sudo. Forked from pr2-grant
Homepage:http://www.shadowrobot.com/ License: BSD
ethercat_hardware
- Ebuilds: 1, Testing: 1.9.0-r1 Description:
Package for creating a hardware interface to the robot using the EtherCAT motor controller/driver
Homepage:http://ros.org/wiki/ethercat_hardware License: BSD
euslisp
- Ebuilds: 1, Testing: 9.28.0-r1 Description:
EusLisp is an integrated programming system for the
research on intelligent robots based on Common Lisp and
Object-Oriented programming
Homepage:http://euslisp.github.io/EusLisp/manual.html License: BSD
executive_smach
- Ebuilds: 1, Testing: 2.5.0-r1 Description:
This metapackage depends on the SMACH library and ROS SMACH integration
packages.
Homepage:http://ros.org/wiki/smach License: BSD
exotica
- 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
exotica_core
- Ebuilds: 1, Testing: 6.2.0-r1 Description:
The Extensible Optimization Toolset (EXOTica) is a library for defining problems for robot motion planning.
Homepage:https://github.com/ipab-slmc/exotica License: BSD
exotica_ompl_solver
- Ebuilds: 1, Testing: 6.2.0-r1 Description:
Exotica solvers based on the Open Motion Planning Libary (OMPL)
Homepage:https://wiki.ros.org License: BSD
exotica_val_description
- 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
fetch_drivers
- 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
fetch_moveit_config
- Ebuilds: 1, Testing: 0.9.1-r1 Description:
An automatically generated package with all the configuration and launch files for using the fetch_urdf with the MoveIt Motion Planning Framework
Homepage:http://moveit.ros.org/ License: BSD
fetch_open_auto_dock
- Ebuilds: 1, Testing: 0.1.3-r2 Description:
An open-source version of the Fetch charge docking system.
Homepage:https://wiki.ros.org License: LGPL-2
fetch_ros
- Ebuilds: 1, Testing: 0.9.1-r1 Description:
Fetch ROS, packages for working with Fetch and Freight
Homepage:https://docs.fetchrobotics.com/ License: BSD
fiducial_slam
- Ebuilds: 1, Testing: 0.12.0-r1 Description:
ROS node to build a 3D map of fiducials and estimate robot pose from fiducial transforms
Homepage:https://wiki.ros.org License: BSD
filters
- 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
fkie_master_discovery
- 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
fkie_master_sync
- Ebuilds: 1, Testing: 1.2.7-r1 Description:
Synchronize the local ROS master to the remote masters
discovered by fkie_master_discovery node. The registration
of topics and services is only perform by local ROS master.
Homepage:http://ros.org/wiki/master_sync_fkie License: BSD
fkie_multimaster
- 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
flexbe_core
- Ebuilds: 1, Testing: 1.3.1-r1 Description:
flexbe_core provides the core components for the FlexBE behavior engine.
Homepage:http://ros.org/wiki/flexbe_core License: BSD
flexbe_input
- Ebuilds: 1, Testing: 1.3.1-r1 Description:
flexbe_input enables to send data to onboard behavior when required.
Homepage:http://ros.org/wiki/flexbe_input License: BSD
flexbe_mirror
- Ebuilds: 1, Testing: 1.3.1-r1 Description:
flexbe_mirror implements functionality to remotely mirror an executed behavior.
Homepage:http://ros.org/wiki/flexbe_mirror License: BSD
flexbe_onboard
- Ebuilds: 1, Testing: 1.3.1-r1 Description:
flexbe_onboard implements the robot-side of the behavior engine from where all behaviors are started.
Homepage:http://ros.org/wiki/flexbe_onboard License: BSD
flexbe_states
- Ebuilds: 1, Testing: 1.3.1-r1 Description:
flexbe_states provides a collection of predefined states.
Feel free to add new states.
Homepage:http://ros.org/wiki/flexbe_states License: BSD
flexbe_widget
- Ebuilds: 1, Testing: 1.3.1-r1 Description:
flexbe_widget implements some smaller scripts for the behavior engine.
Homepage:http://ros.org/wiki/flexbe_widget License: BSD
floam
- Ebuilds: 1, Testing: 0.1.0-r1 Description:
A generic Lidar SLAM package based on FLOAM which was based on ALOAM by HKUST and LOAM by CMU
Homepage:https://wanghan.pro License: BSD
foxglove_msgs
- Ebuilds: 1, Testing: 1.0.0-r1 Description:
foxglove_msgs extends the common ROS visualization messages with additional
useful messages that are supported by Foxglove Studio.
Homepage:https://foxglove.dev/ License: MIT
franka_control
- Ebuilds: 1, Testing: 0.8.1-r1 Description:
franka_control provides a hardware node to control a Franka Emika research robot
Homepage:http://wiki.ros.org/franka_control License: Apache-2.0
franka_gazebo
- Ebuilds: 1, Testing: 0.8.1-r1 Description:
This package offers the FrankaHWSim Class to simulate a Franka Robot in Gazebo
Homepage:http://wiki.ros.org/franka_gazebo License: Apache-2.0
franka_gripper
- Ebuilds: 1, Testing: 0.8.1-r1 Description:
This package implements the franka gripper of type Franka Hand for the use in ros
Homepage:http://wiki.ros.org/franka_gripper License: Apache-2.0
franka_hw
- Ebuilds: 1, Testing: 0.8.1-r1 Description:
franka_hw provides hardware interfaces for using Franka Emika research robots with ros_control
Homepage:http://wiki.ros.org/franka_hw License: Apache-2.0
franka_msgs
- Ebuilds: 1, Testing: 0.8.1-r1 Description:
franka_msgs provides messages specific to Franka Emika research robots
Homepage:http://wiki.ros.org/franka_msgs License: Apache-2.0
franka_ros
- Ebuilds: 1, Testing: 0.8.1-r1 Description:
franka_ros is a metapackage for all Franka Emika ROS packages
Homepage:http://wiki.ros.org/franka_ros License: Apache-2.0
fuse_core
- 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
fuse_doc
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
The fuse_doc package provides documentation and examples for the fuse package.
Homepage:https://wiki.ros.org License: BSD
fuse_loss
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
The fuse_loss package provides a set of commonly used loss functions, such as the basic ones provided by Ceres.
Homepage:https://wiki.ros.org License: BSD
fuse_optimizers
- 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
fuse_publishers
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
The fuse_publishers package provides a set of common publisher plugins.
Homepage:https://wiki.ros.org License: BSD
fuse_variables
- 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
fuse_viz
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
The fuse_viz package provides visualization tools for fuse.
Homepage:https://wiki.ros.org License: BSD
gazebo_ros
- Ebuilds: 1, Testing: 2.9.2-r1 Description:
Provides ROS plugins that offer message and service publishers for interfacing with <a href="http://gazebosim.org">Gazebo</a> through ROS.
Formally simulator_gazebo/gazebo
Homepage:http://gazebosim.org/tutorials?cat=connect_ros License: Apache-2.0
gazebo_video_monitor_msgs
- Ebuilds: 1, Testing: 0.7.0-r1 Description:
gazebo_video_monitor_msgs defines interfaces for the gazebo_video_monitor_plugins package.
Homepage:https://wiki.ros.org License: GPL-3
gazebo_video_monitor_plugins
- 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
gazebo_video_monitor_utils
- Ebuilds: 1, Testing: 0.7.0-r1 Description:
gazebo_video_monitor_utils contains utility scripts that are meant to interact with the gazebo video monitor plugins.
Homepage:https://wiki.ros.org License: GPL-3
gazebo_video_monitors
- Ebuilds: 1, Testing: 0.7.0-r1 Description:
Metapackage that groups together the gazebo_video_monitors packages.
Homepage:https://wiki.ros.org License: GPL-3
generic_throttle
- Ebuilds: 1, Testing: 0.6.21-r1 Description:
This package provides a throttle for ROS topics
Homepage:https://wiki.ros.org License: Apache-2.0
geneus
- Ebuilds: 1, Testing: 3.0.0-r1 Description:
EusLisp ROS message and service generators.
Homepage:https://wiki.ros.org License: BSD
genlisp
- Ebuilds: 1, Testing: 0.4.18-r1 Description:
Common-Lisp ROS message and service generators.
Homepage:http://www.ros.org/wiki/roslisp License: BSD
genmsg
- Ebuilds: 1, Testing: 0.5.16-r1 Description:
Standalone Python library for generating ROS message and service data structures for various languages.
Homepage:http://wiki.ros.org/genmsg License: BSD
gennodejs
- Ebuilds: 1, Testing: 2.0.2-r1 Description:
Javascript ROS message and service generators.
Homepage:https://wiki.ros.org License: Apache-2.0
genpy
- Ebuilds: 1, Testing: 0.6.15-r1 Description:
Python ROS message and service generators.
Homepage:http://wiki.ros.org/genpy License: BSD
geodesy
- Ebuilds: 1, Testing: 0.5.6-r1 Description:
Python and C++ interfaces for manipulating geodetic coordinates.
Homepage:http://wiki.ros.org/geodesy License: BSD
geographic_info
- Ebuilds: 1, Testing: 0.5.6-r1 Description:
Geographic information metapackage.
Not needed for wet packages, use only to resolve dry stack
dependencies.
Homepage:http://wiki.ros.org/geographic_info License: BSD
geometry
- 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
geometry2
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
A metapackage to bring in the default packages second generation Transform Library in ros, tf2.
Homepage:http://www.ros.org/wiki/geometry2 License: BSD
geometry_msgs
- 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
gl_dependency
- Ebuilds: 1, Testing: 1.1.2-r1 Description:
This encapsulates the GL dependency for a specific ROS distribution and its Qt version
Homepage:https://wiki.ros.org License: BSD
global_planner_tests
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
A collection of tests for checking the validity and completeness of global planners.
Homepage:https://wiki.ros.org License: BSD
gmapping
- 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 )
gmcl
- 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
goal_passer
- Ebuilds: 1, Testing: 0.3.4-r1 Description:
A global planner plugin for move_base that simply passes the target pose on
as a global plan. Useful for debugging local planners.
Homepage:http://wiki.ros.org/goal_passer License: BSD
gpp_interface
- Ebuilds: 1, Testing: 0.1.0-r1 Description:
The gpp_interface package defines the interfaces for
pre and post-planning inside the global_planner_pipeline framework
Homepage:https://wiki.ros.org License: MIT
gpp_plugin
- 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
gpp_prune_path
- Ebuilds: 1, Testing: 0.1.0-r1 Description:
The gpp_prune_path plugin will prune the path produced by a global-planner
Homepage:https://wiki.ros.org License: MIT
gpp_update_map
- Ebuilds: 1, Testing: 0.1.0-r1 Description:
The gpp_update_map plugin will update the map before running the global planner
Homepage:https://wiki.ros.org License: MIT
gps_common
- Ebuilds: 1, Testing: 0.3.2-r1 Description:
GPS messages and common routines for use in GPS drivers
Homepage:http://ros.org/wiki/gps_common License: BSD
gpsd_client
- Ebuilds: 1, Testing: 0.3.2-r1 Description:
connects to a GPSd server and broadcasts GPS fixes
using the NavSatFix message
Homepage:http://ros.org/wiki/gpsd_client License: BSD
graft
- 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
hebi_cpp_api
- Ebuilds: 1, Testing: 3.2.0-r1 Description:
A ROS package providing access to the HEBI C++ API.
Homepage:http://docs.hebi.us/tools.html#cpp-api License: HEBI C++ Software License (https://www.hebirobotics.com/softwarelicense)
hector_gazebo
- Ebuilds: 1, Testing: 0.5.4-r1 Description:
hector_gazebo provides packages related to to simulation of robots using gazebo (gazebo plugins, world files etc.)
Homepage:http://ros.org/wiki/hector_gazebo License: BSD
hector_gazebo_plugins
- 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
hector_gazebo_thermal_camera
- Ebuilds: 1, Testing: 0.5.4-r1 Description:
hector_gazebo_thermal_camera provides a gazebo plugin that produces simulated thermal camera images. The plugin uses modified code from the gazebo_ros_camera plugin.
Homepage:http://ros.org/wiki/hector_gazebo_thermal_camera License: BSD
hector_localization
- 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
hector_map_server
- Ebuilds: 1, Testing: 0.5.2-r4 Description:
hector_map_server provides a service for retrieving the map, as well as for raycasting based obstacle queries (finds next obstacle in the map, given start and endpoint
in any tf coordinate frame).
Homepage:http://ros.org/wiki/hector_map_server License: BSD
hector_map_tools
- Ebuilds: 1, Testing: 0.5.2-r4 Description:
hector_map_tools contains some functions related to accessing information from OccupancyGridMap maps.
Currently consists of a single header.
Homepage:http://ros.org/wiki/hector_map_tools License: BSD
hector_mapping
- 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
hector_pose_estimation_core
- 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
hector_slam
- Ebuilds: 1, Testing: 0.5.2-r4 Description:
The hector_slam metapackage that installs hector_mapping and related packages.
Homepage:http://ros.org/wiki/hector_slam License: BSD
hector_slam_launch
- Ebuilds: 1, Testing: 0.5.2-r4 Description:
hector_slam_launch contains launch files for launching hector_slam with different robot systems/setups/postprocessing scenarios.
Homepage:http://ros.org/wiki/hector_slam_launch License: BSD
hls_lfcd_lds_driver
- 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
hokuyo3d
- Ebuilds: 1, Testing: 0.2.1-r1 Description:
ROS driver node for HOKUYO 3D LIDARs
Homepage:https://wiki.ros.org License: BSD
ifm3d_core
- Ebuilds: 1, Testing: 0.18.0-r5 Description:
Library and Utilities for working with ifm pmd-based 3D ToF Cameras
Homepage:https://github.com/ifm/ifm3d License: Apache-1.0
image_cb_detector
- Ebuilds: 1, Testing: 0.10.15-r1 Description:
Provide a node that extracts checkerboard corners from ROS images.
This package is still experimental and unstable.
Expect its APIs to change.
Homepage:http://ros.org/wiki/image_cb_detector License: BSD
image_geometry
- 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
image_pipeline
- Ebuilds: 1, Testing: 1.16.0-r1 Description:
image_pipeline fills the gap between getting raw images from a camera driver and higher-level vision processing.
Homepage:http://www.ros.org/wiki/image_pipeline License: BSD
image_publisher
- Ebuilds: 1, Testing: 1.16.0-r1 Description:
<p>
Contains a node publish an image stream from single image file
or avi motion file.
</p>
Homepage:http://ros.org/wiki/image_publisher License: BSD
image_rotate
- 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
image_transport
- 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
image_transport_plugins
- 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
image_view
- Ebuilds: 1, Testing: 1.16.0-r1 Description:
A simple viewer for ROS image topics. Includes a specialized viewer
for stereo + disparity images.
Homepage:http://www.ros.org/wiki/image_view License: BSD
image_view2
- Ebuilds: 1, Testing: 2.2.11-r2 Description:
A simple viewer for ROS image topics with draw-on features
Homepage:http://ros.org/wiki/image_view2 License: BSD
imagesift
- Ebuilds: 1, Testing: 1.2.15-r1 Description:
For every image, computes its sift features and send a new message with the image, its intrinsic parameters, and the features.
Parameters include:
display - shows the image on the local computer
Homepage:https://jsk-docs.readthedocs.io/projects/jsk_recognition/en/latest/imagesift License: LGPL-2
imu_complementary_filter
- 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
imu_filter_madgwick
- 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
imu_transformer
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Node/nodelet combination to transform sensor_msgs::Imu data from one frame into another.
Homepage:http://ros.org/wiki/imu_transformer License: GPL-1
industrial_core
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
ROS-Industrial core stack contains packages and libraries for supporing industrial systems
Homepage:http://ros.org/wiki/industrial_core License: BSD
industrial_deprecated
- 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
industrial_msgs
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
The industrial message package containes industrial specific messages
definitions. This package is part of the ROS-Industrial program.
Homepage:http://ros.org/wiki/industrial_msg License: BSD
industrial_robot_client
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
industrial robot client contains generic clients for connecting
to industrial robot controllers with servers that adhere to the
simple message protocol.
Homepage:http://ros.org/wiki/industrial_robot_client License: BSD
industrial_robot_simulator
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
The industrial robot simulator is a stand in for industrial robot driver node(s). It adheres to the driver specification for industrial robot controllers.
Homepage:http://ros.org/wiki/industrial_robot_simulator License: BSD
industrial_robot_status_controller
- Ebuilds: 1, Testing: 0.1.2-r1 Description:
A ros_control controller that reports robot status using the ROS-Industrial RobotStatus message.
Homepage:https://wiki.ros.org License: Apache-2.0
industrial_robot_status_interface
- Ebuilds: 1, Testing: 0.1.2-r1 Description:
Exposes ROS-Industrial's RobotStatus info from hardware_interfaces for consumption by ros_control controllers.
Homepage:https://wiki.ros.org License: Apache-2.0
industrial_utils
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
Industrial utils is a library package that captures common funcitonality for the ROS-Industrial distribution.
Homepage:http://ros.org/wiki/industrial_utils License: BSD
interval_intersection
- Ebuilds: 1, Testing: 0.10.15-r1 Description:
Tools for calculating the intersection of interval messages coming
in on several topics. This package is experimental and unstable.
Expect its APIs to change.
Homepage:http://www.ros.org/wiki/interval_intersection License: BSD
ipa_3d_fov_visualization
- Ebuilds: 1, Testing: 0.6.17-r1 Description:
The ipa_3d_fov_visualization package allows to visualize the field-of-view of a camera.
Homepage:https://wiki.ros.org License: Apache-2.0
ira_laser_tools
- 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
iris_lama
- 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
iris_lama_ros
- Ebuilds: 1, Testing: 1.2.0-r1 Description:
ROS package of IRIS Localization and Mapping (LaMa).
Homepage:https://wiki.ros.org License: BSD
ivcon
- 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
jackal_msgs
- Ebuilds: 1, Testing: 0.8.0-r2 Description:
Messages exclusive to Jackal, especially for representing low-level motor commands and sensors.
Homepage:http://wiki.ros.org/jackal_msgs License: BSD
jackal_navigation
- Ebuilds: 1, Testing: 0.8.0-r2 Description:
Launch files and code for autonomous navigation of the Jackal
Homepage:https://wiki.ros.org License: BSD
joint_states_settler
- 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
joy
- 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
joy_teleop
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
A (to be) generic joystick interface to control a robot
Homepage:https://wiki.ros.org License: BSD
kdl_parser
- 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
kdl_parser_py
- 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
key_teleop
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
A text-based interface to send a robot movement commands
Homepage:https://wiki.ros.org License: BSD
kobuki_core
- Ebuilds: 1, Testing: 0.7.12-r1 Description:
Non-ROS software for Kobuki, Yujin Robot's mobile research base.
Homepage:http://ros.org/wiki/kobuki_core License: BSD
kobuki_dock_drive
- Ebuilds: 1, Testing: 0.7.12-r1 Description:
Dock driving library for Kobuki. Users owning a docking station for Kobuki
can use this tool to develop autonomous docking drive algorithms.
Homepage:http://ros.org/wiki/kobuki_dock_drive License: BSD
kobuki_driver
- Ebuilds: 1, Testing: 0.7.12-r1 Description:
C++ driver library for Kobuki:
Pure C++ driver library for Kobuki. This is for those who do not wish to use ROS on their systems.
Homepage:http://ros.org/wiki/kobuki_driver License: BSD
kobuki_ftdi
- 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
kobuki_msgs
- Ebuilds: 1, Testing: 0.7.0-r1 Description:
<p>
Kobuki message and service types: custom messages and services for Kobuki packages.
</p>
Homepage:http://ros.org/wiki/kobuki_msgs License: BSD
kvh_geo_fog_3d
- Ebuilds: 1, Testing: 1.5.1-r1 Description:
Provides a driver node for KVH GEO FOG 3D INS sensors, messages, and rviz plugins.
Homepage:https://wiki.ros.org License: Apache-2.0
kvh_geo_fog_3d_driver
- Ebuilds: 1, Testing: 1.5.1-r1 Description:
A ROS driver for the KVH Geo Fog 3D INS family of systems.
Homepage:https://wiki.ros.org License: Apache-2.0
kvh_geo_fog_3d_msgs
- Ebuilds: 1, Testing: 1.5.1-r1 Description:
kvh_geo_fog_3d_msgs contains raw messages for the KVH GEO FOG 3D INS devices.
Homepage:https://wiki.ros.org License: Apache-2.0
laser_assembler
- Ebuilds: 1, Testing: 1.7.8-r1 Description:
Provides nodes to assemble point clouds from either LaserScan or PointCloud messages
Homepage:http://ros.org/wiki/laser_assembler License: BSD
laser_cb_detector
- Ebuilds: 1, Testing: 0.10.15-r1 Description:
Extracts checkerboard corners from a dense laser snapshot.
This package is experimental and unstable. Expect its APIs to change.
Homepage:http://www.ros.org/wiki/laser_cb_detector License: BSD
laser_filtering
- Ebuilds: 1, Testing: 0.0.5-r1 Description:
ROS Libraries for filtering specific kinds of laser scans
Homepage:https://wiki.ros.org License: BSD
laser_filters
- Ebuilds: 1, Testing: 1.9.0-r1 Description:
Assorted filters designed to operate on 2D planar laser scanners,
which use the sensor_msgs/LaserScan type.
Homepage:http://ros.org/wiki/laser_filters License: BSD
laser_geometry
- 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
laser_pipeline
- Ebuilds: 1, Testing: 1.6.4-r1 Description:
Meta-package of libraries for processing laser data, including converting laser data
into 3D representations.
Homepage:http://www.ros.org/wiki/laser_pipeline License: BSD
laser_scan_densifier
- 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
laser_scan_matcher
- 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 )
laser_scan_splitter
- 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
leo
- Ebuilds: 1, Testing: 1.2.2-r1 Description:
Metapackage of software for Leo Rover common to the robot and ROS desktop
Homepage:http://wiki.ros.org/leo License: MIT
leo_bringup
- Ebuilds: 1, Testing: 1.2.1-r1 Description:
Scripts and launch files for starting basic Leo Rover functionalities.
Homepage:http://wiki.ros.org/leo_bringup License: MIT
leo_desktop
- Ebuilds: 1, Testing: 0.2.3-r1 Description:
Metapackage of software for operating Leo Rover from ROS desktop
Homepage:http://wiki.ros.org/leo_desktop License: MIT
leo_gazebo
- Ebuilds: 1, Testing: 0.2.0-r1 Description:
Launch files and other resources for simulating Leo Rover in Gazebo.
Homepage:http://wiki.ros.org/leo_gazebo License: MIT
leo_robot
- Ebuilds: 1, Testing: 1.2.1-r1 Description:
Metapackage of software to install on Leo Rover.
Homepage:http://wiki.ros.org/leo_robot License: MIT
leo_teleop
- Ebuilds: 1, Testing: 1.2.2-r1 Description:
Scripts and launch files for Leo Rover teleoperation
Homepage:http://wiki.ros.org/leo License: MIT
leo_viz
- Ebuilds: 1, Testing: 0.2.3-r1 Description:
Visualization launch files and RViz configurations for Leo Rover
Homepage:http://wiki.ros.org/leo_viz License: MIT
libdlib
- 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
libfranka
- Ebuilds: 1, Testing: 0.8.0-r4 Description:
libfranka is a C++ library for Franka Emika research robots
Homepage:https://frankaemika.github.io License: Apache-2.0
libmavconn
- 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 )
libntcan
- Ebuilds: 1, Testing: 0.6.17-r1 Description:
This package wraps the libntcan to use it as a ros dependency.
Homepage:http://www.esd-electronics.com License: proprietary
libphidget22
- Ebuilds: 1, Testing: 1.0.4-r1 Description:
This package wraps the libphidget22 to use it as a ROS dependency
Homepage:http://ros.org/wiki/libphidget22 License: LGPL-2
libphidgets
- Ebuilds: 1, Testing: 0.6.17-r1 Description:
This package wraps the libphidgets to use it as a ros dependency
Homepage:http://ros.org/wiki/libphidgets License: LGPL-2
librealsense2
- 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
lms1xx
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
The lms1xx package contains a basic ROS driver for the SICK LMS1xx line of LIDARs.
Homepage:http://ros.org/wiki/LMS1xx License: LGPL-2
lockfree
- 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
locomotor
- 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
locomove_base
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Extension of locomotor that implements move_base's functionality.
Homepage:https://wiki.ros.org License: BSD
log_view
- 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
map_laser
- Ebuilds: 1, Testing: 0.0.5-r1 Description:
Filters a laser scan to remove points that are in the current static map
Homepage:http://wiki.ros.org/map_laser License: BSD
map_msgs
- Ebuilds: 1, Testing: 1.14.1-r1 Description:
This package defines messages commonly used in mapping packages.
Homepage:http://ros.org/wiki/map_msgs License: BSD
map_server
- 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
marker_msgs
- 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
mbf_abstract_core
- 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
mbf_abstract_nav
- 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
mbf_costmap_core
- 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
mbf_costmap_nav
- 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
mbf_msgs
- 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
mbf_simple_nav
- 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
mesh_msgs_conversions
- Ebuilds: 1, Testing: 1.1.0-r1 Description:
converts point clouds and attributes into meshes and mesh attributes
Homepage:https://wiki.ros.org License: BSD
mesh_navigation
- 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
message_filters
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
A set of message filters which take in messages and may output those messages at a later time, based on the conditions that filter needs met.
Homepage:http://ros.org/wiki/message_filters License: BSD
message_to_tf
- 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
microstrain_3dmgx2_imu
- Ebuilds: 1, Testing: 1.5.13-r1 Description:
A driver for IMUs compatible the microstrain 3DM-GX2 and 3DM-GX3 protocol. Includes
a heavily modified standalone driver pulled from the player distribution,
and a ROS node.
Homepage:http://www.ros.org/wiki/microstrain_3dmgx2_imu License: LGPL-2
mir_dwb_critics
- Ebuilds: 1, Testing: 1.1.3-r1 Description:
Trajectory critics for the dwb_local_planner that work well together with the SBPL global planner on the MiR robot
Homepage:https://github.com/dfki-ric/mir_dwb_critics License: BSD
mir_gazebo
- Ebuilds: 1, Testing: 1.1.3-r1 Description:
Simulation specific launch and configuration files for the MiR100 robot.
Homepage:https://github.com/dfki-ric/mir_robot License: BSD
mir_robot
- Ebuilds: 1, Testing: 1.1.3-r1 Description:
URDF description, Gazebo simulation, navigation, bringup launch files, message and action descriptions for the MiR100 robot.
Homepage:https://github.com/dfki-ric/mir_robot License: BSD
mk
- 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
mocap_optitrack
- 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
monocam_settler
- Ebuilds: 1, Testing: 0.10.15-r1 Description:
Listens on a ImageFeatures topic, and waits for the data to settle.
This package is experimental and unstable.
Expect its APIs to change.
Homepage:http://www.ros.org/wiki/monocam_settler License: BSD
move_base
- 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
move_base_flex
- 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
move_base_msgs
- Ebuilds: 1, Testing: 1.14.1-r1 Description:
Holds the action description and relevant messages for the move_base package.
Homepage:http://wiki.ros.org/move_base_msgs License: BSD
moveit
- 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
moveit_msgs
- Ebuilds: 1, Testing: 0.11.2-r1 Description:
Messages, services and actions used by MoveIt
Homepage:http://moveit.ros.org License: BSD
moveit_opw_kinematics_plugin
- 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
moveit_planners
- Ebuilds: 1, Testing: 1.1.6-r1 Description:
Metapacakge that installs all available planners for MoveIt
Homepage:http://moveit.ros.org License: BSD
moveit_runtime
- Ebuilds: 1, Testing: 1.1.6-r1 Description:
moveit_runtime meta package contains MoveIt packages that are essential for its runtime (e.g. running MoveIt on robots).
Homepage:http://moveit.ros.org License: BSD
moveit_setup_assistant
- Ebuilds: 1, Testing: 1.1.6-r1 Description:
Generates a configuration package that makes it easy to use MoveIt
Homepage:http://moveit.ros.org License: BSD
mpc_local_planner
- 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
nav_2d_msgs
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Basic message types for two dimensional navigation, extending from geometry_msgs::Pose2D.
Homepage:https://wiki.ros.org License: BSD
nav_2d_utils
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
A handful of useful utility functions for nav_core2 packages.
Homepage:https://wiki.ros.org License: BSD
nav_core
- 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
nav_core2
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Interfaces for Costmap, LocalPlanner and GlobalPlanner. Replaces nav_core.
Homepage:https://wiki.ros.org License: BSD
nav_core_adapter
- 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
nav_grid
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
A templatized interface for overlaying a two dimensional grid on the world.
Homepage:https://wiki.ros.org License: BSD
nav_grid_iterators
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Iterator implementations for moving around the cells of a nav_grid in a number of common patterns.
Homepage:https://wiki.ros.org License: BSD
nav_grid_pub_sub
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Publishers and Subscribers for nav_grid data.
Homepage:https://wiki.ros.org License: BSD
nav_grid_server
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Customizable tools for publishing images as NavGrids or OccupancyGrids
Homepage:https://wiki.ros.org License: BSD
nav_msgs
- Ebuilds: 1, Testing: 1.13.1-r1 Description:
nav_msgs defines the common messages used to interact with the
<a href="http://wiki.ros.org/navigation">navigation</a> stack.
Homepage:http://wiki.ros.org/nav_msgs License: BSD
navfn
- 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
navigation
- 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 )
navigation_experimental
- Ebuilds: 1, Testing: 0.3.4-r1 Description:
A collection of navigation plugins and tools: Various recovery behaviors,
local and global planner plugins for move_base, a teleop filter for
obstacle avoidance, a simple control-based move_base replacement
etc.
Homepage:http://wiki.ros.org/navigation_experimental License: BSD
ncd_parser
- Ebuilds: 1, Testing: 0.3.3-r1 Description:
The ncd_parser package reads in .alog data files from the New College Dataset and broadcasts scan and odometry messages to ROS.
Homepage:http://wiki.ros.org/ncd_parser License: BSD
neo_local_planner
- 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
neonavigation
- Ebuilds: 1, Testing: 0.11.2-r1 Description:
The neonavigation meta-package including 3-dof configuration space planner
Homepage:https://wiki.ros.org License: BSD
nmea_comms
- Ebuilds: 1, Testing: 1.2.0-r3 Description:
The nmea_comms package provides helper nodes for transmitting and receiving
the NMEA sentences.
Homepage:http://wiki.ros.org/nmea_comms License: BSD
nmea_msgs
- Ebuilds: 1, Testing: 1.1.0-r1 Description:
The nmea_msgs package contains messages related to data in the NMEA format.
Homepage:http://ros.org/wiki/nmea_msgs License: BSD
nodelet
- 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
nonpersistent_voxel_layer
- Ebuilds: 1, Testing: 1.3.0-r2 Description:
include
This package provides an implementation of a 3D costmap that takes in sensor
data from the world, builds a 3D occupancy grid of the data for only one iteration.
Homepage:http://wiki.ros.org/non-persisent-voxel-layer License: BSD
octomap_mapping
- Ebuilds: 1, Testing: 0.6.6-r1 Description:
Mapping tools to be used with the <a href="https://octomap.github.io/">OctoMap library</a>, implementing a 3D occupancy grid mapping.
Homepage:http://ros.org/wiki/octomap_mapping License: BSD
octomap_msgs
- Ebuilds: 1, Testing: 0.3.5-r1 Description:
This package provides messages and serializations / conversion for the <a href="http://octomap.github.io">OctoMap library</a>.
Homepage:http://ros.org/wiki/octomap_msgs License: BSD
octomap_ros
- Ebuilds: 1, Testing: 0.4.1-r1 Description:
octomap_ros provides conversion functions between ROS and OctoMap's native types.
This enables a convenvient use of the octomap package in ROS.
Homepage:http://ros.org/wiki/octomap_ros License: BSD
octomap_server
- 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
opencv_apps
- 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
opengm
- 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
openni2_camera
- 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
openni2_launch
- Ebuilds: 1, Testing: 1.5.1-r1 Description:
Launch files to start the openni2_camera drivers using rgbd_launch.
Homepage:https://wiki.ros.org License: BSD
openslam_gmapping
- Ebuilds: 1, Testing: 0.2.1-r1 Description:
The catkinized verseion of openslam_gmapping package (https://github.com/OpenSLAM-org/openslam_gmapping/tree/79ef0b0e6d9a12d6390ae64c4c00d37d776abefb)
Homepage:http://openslam.org/gmapping License: BSD
openzen_sensor
- Ebuilds: 1, Testing: 1.2.0-r1 Description:
ROS driver for LP-Research OpenZen
Homepage:https://wiki.ros.org License: ( MIT Boost-1.0 LGPL-2 BSD )
opw_kinematics
- 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
p2os_launch
- Ebuilds: 1, Testing: 2.2.1-r2 Description:
Launch and config files designed for use with the p2os stack.
Homepage:http://ros.org/wiki/p2os-purdue License: BSD
p2os_msgs
- Ebuilds: 1, Testing: 2.2.1-r2 Description:
Defines the messages that are used to communicate with the
p2os_driver package and the ROS infrastructure.
Homepage:http://ros.org/wiki/p2os-purdue License: BSD
panda_moveit_config
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
An automatically generated package with all the configuration and launch files for using the panda with the MoveIt! Motion Planning Framework
Homepage:http://moveit.ros.org/ License: BSD
pass_through_controllers
- 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
pcl_ros
- 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
people
- Ebuilds: 1, Testing: 1.4.2-r1 Description:
The people stack holds algorithms for perceiving people from a number of sensors.
Homepage:http://ros.org/wiki/people License: BSD
perception_pcl
- 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
picovoice_driver
- Ebuilds: 1, Testing: 0.0.4-r1 Description:
ROS Wrappers for the Picovoice libraries
Homepage:https://wiki.ros.org License: Apache-2.0
picovoice_msgs
- Ebuilds: 1, Testing: 0.0.4-r1 Description:
ROS interfaces for interacting with Picovoice driver nodes
Homepage:https://wiki.ros.org License: Apache-2.0
pid
- Ebuilds: 1, Testing: 0.0.28-r1 Description:
Launch a PID control node.
Homepage:http://wiki.ros.org/pid License: BSD
pilz_control
- 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
pilz_robot_programming
- Ebuilds: 1, Testing: 0.5.0-r4 Description:
An Easy to use API to execute standard industrial robot commands like Ptp, Lin, Circ and Sequence using Moveit.
Homepage:https://wiki.ros.org License: LGPL-2
pincher_arm_moveit_config
- Ebuilds: 1, Testing: 0.2.0-r1 Description:
An automatically generated package with all the configuration and launch files for using the pincher_arm with the MoveIt! Motion Planning Framework
Homepage:http://moveit.ros.org/ License: BSD
pluginlib
- 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
pointcloud_to_laserscan
- Ebuilds: 1, Testing: 1.4.1-r1 Description:
Converts a 3D Point Cloud into a 2D laser scan. This is useful for making devices like the Kinect appear like a laser scanner for 2D-based algorithms (e.g. laser-based SLAM).
Homepage:http://ros.org/wiki/perception_pcl License: BSD
polar_scan_matcher
- Ebuilds: 1, Testing: 0.3.3-r1 Description:
<p>
A wrapper around Polar Scan Matcher by Albert Diosi and Lindsay Kleeman, used for laser scan registration.
</p>
Homepage:http://ros.org/wiki/polar_scan_matcher License: GPL-1
polled_camera
- 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
pose_base_controller
- Ebuilds: 1, Testing: 0.3.4-r1 Description:
A node that provides the move_base action server interface, but instead of
planning simply drives towards the target pose using a control-based
approach.
Homepage:http://wiki.ros.org/pose_base_controller License: BSD
pose_follower
- Ebuilds: 1, Testing: 0.3.4-r1 Description:
A implementation of a local planner that attempts to follow a plan as closely as possible.
Homepage:http://wiki.ros.org/pose_follower License: BSD
posedetection_msgs
- Ebuilds: 1, Testing: 4.3.2-r1 Description:
posedetection_msgs provides messages and services to facilitate passing pose detection results and features.
Homepage:http://ros.org/wiki/posedetection_msgs License: BSD
power_monitor
- Ebuilds: 1, Testing: 1.1.10-r1 Description:
The power_monitor collects messages from the ocean_battery_server and
the pr2_power_board, and publishes a summary of their data in a
friendlier message format.
Homepage:http://www.ros.org/wiki/power_monitor License: BSD
power_msgs
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
ROS messages for power measurement and breaker control.
Homepage:http://ros.org/wiki/power_msgs License: BSD
pr2_arm_kinematics
- Ebuilds: 1, Testing: 1.0.11-r1 Description:
This package provides a kinematics implementation for the PR2 robot. It can be used to compute forward and inverse kinematics.
Homepage:http://ros.org/wiki/pr2_arm_kinematics License: BSD
pr2_bringup
- Ebuilds: 1, Testing: 1.6.32-r1 Description:
Launch files and scripts needed to bring a PR2 up into a running state.
Homepage:http://ros.org/wiki/pr2_bringup License: BSD
pr2_bringup_tests
- Ebuilds: 1, Testing: 1.0.15-r1 Description:
Complete functionality tests for PR2. Contains utilities designed to test and verify devices, mechanicals and sensors.
Homepage:http://ros.org/wiki/pr2_bringup_tests License: BSD
pr2_camera_synchronizer
- 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
pr2_common
- 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
pr2_controller_interface
- 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
pr2_controller_manager
- Ebuilds: 1, Testing: 1.8.18-r1 Description:
The controller manager (CM) package provides the infrastructure to run controllers in a hard realtime loop.
Homepage:http://ros.org/pr2_controller_manager License: BSD
pr2_controllers
- Ebuilds: 1, Testing: 1.10.18-r1 Description:
Contains the controllers that run in realtime on the PR2 and supporting packages.
Homepage:http://ros.org/wiki/pr2_controllers License: BSD
pr2_description
- 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
pr2_ethercat_drivers
- Ebuilds: 1, Testing: 1.9.0-r1 Description:
This stack contains drivers for the ethercat system and the peripherals
that connect to it: motor control boards, fingertip sensors, texture
projector, hand accelerometer.
Homepage:http://ros.org/wiki/pr2_ethercat_drivers License: ( BSD GPL-1 )
pr2_gripper_action
- 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
pr2_hardware_interface
- 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
pr2_machine
- 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
pr2_mechanism
- Ebuilds: 1, Testing: 1.8.18-r1 Description:
The pr2_mechanism stack contains the infrastructure to control the PR2 robot in a hard realtime control loop.
Homepage:http://ros.org/wiki/pr2_mechanism License: BSD
pr2_mechanism_diagnostics
- Ebuilds: 1, Testing: 1.8.18-r1 Description:
The `pr2_mechanism_diagnostics` node subscribes to `mechanism_statistics` and publishes diagnostics data for joints and controllers on `/diagnostics`.
Homepage:http://ros.org/wiki/pr2_mechanism_diagnostics License: BSD
pr2_mechanism_model
- 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
pr2_mechanism_msgs
- Ebuilds: 1, Testing: 1.8.2-r1 Description:
This package defines services that are used to communicate with
the realtime control loop. It also defines messages
that represent the state of the realtime controllers, the joints
and the actuators.
Homepage:http://ros.org/wiki/pr2_mechanism_msgs License: BSD
pr2_msgs
- Ebuilds: 1, Testing: 1.13.0-r1 Description:
Messages for representing PR2 state, such as battery information and the PR2 fingertip sensors.
Homepage:http://ros.org/wiki/pr2_msgs License: BSD
pr2_position_scripts
- Ebuilds: 1, Testing: 0.6.2-r1 Description:
This package contains a number of scripts to set various components of the PR2. They are used in the apps to improve usablity.
Homepage:http://ros.org/wiki/pr2_position_scripts License: BSD
pr2_robot
- Ebuilds: 1, Testing: 1.6.32-r1 Description:
This stack collects PR2-specific components that are used in bringing up
a robot.
Homepage:http://ros.org/wiki/pr2_robot License: BSD
pr2_run_stop_auto_restart
- 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
pr2_teleop
- Ebuilds: 1, Testing: 0.6.2-r1 Description:
The pr2_teleop package
Homepage:https://wiki.ros.org License: TODO
pr2_tilt_laser_interface
- 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
pr2_tuckarm
- 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
prbt_grippers
- Ebuilds: 1, Testing: 0.0.5-r2 Description:
The package provides gripper support for the pilz_robots package.
Homepage:http://ros.org/wiki/prbt_grippers License: Apache-2.0
prbt_moveit_config
- Ebuilds: 1, Testing: 0.6.0-r1 Description:
An automatically generated package with all the configuration and launch files for using the prbt with the MoveIt! Motion Planning Framework
Homepage:https://wiki.ros.org/prbt_moveit_config License: Apache-2.0
ps3joy
- 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
psen_scan_v2
- Ebuilds: 1, Testing: 0.3.3-r1 Description:
ROS support for the Pilz laser scanner
Homepage:https://wiki.ros.org License: LGPL-2
py_trees_msgs
- Ebuilds: 1, Testing: 0.3.7-r2 Description:
Messages used by py_trees_ros and some extras for the mock demos/tests.
Homepage:http://ros.org/wiki/py_trees_msgs License: BSD
python_qt_binding
- 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
qpoases_vendor
- Ebuilds: 1, Testing: 3.2.1-r1 Description:
Wrapper around qpOASES to make it available to the ROS ecosystem.
Homepage:https://projects.coin-or.org/qpOASES License: ( Apache-2.0 LGPL-2 )
qt_gui
- 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
qt_gui_app
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
qt_gui_app provides the main to start an instance of the integrated graphical user interface provided by qt_gui.
Homepage:http://ros.org/wiki/qt_gui_app License: BSD
qt_gui_core
- Ebuilds: 1, Testing: 0.4.2-r1 Description:
Integration of the ROS package system and ROS-specific plugins for a Qt-based GUI.
Homepage:http://ros.org/wiki/qt_gui_core License: BSD
qt_gui_cpp
- 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
quanergy_client_ros
- Ebuilds: 1, Testing: 4.0.1-r1 Description:
The quanergy_client_ros package provides a ROS driver for Quanergy sensors
Homepage:https://wiki.ros.org License: MIT
qwt_dependency
- Ebuilds: 1, Testing: 1.1.1-r1 Description:
This encapsulates the Qwt dependency for a specific ROS distribution and its Qt version
Homepage:https://wiki.ros.org License: BSD
radar_msgs
- Ebuilds: 1, Testing: 0.1.0-r2 Description:
Standard ROS messages for radars
Homepage:https://wiki.ros.org License: Apache-2.0
random_numbers
- 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
raw_description
- 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
rc_dynamics_api
- 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
rc_genicam_api
- 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
rc_genicam_camera
- Ebuilds: 1, Testing: 1.3.0-r1 Description:
The rc_genicam_camera provides images from a GenICam compatible camera.
Homepage:https://wiki.ros.org License: BSD
rc_genicam_driver
- Ebuilds: 1, Testing: 0.6.3-r1 Description:
The rc_genicam_driver provides data from a Roboception rc_visard 3D sensor or rc_cube on several ROS topics.
Homepage:http://wiki.ros.org/rc_visard_driver License: BSD
rc_visard_driver
- Ebuilds: 1, Testing: 3.2.4-r1 Description:
The rc_visard_driver provides data from a Roboception rc_visard 3D sensor on several ROS topics.
Homepage:http://wiki.ros.org/rc_visard_driver License: BSD
rcdiscover
- Ebuilds: 1, Testing: 1.1.4-r1 Description:
This package contains tools for the discovery of Roboception devices via GigE Vision.
Homepage:https://github.com/roboception/rcdiscover License: BSD
realsense2_camera
- Ebuilds: 1, Testing: 2.3.2-r1 Description:
RealSense Camera package allowing access to Intel T265 Tracking module and SR300 and D400 3D cameras
Homepage:http://www.ros.org/wiki/RealSense License: Apache-2.0
realtime_tools
- Ebuilds: 1, Testing: 1.16.1-r1 Description:
Contains a set of tools that can be used from a hard
realtime thread, without breaking the realtime behavior.
Homepage:http://ros.org/wiki/realtime_tools License: BSD
resource_retriever
- 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
rgbd_launch
- Ebuilds: 1, Testing: 2.3.0-r1 Description:
Launch files to open an RGBD device and load all nodelets to
convert raw depth/RGB/IR streams to depth images, disparity images,
and (registered) point clouds.
Homepage:http://www.ros.org/wiki/rgbd_launch License: BSD
rm_dbus
- Ebuilds: 1, Testing: 0.1.7-r4 Description:
A package that uses dbus to read remote control information
Homepage:https://wiki.ros.org License: BSD
rm_hw
- Ebuilds: 1, Testing: 0.1.7-r4 Description:
ROS control warped interface for RoboMaster motor and some robot hardware
Homepage:https://wiki.ros.org License: BSD
rm_msgs
- Ebuilds: 1, Testing: 0.1.7-r4 Description:
The rm_msgs package provides all the messages for all kind of robot
Homepage:https://wiki.ros.org License: BSD
robot
- Ebuilds: 1, Testing: 1.5.0-r1 Description:
A metapackage which extends ros_base and includes ROS libaries for any robot hardware. It may not contain any GUI dependencies.
Homepage:https://github.com/ros/metapackages License: BSD
robot_nav_tools
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
A collection of tools / accessories for the robot_navigation packages
Homepage:https://wiki.ros.org License: BSD
robot_nav_viz_demos
- Ebuilds: 1, Testing: 0.3.0-r2 Description:
Demos for testing/demonstrating the robot_nav_rviz_plugins and color_util packages
Homepage:https://wiki.ros.org License: BSD
robot_state_publisher
- 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
robot_upstart
- 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_babel_fish
- Ebuilds: 1, Testing: 0.9.1-r1 Description:
A runtime message handler for ROS.
Allows subscription, publishing, calling of services and actions with messages known only at runtime.
Homepage:https://wiki.ros.org License: MIT
ros_base
- Ebuilds: 1, Testing: 1.5.0-r1 Description:
A metapackage which extends ros_core and includes other basic non-robot tools like actionlib, dynamic reconfigure, nodelets, and pluginlib.
Homepage:https://github.com/ros/metapackages License: BSD
ros_control
- Ebuilds: 1, Testing: 0.19.5-r1 Description:
A set of packages that include controller interfaces, controller managers, transmissions and hardware_interfaces.
Homepage:http://ros.org/wiki/ros_control License: BSD
ros_core
- Ebuilds: 1, Testing: 1.5.0-r1 Description:
A metapackage to aggregate the packages required to use publish / subscribe, services, launch files, and other core ROS concepts.
Homepage:https://github.com/ros/metapackages License: BSD
ros_environment
- Ebuilds: 1, Testing: 1.3.2-r1 Description:
The package provides the environment variables `ROS_VERSION`, `ROS_DISTRO`, `ROS_PACKAGE_PATH`, and `ROS_ETC_DIR`.
Homepage:https://github.com/ros/ros_environment License: Apache-2.0
ros_ign
- Ebuilds: 1, Testing: 0.111.1-r2 Description:
Meta-package containing interfaces for using ROS with <a href="https://ignitionrobotics.org">Ignition</a> simulation.
Homepage:https://wiki.ros.org License: Apache-2.0
ros_numpy
- Ebuilds: 1, Testing: 0.0.5-r2 Description:
A collection of conversion function for extracting numpy arrays from messages
Homepage:http://wiki.ros.org/ros_numpy License: MIT
ros_pytest
- Ebuilds: 1, Testing: 0.2.1-r1 Description:
The ros_pytest package
Homepage:https://wiki.ros.org License: MIT
ros_tutorials
- Ebuilds: 1, Testing: 0.10.2-r1 Description:
ros_tutorials contains packages that demonstrate various features of ROS,
as well as support packages which help demonstrate those features.
Homepage:http://www.ros.org/wiki/ros_tutorials License: BSD
rosapi
- Ebuilds: 1, Testing: 0.11.13-r1 Description:
Provides service calls for getting ros meta-information, like list of
topics, services, params, etc.
Homepage:http://ros.org/wiki/rosapi License: BSD
rosatomic
- 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 )
rosauth
- Ebuilds: 1, Testing: 1.0.1-r1 Description:
Server Side tools for Authorization and Authentication of ROS Clients
Homepage:http://ros.org/wiki/rosauth License: BSD
rosbag
- 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
rosbag_pandas
- Ebuilds: 1, Testing: 0.5.4-r1 Description:
Create a Pandas data frame from a ros bag file.
Homepage:https://wiki.ros.org License: Apache-2.0
rosbag_snapshot_msgs
- Ebuilds: 1, Testing: 1.0.3-r1 Description:
Service and message definitions for rosbag_snapshot
Homepage:https://wiki.ros.org License: BSD
rosbag_storage
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
This is a set of tools for recording from and playing back ROS
message without relying on the ROS client library.
Homepage:https://wiki.ros.org License: BSD
rosbash
- Ebuilds: 1, Testing: 1.15.8-r1 Description:
Assorted shell commands for using ros with bash.
Homepage:http://www.ros.org/wiki/rosbash License: BSD
rosboost_cfg
- Ebuilds: 1, Testing: 1.15.8-r1 Description:
Contains scripts used by the rosboost-cfg tool for determining cflags/lflags/etc. of boost on your system
Homepage:http://ros.org/wiki/rosboost_cfg License: BSD
rosbridge_library
- Ebuilds: 1, Testing: 0.11.13-r1 Description:
The core rosbridge package, responsible for interpreting JSON and performing
the appropriate ROS action, like subscribe, publish, call service, and
interact with params.
Homepage:http://ros.org/wiki/rosbridge_library License: BSD
rosbridge_suite
- 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
rosbuild
- Ebuilds: 1, Testing: 1.15.8-r1 Description:
rosbuild contains scripts for managing the CMake-based build system for ROS.
Homepage:http://ros.org/wiki/rosbuild License: BSD
rosconsole_bridge
- Ebuilds: 1, Testing: 0.5.4-r1 Description:
rosconsole_bridge is a package used in conjunction with console_bridge and rosconsole for connecting console_bridge-based logging to rosconsole-based logging.
Homepage:http://www.ros.org/wiki/rosconsole_bridge License: BSD
roscpp
- 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
roscpp_serialization
- 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
roscpp_traits
- 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
roscpp_tutorials
- Ebuilds: 1, Testing: 0.10.2-r1 Description:
This package attempts to show the features of ROS step-by-step,
including using messages, servers, parameters, etc.
Homepage:http://www.ros.org/wiki/roscpp_tutorials License: BSD
roscreate
- 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
rosdiagnostic
- Ebuilds: 1, Testing: 1.10.4-r1 Description:
Command to print aggregated diagnostic contents to the command line
Homepage:https://wiki.ros.org License: BSD
rosfmt
- 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
rosgraph
- 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
rosgraph_msgs
- Ebuilds: 1, Testing: 1.11.3-r1 Description:
Messages relating to the ROS Computation Graph. These are generally considered to be low-level messages that end users do not interact with.
Homepage:http://ros.org/wiki/rosgraph_msgs License: BSD
roslang
- 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
roslaunch
- 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
roslib
- 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
roslint
- 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
roslisp
- Ebuilds: 1, Testing: 1.9.24-r1 Description:
Lisp client library for ROS, the Robot Operating System.
Homepage:http://ros.org/wiki/roslisp License: BSD
roslisp_repl
- Ebuilds: 1, Testing: 0.4.15-r1 Description:
This package provides a script that launches Emacs with Slime (the
Superior Lisp Interaction Mode) ready for Lisp development and
roslisp.
Homepage:https://github.com/code-iai/ros_emacs_utils License: public_domain
roslz4
- 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
rosmake
- Ebuilds: 1, Testing: 1.15.8-r1 Description:
rosmake is a ros dependency aware build tool which can be used to
build all dependencies in the correct order.
Homepage:http://wiki.ros.org/rosmake License: BSD
rosmon
- 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
rosmon_core
- 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
rosmon_msgs
- 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
rosmsg
- 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
rosnode
- 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
rosout
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
System-wide logging mechanism for messages sent to the /rosout topic.
Homepage:http://ros.org/wiki/rosout License: BSD
rosparam
- 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
rosping
- 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
rospy
- 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
rospy_tutorials
- Ebuilds: 1, Testing: 0.10.2-r1 Description:
This package attempts to show the features of ROS python API step-by-step,
including using messages, servers, parameters, etc. These tutorials are compatible with the nodes in roscpp_tutorial.
Homepage:http://www.ros.org/wiki/rospy_tutorials License: BSD
rosrt
- 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
rosserial_server
- Ebuilds: 1, Testing: 0.9.2-r1 Description:
A more performance- and stability-oriented server alternative implemented
in C++ to rosserial_python.
Homepage:https://wiki.ros.org License: BSD
rosservice
- 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
rostest
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
Integration test suite based on roslaunch that is compatible with xUnit frameworks.
Homepage:http://ros.org/wiki/rostest License: BSD
rostime
- Ebuilds: 1, Testing: 0.7.2-r1 Description:
Time and Duration implementations for C++ libraries, including roscpp.
Homepage:http://ros.org/wiki/rostime License: BSD
rostopic
- 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
rosunit
- Ebuilds: 1, Testing: 1.15.8-r1 Description:
Unit-testing package for ROS. This is a lower-level library for rostest and handles unit tests, whereas rostest handles integration tests.
Homepage:http://wiki.ros.org/rosunit License: BSD
roswtf
- Ebuilds: 1, Testing: 1.15.13-r1 Description:
roswtf is a tool for diagnosing issues with a running ROS system. Think of it as a FAQ implemented in code.
Homepage:http://wiki.ros.org/roswtf License: BSD
rotate_recovery
- Ebuilds: 1, Testing: 1.17.1-r1 Description:
This package provides a recovery behavior for the navigation stack that attempts to clear space by performing a 360 degree rotation of the robot.
Homepage:http://wiki.ros.org/rotate_recovery License: BSD
rqt
- 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
rqt_action
- 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
rqt_bag
- Ebuilds: 1, Testing: 0.5.1-r1 Description:
rqt_bag provides a GUI plugin for displaying and replaying ROS bag files.
Homepage:http://wiki.ros.org/rqt_bag License: BSD
rqt_bag_plugins
- Ebuilds: 1, Testing: 0.5.1-r1 Description:
rqt_bag provides a GUI plugin for displaying and replaying ROS bag files.
Homepage:http://wiki.ros.org/rqt_bag License: BSD
rqt_common_plugins
- 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
rqt_console
- Ebuilds: 1, Testing: 0.4.11-r1 Description:
rqt_console provides a GUI plugin for displaying and filtering ROS messages.
Homepage:http://wiki.ros.org/rqt_console License: BSD
rqt_dep
- Ebuilds: 1, Testing: 0.4.12-r1 Description:
rqt_dep provides a GUI plugin for visualizing the ROS dependency graph.
Homepage:http://wiki.ros.org/rqt_dep License: BSD
rqt_drone_teleop
- Ebuilds: 1, Testing: 1.4.2-r1 Description:
A common drone teleop interface for all drone exercises in the JdeRobot Robotics Academy
Homepage:https://wiki.ros.org License: MIT
rqt_graph
- 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
rqt_ground_robot_teleop
- Ebuilds: 1, Testing: 1.4.2-r1 Description:
A common ground robot teleop interface for all ground robot exercises in the JdeRobot Robotics Academy
Homepage:https://wiki.ros.org License: MIT
rqt_gui
- Ebuilds: 1, Testing: 0.5.2-r1 Description:
rqt_gui provides the main to start an instance of the ROS integrated graphical user interface provided by qt_gui.
Homepage:http://ros.org/wiki/rqt_gui License: BSD
rqt_gui_cpp
- Ebuilds: 1, Testing: 0.5.2-r1 Description:
rqt_gui_cpp enables GUI plugins to use the C++ client library for ROS.
Homepage:http://ros.org/wiki/rqt_gui_cpp License: BSD
rqt_gui_py
- Ebuilds: 1, Testing: 0.5.2-r1 Description:
rqt_gui_py enables GUI plugins to use the Python client library for ROS.
Homepage:http://ros.org/wiki/rqt_gui_py License: BSD
rqt_image_view
- Ebuilds: 1, Testing: 0.4.16-r1 Description:
rqt_image_view provides a GUI plugin for displaying images using image_transport.
Homepage:http://wiki.ros.org/rqt_image_view License: BSD
rqt_launch
- Ebuilds: 1, Testing: 0.4.9-r1 Description:
This rqt plugin ROS package provides easy view of .launch files.
User can also start and end node by node that are defined in those files.
Homepage:http://wiki.ros.org/rqt_launch License: BSD
rqt_logger_level
- Ebuilds: 1, Testing: 0.4.11-r1 Description:
rqt_logger_level provides a GUI plugin for configuring the logger level of ROS nodes.<br/>
<br/>
rqt_logger_level takes over `wx`-based tool [[rxloggerlevel]].
Homepage:http://wiki.ros.org/rqt_logger_level License: BSD
rqt_moveit
- 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
rqt_msg
- 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
rqt_multiplot
- Ebuilds: 1, Testing: 0.0.12-r1 Description:
rqt_multiplot provides a GUI plugin for visualizing numeric values in multiple 2D plots using the Qwt plotting backend.
Homepage:https://wiki.ros.org License: LGPL-2
rqt_nav_view
- Ebuilds: 1, Testing: 0.5.7-r1 Description:
rqt_nav_view provides a gui for viewing navigation maps and paths.
Homepage:http://wiki.ros.org/rqt_nav_view License: BSD
rqt_plot
- Ebuilds: 1, Testing: 0.4.13-r1 Description:
rqt_plot provides a GUI plugin visualizing numeric values in a 2D plot using different plotting backends.
Homepage:http://wiki.ros.org/rqt_plot License: BSD
rqt_pr2_dashboard
- 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
rqt_publisher
- Ebuilds: 1, Testing: 0.4.10-r1 Description:
rqt_publisher provides a GUI plugin for publishing arbitrary messages with fixed or computed field values.
Homepage:http://wiki.ros.org/rqt_publisher License: BSD
rqt_py_common
- 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
rqt_py_console
- Ebuilds: 1, Testing: 0.4.10-r1 Description:
rqt_py_console is a Python GUI plugin providing an interactive Python console.
Homepage:http://wiki.ros.org/rqt_py_console License: BSD
rqt_py_trees
- Ebuilds: 1, Testing: 0.4.1-r1 Description:
rqt_py_trees provides a GUI plugin for visualizing py_trees behaviour trees based on rqt_tf_tree.
Homepage:http://ros.org/wiki/rqt_py_trees License: BSD
rqt_reconfigure
- 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
rqt_robot_monitor
- 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
rqt_robot_plugins
- 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
rqt_rosmon
- 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
rqt_rviz
- 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
rqt_shell
- Ebuilds: 1, Testing: 0.4.11-r1 Description:
rqt_shell is a Python GUI plugin providing an interactive shell.
Homepage:http://wiki.ros.org/rqt_shell License: BSD
rqt_srv
- 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
rqt_tf_tree
- Ebuilds: 1, Testing: 0.6.2-r1 Description:
rqt_tf_tree provides a GUI plugin for visualizing the ROS TF frame tree.
Homepage:http://wiki.ros.org/rqt_tf_tree License: BSD
rqt_topic
- Ebuilds: 1, Testing: 0.4.12-r1 Description:
rqt_topic provides a GUI plugin for displaying debug information about ROS topics including publishers, subscribers, publishing rate, and ROS Messages.
Homepage:http://wiki.ros.org/rqt_topic License: BSD
rqt_web
- Ebuilds: 1, Testing: 0.4.10-r1 Description:
rqt_web is a simple web content viewer for rqt. Users can show web content in Qt-based window by specifying its URL.
Homepage:http://wiki.ros.org/rqt_web License: BSD
rtcm_msgs
- Ebuilds: 1, Testing: 1.0.0-r1 Description:
The rtcm_msgs package contains messages related to data in the RTCM format.
Homepage:https://wiki.ros.org License: BSD
sbg_driver
- Ebuilds: 1, Testing: 3.1.1-r7 Description:
ROS driver package for communication with the SBG navigation systems.
Homepage:http://wiki.ros.org/sbg_driver License: MIT
sbpl_lattice_planner
- Ebuilds: 1, Testing: 0.3.4-r1 Description:
The sbpl_lattice_planner is a global planner plugin for move_base and wraps
the SBPL search-based planning library.
Homepage:http://wiki.ros.org/sbpl_lattice_planner License: BSD
sbpl_recovery
- Ebuilds: 1, Testing: 0.3.4-r1 Description:
A recovery behavior that uses the sbpl lattice planner and the pose
follower to try to plan in full 3D to get the robot out of really tricky
situations.
Homepage:http://wiki.ros.org/sbpl_recovery License: BSD
scenario_test_tools
- 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
schunk_description
- 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
schunk_libm5api
- 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
schunk_powercube_chain
- 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
schunk_sdh
- Ebuilds: 1, Testing: 0.6.14-r1 Description:
This package provides an interface for operating the schunk dexterous hand (SDH), including the tactile sensors.
Homepage:http://ros.org/wiki/schunk_sdh License: Apache-2.0
schunk_simulated_tactile_sensors
- 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
sdhlibrary_cpp
- Ebuilds: 1, Testing: 0.2.10-r1 Description:
This is SDHLibrary-CPP, the C++ library to access
an SDH (SCHUNK Dexterous Hand)
Homepage:https://wiki.ros.org License: Apache-2.0
sensor_msgs
- Ebuilds: 1, Testing: 1.13.1-r1 Description:
This package defines messages for commonly used sensors, including
cameras and scanning laser rangefinders.
Homepage:http://ros.org/wiki/sensor_msgs License: BSD
settlerlib
- 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
shape_msgs
- Ebuilds: 1, Testing: 1.13.1-r1 Description:
This package contains messages for defining shapes, such as simple solid
object primitives (cube, sphere, etc), planes, and meshes.
Homepage:http://wiki.ros.org/shape_msgs License: BSD
sick_safetyscanners
- Ebuilds: 1, Testing: 1.0.8-r1 Description:
Provides an Interface to read the sensor output of a SICK
Safety Scanner
Homepage:https://wiki.ros.org License: ALv2
sick_scan
- Ebuilds: 1, Testing: 1.10.1-r1 Description:
A ROS driver for the SICK TiM and SICK MRS series of lidars.
This package is based on the original sick_tim-repository of Martin Günther et al.
Homepage:http://wiki.ros.org/sick_scan License: BSD
sick_tim
- Ebuilds: 1, Testing: 0.0.17-r1 Description:
A ROS driver for the SICK TiM and the SICK MRS 1000 laser scanners.
Homepage:http://wiki.ros.org/sick_tim License: BSD
simple_message
- 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
single_joint_position_action
- Ebuilds: 1, Testing: 1.10.18-r1 Description:
The single joint position action is a node that provides an action
interface for commanding a trajectory to move a joint to a particular
position. The action reports success when the joint reaches the desired
position.
Homepage:http://ros.org/wiki/single_joint_position_action License: BSD
slam_gmapping
- Ebuilds: 1, Testing: 1.4.2-r1 Description:
slam_gmapping contains a wrapper around gmapping which provides SLAM capabilities.
Homepage:http://ros.org/wiki/slam_gmapping License: ( BSD Apache-2.0 )
slam_karto
- Ebuilds: 1, Testing: 0.8.1-r1 Description:
This package pulls in the Karto mapping library, and provides a ROS
wrapper for using it.
Homepage:https://wiki.ros.org License: LGPL-2
slam_toolbox
- Ebuilds: 1, Testing: 1.5.6-r1 Description:
This package provides a sped up improved slam karto with updated SDK and visualization and modification toolsets
Homepage:https://wiki.ros.org License: LGPL-2
slam_toolbox_msgs
- Ebuilds: 1, Testing: 1.5.6-r1 Description:
This package provides a sped up improved slam karto with updated SDK and visualization and modification toolsets
Homepage:https://wiki.ros.org License: LGPL-2
slam_toolbox_rviz
- Ebuilds: 1, Testing: 1.5.6-r1 Description:
This package provides a sped up improved slam karto with updated SDK and visualization and modification toolsets
Homepage:https://wiki.ros.org License: LGPL-2
slic
- 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
smach
- 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
smach_msgs
- Ebuilds: 1, Testing: 2.5.0-r1 Description:
this package contains a set of messages that are used by the introspection
interfaces for smach.
Homepage:https://wiki.ros.org License: BSD
smach_ros
- 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
smach_viewer
- 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
smclib
- 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
sob_layer
- Ebuilds: 1, Testing: 0.1.0-r1 Description:
Plugin-replacement for the default costmap_2d::InflationLayer.
Homepage:https://wiki.ros.org License: MIT
socketcan_interface
- Ebuilds: 1, Testing: 0.8.5-r1 Description:
Generic CAN interface description with helpers for filtering and driver implementation. Further a socketcan implementation based on boost::asio is included.
Homepage:http://wiki.ros.org/socketcan_interface License: LGPL-2
soem
- 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
std_msgs
- 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
stereo_msgs
- Ebuilds: 1, Testing: 1.13.1-r1 Description:
stereo_msgs contains messages specific to stereo processing, such as disparity images.
Homepage:http://wiki.ros.org/stereo_msgs License: BSD
swri_console
- Ebuilds: 1, Testing: 1.1.0-r1 Description:
A rosout GUI viewer developed at Southwest Research Insititute as an
alternative to rqt_console.
Homepage:http://ros.org/wiki/swri_console License: BSD
swri_nodelet
- 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
swri_rospy
- Ebuilds: 1, Testing: 2.14.2-r1 Description:
This package provides added functionality on top of rospy, including a
single-threaded callback queue.
Homepage:https://wiki.ros.org License: BSD
swri_route_util
- Ebuilds: 1, Testing: 2.14.2-r1 Description:
This library provides functionality to simplify working with the
navigation messages defined in marti_nav_msgs.
Homepage:https://wiki.ros.org License: BSD
swri_yaml_util
- Ebuilds: 1, Testing: 2.14.2-r1 Description:
Provides wrappers around the yaml-cpp library for various utility functions
and to abstract out the API changes made to yaml-cpp between ubuntu:precise
and ubuntu:trusty.
Homepage:https://github.com/swri-robotics/marti_common License: BSD
taskflow
- Ebuilds: 1, Testing: 3.0.0-r3 Description:
The taskflow package
Homepage:https://wiki.ros.org License: MIT
teb_local_planner
- 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
teleop_tools
- Ebuilds: 1, Testing: 0.4.0-r1 Description:
A set of generic teleoperation tools for any robot.
Homepage:https://wiki.ros.org License: BSD
tesseract_srdf
- Ebuilds: 1, Testing: 0.6.7-r1 Description:
The tesseract_srdf package for parsing Tesseract specific srdf
Homepage:https://wiki.ros.org License: Apache-2.0
tesseract_support
- Ebuilds: 1, Testing: 0.6.7-r1 Description:
The tesseract_support package containing files for test and examples
Homepage:https://wiki.ros.org License: Apache-2.0
tesseract_urdf
- Ebuilds: 1, Testing: 0.6.7-r1 Description:
The tesseract_urdf package for parsing tesseract specific urdf
Homepage:https://wiki.ros.org License: Apache-2.0
test_osm
- 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
tf
- 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
tf2
- 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
tf2_2d
- Ebuilds: 1, Testing: 0.6.4-r1 Description:
A set of 2D geometry classes modeled after the 3D geometry classes in tf2.
Homepage:https://wiki.ros.org License: BSD
tf2_ros
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
This package contains the ROS bindings for the tf2 library, for both Python and C++.
Homepage:http://www.ros.org/wiki/tf2_ros License: BSD
tf2_sensor_msgs
- Ebuilds: 1, Testing: 0.7.5-r1 Description:
Small lib to transform sensor_msgs with tf. Most notably, PointCloud2
Homepage:http://www.ros.org/wiki/tf2_ros License: BSD
tf_conversions
- 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
thunder_line_follower_pmr3100
- Ebuilds: 1, Testing: 0.1.1-r1 Description:
<p>Simulation environment for a line follower development</p>
<p>Created for the discipline PMR3100 - Intro to Mechatronics from Poli-USP</p>
Homepage:https://wiki.ros.org License: MIT
tile_map
- Ebuilds: 1, Testing: 1.4.1-r1 Description:
Tile map provides a slippy map style interface for visualizing
OpenStreetMap and GooleMap tiles. A mapviz visualization plug-in is also
implemented
Homepage:https://github.com/swri-robotics/mapviz License: BSD
timestamp_tools
- Ebuilds: 1, Testing: 1.6.9-r1 Description:
This package is currently for internal use only. Its API may change
without warning in the future. This package is deprecated.
Homepage:http://www.ros.org/wiki/timestamp_tools License: BSD
topic_tools
- 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
trac_ik
- 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
trac_ik_lib
- 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
trac_ik_python
- Ebuilds: 1, Testing: 1.6.6-r1 Description:
The trac_ik_python package contains a python wrapper using SWIG
for trac_ik_lib
Homepage:https://wiki.ros.org License: BSD
trajectory_msgs
- 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
trajectory_tracker
- Ebuilds: 1, Testing: 0.11.2-r1 Description:
Path following control package for wheeled mobile robot
Homepage:https://wiki.ros.org License: BSD
turtle_actionlib
- Ebuilds: 1, Testing: 0.2.0-r1 Description:
turtle_actionlib demonstrates how to write an action server and client with the turtlesim. The shape_server provides and action interface for drawing regular polygons with the turtlesim.
Homepage:http://ros.org/wiki/turtle_actionlib License: BSD
turtle_tf
- 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
turtle_tf2
- 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
turtlebot3
- Ebuilds: 1, Testing: 1.2.5-r1 Description:
ROS packages for the Turtlebot3 (meta package)
Homepage:http://wiki.ros.org/turtlebot3 License: ( Apache-2.0 BSD )
turtlebot3_example
- 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
turtlebot3_fake
- Ebuilds: 1, Testing: 1.3.2-r2 Description:
Package for TurtleBot3 fake node. With this package, simple tests can be done without a robot.
You can do simple tests using this package on rviz without real robots.
Homepage:http://wiki.ros.org/turtlebot3_fake License: Apache-2.0
turtlebot3_slam
- Ebuilds: 1, Testing: 1.2.5-r1 Description:
The turtlebot3_slam package provides roslaunch scripts for starting the SLAM
Homepage:http://wiki.ros.org/turtlebot3_slam License: Apache-2.0
turtlesim
- Ebuilds: 1, Testing: 0.10.2-r1 Description:
turtlesim is a tool made for teaching ROS and ROS packages.
Homepage:http://www.ros.org/wiki/turtlesim License: BSD
twist_controller
- 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
twist_mux
- 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
twist_mux_msgs
- Ebuilds: 1, Testing: 2.1.0-r1 Description:
The twist_mux msgs and actions package
Homepage:https://wiki.ros.org License: CC-BY-NC-SA-4.0
ublox_msgs
- Ebuilds: 1, Testing: 1.5.0-r1 Description:
ublox_msgs contains raw messages for u-blox GNSS devices.
Homepage:http://ros.org/wiki/ublox License: BSD
ublox_serialization
- Ebuilds: 1, Testing: 1.5.0-r1 Description:
ublox_serialization provides header files for serialization of ROS messages to and from u-blox message format.
Homepage:http://ros.org/wiki/ublox License: BSD
ueye_cam
- Ebuilds: 1, Testing: 1.0.19-r1 Description:
A ROS nodelet and node that wraps the driver API for UEye cameras
by IDS Imaging Development Systems GMBH.
Homepage:https://wiki.ros.org License: BSD
unique_id
- Ebuilds: 1, Testing: 1.0.6-r1 Description:
ROS Python and C++ interfaces for universally unique identifiers.
Homepage:http://ros.org/wiki/unique_id License: BSD
unique_identifier
- Ebuilds: 1, Testing: 1.0.6-r1 Description:
ROS messages and interfaces for universally unique identifiers.
Not needed for wet packages, use only to resolve dry stack
dependencies.
Homepage:http://ros.org/wiki/unique_identifier License: BSD
ur_msgs
- Ebuilds: 1, Testing: 1.3.4-r1 Description:
Message and service definitions for interacting with Universal Robots robot controllers.
Homepage:https://wiki.ros.org License: BSD
urdf
- 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
urdf_parser_plugin
- Ebuilds: 1, Testing: 1.13.2-r1 Description:
This package contains a C++ base class for URDF parsers.
Homepage:http://ros.org/wiki/urdf License: BSD
variant_msgs
- 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
video_stream_opencv
- 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
vision_msgs
- Ebuilds: 1, Testing: 0.0.1-r1 Description:
Messages for interfacing with various computer vision pipelines, such as
object detectors.
Homepage:https://wiki.ros.org License: Apache-2.0
vision_opencv
- Ebuilds: 1, Testing: 1.15.0-r1 Description:
Packages for interfacing ROS with OpenCV, a library of programming functions for real time computer vision.
Homepage:http://www.ros.org/wiki/vision_opencv License: BSD
visp_auto_tracker
- 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
visp_tracker
- 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
visualization_msgs
- 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
voxel_grid
- 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
vrpn
- Ebuilds: 1, Testing: 7.34.0-r2 Description:
The VRPN is a library and set of servers that interfaces with virtual-reality systems, such as VICON, OptiTrack, and others.
Homepage:https://github.com/vrpn/vrpn/wiki License: BSL1.0
vrpn_client_ros
- Ebuilds: 1, Testing: 0.2.2-r1 Description:
ROS client nodes for the <a href="https://github.com/vrpn/vrpn/wiki">VRPN</a> library, compatible with VICON, OptiTrack, and other <a href="https://github.com/vrpn/vrpn/wiki/Supported-hardware-devices">hardware interfaces</a>.
Homepage:https://wiki.ros.org License: BSD
warthog_msgs
- Ebuilds: 1, Testing: 0.1.4-r1 Description:
Messages exclusive to Warthog, especially for representing low-level motor commands and sensors.
Homepage:http://wiki.ros.org/warthog_msgs License: BSD
webkit_dependency
- Ebuilds: 1, Testing: 1.1.2-r1 Description:
This encapsulates the WebKit dependency for a specific ROS distribution and its Qt version
Homepage:https://wiki.ros.org License: BSD
webots_ros
- Ebuilds: 1, Testing: 4.1.0-r1 Description:
The ROS package containing examples for interfacing ROS with the standard ROS controller of Webots
Homepage:http://wiki.ros.org/webots_ros License: Apache-2.0
wge100_camera
- Ebuilds: 1, Testing: 1.8.5-r1 Description:
A ROS node and assorted tools to provide access to the WGE100
camera used in the forearms and the stereo cameras of the PR2
robot.
Homepage:http://www.ros.org/wiki/wge100_camera License: GPL-1
wge100_camera_firmware
- 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
wge100_driver
- Ebuilds: 1, Testing: 1.8.5-r1 Description:
This stack contains the ROS driver and firmware for the WGE100 camera used on the PR2 robot.
Homepage:http://ros.org/wiki/wge100_driver License: ( BSD GPL-1 GPL-1 )
wiimote
- 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
wireless_msgs
- Ebuilds: 1, Testing: 0.1.1-r2 Description:
Messages for describing a wireless network such as bitrate, essid, and link quality.
Homepage:https://wiki.ros.org License: BSD
wireless_watcher
- Ebuilds: 1, Testing: 0.1.1-r2 Description:
A Python-based which publishes connection information about a linux wireless interface.
Homepage:https://wiki.ros.org License: BSD
wu_ros_tools
- Ebuilds: 1, Testing: 0.3.0-r1 Description:
A collection of tools for making a variety of generic ROS-related tasks easier.
Homepage:http://ros.org/wiki/wu_ros_tools License: BSD
xacro
- 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
xmlrpcpp
- 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
xpp
- 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
xpp_hyq
- 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
xpp_quadrotor
- 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
xpp_states
- 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
xv_11_laser_driver
- Ebuilds: 1, Testing: 0.3.0-r1 Description:
Neato XV-11 Laser Driver. This driver works with the laser when it is removed from the XV-11 Robot as opposed to reading scans from the Neato's USB port.
Homepage:http://ros.org/wiki/xv_11_laser_driver License: BSD
ypspur
- Ebuilds: 1, Testing: 1.20.2-r1 Description:
YP-Spur is a mobile robot motion control software with coordinate frame based commands.
Homepage:https://wiki.ros.org License: MIT
ypspur_ros
- Ebuilds: 1, Testing: 0.3.5-r1 Description:
ROS wrapper for the mobile robot control platform YP-Spur
Homepage:https://wiki.ros.org License: BSD