Package for generic cartesian control of floating base robots. It includes a ROS-based front end, as well as a programmatic API that can be used inside a real-time loop.
We have recently considered the possibility to change the distal_link name on the fly in our Cartesian tasks. This creates a series of issues related on how we handle the tasks, topics names and so on.
In particular: the task distal_link at the moment is also the topic name which eventually may change if we implement the possibility to change it. This is not wanted of course.
A possible solution could be to use the task name as topic name.
Another point is to refactor a little the yaml creation so that sub tasks are particular types of tasks which refers to tasks that are already defined. Something like:
We have recently considered the possibility to change the
distal_link
name on the fly in our Cartesian tasks. This creates a series of issues related on how we handle the tasks, topics names and so on. In particular: the taskdistal_link
at the moment is also the topic name which eventually may change if we implement the possibility to change it. This is not wanted of course. A possible solution could be to use the task name as topic name.Another point is to refactor a little the yaml creation so that sub tasks are particular types of tasks which refers to tasks that are already defined. Something like: