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