hello_helpers
Overview
hello_helpers mostly consists of the hello_helpers Python module. This module provides various Python files used across stretch_ros2 that have not attained sufficient status to stand on their own.
Capabilities
fit_plane.py : Fits planes to 3D data.
hello_misc.py : Various functions, including a helpful Python object with which to create ROS nodes.
hello_ros_viz.py : Various helper functions for vizualizations using RViz.
Typical Usage
import hello_helpers.fit_plane as fpimport hello_helpers.hello_misc as hmimport hello_helpers.hello_ros_viz as hrAPI
Classes
This class is a convenience class for creating a ROS 2 node for Stretch. The most common way to use this class is to extend it. In your extending class, the main function would call HelloNode's main function. This would look like:
There is also a one-liner class method for instantiating a HelloNode for easy prototyping. One example where this is handy in sending pose commands from iPython:
Attributes
dryrun
This attribute allows you to control whether the robot actually moves when calling move_to_pose(), home_the_robot(), stow_the_robot(), or other motion methods in this class. When dryrun is set to True, these motion methods return immediately. This attribute is helpful when you want to run just the perception/planning part of your node without actually moving the robot. For example, you could replace the following verbose snippet:
to be more consise:
Methods
move_to_pose(pose, blocking=False, custom_contact_thresholds=False, duration=2.0)
This method takes in a dictionary that describes a desired pose for the robot and communicates with stretch_driver to execute it. The basic format of this dictionary is string/number key/value pairs, where the keys are joint names and the values are desired position goals. For example, {'lift_joint': 0.5} would put the lift at 0.5m in its joint range. A full list of command-able joints is published to the /stretch/joint_states topic. Used within a node extending HelloNode, calling this method would look like:
Internally, this dictionary is converted into a JointTrajectory message that is sent to a FollowJointTrajectory action server in stretch_driver. This method waits by default for the server to report that the goal has completed executing. However, you can return before the goal has completed by setting the blocking argument to False. This can be useful for preempting goals.
When the robot is in position mode, if you set custom_contact_thresholds to True, this method expects a different format dictionary: string/tuple key/value pairs, where the keys are still joint names, but the values are (position_goal, effort_threshold). The addition of a effort threshold enables you to detect when a joint has made contact with something in the environment, which is useful for manipulation or safe movements. For example, {'arm_joint': (0.5, 20)} commands the telescoping arm fully out (the arm is nearly fully extended at 0.5 meters) but with a low enough effort threshold (20% of the arm motor's max effort) that the motor will stop when the end of arm has made contact with something. Again, in a node, this would look like:
When the robot is in trajectory mode, if you set argument duration as ts, this method will ensure that the target joint positions are achieved over ts seconds. For example, the below would put the lift at 0.5m from its current position in 5.0 seconds:
home_the_robot()
This is a convenience method to interact with the driver's /home_the_robot service.
stow_the_robot()
This is a convenience method to interact with the driver's /stow_the_robot service.
stop_the_robot()
This is a convenience method to interact with the driver's /stop_the_robot service.
get_tf(from_frame, to_frame)
Use this method to get the transform (geometry_msgs/TransformStamped) between two frames. This method is blocking. For example, this method can do forward kinematics from the base_link to the link between the gripper fingers, grasp_center_link, using:
get_robot_floor_pose_xya(floor_frame='odom')
Returns the current estimated x, y position and angle of the robot on the floor. This is typically called with respect to the odom frame or the map frame. x and y are in meters and the angle is in radians.
main(node_name, node_topic_namespace, wait_for_first_pointcloud=True)
When extending the HelloNode class, call this method at the very beginning of your main() method. This method handles setting up a few ROS components, including registering the node with the ROS server, creating a TF listener, creating a FollowJointTrajectory client for the move_to_pose() method, subscribing to depth camera point cloud topic, and connecting to the quick-stop service.
Since it takes up to 30 seconds for the head camera to start streaming data, the wait_for_first_pointcloud argument will get the node to wait until it has seen camera data, which is helpful if your node is processing camera data.
quick_create(name, wait_for_first_pointcloud=False)
A class level method for quick testing. This allows you to avoid having to extend HelloNode to use it.
Subscribed Topics
/camera/depth/color/points (sensor_msgs/PointCloud2)
Provides a point cloud as currently seen by the Realsense depth camera in Stretch's head. Accessible from the self.point_cloud attribute.
/stretch/joint_states (sensor_msgs/JointState)
Provides the current state of robot joints that includes joint names, positions, velocities, efforts. Accessible from the self.joint_state attribute.
/mode (std_msgs/String)
Provides the mode the stretch driver is currently in. Possible values include position, trajectory, navigation, homing, stowing.
/tool (std_msgs/String)
Provides the end of arm tool attached to the robot.
Subscribed Services
/stop_the_robot (std_srvs/Trigger)
Provides a service to quickly stop any motion currently executing on the robot.
/stow_the_robot (std_srvs/Trigger)
Provides a service to stow the robot arm.
/home_the_robot (std_srvs/Trigger)
Provides a service to home the robot joints.
/switch_to_trajectory_mode (std_srvs/Trigger)
Provides a service to quickly stop any motion currently executing on the robot.
/switch_to_position_mode (std_srvs/Trigger)
Provides a service to quickly stop any motion currently executing on the robot.
/switch_to_navigation_mode (std_srvs/Trigger)
Provides a service to quickly stop any motion currently executing on the robot.
License
For license information, please see the LICENSE files.
Last updated
Was this helpful?
