Stateless Client and Planning Backend
No due date
100% complete
Instead of a state-ful planner where tools and collision objects are 'added' or 'removed', a state-less planner will be one that can keep track of its internal states and present an API that does not make any assumption to "Fixed Collision Objects", "Attached Collision Objects", "Attached Tools", "Current Robot Position" etc.
There are no open issues in this milestone.
Add issues to milestones to help organize your work for a particular release or project.
Create new issueOr find and add issues with no milestone in this repo.