Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Planning for moving the PR2 base with MoveIt! #375
Overview of your issue here.
I would like to use MoveIt for motion planning of the PR2 (only moving the base in a scene).
I followed the tutorial on moveit site to use the motion_planning_interface to plan the movement of an arm of pr2 but I can not figure out how to implement the planning of the base movement.
I found this thread planning move base but I have many doubts about how this solution was implemented.
It is possible also extract the path generated by moveit through OMPL and not the entire trajectory?
Last question, there is a way to send moveit an already created octomap instead of PointCloud generated by the robot's sensors?
@Tenrampi please do not double post both here and on the mailing list, and try to keep questions separate: your octomap question is a very different topic of mobile base planning
There has not been much work with mobile base planning and MoveIt!. It is possible with customization and extra development, but not something that is easy to do out of the box AFAIK
Sorry for the double post, I did not know that they were connected! I'm asking for the planning of the basic movement because running the demo of pr2 contained in the folder pr2_moveit_config you can make the planning of the movement of the base by selecting the base as a group, while I would like to conduct the planning of the base movement but using various interfaces like in tutorials on moveit site, so without having to use the present GUI rviz but using the scheduling parameters within the code. the problem is that from the tutorial I do not understand how to plan the movement of the base being the tutorial totally focused by the arm movements.
Hi everybody! coming here after using the non-standard way of planning alongwith base (i.e. modelling with 2prismatic-1revolute joint) and thought this might be the place to put this.
I am trying to sort out how would planning for base should be implemented. From my current understanding, I imagine it requires modifying/extending Robot Model, Robot State and Kinematic Base/Plugin interfaces for differential kinematics for a special group case that is the base.
If somebody has an idea, insights or ideally a rough roadmap of how things should be implemented within MoveIt, it would be good to have it somewhere. (in other words to know if I am able to attempt that).