Demos showing the functionality of the Baxter Research Robot.
Python C++ Objective-C Shell
Switch branches/tags
Nothing to show
Clone or download
Jackie Kay
Jackie Kay extra launchfile
Latest commit 1678291 Sep 6, 2014

README.md

#baxter_demos Demos for the Baxter Research Robot written by Jackie Kay at OSRF during Summer 2014.

##Prerequisites

Install dependencies (assumes that you have the repo cloned into your ROS_PACKAGE_PATH):

rosdep install baxter_demos

Also clone baxter_pykdl into your workspace:

git clone https://github.com/rethink-kmaroney/baxter_pykdl.git

And install its dependencies:

rosdep install baxter_pykdl

###3D Vision and PCL To run 3D vision demos (get_ar_calib, goal_object_detector, stackit) you need a 3D camera such as a Kinect, Primesense or Asus Xtion. To run goal_object_detector and stackit, you need to install PCL (Point Cloud Library) from source (version 1.7.2). This is because the code currently uses moment of inertia estimation features that are not available in PCL 1.7.1, which is the version currently available to install from debs in Ubuntu. However, PCL 1.7.2 relies on a higher version of Boost than is used by ROS, and installing the right Boost for the latest PCL using the package manager may wreak havoc on your ROS installation.

PCL installation instructions (at your own risk):

  • Download Boost 1.47.0 source from http://www.boost.org/users/history/version_1_47_0.html
  • Build Boost 1.47.0 using the boostrap.sh script.
  • Clone the PCL 1.7.2 source from https://github.com/PointCloudLibrary/pcl
  • At the top of $(pcl)/cmake/pcl_find_boost.cmake, add the line "set(BOOST_ROOT <boost 1.47.0 dir>)", replacing <boost 1.47.0 dir> with the path to Boost 1.47.0.
  • (optional) In the PCL directory, make a build directory and call ccmake in that directory to configure your install. You could set the build type to "release" instead of debug, which will compile PCL with -O3 optimzations, but it will get rid of debug symbols.
  • Make and install PCL.
  • When you catkin_make the workspace with baxter_demos, it should find PCL automatically and build the 3D vision demos.

The planned fix for this issue is integrating moment of inertia estimation code that is not dependent on Boost and make baxter_demos reliant on PCL 1.7.1.

##Applications

####Keyboard teleop demos

rosrun baxter_demos ee_position_keyboard.py

Teleoperate the robot’s end effectors through Cartesian space. Press ‘?’ in the terminal you launched it from to view the possible commands.

roslaunch baxter_demos ee_position_joystick joystick:=logitech

Teleoperate the robot’s end effectors through Cartesian space using a joystick/gamepad. Visit http://wiki.ros.org/joy for instructions on configuring your device.

####Repetitive motion

roslaunch point_input_trajectory.launch limb:=[left/right] img_folder:=[path to asset folder]

This demo will give you instructions on Baxter’s head screen. Move Baxter’s arm to a start configuration using the wrist sensor, then press the round cuff button. Then move Baxter’s arm to an end configuration and press the cuff button again. Baxter will repeatedly move between those two positions. Requires the Joint Trajectory Action Server (see below).

####2D Perception and Manipulation

roslaunch baxter_demos object_finder.launch

Or you can supply options:

roslaunch baxter_demos object_finder.launch topic:=[topic name] limb:=[left/right] method:=[color/star/watershed]

Run a standalone 2D image segmentation routine. The default behavior uses the image feed from Baxter’s right hand camera. It requires you to click on a point in the scene and then uses color segmentation to identify objects of that same color. Three windows will pop up once segmentation begins: the raw image feed, the thresholded image resulting from segmentation processing, and the contours in the thresholded image. The thresholded image window also has sliders that adjust various segmentation parameters. The raw image feed displays the centroid, bounding box, and dominant axis in green for each contour. The other working option for segmentation method is Star Classifier Detection, which uses corner detection to find key points in the image, gets the color of those points and then color segments the image. Make sure the camera topic displays the scene you want to segment before starting object_finder with this segmentation method. object_finder publishes the centroid and dominant axis of each detected object to /object_tracker/blob_info.

roslaunch baxter_demos object_tracker.py

Or you can supply options:

roslaunch baxter_demos object_tracker.py limb:=[left/right] method:=[color/star/watershed] folder:=[path to asset folder]

A simple object pick and place demo. Make sure Baxter’s hand camera can see the desired object and click on the object in the image window. Then use the cuff buttons to give Baxter a start and end configuration (make sure the hand camera can see the object in the start configuration). The robot will then use object_finder.launch as well as its rangefinder and visual servoing logic to position the gripper over the object, grasp it, move to the end configuration, and drop it.

####3D Camera-Robot Extrinsic Calibration

roslaunch baxter_demos track_ar_tag.launch

Run a node from ar_track_alvar to give the pose of an AR tag in the camera scene. Edit this script with the correct image topic name and dimensions of the marker you are trying to track. See http://wiki.ros.org/ar_track_alvar for more information. To run this node in hydro or higher, you will need to install ar_track_alvar from source. I found that the default size suggested in ar_track_alvar gives very noisy results for an Asus Xtion. However, pose tracking was robust for a marker with a side of nearly 12 cm.

roslaunch baxter_demos get_ar_calib.py

Runs track_ar_tag and an additional node to calculate the transformation between Baxter’s base frame and the camera. To get an accurate extrinsic calibration, you need to carefully measure the transformation between the AR marker and one of Baxter’s coordinate frames and edit $(baxter_demos)/config/ar_calib.yaml with appropriate values. get_ar_calib saves the transformation to config/base_camera_tf.yaml, which gets passed to a transform publisher launched by baxter_osrf.launch.

roslaunch baxter_demos baxter_osrf.launch

Publishes the Baxter URDF with the camera box modification and the saved static transform between the base and camera frames that results from get_ar_calib.py. This is a startup script meant for use with OSRF’s Baxter, so I don’t suggest using it for another robot unless you modify it first.

####3D Perception

roslaunch baxter_demos goal_object_detector.launch kinect:=[true/false]

Runs a standalone 3D image segmentation routine. This node manager will start Openni/Freenect drivers for your 3D camera and show you a registered color point cloud. Shift-click on the object you want to track (make sure that you don’t accidentally click on a background pixel). Enjoy the ensuing mountain of vaguely helpful terminal printouts.

This file relies on baxter_nodelets.xml in the top level of the baxter_demos repo.

##Unfinished/broken applications

launch/stackit.sh

An unfinished pick-and place demo that combines Moveit, 3D image segmentation, and visual servoing. Run and be amazed at this program’s inability to deal with collisions!

The stackit.sh script runs the Joint Trajectory Action Server and the baxter_moveit_config GUI before starting the stackit script. If you want to run stackit on its own, use:

roslaunch baxter_demos stackit.launch

(This launchfile includes goal_object_detector.launch and runs stackit.py as its own node.)

super_stacker.launch

An attempt at 2D pick-and-place stacking.

##Tests

roslaunch baxter_demos object_finder_test.launch

Tests the object_finder node on a set of pre-selected images. Press "Space" in the "Test Image" window to cycle through the test images. We expect to see the contour of the orange block in each window, though the segmentation is not perfect.