| hector-imu-attitude-to-tf |
0.4.1-1 |
hector_imu_attitude_to_tf is a lightweight node that can be used to publish the roll/pitch attitude angles reported via a imu message to tf. |
meta-ros1-melodic |
| hector-imu-tools |
0.4.1-1 |
hector_imu_tools provides some tools for processing IMU messages |
meta-ros1-melodic |
| hector-localizationblacklisted |
0.3.0-1 |
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. |
meta-ros1-melodic |
| hector-map-server |
0.4.1-1 |
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). |
meta-ros1-melodic |
| hector-map-tools |
0.4.1-1 |
hector_map_tools contains some functions related to accessing information from OccupancyGridMap maps. Currently consists of a single header. |
meta-ros1-melodic |
| hector-mapping |
0.4.1-1 |
hector_mapping is a SLAM approach that can be used without odometry as well as on platforms that exhibit roll/pitch motion (of the sensor, the platform or both). It leverages the high update rate of modern LIDAR systems like the Hokuyo UTM-30LX and provides 2D pose estimates at scan rate of the sensors (40Hz for the UTM-30LX). While the system does not provide explicit loop closing ability, it is sufficiently accurate for many real world scenarios. The system has successfully been used on Unmanned Ground Robots, Unmanned Surface Vehicles, Handheld Mapping Devices and logged data from quadrotor UAVs. |
meta-ros1-melodic |
| hector-marker-drawing |
0.4.1-1 |
hector_marker_drawing provides convenience functions for easier publishing of visualization markers. |
meta-ros1-melodic |
| hector-models |
0.5.0 |
hector_models contains (urdf) models of robots, sensors etc. |
meta-ros1-melodic |
| hector-nav-msgs |
0.4.1-1 |
hector_nav_msgs contains messages and services used in the hector_slam stack. |
meta-ros1-melodic |
| hector-pose-estimationblacklisted |
0.3.0-1 |
hector_pose_estimation provides the hector_pose_estimation node and the hector_pose_estimation nodelet. |
meta-ros1-melodic |
| hector-pose-estimation-coreblacklisted |
0.3.0-1 |
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. |
meta-ros1-melodic |
| hector-sensors-description |
0.5.0 |
hector_sensors_description contains URDF xacro macros for sensors, so they are easily attachable to robot models and usable in gazebo. |
meta-ros1-melodic |
| hector-sensors-gazeboblacklisted |
0.5.4-1 |
hector_sensors_gazebo depends on the necessary plugins for using the sensors from the hector_models repository. |
meta-ros1-melodic |
| hector-slamblacklisted |
0.4.1-1 |
The hector_slam metapackage that installs hector_mapping and related packages. |
meta-ros1-melodic |
| hector-slam-launchblacklisted |
0.4.1-1 |
hector_slam_launch contains launch files for launching hector_slam with different robot systems/setups/postprocessing scenarios. |
meta-ros1-melodic |
| hector-trajectory-server |
0.4.1-1 |
hector_trajectory_server keeps track of tf trajectories extracted from tf data and makes this data accessible via a service and topic. |
meta-ros1-melodic |
| hector-xacro-tools |
0.5.0 |
hector_xacro_tools |
meta-ros1-melodic |
| heifublacklisted |
0.7.7-2 |
The heifu metapackage that installs all heifu related packages. |
meta-ros1-melodic |
| heifu-bringupblacklisted |
0.7.7-2 |
Heifu is a ROS driver for PDMFC and BEV drone |
meta-ros1-melodic |
| heifu-descriptionblacklisted |
0.7.7-2 |
SDF robot description for HEIFU |
meta-ros1-melodic |
| heifu-diagnosticblacklisted |
0.7.7-2 |
Heifu diagnostic to get GPS status |
meta-ros1-melodic |
| heifu-mavrosblacklisted |
0.7.7-2 |
Heifu mavros interface |
meta-ros1-melodic |
| heifu-msgs |
0.7.7-2 |
Common message definitions for heifu |
meta-ros1-melodic |
| heifu-safetyblacklisted |
0.7.7-2 |
This package enables an allowable safety zone to control the drone with a joystick. |
meta-ros1-melodic |
| heifu-simple-waypointblacklisted |
0.7.7-2 |
Heifu mavros interface |
meta-ros1-melodic |
| heifu-tools |
0.7.7-2 |
Heifu Tools |
meta-ros1-melodic |
| heron-control |
0.3.4-1 |
Control package for Heron |
meta-ros1-melodic |
| heron-controller |
0.2.0-1 |
The heron_controller package |
meta-ros1-melodic |
| heron-description |
0.3.4-1 |
URDF description for Heron |
meta-ros1-melodic |
| heron-desktopblacklisted |
0.0.3-2 |
The heron_desktop metapackage |
meta-ros1-melodic |
| heron-gazeboblacklisted |
0.3.3-1 |
Simulator package for Heron |
meta-ros1-melodic |
| heron-msgs |
0.3.4-1 |
Provides standard messages specific to Heron, especially for the microcontroller's rosserial interface. |
meta-ros1-melodic |
| heron-simulator |
0.3.3-1 |
Simulator package for Heron |
meta-ros1-melodic |
| heron-vizblacklisted |
0.0.3-2 |
Visualization and rviz helpers for Heron. |
meta-ros1-melodic |
| hfl-driver |
0.1.0-1 |
The hfl package |
meta-ros1-melodic |
| hiawatha |
10.11 |
Lightweight secure web server |
meta-webserver |
| hironx-calibrationblacklisted |
2.2.0-1 |
Launch and configuration files for calibrating hironx using the generic <a href="http://wiki.ros.org/calibration_setup_helper">calibration_setup_helper</a> package. THIS FILE IS AUTOMATICALLY GENERATED BY:<br/> <code> rosrun calibration_setup_helper calibration_setup_helper.py `rospack find hironx_moveit_config`/HiroNX.urdf --base-link CHEST_JOINT0_Link --arm-tip-link RARM_JOINT5_Link --head-tip-link HEAD_JOINT1_Link --arm-controller=rarm_controller/command --head-controller=head_controller/command --head-camera-frame camera_rgb_optical_frame --head-camera-joint head_to_kinect_joint </code> |
meta-ros1-melodic |
| hironx-moveit-configblacklisted |
2.2.0-1 |
An automatically generated package with all the configuration and launch files for using the HiroNX with the MoveIt Motion Planning Framework |
meta-ros1-melodic |
| hironx-ros-bridgeblacklisted |
2.2.0-1 |
ROS-OpenRTM interfacing package for the opensource version of Kawada's Hiro/NEXTAGE dual-arm robot. NOTE: This package is multi-license -- pay attention to file header in each file where license is declared. For Creative Commons nc 4.0 applied, see <a href="http://creativecommons.org/licenses/by-nc/4.0">here</a>. <p>This package also contains some sensor driver software (as of April 2016 they are the following force sensors such as <a href="http://www.wacoh-tech.com/products/dynpick/wdf-6m200-3.html">Dynpick</a> and <a href="http://www.jr3.com/products.html">JR3</a>) for QNX. These drivers are stored in this robot-specific package for not many reasons than they are slightly customized for the robot. So if you can separate those as a standalone, generic package that'll be appreciated (please just let us know if you will).</p> |
meta-ros1-melodic |
| hls-lfcd-lds-driver |
1.1.2-1 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros1-melodic |
| hls-lfcd-lds-driver |
2.0.3-1 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros2-dashing |
| hls-lfcd-lds-driver |
2.0.1-1 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros2-eloquent |
| hls-lfcd-lds-driver |
2.0.1-1 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros2-foxy |
| hls-lfcd-lds-driver |
2.0.4-1 |
ROS package for LDS(HLS-LFCD2). The LDS (Laser Distance Sensor) is a sensor sending the data to Host for the simultaneous localization and mapping (SLAM). Simultaneously the detecting obstacle data can also be sent to Host. HLDS(Hitachi-LG Data Storage) is developing the technology for the moving platform sensor such as Robot Vacuum Cleaners, Home Robot, Robotics Lawn Mower Sensor, etc. |
meta-ros2-rolling |
| hokuyo3d |
0.2.1-1 |
ROS driver node for HOKUYO 3D LIDARs |
meta-ros1-melodic |
| hostapd-access-point |
1.0.16-1 |
A ROS node that controls a hostapd-based access point. It is mainly intended for use with a wireless network adapter running in master mode. It implements the dynamic_reconfigure interface defined in the [[access_point_control]] package. |
meta-ros1-melodic |
| hpp-fclblacklisted |
1.0.1-2 |
HPP fork of FCL with bug fixes. |
meta-ros1-melodic |
| hrpsysblacklisted |
315.15.0-8 |
<p>An <a href="http://www.openrtm.org/pub/OpenRTM-aist/">OpenRTM-aist</a>-based robot controller. This package is the most tailored for humanoid (dual-arm and/or biped) robots for historical reason.</p> <p>hrpsys package does not only wraps but build and installs the code from its mainstream repository (<a href="https://github.com/fkanehiro/hrpsys-base/">github.com/fkanehiro/hrpsys-base</a>).</p> <p>The package version number is synchronized to that of mainstream, based on <a href="https://github.com/start-jsk/rtmros_common/issues/165#issuecomment-34536168">this decision</a>. Its semantics:<br/> <ul> <li><b>MAJOR</b>: Synchronized with <a href="http://wiki.ros.org/openhrp3">OpenHRP3</a></li> <li><b>MINOR</b>: Indicate IDL compatibility (packages with different version numbers in this section are NOT compatible)</li> <li><b>PATCH</b>: Packages with different version numbers in this section ARE compatible.</li> </ul> </p> <p>API document is <a href="http://fkanehiro.github.io/hrpsys-base/">auto-generated on github</a>. </p> |
meta-ros1-melodic |
| hrpsys-ros-bridgeblacklisted |
1.4.3-1 |
hrpsys_ros_bridge package provides basic functionalities to bind <a href="http://wiki.ros.org/hrpsys">hrpsys</a>, a <a href="http://openrtm.org/">OpenRTM</a>-based controller, and ROS.<br/> By using this package, you can write your ROS packages that communicate with your non-ROS robots that run on hrpsys. For communicating with the robots that run on OpenRTM without hrpsys, you can use <a href="http://wiki.ros.org/openrtm_ros_bridge">openrtm_ros_bridge</a> package. |
meta-ros1-melodic |
| hrpsys-toolsblacklisted |
1.4.3-1 |
The hrpsys_tools package |
meta-ros1-melodic |