Conversation
|
Ping @felixvd, can you handle the remaining Travis issues and finalizes this? |
felixvd
left a comment
There was a problem hiding this comment.
I forgot to submit this comment when I took a look a few weeks ago apparently.
| planning_scene_interface.applyAttachedCollisionObject(att_coll_object); | ||
|
|
||
| // Wait a bit for ROS things to initialize | ||
| ros::WallDuration(1.0).sleep(); |
There was a problem hiding this comment.
Sure this is unnecessary? I took it from another tutorial.
There was a problem hiding this comment.
Yes, it was probably needed before when addAttachedCollisionObject was used.
This is probably a leftover from before the apply* functions existed.
|
Sorry for the long wait. I couldn't focus on this because I have a deadline for a few papers to meet at the end of the month, but I was planning on making this a proper tutorial instead of a stub before merging. First half of July I hope! |
| return false; | ||
| } | ||
|
|
||
| void addCollisionObjects(moveit::planning_interface::PlanningSceneInterface& planning_scene_interface) |
There was a problem hiding this comment.
Could you maybe rename this function to setupCollisionObjects or prepareCollisionObjects instead to avoid name collision with the PSI functions?
Personally I would prefer setting up a vector of collision objects here instead of passing the PSI, but that's personal preference.
There was a problem hiding this comment.
I renamed it but kept the PSI as an argument, because the point is to keep the collision object definition inside the function.
| planning_scene_interface.applyCollisionObject(co); | ||
| co = cylinder; | ||
| co.operation = moveit_msgs::CollisionObject::ADD; | ||
| planning_scene_interface.applyCollisionObject(co); |
There was a problem hiding this comment.
Please use applyCollisionObjects here to perform the updates in one ROS service call.
| /********************************************************************* | ||
| * Software License Agreement (BSD License) | ||
| * | ||
| * Copyright (c) 2019, who? |
| * copyright notice, this list of conditions and the following | ||
| * disclaimer in the documentation and/or other materials provided | ||
| * with the distribution. | ||
| * * Neither the name of Willow Garage nor the names of its |
| ROS_INFO_STREAM("Attaching cylinder to robot."); | ||
| planning_scene_interface.applyAttachedCollisionObject(att_coll_object); | ||
|
|
||
| //--- |
There was a problem hiding this comment.
Especially since this is a tutorial, please add a lot more inline documentation
| planning_scene_interface.applyAttachedCollisionObject(att_coll_object); | ||
|
|
||
| //--- | ||
| int c; |
There was a problem hiding this comment.
please use full-word variable names
| //--- | ||
| int c; | ||
| tf2::Quaternion orientation, orientation2, orientation3; | ||
| geometry_msgs::PoseStamped ps, ps_0; |
| "\n11 to move to a certain point in space with end effector (for visualizing the subframe pose)" | ||
| "\n12 to move to a certain point in space with cylinder/tip "); | ||
| std::cin >> c; | ||
| if (c == 0) |
There was a problem hiding this comment.
not a big deal, but a switch statement would be best, right?
| Subframes Tutorial | ||
| ============================ | ||
|
|
||
| This is just to test the subframes in a easy to run format. |
There was a problem hiding this comment.
I'd be fine merging this tutorial as-is now (after addressing feedback), and improving it in the future when you have time. Please add note here that its a stub, though.
There was a problem hiding this comment.
Thanks for all the comments in a very rough file that wasn't meant to be in a PR yet :)
I would prefer to finish this up properly before merging it. Otherwise it won't really be displayable on the website at all. Give me a week or two until things cool down and I'll write up something proper.
There was a problem hiding this comment.
From many experiences, the statement "I'll get to it when things cool down" rarely happens, so even this would be better than nothing ;-)
|
True! I already have a newer local version though and a talk at Roscon JP
about this, so I'll push an update soon.
…On Fri, Jul 12, 2019, 06:31 Dave Coleman ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In doc/subframes/subframes_tutorial.rst
<#326 (comment)>
:
> @@ -0,0 +1,29 @@
+Subframes Tutorial
+============================
+
+This is just to test the subframes in a easy to run format.
From many experiences, the statement "I'll get to it when things cool
down" rarely happens, so even this would be better than nothing ;-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#326>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCTLOLJHJ3L6NLFJOQIZX3P66RBNANCNFSM4HN4VE6Q>
.
|
|
friendly ping @felixvd |
|
I addressed all the changes except the switch statement in this branch in my fork, but I don't know how to add it here. With these changes it should be an actual tutorial. Can you cherry-pick the two commits @rhaschke ? Otherwise I can do a PR from the other branch as well. I added a ~2 MB gif, but I can also send the video file for uploading to Youtube. You decide. |
|
Closed by #365 |

I cleaned @felixvd's initial tutorial for the new subframes feature a little bit to prepare it for inclusion into the main repo. Felix, please have a look.
This belongs to moveit/moveit#1439.