| refpolicy-mls |
2.20210203+gitX |
MLS (Multi Level Security) variant of the SELinux policy |
meta-selinux |
| remmina |
1.4.11+gitX |
A feature rich Remote Desktop Application written in GTK+ |
meta-oe |
| ros-comm |
1.14.12-1 |
ROS communications-related packages, including core client libraries (roscpp, rospy) and graph introspection tools (rostopic, rosnode, rosservice, rosparam). |
meta-ros1-melodic |
| ros-comm |
1.15.13-1 |
ROS communications-related packages, including core client libraries (roscpp, rospy) and graph introspection tools (rostopic, rosnode, rosservice, rosparam). |
meta-ros1-noetic |
| rosapi |
0.11.13-1 |
Provides service calls for getting ros meta-information, like list of topics, services, params, etc. |
meta-ros1-melodic |
| rosapi |
1.0.2-1 |
Provides service calls for getting ros meta-information, like list of topics, services, params, etc. |
meta-ros2-dashing |
| rosapi |
1.1.0-1 |
Provides service calls for getting ros meta-information, like list of topics, services, params, etc. |
meta-ros2-foxy |
| rosapi |
1.1.0-1 |
Provides service calls for getting ros meta-information, like list of topics, services, params, etc. |
meta-ros2-rolling |
| rosapi |
0.11.13-1 |
Provides service calls for getting ros meta-information, like list of topics, services, params, etc. |
meta-ros1-noetic |
| rosapi |
1.1.0-1 |
Provides service calls for getting ros meta-information, like list of topics, services, params, etc. |
meta-ros2-galactic |
| rosapi-msgs |
1.1.0-1 |
Provides service calls for getting ros meta-information, like list of topics, services, params, etc. |
meta-ros2-foxy |
| rosapi-msgs |
1.1.0-1 |
Provides service calls for getting ros meta-information, like list of topics, services, params, etc. |
meta-ros2-rolling |
| rosapi-msgs |
1.1.0-1 |
Provides service calls for getting ros meta-information, like list of topics, services, params, etc. |
meta-ros2-galactic |
| rosbag |
1.14.12-1 |
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. |
meta-ros1-melodic |
| rosbag |
1.15.13-1 |
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. |
meta-ros1-noetic |
| roscpp |
1.14.12-1 |
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. |
meta-ros1-melodic |
| roscpp |
1.15.13-1 |
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. |
meta-ros1-noetic |
| rosflightblacklisted |
1.3.1-1 |
Package for interfacing to the ROSflight autopilot firmware over MAVLink |
meta-ros1-melodic |
| rosnode-rtcblacklisted |
1.4.3-1 |
This package gives transparency between RTM and ROS. rtmros-data-bridge.py is a RT-Component for dataport/topic. This automatically convert ROS/topic into RTM/dataport. |
meta-ros1-melodic |
| rosout |
1.14.12-1 |
System-wide logging mechanism for messages sent to the /rosout topic. |
meta-ros1-melodic |
| rosout |
1.15.13-1 |
System-wide logging mechanism for messages sent to the /rosout topic. |
meta-ros1-noetic |
| rosping |
2.1.24-1 |
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>. |
meta-ros1-melodic |
| rosping |
2.1.21-2 |
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>. |
meta-ros1-noetic |
| rospy |
1.14.12-1 |
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. |
meta-ros1-melodic |
| rospy |
1.15.13-1 |
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. |
meta-ros1-noetic |
| rosserial-msgs |
0.8.0 |
Messages for automatic topic configuration using rosserial. |
meta-ros1-melodic |
| rosserial-msgs |
0.9.2-1 |
Messages for automatic topic configuration using rosserial. |
meta-ros1-noetic |
| rosthrottle |
1.2.0-3 |
ROS Python package for throttling ROS topics programatically in Python. Sits on top of the ros_comm topic_tools throttle utility. |
meta-ros1-melodic |
| rqt-moveitblacklisted |
0.5.10-1 |
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). |
meta-ros1-melodic |
| rqt-moveitblacklisted |
1.0.1-2 |
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). |
meta-ros2-eloquent |
| rqt-moveitblacklisted |
1.0.1-1 |
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). |
meta-ros2-foxy |
| rqt-moveitblacklisted |
1.0.1-1 |
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). |
meta-ros2-rolling |
| rqt-moveitblacklisted |
0.5.10-1 |
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). |
meta-ros1-noetic |
| rqt-moveitblacklisted |
1.0.1-2 |
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). |
meta-ros2-galactic |
| rqt-robot-monitorblacklisted |
0.5.13-1 |
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. |
meta-ros1-melodic |
| rqt-robot-monitorblacklisted |
1.0.4-1 |
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. |
meta-ros2-dashing |
| rqt-robot-monitorblacklisted |
1.0.4-1 |
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. |
meta-ros2-eloquent |
| rqt-robot-monitorblacklisted |
1.0.4-1 |
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. |
meta-ros2-foxy |
| rqt-robot-monitorblacklisted |
1.0.4-1 |
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. |
meta-ros2-rolling |
| rqt-robot-monitorblacklisted |
0.5.13-1 |
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. |
meta-ros1-noetic |
| rqt-robot-monitorblacklisted |
1.0.4-2 |
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. |
meta-ros2-galactic |
| rr-openrover-driver |
1.1.1-1 |
Provides an interface between ros and Rover Robotics rover hardware. Inputs to rr_openrover_driver include emergency stop and velocity commands. It outputs diagnostic data such as encoder readings and battery charge. |
meta-ros1-melodic |
| rubygems-public-suffix |
4.0.6 |
RubyGem: public_suffix |
meta-rubygems |
| ruli |
0.36 |
RULI stands for Resolver User Layer Interface It's a library built on top of an asynchronous DNS stub resolver |
meta-networking |
| schunk-simulated-tactile-sensorsblacklisted |
0.6.14-1 |
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. |
meta-ros1-melodic |
| schunk-simulated-tactile-sensorsblacklisted |
0.6.14-1 |
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. |
meta-ros1-noetic |
| scribus |
1.5.7 |
Scribus: Open source desktop publishing |
meta-qt5-extra |
| smach-ros |
2.0.1 |
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. |
meta-ros1-melodic |
| smach-ros |
2.5.0-1 |
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. |
meta-ros1-noetic |
| socketcan-bridge |
0.8.5-1 |
Conversion nodes for messages from SocketCAN to a ROS Topic and vice versa. |
meta-ros1-melodic |