ReactiveGraspAction.h
Go to the documentation of this file.
00001 /* Auto-generated by genmsg_cpp for file /home/rosbuild/hudson/workspace/doc-groovy-object_manipulation/doc_stacks/2014-10-06_02-51-20.607186/object_manipulation/object_manipulation_msgs/msg/ReactiveGraspAction.msg */
00002 #ifndef OBJECT_MANIPULATION_MSGS_MESSAGE_REACTIVEGRASPACTION_H
00003 #define OBJECT_MANIPULATION_MSGS_MESSAGE_REACTIVEGRASPACTION_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 "object_manipulation_msgs/ReactiveGraspActionGoal.h"
00018 #include "object_manipulation_msgs/ReactiveGraspActionResult.h"
00019 #include "object_manipulation_msgs/ReactiveGraspActionFeedback.h"
00020 
00021 namespace object_manipulation_msgs
00022 {
00023 template <class ContainerAllocator>
00024 struct ReactiveGraspAction_ {
00025   typedef ReactiveGraspAction_<ContainerAllocator> Type;
00026 
00027   ReactiveGraspAction_()
00028   : action_goal()
00029   , action_result()
00030   , action_feedback()
00031   {
00032   }
00033 
00034   ReactiveGraspAction_(const ContainerAllocator& _alloc)
00035   : action_goal(_alloc)
00036   , action_result(_alloc)
00037   , action_feedback(_alloc)
00038   {
00039   }
00040 
00041   typedef  ::object_manipulation_msgs::ReactiveGraspActionGoal_<ContainerAllocator>  _action_goal_type;
00042    ::object_manipulation_msgs::ReactiveGraspActionGoal_<ContainerAllocator>  action_goal;
00043 
00044   typedef  ::object_manipulation_msgs::ReactiveGraspActionResult_<ContainerAllocator>  _action_result_type;
00045    ::object_manipulation_msgs::ReactiveGraspActionResult_<ContainerAllocator>  action_result;
00046 
00047   typedef  ::object_manipulation_msgs::ReactiveGraspActionFeedback_<ContainerAllocator>  _action_feedback_type;
00048    ::object_manipulation_msgs::ReactiveGraspActionFeedback_<ContainerAllocator>  action_feedback;
00049 
00050 
00051   typedef boost::shared_ptr< ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> > Ptr;
00052   typedef boost::shared_ptr< ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator>  const> ConstPtr;
00053   boost::shared_ptr<std::map<std::string, std::string> > __connection_header;
00054 }; // struct ReactiveGraspAction
00055 typedef  ::object_manipulation_msgs::ReactiveGraspAction_<std::allocator<void> > ReactiveGraspAction;
00056 
00057 typedef boost::shared_ptr< ::object_manipulation_msgs::ReactiveGraspAction> ReactiveGraspActionPtr;
00058 typedef boost::shared_ptr< ::object_manipulation_msgs::ReactiveGraspAction const> ReactiveGraspActionConstPtr;
00059 
00060 
00061 template<typename ContainerAllocator>
00062 std::ostream& operator<<(std::ostream& s, const  ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> & v)
00063 {
00064   ros::message_operations::Printer< ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> >::stream(s, "", v);
00065   return s;}
00066 
00067 } // namespace object_manipulation_msgs
00068 
00069 namespace ros
00070 {
00071 namespace message_traits
00072 {
00073 template<class ContainerAllocator> struct IsMessage< ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> > : public TrueType {};
00074 template<class ContainerAllocator> struct IsMessage< ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator>  const> : public TrueType {};
00075 template<class ContainerAllocator>
00076 struct MD5Sum< ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> > {
00077   static const char* value() 
00078   {
00079     return "48142d08b2d5130ed6cb2d343e39b1e5";
00080   }
00081 
00082   static const char* value(const  ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> &) { return value(); } 
00083   static const uint64_t static_value1 = 0x48142d08b2d5130eULL;
00084   static const uint64_t static_value2 = 0xd6cb2d343e39b1e5ULL;
00085 };
00086 
00087 template<class ContainerAllocator>
00088 struct DataType< ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> > {
00089   static const char* value() 
00090   {
00091     return "object_manipulation_msgs/ReactiveGraspAction";
00092   }
00093 
00094   static const char* value(const  ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> &) { return value(); } 
00095 };
00096 
00097 template<class ContainerAllocator>
00098 struct Definition< ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> > {
00099   static const char* value() 
00100   {
00101     return "# ====== DO NOT MODIFY! AUTOGENERATED FROM AN ACTION DEFINITION ======\n\
00102 \n\
00103 ReactiveGraspActionGoal action_goal\n\
00104 ReactiveGraspActionResult action_result\n\
00105 ReactiveGraspActionFeedback action_feedback\n\
00106 \n\
00107 ================================================================================\n\
00108 MSG: object_manipulation_msgs/ReactiveGraspActionGoal\n\
00109 # ====== DO NOT MODIFY! AUTOGENERATED FROM AN ACTION DEFINITION ======\n\
00110 \n\
00111 Header header\n\
00112 actionlib_msgs/GoalID goal_id\n\
00113 ReactiveGraspGoal goal\n\
00114 \n\
00115 ================================================================================\n\
00116 MSG: std_msgs/Header\n\
00117 # Standard metadata for higher-level stamped data types.\n\
00118 # This is generally used to communicate timestamped data \n\
00119 # in a particular coordinate frame.\n\
00120 # \n\
00121 # sequence ID: consecutively increasing ID \n\
00122 uint32 seq\n\
00123 #Two-integer timestamp that is expressed as:\n\
00124 # * stamp.secs: seconds (stamp_secs) since epoch\n\
00125 # * stamp.nsecs: nanoseconds since stamp_secs\n\
00126 # time-handling sugar is provided by the client library\n\
00127 time stamp\n\
00128 #Frame this data is associated with\n\
00129 # 0: no frame\n\
00130 # 1: global frame\n\
00131 string frame_id\n\
00132 \n\
00133 ================================================================================\n\
00134 MSG: actionlib_msgs/GoalID\n\
00135 # The stamp should store the time at which this goal was requested.\n\
00136 # It is used by an action server when it tries to preempt all\n\
00137 # goals that were requested before a certain time\n\
00138 time stamp\n\
00139 \n\
00140 # The id provides a way to associate feedback and\n\
00141 # result message with specific goal requests. The id\n\
00142 # specified must be unique.\n\
00143 string id\n\
00144 \n\
00145 \n\
00146 ================================================================================\n\
00147 MSG: object_manipulation_msgs/ReactiveGraspGoal\n\
00148 # ====== DO NOT MODIFY! AUTOGENERATED FROM AN ACTION DEFINITION ======\n\
00149 # an action for reactive grasping\n\
00150 # a reactive grasp starts from the current pose of the gripper and ends\n\
00151 # at a desired grasp pose, presumably using the touch sensors along the way\n\
00152 \n\
00153 # the name of the arm being used\n\
00154 string arm_name\n\
00155 \n\
00156 # the object to be grasped\n\
00157 manipulation_msgs/GraspableObject target\n\
00158 \n\
00159 # the desired grasp pose for the hand\n\
00160 geometry_msgs/PoseStamped final_grasp_pose\n\
00161 \n\
00162 # the joint trajectory to use for the approach (if available)\n\
00163 # this trajectory is expected to start at the current pose of the gripper\n\
00164 # and end at the desired grasp pose\n\
00165 trajectory_msgs/JointTrajectory trajectory\n\
00166 \n\
00167 # the name of the support surface in the collision environment, if any\n\
00168 string collision_support_surface_name\n\
00169 \n\
00170 # The internal posture of the hand for the pre-grasp\n\
00171 # only positions are used\n\
00172 sensor_msgs/JointState pre_grasp_posture\n\
00173 \n\
00174 # The internal posture of the hand for the grasp\n\
00175 # positions and efforts are used\n\
00176 sensor_msgs/JointState grasp_posture\n\
00177 \n\
00178 # The max contact force to use while grasping (<=0 to disable)\n\
00179 float32 max_contact_force\n\
00180 \n\
00181 \n\
00182 ================================================================================\n\
00183 MSG: manipulation_msgs/GraspableObject\n\
00184 # an object that the object_manipulator can work on\n\
00185 \n\
00186 # a graspable object can be represented in multiple ways. This message\n\
00187 # can contain all of them. Which one is actually used is up to the receiver\n\
00188 # of this message. When adding new representations, one must be careful that\n\
00189 # they have reasonable lightweight defaults indicating that that particular\n\
00190 # representation is not available.\n\
00191 \n\
00192 # the tf frame to be used as a reference frame when combining information from\n\
00193 # the different representations below\n\
00194 string reference_frame_id\n\
00195 \n\
00196 # potential recognition results from a database of models\n\
00197 # all poses are relative to the object reference pose\n\
00198 household_objects_database_msgs/DatabaseModelPose[] potential_models\n\
00199 \n\
00200 # the point cloud itself\n\
00201 sensor_msgs/PointCloud cluster\n\
00202 \n\
00203 # a region of a PointCloud2 of interest\n\
00204 SceneRegion region\n\
00205 \n\
00206 # the name that this object has in the collision environment\n\
00207 string collision_name\n\
00208 ================================================================================\n\
00209 MSG: household_objects_database_msgs/DatabaseModelPose\n\
00210 # Informs that a specific model from the Model Database has been \n\
00211 # identified at a certain location\n\
00212 \n\
00213 # the database id of the model\n\
00214 int32 model_id\n\
00215 \n\
00216 # if the object was recognized by the ORK pipeline, its type will be in here\n\
00217 # if this is not empty, then the string in here will be converted to a household_objects_database id\n\
00218 # leave this empty if providing an id in the model_id field\n\
00219 object_recognition_msgs/ObjectType type\n\
00220 \n\
00221 # the pose that it can be found in\n\
00222 geometry_msgs/PoseStamped pose\n\
00223 \n\
00224 # a measure of the confidence level in this detection result\n\
00225 float32 confidence\n\
00226 \n\
00227 # the name of the object detector that generated this detection result\n\
00228 string detector_name\n\
00229 \n\
00230 ================================================================================\n\
00231 MSG: object_recognition_msgs/ObjectType\n\
00232 ################################################## OBJECT ID #########################################################\n\
00233 \n\
00234 # Contains information about the type of a found object. Those two sets of parameters together uniquely define an\n\
00235 # object\n\
00236 \n\
00237 # The key of the found object: the unique identifier in the given db\n\
00238 string key\n\
00239 \n\
00240 # The db parameters stored as a JSON/compressed YAML string. An object id does not make sense without the corresponding\n\
00241 # database. E.g., in object_recognition, it can look like: \"{'type':'CouchDB', 'root':'http://localhost'}\"\n\
00242 # There is no conventional format for those parameters and it's nice to keep that flexibility.\n\
00243 # The object_recognition_core as a generic DB type that can read those fields\n\
00244 # Current examples:\n\
00245 # For CouchDB:\n\
00246 #   type: 'CouchDB'\n\
00247 #   root: 'http://localhost:5984'\n\
00248 #   collection: 'object_recognition'\n\
00249 # For SQL household database:\n\
00250 #   type: 'SqlHousehold'\n\
00251 #   host: 'wgs36'\n\
00252 #   port: 5432\n\
00253 #   user: 'willow'\n\
00254 #   password: 'willow'\n\
00255 #   name: 'household_objects'\n\
00256 #   module: 'tabletop'\n\
00257 string db\n\
00258 \n\
00259 ================================================================================\n\
00260 MSG: geometry_msgs/PoseStamped\n\
00261 # A Pose with reference coordinate frame and timestamp\n\
00262 Header header\n\
00263 Pose pose\n\
00264 \n\
00265 ================================================================================\n\
00266 MSG: geometry_msgs/Pose\n\
00267 # A representation of pose in free space, composed of postion and orientation. \n\
00268 Point position\n\
00269 Quaternion orientation\n\
00270 \n\
00271 ================================================================================\n\
00272 MSG: geometry_msgs/Point\n\
00273 # This contains the position of a point in free space\n\
00274 float64 x\n\
00275 float64 y\n\
00276 float64 z\n\
00277 \n\
00278 ================================================================================\n\
00279 MSG: geometry_msgs/Quaternion\n\
00280 # This represents an orientation in free space in quaternion form.\n\
00281 \n\
00282 float64 x\n\
00283 float64 y\n\
00284 float64 z\n\
00285 float64 w\n\
00286 \n\
00287 ================================================================================\n\
00288 MSG: sensor_msgs/PointCloud\n\
00289 # This message holds a collection of 3d points, plus optional additional\n\
00290 # information about each point.\n\
00291 \n\
00292 # Time of sensor data acquisition, coordinate frame ID.\n\
00293 Header header\n\
00294 \n\
00295 # Array of 3d points. Each Point32 should be interpreted as a 3d point\n\
00296 # in the frame given in the header.\n\
00297 geometry_msgs/Point32[] points\n\
00298 \n\
00299 # Each channel should have the same number of elements as points array,\n\
00300 # and the data in each channel should correspond 1:1 with each point.\n\
00301 # Channel names in common practice are listed in ChannelFloat32.msg.\n\
00302 ChannelFloat32[] channels\n\
00303 \n\
00304 ================================================================================\n\
00305 MSG: geometry_msgs/Point32\n\
00306 # This contains the position of a point in free space(with 32 bits of precision).\n\
00307 # It is recommeded to use Point wherever possible instead of Point32.  \n\
00308 # \n\
00309 # This recommendation is to promote interoperability.  \n\
00310 #\n\
00311 # This message is designed to take up less space when sending\n\
00312 # lots of points at once, as in the case of a PointCloud.  \n\
00313 \n\
00314 float32 x\n\
00315 float32 y\n\
00316 float32 z\n\
00317 ================================================================================\n\
00318 MSG: sensor_msgs/ChannelFloat32\n\
00319 # This message is used by the PointCloud message to hold optional data\n\
00320 # associated with each point in the cloud. The length of the values\n\
00321 # array should be the same as the length of the points array in the\n\
00322 # PointCloud, and each value should be associated with the corresponding\n\
00323 # point.\n\
00324 \n\
00325 # Channel names in existing practice include:\n\
00326 #   \"u\", \"v\" - row and column (respectively) in the left stereo image.\n\
00327 #              This is opposite to usual conventions but remains for\n\
00328 #              historical reasons. The newer PointCloud2 message has no\n\
00329 #              such problem.\n\
00330 #   \"rgb\" - For point clouds produced by color stereo cameras. uint8\n\
00331 #           (R,G,B) values packed into the least significant 24 bits,\n\
00332 #           in order.\n\
00333 #   \"intensity\" - laser or pixel intensity.\n\
00334 #   \"distance\"\n\
00335 \n\
00336 # The channel name should give semantics of the channel (e.g.\n\
00337 # \"intensity\" instead of \"value\").\n\
00338 string name\n\
00339 \n\
00340 # The values array should be 1-1 with the elements of the associated\n\
00341 # PointCloud.\n\
00342 float32[] values\n\
00343 \n\
00344 ================================================================================\n\
00345 MSG: manipulation_msgs/SceneRegion\n\
00346 # Point cloud\n\
00347 sensor_msgs/PointCloud2 cloud\n\
00348 \n\
00349 # Indices for the region of interest\n\
00350 int32[] mask\n\
00351 \n\
00352 # One of the corresponding 2D images, if applicable\n\
00353 sensor_msgs/Image image\n\
00354 \n\
00355 # The disparity image, if applicable\n\
00356 sensor_msgs/Image disparity_image\n\
00357 \n\
00358 # Camera info for the camera that took the image\n\
00359 sensor_msgs/CameraInfo cam_info\n\
00360 \n\
00361 # a 3D region of interest for grasp planning\n\
00362 geometry_msgs/PoseStamped  roi_box_pose\n\
00363 geometry_msgs/Vector3      roi_box_dims\n\
00364 \n\
00365 ================================================================================\n\
00366 MSG: sensor_msgs/PointCloud2\n\
00367 # This message holds a collection of N-dimensional points, which may\n\
00368 # contain additional information such as normals, intensity, etc. The\n\
00369 # point data is stored as a binary blob, its layout described by the\n\
00370 # contents of the \"fields\" array.\n\
00371 \n\
00372 # The point cloud data may be organized 2d (image-like) or 1d\n\
00373 # (unordered). Point clouds organized as 2d images may be produced by\n\
00374 # camera depth sensors such as stereo or time-of-flight.\n\
00375 \n\
00376 # Time of sensor data acquisition, and the coordinate frame ID (for 3d\n\
00377 # points).\n\
00378 Header header\n\
00379 \n\
00380 # 2D structure of the point cloud. If the cloud is unordered, height is\n\
00381 # 1 and width is the length of the point cloud.\n\
00382 uint32 height\n\
00383 uint32 width\n\
00384 \n\
00385 # Describes the channels and their layout in the binary data blob.\n\
00386 PointField[] fields\n\
00387 \n\
00388 bool    is_bigendian # Is this data bigendian?\n\
00389 uint32  point_step   # Length of a point in bytes\n\
00390 uint32  row_step     # Length of a row in bytes\n\
00391 uint8[] data         # Actual point data, size is (row_step*height)\n\
00392 \n\
00393 bool is_dense        # True if there are no invalid points\n\
00394 \n\
00395 ================================================================================\n\
00396 MSG: sensor_msgs/PointField\n\
00397 # This message holds the description of one point entry in the\n\
00398 # PointCloud2 message format.\n\
00399 uint8 INT8    = 1\n\
00400 uint8 UINT8   = 2\n\
00401 uint8 INT16   = 3\n\
00402 uint8 UINT16  = 4\n\
00403 uint8 INT32   = 5\n\
00404 uint8 UINT32  = 6\n\
00405 uint8 FLOAT32 = 7\n\
00406 uint8 FLOAT64 = 8\n\
00407 \n\
00408 string name      # Name of field\n\
00409 uint32 offset    # Offset from start of point struct\n\
00410 uint8  datatype  # Datatype enumeration, see above\n\
00411 uint32 count     # How many elements in the field\n\
00412 \n\
00413 ================================================================================\n\
00414 MSG: sensor_msgs/Image\n\
00415 # This message contains an uncompressed image\n\
00416 # (0, 0) is at top-left corner of image\n\
00417 #\n\
00418 \n\
00419 Header header        # Header timestamp should be acquisition time of image\n\
00420                      # Header frame_id should be optical frame of camera\n\
00421                      # origin of frame should be optical center of cameara\n\
00422                      # +x should point to the right in the image\n\
00423                      # +y should point down in the image\n\
00424                      # +z should point into to plane of the image\n\
00425                      # If the frame_id here and the frame_id of the CameraInfo\n\
00426                      # message associated with the image conflict\n\
00427                      # the behavior is undefined\n\
00428 \n\
00429 uint32 height         # image height, that is, number of rows\n\
00430 uint32 width          # image width, that is, number of columns\n\
00431 \n\
00432 # The legal values for encoding are in file src/image_encodings.cpp\n\
00433 # If you want to standardize a new string format, join\n\
00434 # ros-users@lists.sourceforge.net and send an email proposing a new encoding.\n\
00435 \n\
00436 string encoding       # Encoding of pixels -- channel meaning, ordering, size\n\
00437                       # taken from the list of strings in include/sensor_msgs/image_encodings.h\n\
00438 \n\
00439 uint8 is_bigendian    # is this data bigendian?\n\
00440 uint32 step           # Full row length in bytes\n\
00441 uint8[] data          # actual matrix data, size is (step * rows)\n\
00442 \n\
00443 ================================================================================\n\
00444 MSG: sensor_msgs/CameraInfo\n\
00445 # This message defines meta information for a camera. It should be in a\n\
00446 # camera namespace on topic \"camera_info\" and accompanied by up to five\n\
00447 # image topics named:\n\
00448 #\n\
00449 #   image_raw - raw data from the camera driver, possibly Bayer encoded\n\
00450 #   image            - monochrome, distorted\n\
00451 #   image_color      - color, distorted\n\
00452 #   image_rect       - monochrome, rectified\n\
00453 #   image_rect_color - color, rectified\n\
00454 #\n\
00455 # The image_pipeline contains packages (image_proc, stereo_image_proc)\n\
00456 # for producing the four processed image topics from image_raw and\n\
00457 # camera_info. The meaning of the camera parameters are described in\n\
00458 # detail at http://www.ros.org/wiki/image_pipeline/CameraInfo.\n\
00459 #\n\
00460 # The image_geometry package provides a user-friendly interface to\n\
00461 # common operations using this meta information. If you want to, e.g.,\n\
00462 # project a 3d point into image coordinates, we strongly recommend\n\
00463 # using image_geometry.\n\
00464 #\n\
00465 # If the camera is uncalibrated, the matrices D, K, R, P should be left\n\
00466 # zeroed out. In particular, clients may assume that K[0] == 0.0\n\
00467 # indicates an uncalibrated camera.\n\
00468 \n\
00469 #######################################################################\n\
00470 #                     Image acquisition info                          #\n\
00471 #######################################################################\n\
00472 \n\
00473 # Time of image acquisition, camera coordinate frame ID\n\
00474 Header header    # Header timestamp should be acquisition time of image\n\
00475                  # Header frame_id should be optical frame of camera\n\
00476                  # origin of frame should be optical center of camera\n\
00477                  # +x should point to the right in the image\n\
00478                  # +y should point down in the image\n\
00479                  # +z should point into the plane of the image\n\
00480 \n\
00481 \n\
00482 #######################################################################\n\
00483 #                      Calibration Parameters                         #\n\
00484 #######################################################################\n\
00485 # These are fixed during camera calibration. Their values will be the #\n\
00486 # same in all messages until the camera is recalibrated. Note that    #\n\
00487 # self-calibrating systems may \"recalibrate\" frequently.              #\n\
00488 #                                                                     #\n\
00489 # The internal parameters can be used to warp a raw (distorted) image #\n\
00490 # to:                                                                 #\n\
00491 #   1. An undistorted image (requires D and K)                        #\n\
00492 #   2. A rectified image (requires D, K, R)                           #\n\
00493 # The projection matrix P projects 3D points into the rectified image.#\n\
00494 #######################################################################\n\
00495 \n\
00496 # The image dimensions with which the camera was calibrated. Normally\n\
00497 # this will be the full camera resolution in pixels.\n\
00498 uint32 height\n\
00499 uint32 width\n\
00500 \n\
00501 # The distortion model used. Supported models are listed in\n\
00502 # sensor_msgs/distortion_models.h. For most cameras, \"plumb_bob\" - a\n\
00503 # simple model of radial and tangential distortion - is sufficent.\n\
00504 string distortion_model\n\
00505 \n\
00506 # The distortion parameters, size depending on the distortion model.\n\
00507 # For \"plumb_bob\", the 5 parameters are: (k1, k2, t1, t2, k3).\n\
00508 float64[] D\n\
00509 \n\
00510 # Intrinsic camera matrix for the raw (distorted) images.\n\
00511 #     [fx  0 cx]\n\
00512 # K = [ 0 fy cy]\n\
00513 #     [ 0  0  1]\n\
00514 # Projects 3D points in the camera coordinate frame to 2D pixel\n\
00515 # coordinates using the focal lengths (fx, fy) and principal point\n\
00516 # (cx, cy).\n\
00517 float64[9]  K # 3x3 row-major matrix\n\
00518 \n\
00519 # Rectification matrix (stereo cameras only)\n\
00520 # A rotation matrix aligning the camera coordinate system to the ideal\n\
00521 # stereo image plane so that epipolar lines in both stereo images are\n\
00522 # parallel.\n\
00523 float64[9]  R # 3x3 row-major matrix\n\
00524 \n\
00525 # Projection/camera matrix\n\
00526 #     [fx'  0  cx' Tx]\n\
00527 # P = [ 0  fy' cy' Ty]\n\
00528 #     [ 0   0   1   0]\n\
00529 # By convention, this matrix specifies the intrinsic (camera) matrix\n\
00530 #  of the processed (rectified) image. That is, the left 3x3 portion\n\
00531 #  is the normal camera intrinsic matrix for the rectified image.\n\
00532 # It projects 3D points in the camera coordinate frame to 2D pixel\n\
00533 #  coordinates using the focal lengths (fx', fy') and principal point\n\
00534 #  (cx', cy') - these may differ from the values in K.\n\
00535 # For monocular cameras, Tx = Ty = 0. Normally, monocular cameras will\n\
00536 #  also have R = the identity and P[1:3,1:3] = K.\n\
00537 # For a stereo pair, the fourth column [Tx Ty 0]' is related to the\n\
00538 #  position of the optical center of the second camera in the first\n\
00539 #  camera's frame. We assume Tz = 0 so both cameras are in the same\n\
00540 #  stereo image plane. The first camera always has Tx = Ty = 0. For\n\
00541 #  the right (second) camera of a horizontal stereo pair, Ty = 0 and\n\
00542 #  Tx = -fx' * B, where B is the baseline between the cameras.\n\
00543 # Given a 3D point [X Y Z]', the projection (x, y) of the point onto\n\
00544 #  the rectified image is given by:\n\
00545 #  [u v w]' = P * [X Y Z 1]'\n\
00546 #         x = u / w\n\
00547 #         y = v / w\n\
00548 #  This holds for both images of a stereo pair.\n\
00549 float64[12] P # 3x4 row-major matrix\n\
00550 \n\
00551 \n\
00552 #######################################################################\n\
00553 #                      Operational Parameters                         #\n\
00554 #######################################################################\n\
00555 # These define the image region actually captured by the camera       #\n\
00556 # driver. Although they affect the geometry of the output image, they #\n\
00557 # may be changed freely without recalibrating the camera.             #\n\
00558 #######################################################################\n\
00559 \n\
00560 # Binning refers here to any camera setting which combines rectangular\n\
00561 #  neighborhoods of pixels into larger \"super-pixels.\" It reduces the\n\
00562 #  resolution of the output image to\n\
00563 #  (width / binning_x) x (height / binning_y).\n\
00564 # The default values binning_x = binning_y = 0 is considered the same\n\
00565 #  as binning_x = binning_y = 1 (no subsampling).\n\
00566 uint32 binning_x\n\
00567 uint32 binning_y\n\
00568 \n\
00569 # Region of interest (subwindow of full camera resolution), given in\n\
00570 #  full resolution (unbinned) image coordinates. A particular ROI\n\
00571 #  always denotes the same window of pixels on the camera sensor,\n\
00572 #  regardless of binning settings.\n\
00573 # The default setting of roi (all values 0) is considered the same as\n\
00574 #  full resolution (roi.width = width, roi.height = height).\n\
00575 RegionOfInterest roi\n\
00576 \n\
00577 ================================================================================\n\
00578 MSG: sensor_msgs/RegionOfInterest\n\
00579 # This message is used to specify a region of interest within an image.\n\
00580 #\n\
00581 # When used to specify the ROI setting of the camera when the image was\n\
00582 # taken, the height and width fields should either match the height and\n\
00583 # width fields for the associated image; or height = width = 0\n\
00584 # indicates that the full resolution image was captured.\n\
00585 \n\
00586 uint32 x_offset  # Leftmost pixel of the ROI\n\
00587                  # (0 if the ROI includes the left edge of the image)\n\
00588 uint32 y_offset  # Topmost pixel of the ROI\n\
00589                  # (0 if the ROI includes the top edge of the image)\n\
00590 uint32 height    # Height of ROI\n\
00591 uint32 width     # Width of ROI\n\
00592 \n\
00593 # True if a distinct rectified ROI should be calculated from the \"raw\"\n\
00594 # ROI in this message. Typically this should be False if the full image\n\
00595 # is captured (ROI not used), and True if a subwindow is captured (ROI\n\
00596 # used).\n\
00597 bool do_rectify\n\
00598 \n\
00599 ================================================================================\n\
00600 MSG: geometry_msgs/Vector3\n\
00601 # This represents a vector in free space. \n\
00602 \n\
00603 float64 x\n\
00604 float64 y\n\
00605 float64 z\n\
00606 ================================================================================\n\
00607 MSG: trajectory_msgs/JointTrajectory\n\
00608 Header header\n\
00609 string[] joint_names\n\
00610 JointTrajectoryPoint[] points\n\
00611 ================================================================================\n\
00612 MSG: trajectory_msgs/JointTrajectoryPoint\n\
00613 float64[] positions\n\
00614 float64[] velocities\n\
00615 float64[] accelerations\n\
00616 duration time_from_start\n\
00617 ================================================================================\n\
00618 MSG: sensor_msgs/JointState\n\
00619 # This is a message that holds data to describe the state of a set of torque controlled joints. \n\
00620 #\n\
00621 # The state of each joint (revolute or prismatic) is defined by:\n\
00622 #  * the position of the joint (rad or m),\n\
00623 #  * the velocity of the joint (rad/s or m/s) and \n\
00624 #  * the effort that is applied in the joint (Nm or N).\n\
00625 #\n\
00626 # Each joint is uniquely identified by its name\n\
00627 # The header specifies the time at which the joint states were recorded. All the joint states\n\
00628 # in one message have to be recorded at the same time.\n\
00629 #\n\
00630 # This message consists of a multiple arrays, one for each part of the joint state. \n\
00631 # The goal is to make each of the fields optional. When e.g. your joints have no\n\
00632 # effort associated with them, you can leave the effort array empty. \n\
00633 #\n\
00634 # All arrays in this message should have the same size, or be empty.\n\
00635 # This is the only way to uniquely associate the joint name with the correct\n\
00636 # states.\n\
00637 \n\
00638 \n\
00639 Header header\n\
00640 \n\
00641 string[] name\n\
00642 float64[] position\n\
00643 float64[] velocity\n\
00644 float64[] effort\n\
00645 \n\
00646 ================================================================================\n\
00647 MSG: object_manipulation_msgs/ReactiveGraspActionResult\n\
00648 # ====== DO NOT MODIFY! AUTOGENERATED FROM AN ACTION DEFINITION ======\n\
00649 \n\
00650 Header header\n\
00651 actionlib_msgs/GoalStatus status\n\
00652 ReactiveGraspResult result\n\
00653 \n\
00654 ================================================================================\n\
00655 MSG: actionlib_msgs/GoalStatus\n\
00656 GoalID goal_id\n\
00657 uint8 status\n\
00658 uint8 PENDING         = 0   # The goal has yet to be processed by the action server\n\
00659 uint8 ACTIVE          = 1   # The goal is currently being processed by the action server\n\
00660 uint8 PREEMPTED       = 2   # The goal received a cancel request after it started executing\n\
00661                             #   and has since completed its execution (Terminal State)\n\
00662 uint8 SUCCEEDED       = 3   # The goal was achieved successfully by the action server (Terminal State)\n\
00663 uint8 ABORTED         = 4   # The goal was aborted during execution by the action server due\n\
00664                             #    to some failure (Terminal State)\n\
00665 uint8 REJECTED        = 5   # The goal was rejected by the action server without being processed,\n\
00666                             #    because the goal was unattainable or invalid (Terminal State)\n\
00667 uint8 PREEMPTING      = 6   # The goal received a cancel request after it started executing\n\
00668                             #    and has not yet completed execution\n\
00669 uint8 RECALLING       = 7   # The goal received a cancel request before it started executing,\n\
00670                             #    but the action server has not yet confirmed that the goal is canceled\n\
00671 uint8 RECALLED        = 8   # The goal received a cancel request before it started executing\n\
00672                             #    and was successfully cancelled (Terminal State)\n\
00673 uint8 LOST            = 9   # An action client can determine that a goal is LOST. This should not be\n\
00674                             #    sent over the wire by an action server\n\
00675 \n\
00676 #Allow for the user to associate a string with GoalStatus for debugging\n\
00677 string text\n\
00678 \n\
00679 \n\
00680 ================================================================================\n\
00681 MSG: object_manipulation_msgs/ReactiveGraspResult\n\
00682 # ====== DO NOT MODIFY! AUTOGENERATED FROM AN ACTION DEFINITION ======\n\
00683 \n\
00684 # the result of the reactive grasp attempt\n\
00685 \n\
00686 ManipulationResult manipulation_result\n\
00687 \n\
00688 \n\
00689 ================================================================================\n\
00690 MSG: object_manipulation_msgs/ManipulationResult\n\
00691 # Result codes for manipulation tasks\n\
00692 \n\
00693 # task completed as expected\n\
00694 # generally means you can proceed as planned\n\
00695 int32 SUCCESS = 1\n\
00696 \n\
00697 # task not possible (e.g. out of reach or obstacles in the way)\n\
00698 # generally means that the world was not disturbed, so you can try another task\n\
00699 int32 UNFEASIBLE = -1\n\
00700 \n\
00701 # task was thought possible, but failed due to unexpected events during execution\n\
00702 # it is likely that the world was disturbed, so you are encouraged to refresh\n\
00703 # your sensed world model before proceeding to another task\n\
00704 int32 FAILED = -2\n\
00705 \n\
00706 # a lower level error prevented task completion (e.g. joint controller not responding)\n\
00707 # generally requires human attention\n\
00708 int32 ERROR = -3\n\
00709 \n\
00710 # means that at some point during execution we ended up in a state that the collision-aware\n\
00711 # arm navigation module will not move out of. The world was likely not disturbed, but you \n\
00712 # probably need a new collision map to move the arm out of the stuck position\n\
00713 int32 ARM_MOVEMENT_PREVENTED = -4\n\
00714 \n\
00715 # specific to grasp actions\n\
00716 # the object was grasped successfully, but the lift attempt could not achieve the minimum lift distance requested\n\
00717 # it is likely that the collision environment will see collisions between the hand/object and the support surface\n\
00718 int32 LIFT_FAILED = -5\n\
00719 \n\
00720 # specific to place actions\n\
00721 # the object was placed successfully, but the retreat attempt could not achieve the minimum retreat distance requested\n\
00722 # it is likely that the collision environment will see collisions between the hand and the object\n\
00723 int32 RETREAT_FAILED = -6\n\
00724 \n\
00725 # indicates that somewhere along the line a human said \"wait, stop, this is bad, go back and do something else\"\n\
00726 int32 CANCELLED = -7\n\
00727 \n\
00728 # the actual value of this error code\n\
00729 int32 value\n\
00730 \n\
00731 ================================================================================\n\
00732 MSG: object_manipulation_msgs/ReactiveGraspActionFeedback\n\
00733 # ====== DO NOT MODIFY! AUTOGENERATED FROM AN ACTION DEFINITION ======\n\
00734 \n\
00735 Header header\n\
00736 actionlib_msgs/GoalStatus status\n\
00737 ReactiveGraspFeedback feedback\n\
00738 \n\
00739 ================================================================================\n\
00740 MSG: object_manipulation_msgs/ReactiveGraspFeedback\n\
00741 # ====== DO NOT MODIFY! AUTOGENERATED FROM AN ACTION DEFINITION ======\n\
00742 \n\
00743 # which phase the grasp is in\n\
00744 \n\
00745 ManipulationPhase manipulation_phase\n\
00746 \n\
00747 \n\
00748 \n\
00749 \n\
00750 ================================================================================\n\
00751 MSG: object_manipulation_msgs/ManipulationPhase\n\
00752 int32 CHECKING_FEASIBILITY = 0\n\
00753 int32 MOVING_TO_PREGRASP = 1\n\
00754 int32 MOVING_TO_GRASP = 2\n\
00755 int32 CLOSING = 3 \n\
00756 int32 ADJUSTING_GRASP = 4\n\
00757 int32 LIFTING = 5\n\
00758 int32 MOVING_WITH_OBJECT = 6\n\
00759 int32 MOVING_TO_PLACE = 7\n\
00760 int32 PLACING = 8\n\
00761 int32 OPENING = 9\n\
00762 int32 RETREATING = 10\n\
00763 int32 MOVING_WITHOUT_OBJECT = 11\n\
00764 int32 SHAKING = 12\n\
00765 int32 SUCCEEDED = 13\n\
00766 int32 FAILED = 14\n\
00767 int32 ABORTED = 15\n\
00768 int32 HOLDING_OBJECT = 16\n\
00769 \n\
00770 int32 phase\n\
00771 ";
00772   }
00773 
00774   static const char* value(const  ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> &) { return value(); } 
00775 };
00776 
00777 } // namespace message_traits
00778 } // namespace ros
00779 
00780 namespace ros
00781 {
00782 namespace serialization
00783 {
00784 
00785 template<class ContainerAllocator> struct Serializer< ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> >
00786 {
00787   template<typename Stream, typename T> inline static void allInOne(Stream& stream, T m)
00788   {
00789     stream.next(m.action_goal);
00790     stream.next(m.action_result);
00791     stream.next(m.action_feedback);
00792   }
00793 
00794   ROS_DECLARE_ALLINONE_SERIALIZER;
00795 }; // struct ReactiveGraspAction_
00796 } // namespace serialization
00797 } // namespace ros
00798 
00799 namespace ros
00800 {
00801 namespace message_operations
00802 {
00803 
00804 template<class ContainerAllocator>
00805 struct Printer< ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> >
00806 {
00807   template<typename Stream> static void stream(Stream& s, const std::string& indent, const  ::object_manipulation_msgs::ReactiveGraspAction_<ContainerAllocator> & v) 
00808   {
00809     s << indent << "action_goal: ";
00810 s << std::endl;
00811     Printer< ::object_manipulation_msgs::ReactiveGraspActionGoal_<ContainerAllocator> >::stream(s, indent + "  ", v.action_goal);
00812     s << indent << "action_result: ";
00813 s << std::endl;
00814     Printer< ::object_manipulation_msgs::ReactiveGraspActionResult_<ContainerAllocator> >::stream(s, indent + "  ", v.action_result);
00815     s << indent << "action_feedback: ";
00816 s << std::endl;
00817     Printer< ::object_manipulation_msgs::ReactiveGraspActionFeedback_<ContainerAllocator> >::stream(s, indent + "  ", v.action_feedback);
00818   }
00819 };
00820 
00821 
00822 } // namespace message_operations
00823 } // namespace ros
00824 
00825 #endif // OBJECT_MANIPULATION_MSGS_MESSAGE_REACTIVEGRASPACTION_H
00826 


object_manipulation_msgs
Author(s): Matei Ciocarlie
autogenerated on Mon Oct 6 2014 02:58:12