-
Notifications
You must be signed in to change notification settings - Fork 89
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
FetchIt Challenge Package addition and minor melodic Moveit Fix #32
Conversation
@@ -151,7 +151,7 @@ def updateScene(self): | |||
self.scene.addSolidPrimitive(obj.object.name, | |||
obj.object.primitives[0], | |||
obj.object.primitive_poses[0], | |||
wait = False) | |||
use_service = False) |
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.
same comment as on #26 - I think you actually want to just remove the "wait = False" -- the new service interface is quite speedy and very reliable (unlike the old "wait for sync").
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.
I dont quite get you there. So you mean that its not necessary to indicate the
use_service = False
? We just need to remove the wait?
And as for the addition of the fetchit_challenge package, everything ok there?
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.
You just need to remove the line, which will use_service=True
http://docs.ros.org/kinetic/api/moveit_python/html/classmoveit__python_1_1planning__scene__interface_1_1PlanningSceneInterface.html#a72a7f448769da906ae689420092ce4c4
The addition of the fetchit_challenge looks good enough for as the first pass, the diff is too large to really see in GitHub.
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.
Just the same thing pointed out by @mikeferguson.
GitHub doesn't support multi-line suggestions so if you want to use the web interface to accept the changes for this version- I'm sure the next time someone edits the files properly pep8 will likely complain about the )
being all alone on a line.
The tables will be (approx)
I don’t know the exact surface colour yet. They’re currently particle board. So wood is close enough... but the final version will likely be white. The tables will be filled in, with a hard material (so they can be used for navigation) and on that material will be the sponsor logos. I will upload a photo of the first prototype |
This was one of our old demo warehouse shelves. I've cut it down to match the height of the Schunk machine. They can be disassembled and then they flat-pack for shipping, so we will use the same shelves in Montreal. We don't have hard covers for the sides yet, but lets assume they'll look similar to the Schunk machine. They will be made out of some stiff material (likely foam-core board) and attach sides with "velcro". I just took a photo of the back to show that it was a shelf. But the version for gazebo does not need to model the inside, it can simply be a solid rectangle. |
Oh sorry didnt get this update for some reason. Ok so let me get this straight: I'll start working on that and commit the changes as soon as possible |
Yes, don't worry about the actual sponsor logo matching, just make the tables rectangles for now. The tables being solid, instead of having one thin leg in the middle, or four legs on in the corners, will help make it easier to use them for the laser scanners, and useful for navigation and alignment with the tables. |
I've created new models for the tables based on the specifications given and tested also that the pick and place script demo ;). The logos are just place holders, we afterward can place other logos there if it's needed. Any other suggestion? As soon as we merge this branch I'll generate a new ROSject using the official fetch repositories with the latest changes, and from there we can keep on improving ;). |
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.
LGTM. Thanks!
So, I did the review earlier it looks fine to merge and then we can fix the issues in future PRs. But, the package.xml is missing some dependencies, and the CMakeLists.txt might not be installing meshes in the correct locations, when I ran it on my test machine, which has a bare ros installation, I the new tables had no surfaces, but they were there. Also in future versions, and in the real environment we'll need to settle on colours. |
…in bin and added dependencies
Colour changed to a complementary colour, in theory it should make it as easier as it can get to differenciate between the bolts and the bin. I downloaded the code and compiled and it seemed to work for me. In theory the tag in package.xml in the fetchit_challenge package should do the trick to allow the system to find the models:
So we can debug in another pull request what's happening there. I also added dependencies to the fetchit_challenge package. We should also check in another PR, the compilation of this whole repo because it needs to have precompiled the grasping_msgs package before compiling which is some of a inconveniece. But yeah, lets merge and see what we organise tasks for debugging those issues |
This reverts commit 674f281. See PR ZebraDevs#26 and PR ZebraDevs#32
Here we add the latest version of the files for the FetchIt! Challenge. All the models, environments and launches needed. We also added a minor fix for moveit of the melodic version that has different input parameters.