Skip to content
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

OpenSoT::tasks::velocity::Cartesian should have a default id if possible #15

Closed
arocchi opened this issue Oct 14, 2014 · 0 comments
Closed

Comments

@arocchi
Copy link

arocchi commented Oct 14, 2014

In case we control a distal link wrt a base link (i.e., not trying to control an arbitrary point on a body, but using a named frame) the name for the task could be:
6d::base_link::distal_link for pose control
3p::base_link::distal_link for position control
3o::base_link::distal_link for orientation control

In case issue #11 gets implemented by naming a point location on a link first, the automatic naming can be applied always.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants