-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clear table #9
Clear table #9
Conversation
…_16UC1, in addition to depth/image of type CV_32FC1
…that a full data set is received
…uster service to determine extent of segmented object
…veit fails quite often
… actionlib interface rather than moveit_commander
… an actual bounding box, rather than an approximation. seems to work better, so I am committing, but it needs to be cleaned up a ton before pushing to master
…ok that was used to develop it.
…it now lives with the simple_robot_control package
…it now lives with the simple_robot_control package
…o the clear_table state machine
return 'segmentation_failed' | ||
|
||
userdata.object_points = points | ||
userdata.object_name = 'obj1' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this just a transient name or what does it happen if we assert many objects?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We only segment one object at a time, so it's a temporary name.
|
||
locations.append(pl) | ||
return locations | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general it would be great if frame_ids and joint_names would be parametrized and if place locations came from a config file
We can convert this into an issue!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue #13
To me this looks good, if possible I'd try it out on my account. Mostly parametrization issues which we should convert into the repository issue. |
…; adding loop to try repeatedly to get kinect data rather than reporting failure instantly (takes time for assemble_kinect to get first dataset)
…ther tahn my local copy of it
…s to explain magic number
A way-too-big branch, with lots of changes.
This is what I just demoed to D with the fully-automated table clearing (using ORK) and the shared autonomy table clearing using Grabcut.
For the ipython notebooks, it'll be easier to look review them here:
http://nbviewer.ipython.org/github/SharedAutonomyToolkit/shared_autonomy_perception/blob/clear_table/random_snippets/clear_table.ipynb
http://nbviewer.ipython.org/github/SharedAutonomyToolkit/shared_autonomy_perception/blob/clear_table/random_snippets/moveit_pick.ipynb
Dependencies:
git clone [email protected]:bosch-ros-pkg/cluster_grasp_planner.git -b hydro-devel
apt-get install ros-hydro-moveit*