00001
00002 #ifndef PR2_OBJECT_MANIPULATION_MSGS_MESSAGE_GETGRIPPERPOSEGOAL_H
00003 #define PR2_OBJECT_MANIPULATION_MSGS_MESSAGE_GETGRIPPERPOSEGOAL_H
00004 #include <string>
00005 #include <vector>
00006 #include <map>
00007 #include <ostream>
00008 #include "ros/serialization.h"
00009 #include "ros/builtin_message_traits.h"
00010 #include "ros/message_operations.h"
00011 #include "ros/time.h"
00012
00013 #include "ros/macros.h"
00014
00015 #include "ros/assert.h"
00016
00017 #include "geometry_msgs/PoseStamped.h"
00018 #include "manipulation_msgs/GraspableObject.h"
00019 #include "manipulation_msgs/Grasp.h"
00020
00021 namespace pr2_object_manipulation_msgs
00022 {
00023 template <class ContainerAllocator>
00024 struct GetGripperPoseGoal_ {
00025 typedef GetGripperPoseGoal_<ContainerAllocator> Type;
00026
00027 GetGripperPoseGoal_()
00028 : arm_name()
00029 , gripper_pose()
00030 , gripper_opening(0.0)
00031 , object()
00032 , grasp()
00033 {
00034 }
00035
00036 GetGripperPoseGoal_(const ContainerAllocator& _alloc)
00037 : arm_name(_alloc)
00038 , gripper_pose(_alloc)
00039 , gripper_opening(0.0)
00040 , object(_alloc)
00041 , grasp(_alloc)
00042 {
00043 }
00044
00045 typedef std::basic_string<char, std::char_traits<char>, typename ContainerAllocator::template rebind<char>::other > _arm_name_type;
00046 std::basic_string<char, std::char_traits<char>, typename ContainerAllocator::template rebind<char>::other > arm_name;
00047
00048 typedef ::geometry_msgs::PoseStamped_<ContainerAllocator> _gripper_pose_type;
00049 ::geometry_msgs::PoseStamped_<ContainerAllocator> gripper_pose;
00050
00051 typedef float _gripper_opening_type;
00052 float gripper_opening;
00053
00054 typedef ::manipulation_msgs::GraspableObject_<ContainerAllocator> _object_type;
00055 ::manipulation_msgs::GraspableObject_<ContainerAllocator> object;
00056
00057 typedef ::manipulation_msgs::Grasp_<ContainerAllocator> _grasp_type;
00058 ::manipulation_msgs::Grasp_<ContainerAllocator> grasp;
00059
00060
00061 typedef boost::shared_ptr< ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> > Ptr;
00062 typedef boost::shared_ptr< ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> const> ConstPtr;
00063 boost::shared_ptr<std::map<std::string, std::string> > __connection_header;
00064 };
00065 typedef ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<std::allocator<void> > GetGripperPoseGoal;
00066
00067 typedef boost::shared_ptr< ::pr2_object_manipulation_msgs::GetGripperPoseGoal> GetGripperPoseGoalPtr;
00068 typedef boost::shared_ptr< ::pr2_object_manipulation_msgs::GetGripperPoseGoal const> GetGripperPoseGoalConstPtr;
00069
00070
00071 template<typename ContainerAllocator>
00072 std::ostream& operator<<(std::ostream& s, const ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> & v)
00073 {
00074 ros::message_operations::Printer< ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> >::stream(s, "", v);
00075 return s;}
00076
00077 }
00078
00079 namespace ros
00080 {
00081 namespace message_traits
00082 {
00083 template<class ContainerAllocator> struct IsMessage< ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> > : public TrueType {};
00084 template<class ContainerAllocator> struct IsMessage< ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> const> : public TrueType {};
00085 template<class ContainerAllocator>
00086 struct MD5Sum< ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> > {
00087 static const char* value()
00088 {
00089 return "18c143b3596c98865731ccb80f92a15a";
00090 }
00091
00092 static const char* value(const ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> &) { return value(); }
00093 static const uint64_t static_value1 = 0x18c143b3596c9886ULL;
00094 static const uint64_t static_value2 = 0x5731ccb80f92a15aULL;
00095 };
00096
00097 template<class ContainerAllocator>
00098 struct DataType< ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> > {
00099 static const char* value()
00100 {
00101 return "pr2_object_manipulation_msgs/GetGripperPoseGoal";
00102 }
00103
00104 static const char* value(const ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> &) { return value(); }
00105 };
00106
00107 template<class ContainerAllocator>
00108 struct Definition< ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> > {
00109 static const char* value()
00110 {
00111 return "# ====== DO NOT MODIFY! AUTOGENERATED FROM AN ACTION DEFINITION ======\n\
00112 \n\
00113 # for which arm are we requesting a pose\n\
00114 # useful for knowing which arm to initialize from when seed is empty\n\
00115 string arm_name\n\
00116 \n\
00117 # a seed position for the ghosted gripper. If emtpy (quaternion of norm 0)\n\
00118 # the ghosted gripper will be initialized at the current position of the gripper\n\
00119 geometry_msgs/PoseStamped gripper_pose\n\
00120 float32 gripper_opening\n\
00121 \n\
00122 # An object that the gripper is holding. May be empty.\n\
00123 manipulation_msgs/GraspableObject object\n\
00124 \n\
00125 # how we are holding the object, if any.\n\
00126 manipulation_msgs/Grasp grasp\n\
00127 \n\
00128 \n\
00129 ================================================================================\n\
00130 MSG: geometry_msgs/PoseStamped\n\
00131 # A Pose with reference coordinate frame and timestamp\n\
00132 Header header\n\
00133 Pose pose\n\
00134 \n\
00135 ================================================================================\n\
00136 MSG: std_msgs/Header\n\
00137 # Standard metadata for higher-level stamped data types.\n\
00138 # This is generally used to communicate timestamped data \n\
00139 # in a particular coordinate frame.\n\
00140 # \n\
00141 # sequence ID: consecutively increasing ID \n\
00142 uint32 seq\n\
00143 #Two-integer timestamp that is expressed as:\n\
00144 # * stamp.secs: seconds (stamp_secs) since epoch\n\
00145 # * stamp.nsecs: nanoseconds since stamp_secs\n\
00146 # time-handling sugar is provided by the client library\n\
00147 time stamp\n\
00148 #Frame this data is associated with\n\
00149 # 0: no frame\n\
00150 # 1: global frame\n\
00151 string frame_id\n\
00152 \n\
00153 ================================================================================\n\
00154 MSG: geometry_msgs/Pose\n\
00155 # A representation of pose in free space, composed of postion and orientation. \n\
00156 Point position\n\
00157 Quaternion orientation\n\
00158 \n\
00159 ================================================================================\n\
00160 MSG: geometry_msgs/Point\n\
00161 # This contains the position of a point in free space\n\
00162 float64 x\n\
00163 float64 y\n\
00164 float64 z\n\
00165 \n\
00166 ================================================================================\n\
00167 MSG: geometry_msgs/Quaternion\n\
00168 # This represents an orientation in free space in quaternion form.\n\
00169 \n\
00170 float64 x\n\
00171 float64 y\n\
00172 float64 z\n\
00173 float64 w\n\
00174 \n\
00175 ================================================================================\n\
00176 MSG: manipulation_msgs/GraspableObject\n\
00177 # an object that the object_manipulator can work on\n\
00178 \n\
00179 # a graspable object can be represented in multiple ways. This message\n\
00180 # can contain all of them. Which one is actually used is up to the receiver\n\
00181 # of this message. When adding new representations, one must be careful that\n\
00182 # they have reasonable lightweight defaults indicating that that particular\n\
00183 # representation is not available.\n\
00184 \n\
00185 # the tf frame to be used as a reference frame when combining information from\n\
00186 # the different representations below\n\
00187 string reference_frame_id\n\
00188 \n\
00189 # potential recognition results from a database of models\n\
00190 # all poses are relative to the object reference pose\n\
00191 household_objects_database_msgs/DatabaseModelPose[] potential_models\n\
00192 \n\
00193 # the point cloud itself\n\
00194 sensor_msgs/PointCloud cluster\n\
00195 \n\
00196 # a region of a PointCloud2 of interest\n\
00197 SceneRegion region\n\
00198 \n\
00199 # the name that this object has in the collision environment\n\
00200 string collision_name\n\
00201 ================================================================================\n\
00202 MSG: household_objects_database_msgs/DatabaseModelPose\n\
00203 # Informs that a specific model from the Model Database has been \n\
00204 # identified at a certain location\n\
00205 \n\
00206 # the database id of the model\n\
00207 int32 model_id\n\
00208 \n\
00209 # if the object was recognized by the ORK pipeline, its type will be in here\n\
00210 # if this is not empty, then the string in here will be converted to a household_objects_database id\n\
00211 # leave this empty if providing an id in the model_id field\n\
00212 object_recognition_msgs/ObjectType type\n\
00213 \n\
00214 # the pose that it can be found in\n\
00215 geometry_msgs/PoseStamped pose\n\
00216 \n\
00217 # a measure of the confidence level in this detection result\n\
00218 float32 confidence\n\
00219 \n\
00220 # the name of the object detector that generated this detection result\n\
00221 string detector_name\n\
00222 \n\
00223 ================================================================================\n\
00224 MSG: object_recognition_msgs/ObjectType\n\
00225 ################################################## OBJECT ID #########################################################\n\
00226 \n\
00227 # Contains information about the type of a found object. Those two sets of parameters together uniquely define an\n\
00228 # object\n\
00229 \n\
00230 # The key of the found object: the unique identifier in the given db\n\
00231 string key\n\
00232 \n\
00233 # The db parameters stored as a JSON/compressed YAML string. An object id does not make sense without the corresponding\n\
00234 # database. E.g., in object_recognition, it can look like: \"{'type':'CouchDB', 'root':'http://localhost'}\"\n\
00235 # There is no conventional format for those parameters and it's nice to keep that flexibility.\n\
00236 # The object_recognition_core as a generic DB type that can read those fields\n\
00237 # Current examples:\n\
00238 # For CouchDB:\n\
00239 # type: 'CouchDB'\n\
00240 # root: 'http://localhost:5984'\n\
00241 # collection: 'object_recognition'\n\
00242 # For SQL household database:\n\
00243 # type: 'SqlHousehold'\n\
00244 # host: 'wgs36'\n\
00245 # port: 5432\n\
00246 # user: 'willow'\n\
00247 # password: 'willow'\n\
00248 # name: 'household_objects'\n\
00249 # module: 'tabletop'\n\
00250 string db\n\
00251 \n\
00252 ================================================================================\n\
00253 MSG: sensor_msgs/PointCloud\n\
00254 # This message holds a collection of 3d points, plus optional additional\n\
00255 # information about each point.\n\
00256 \n\
00257 # Time of sensor data acquisition, coordinate frame ID.\n\
00258 Header header\n\
00259 \n\
00260 # Array of 3d points. Each Point32 should be interpreted as a 3d point\n\
00261 # in the frame given in the header.\n\
00262 geometry_msgs/Point32[] points\n\
00263 \n\
00264 # Each channel should have the same number of elements as points array,\n\
00265 # and the data in each channel should correspond 1:1 with each point.\n\
00266 # Channel names in common practice are listed in ChannelFloat32.msg.\n\
00267 ChannelFloat32[] channels\n\
00268 \n\
00269 ================================================================================\n\
00270 MSG: geometry_msgs/Point32\n\
00271 # This contains the position of a point in free space(with 32 bits of precision).\n\
00272 # It is recommeded to use Point wherever possible instead of Point32. \n\
00273 # \n\
00274 # This recommendation is to promote interoperability. \n\
00275 #\n\
00276 # This message is designed to take up less space when sending\n\
00277 # lots of points at once, as in the case of a PointCloud. \n\
00278 \n\
00279 float32 x\n\
00280 float32 y\n\
00281 float32 z\n\
00282 ================================================================================\n\
00283 MSG: sensor_msgs/ChannelFloat32\n\
00284 # This message is used by the PointCloud message to hold optional data\n\
00285 # associated with each point in the cloud. The length of the values\n\
00286 # array should be the same as the length of the points array in the\n\
00287 # PointCloud, and each value should be associated with the corresponding\n\
00288 # point.\n\
00289 \n\
00290 # Channel names in existing practice include:\n\
00291 # \"u\", \"v\" - row and column (respectively) in the left stereo image.\n\
00292 # This is opposite to usual conventions but remains for\n\
00293 # historical reasons. The newer PointCloud2 message has no\n\
00294 # such problem.\n\
00295 # \"rgb\" - For point clouds produced by color stereo cameras. uint8\n\
00296 # (R,G,B) values packed into the least significant 24 bits,\n\
00297 # in order.\n\
00298 # \"intensity\" - laser or pixel intensity.\n\
00299 # \"distance\"\n\
00300 \n\
00301 # The channel name should give semantics of the channel (e.g.\n\
00302 # \"intensity\" instead of \"value\").\n\
00303 string name\n\
00304 \n\
00305 # The values array should be 1-1 with the elements of the associated\n\
00306 # PointCloud.\n\
00307 float32[] values\n\
00308 \n\
00309 ================================================================================\n\
00310 MSG: manipulation_msgs/SceneRegion\n\
00311 # Point cloud\n\
00312 sensor_msgs/PointCloud2 cloud\n\
00313 \n\
00314 # Indices for the region of interest\n\
00315 int32[] mask\n\
00316 \n\
00317 # One of the corresponding 2D images, if applicable\n\
00318 sensor_msgs/Image image\n\
00319 \n\
00320 # The disparity image, if applicable\n\
00321 sensor_msgs/Image disparity_image\n\
00322 \n\
00323 # Camera info for the camera that took the image\n\
00324 sensor_msgs/CameraInfo cam_info\n\
00325 \n\
00326 # a 3D region of interest for grasp planning\n\
00327 geometry_msgs/PoseStamped roi_box_pose\n\
00328 geometry_msgs/Vector3 roi_box_dims\n\
00329 \n\
00330 ================================================================================\n\
00331 MSG: sensor_msgs/PointCloud2\n\
00332 # This message holds a collection of N-dimensional points, which may\n\
00333 # contain additional information such as normals, intensity, etc. The\n\
00334 # point data is stored as a binary blob, its layout described by the\n\
00335 # contents of the \"fields\" array.\n\
00336 \n\
00337 # The point cloud data may be organized 2d (image-like) or 1d\n\
00338 # (unordered). Point clouds organized as 2d images may be produced by\n\
00339 # camera depth sensors such as stereo or time-of-flight.\n\
00340 \n\
00341 # Time of sensor data acquisition, and the coordinate frame ID (for 3d\n\
00342 # points).\n\
00343 Header header\n\
00344 \n\
00345 # 2D structure of the point cloud. If the cloud is unordered, height is\n\
00346 # 1 and width is the length of the point cloud.\n\
00347 uint32 height\n\
00348 uint32 width\n\
00349 \n\
00350 # Describes the channels and their layout in the binary data blob.\n\
00351 PointField[] fields\n\
00352 \n\
00353 bool is_bigendian # Is this data bigendian?\n\
00354 uint32 point_step # Length of a point in bytes\n\
00355 uint32 row_step # Length of a row in bytes\n\
00356 uint8[] data # Actual point data, size is (row_step*height)\n\
00357 \n\
00358 bool is_dense # True if there are no invalid points\n\
00359 \n\
00360 ================================================================================\n\
00361 MSG: sensor_msgs/PointField\n\
00362 # This message holds the description of one point entry in the\n\
00363 # PointCloud2 message format.\n\
00364 uint8 INT8 = 1\n\
00365 uint8 UINT8 = 2\n\
00366 uint8 INT16 = 3\n\
00367 uint8 UINT16 = 4\n\
00368 uint8 INT32 = 5\n\
00369 uint8 UINT32 = 6\n\
00370 uint8 FLOAT32 = 7\n\
00371 uint8 FLOAT64 = 8\n\
00372 \n\
00373 string name # Name of field\n\
00374 uint32 offset # Offset from start of point struct\n\
00375 uint8 datatype # Datatype enumeration, see above\n\
00376 uint32 count # How many elements in the field\n\
00377 \n\
00378 ================================================================================\n\
00379 MSG: sensor_msgs/Image\n\
00380 # This message contains an uncompressed image\n\
00381 # (0, 0) is at top-left corner of image\n\
00382 #\n\
00383 \n\
00384 Header header # Header timestamp should be acquisition time of image\n\
00385 # Header frame_id should be optical frame of camera\n\
00386 # origin of frame should be optical center of cameara\n\
00387 # +x should point to the right in the image\n\
00388 # +y should point down in the image\n\
00389 # +z should point into to plane of the image\n\
00390 # If the frame_id here and the frame_id of the CameraInfo\n\
00391 # message associated with the image conflict\n\
00392 # the behavior is undefined\n\
00393 \n\
00394 uint32 height # image height, that is, number of rows\n\
00395 uint32 width # image width, that is, number of columns\n\
00396 \n\
00397 # The legal values for encoding are in file src/image_encodings.cpp\n\
00398 # If you want to standardize a new string format, join\n\
00399 # ros-users@lists.sourceforge.net and send an email proposing a new encoding.\n\
00400 \n\
00401 string encoding # Encoding of pixels -- channel meaning, ordering, size\n\
00402 # taken from the list of strings in include/sensor_msgs/image_encodings.h\n\
00403 \n\
00404 uint8 is_bigendian # is this data bigendian?\n\
00405 uint32 step # Full row length in bytes\n\
00406 uint8[] data # actual matrix data, size is (step * rows)\n\
00407 \n\
00408 ================================================================================\n\
00409 MSG: sensor_msgs/CameraInfo\n\
00410 # This message defines meta information for a camera. It should be in a\n\
00411 # camera namespace on topic \"camera_info\" and accompanied by up to five\n\
00412 # image topics named:\n\
00413 #\n\
00414 # image_raw - raw data from the camera driver, possibly Bayer encoded\n\
00415 # image - monochrome, distorted\n\
00416 # image_color - color, distorted\n\
00417 # image_rect - monochrome, rectified\n\
00418 # image_rect_color - color, rectified\n\
00419 #\n\
00420 # The image_pipeline contains packages (image_proc, stereo_image_proc)\n\
00421 # for producing the four processed image topics from image_raw and\n\
00422 # camera_info. The meaning of the camera parameters are described in\n\
00423 # detail at http://www.ros.org/wiki/image_pipeline/CameraInfo.\n\
00424 #\n\
00425 # The image_geometry package provides a user-friendly interface to\n\
00426 # common operations using this meta information. If you want to, e.g.,\n\
00427 # project a 3d point into image coordinates, we strongly recommend\n\
00428 # using image_geometry.\n\
00429 #\n\
00430 # If the camera is uncalibrated, the matrices D, K, R, P should be left\n\
00431 # zeroed out. In particular, clients may assume that K[0] == 0.0\n\
00432 # indicates an uncalibrated camera.\n\
00433 \n\
00434 #######################################################################\n\
00435 # Image acquisition info #\n\
00436 #######################################################################\n\
00437 \n\
00438 # Time of image acquisition, camera coordinate frame ID\n\
00439 Header header # Header timestamp should be acquisition time of image\n\
00440 # Header frame_id should be optical frame of camera\n\
00441 # origin of frame should be optical center of camera\n\
00442 # +x should point to the right in the image\n\
00443 # +y should point down in the image\n\
00444 # +z should point into the plane of the image\n\
00445 \n\
00446 \n\
00447 #######################################################################\n\
00448 # Calibration Parameters #\n\
00449 #######################################################################\n\
00450 # These are fixed during camera calibration. Their values will be the #\n\
00451 # same in all messages until the camera is recalibrated. Note that #\n\
00452 # self-calibrating systems may \"recalibrate\" frequently. #\n\
00453 # #\n\
00454 # The internal parameters can be used to warp a raw (distorted) image #\n\
00455 # to: #\n\
00456 # 1. An undistorted image (requires D and K) #\n\
00457 # 2. A rectified image (requires D, K, R) #\n\
00458 # The projection matrix P projects 3D points into the rectified image.#\n\
00459 #######################################################################\n\
00460 \n\
00461 # The image dimensions with which the camera was calibrated. Normally\n\
00462 # this will be the full camera resolution in pixels.\n\
00463 uint32 height\n\
00464 uint32 width\n\
00465 \n\
00466 # The distortion model used. Supported models are listed in\n\
00467 # sensor_msgs/distortion_models.h. For most cameras, \"plumb_bob\" - a\n\
00468 # simple model of radial and tangential distortion - is sufficent.\n\
00469 string distortion_model\n\
00470 \n\
00471 # The distortion parameters, size depending on the distortion model.\n\
00472 # For \"plumb_bob\", the 5 parameters are: (k1, k2, t1, t2, k3).\n\
00473 float64[] D\n\
00474 \n\
00475 # Intrinsic camera matrix for the raw (distorted) images.\n\
00476 # [fx 0 cx]\n\
00477 # K = [ 0 fy cy]\n\
00478 # [ 0 0 1]\n\
00479 # Projects 3D points in the camera coordinate frame to 2D pixel\n\
00480 # coordinates using the focal lengths (fx, fy) and principal point\n\
00481 # (cx, cy).\n\
00482 float64[9] K # 3x3 row-major matrix\n\
00483 \n\
00484 # Rectification matrix (stereo cameras only)\n\
00485 # A rotation matrix aligning the camera coordinate system to the ideal\n\
00486 # stereo image plane so that epipolar lines in both stereo images are\n\
00487 # parallel.\n\
00488 float64[9] R # 3x3 row-major matrix\n\
00489 \n\
00490 # Projection/camera matrix\n\
00491 # [fx' 0 cx' Tx]\n\
00492 # P = [ 0 fy' cy' Ty]\n\
00493 # [ 0 0 1 0]\n\
00494 # By convention, this matrix specifies the intrinsic (camera) matrix\n\
00495 # of the processed (rectified) image. That is, the left 3x3 portion\n\
00496 # is the normal camera intrinsic matrix for the rectified image.\n\
00497 # It projects 3D points in the camera coordinate frame to 2D pixel\n\
00498 # coordinates using the focal lengths (fx', fy') and principal point\n\
00499 # (cx', cy') - these may differ from the values in K.\n\
00500 # For monocular cameras, Tx = Ty = 0. Normally, monocular cameras will\n\
00501 # also have R = the identity and P[1:3,1:3] = K.\n\
00502 # For a stereo pair, the fourth column [Tx Ty 0]' is related to the\n\
00503 # position of the optical center of the second camera in the first\n\
00504 # camera's frame. We assume Tz = 0 so both cameras are in the same\n\
00505 # stereo image plane. The first camera always has Tx = Ty = 0. For\n\
00506 # the right (second) camera of a horizontal stereo pair, Ty = 0 and\n\
00507 # Tx = -fx' * B, where B is the baseline between the cameras.\n\
00508 # Given a 3D point [X Y Z]', the projection (x, y) of the point onto\n\
00509 # the rectified image is given by:\n\
00510 # [u v w]' = P * [X Y Z 1]'\n\
00511 # x = u / w\n\
00512 # y = v / w\n\
00513 # This holds for both images of a stereo pair.\n\
00514 float64[12] P # 3x4 row-major matrix\n\
00515 \n\
00516 \n\
00517 #######################################################################\n\
00518 # Operational Parameters #\n\
00519 #######################################################################\n\
00520 # These define the image region actually captured by the camera #\n\
00521 # driver. Although they affect the geometry of the output image, they #\n\
00522 # may be changed freely without recalibrating the camera. #\n\
00523 #######################################################################\n\
00524 \n\
00525 # Binning refers here to any camera setting which combines rectangular\n\
00526 # neighborhoods of pixels into larger \"super-pixels.\" It reduces the\n\
00527 # resolution of the output image to\n\
00528 # (width / binning_x) x (height / binning_y).\n\
00529 # The default values binning_x = binning_y = 0 is considered the same\n\
00530 # as binning_x = binning_y = 1 (no subsampling).\n\
00531 uint32 binning_x\n\
00532 uint32 binning_y\n\
00533 \n\
00534 # Region of interest (subwindow of full camera resolution), given in\n\
00535 # full resolution (unbinned) image coordinates. A particular ROI\n\
00536 # always denotes the same window of pixels on the camera sensor,\n\
00537 # regardless of binning settings.\n\
00538 # The default setting of roi (all values 0) is considered the same as\n\
00539 # full resolution (roi.width = width, roi.height = height).\n\
00540 RegionOfInterest roi\n\
00541 \n\
00542 ================================================================================\n\
00543 MSG: sensor_msgs/RegionOfInterest\n\
00544 # This message is used to specify a region of interest within an image.\n\
00545 #\n\
00546 # When used to specify the ROI setting of the camera when the image was\n\
00547 # taken, the height and width fields should either match the height and\n\
00548 # width fields for the associated image; or height = width = 0\n\
00549 # indicates that the full resolution image was captured.\n\
00550 \n\
00551 uint32 x_offset # Leftmost pixel of the ROI\n\
00552 # (0 if the ROI includes the left edge of the image)\n\
00553 uint32 y_offset # Topmost pixel of the ROI\n\
00554 # (0 if the ROI includes the top edge of the image)\n\
00555 uint32 height # Height of ROI\n\
00556 uint32 width # Width of ROI\n\
00557 \n\
00558 # True if a distinct rectified ROI should be calculated from the \"raw\"\n\
00559 # ROI in this message. Typically this should be False if the full image\n\
00560 # is captured (ROI not used), and True if a subwindow is captured (ROI\n\
00561 # used).\n\
00562 bool do_rectify\n\
00563 \n\
00564 ================================================================================\n\
00565 MSG: geometry_msgs/Vector3\n\
00566 # This represents a vector in free space. \n\
00567 \n\
00568 float64 x\n\
00569 float64 y\n\
00570 float64 z\n\
00571 ================================================================================\n\
00572 MSG: manipulation_msgs/Grasp\n\
00573 # A name for this grasp\n\
00574 string id\n\
00575 \n\
00576 # The internal posture of the hand for the pre-grasp\n\
00577 # only positions are used\n\
00578 sensor_msgs/JointState pre_grasp_posture\n\
00579 \n\
00580 # The internal posture of the hand for the grasp\n\
00581 # positions and efforts are used\n\
00582 sensor_msgs/JointState grasp_posture\n\
00583 \n\
00584 # The position of the end-effector for the grasp relative to a reference frame \n\
00585 # (that is always specified elsewhere, not in this message)\n\
00586 geometry_msgs/PoseStamped grasp_pose\n\
00587 \n\
00588 # The estimated probability of success for this grasp, or some other\n\
00589 # measure of how \"good\" it is.\n\
00590 float64 grasp_quality\n\
00591 \n\
00592 # The approach motion\n\
00593 GripperTranslation approach\n\
00594 \n\
00595 # The retreat motion\n\
00596 GripperTranslation retreat\n\
00597 \n\
00598 # the maximum contact force to use while grasping (<=0 to disable)\n\
00599 float32 max_contact_force\n\
00600 \n\
00601 # an optional list of obstacles that we have semantic information about\n\
00602 # and that can be touched/pushed/moved in the course of grasping\n\
00603 string[] allowed_touch_objects\n\
00604 \n\
00605 ================================================================================\n\
00606 MSG: sensor_msgs/JointState\n\
00607 # This is a message that holds data to describe the state of a set of torque controlled joints. \n\
00608 #\n\
00609 # The state of each joint (revolute or prismatic) is defined by:\n\
00610 # * the position of the joint (rad or m),\n\
00611 # * the velocity of the joint (rad/s or m/s) and \n\
00612 # * the effort that is applied in the joint (Nm or N).\n\
00613 #\n\
00614 # Each joint is uniquely identified by its name\n\
00615 # The header specifies the time at which the joint states were recorded. All the joint states\n\
00616 # in one message have to be recorded at the same time.\n\
00617 #\n\
00618 # This message consists of a multiple arrays, one for each part of the joint state. \n\
00619 # The goal is to make each of the fields optional. When e.g. your joints have no\n\
00620 # effort associated with them, you can leave the effort array empty. \n\
00621 #\n\
00622 # All arrays in this message should have the same size, or be empty.\n\
00623 # This is the only way to uniquely associate the joint name with the correct\n\
00624 # states.\n\
00625 \n\
00626 \n\
00627 Header header\n\
00628 \n\
00629 string[] name\n\
00630 float64[] position\n\
00631 float64[] velocity\n\
00632 float64[] effort\n\
00633 \n\
00634 ================================================================================\n\
00635 MSG: manipulation_msgs/GripperTranslation\n\
00636 # defines a translation for the gripper, used in pickup or place tasks\n\
00637 # for example for lifting an object off a table or approaching the table for placing\n\
00638 \n\
00639 # the direction of the translation\n\
00640 geometry_msgs/Vector3Stamped direction\n\
00641 \n\
00642 # the desired translation distance\n\
00643 float32 desired_distance\n\
00644 \n\
00645 # the min distance that must be considered feasible before the\n\
00646 # grasp is even attempted\n\
00647 float32 min_distance\n\
00648 \n\
00649 ================================================================================\n\
00650 MSG: geometry_msgs/Vector3Stamped\n\
00651 # This represents a Vector3 with reference coordinate frame and timestamp\n\
00652 Header header\n\
00653 Vector3 vector\n\
00654 \n\
00655 ";
00656 }
00657
00658 static const char* value(const ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> &) { return value(); }
00659 };
00660
00661 }
00662 }
00663
00664 namespace ros
00665 {
00666 namespace serialization
00667 {
00668
00669 template<class ContainerAllocator> struct Serializer< ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> >
00670 {
00671 template<typename Stream, typename T> inline static void allInOne(Stream& stream, T m)
00672 {
00673 stream.next(m.arm_name);
00674 stream.next(m.gripper_pose);
00675 stream.next(m.gripper_opening);
00676 stream.next(m.object);
00677 stream.next(m.grasp);
00678 }
00679
00680 ROS_DECLARE_ALLINONE_SERIALIZER;
00681 };
00682 }
00683 }
00684
00685 namespace ros
00686 {
00687 namespace message_operations
00688 {
00689
00690 template<class ContainerAllocator>
00691 struct Printer< ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> >
00692 {
00693 template<typename Stream> static void stream(Stream& s, const std::string& indent, const ::pr2_object_manipulation_msgs::GetGripperPoseGoal_<ContainerAllocator> & v)
00694 {
00695 s << indent << "arm_name: ";
00696 Printer<std::basic_string<char, std::char_traits<char>, typename ContainerAllocator::template rebind<char>::other > >::stream(s, indent + " ", v.arm_name);
00697 s << indent << "gripper_pose: ";
00698 s << std::endl;
00699 Printer< ::geometry_msgs::PoseStamped_<ContainerAllocator> >::stream(s, indent + " ", v.gripper_pose);
00700 s << indent << "gripper_opening: ";
00701 Printer<float>::stream(s, indent + " ", v.gripper_opening);
00702 s << indent << "object: ";
00703 s << std::endl;
00704 Printer< ::manipulation_msgs::GraspableObject_<ContainerAllocator> >::stream(s, indent + " ", v.object);
00705 s << indent << "grasp: ";
00706 s << std::endl;
00707 Printer< ::manipulation_msgs::Grasp_<ContainerAllocator> >::stream(s, indent + " ", v.grasp);
00708 }
00709 };
00710
00711
00712 }
00713 }
00714
00715 #endif // PR2_OBJECT_MANIPULATION_MSGS_MESSAGE_GETGRIPPERPOSEGOAL_H
00716