class documentation
        
        
        Undocumented
| Method | __init__ | 
    Constructor. Any message fields that are implicitly/explicitly set to None will be assigned a default value. The recommend use is keyword arguments as this is more robust to future message changes. You cannot mix in-order arguments and keyword arguments. | 
| Method | deserialize | 
    unpack serialized message in str into this message instance :param str: byte array of serialized message, str | 
| Method | deserialize | 
    unpack serialized message in str into this message instance using numpy for array types :param str: byte array of serialized message, str :param numpy: numpy python module | 
| Method | serialize | 
    serialize message into buffer :param buff: buffer, StringIO | 
| Method | serialize | 
    serialize message with numpy array types into buffer :param buff: buffer, StringIO :param numpy: numpy python module | 
| Class Variable | __slots__ | 
    Undocumented | 
| Instance Variable | allow | 
    Undocumented | 
| Instance Variable | allowed | 
    Undocumented | 
| Instance Variable | allowed | 
    Undocumented | 
| Instance Variable | attached | 
    Undocumented | 
| Instance Variable | end | 
    Undocumented | 
| Instance Variable | group | 
    Undocumented | 
| Instance Variable | minimize | 
    Undocumented | 
| Instance Variable | path | 
    Undocumented | 
| Instance Variable | planner | 
    Undocumented | 
| Instance Variable | planning | 
    Undocumented | 
| Instance Variable | possible | 
    Undocumented | 
| Instance Variable | support | 
    Undocumented | 
| Instance Variable | target | 
    Undocumented | 
| Method | _get | 
    internal API method | 
| Class Variable | _full | 
    Undocumented | 
| Class Variable | _has | 
    Undocumented | 
| Class Variable | _md5sum | 
    Undocumented | 
| Class Variable | _slot | 
    Undocumented | 
| Class Variable | _type | 
    Undocumented | 
Constructor. Any message fields that are implicitly/explicitly set to None will be assigned a default value. The recommend use is keyword arguments as this is more robust to future message changes. You cannot mix in-order arguments and keyword arguments.
- The available fields are:
 - target_name,group_name,end_effector,possible_grasps,support_surface_name,allow_gripper_support_collision,attached_object_touch_links,minimize_object_distance,path_constraints,planner_id,allowed_touch_objects,allowed_planning_time,planning_options
 
to set specific fields.
| Parameters | |
| *args | complete set of field values, in .msg order | 
| **kwds | use keyword arguments corresponding to message field names | 
unpack serialized message in str into this message instance :param str: byte array of serialized message, str
unpack serialized message in str into this message instance using numpy for array types :param str: byte array of serialized message, str :param numpy: numpy python module