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

Fixed / Floating frame #11

Open
ahoarau opened this issue Sep 20, 2018 · 2 comments
Open

Fixed / Floating frame #11

ahoarau opened this issue Sep 20, 2018 · 2 comments
Labels

Comments

@ahoarau
Copy link
Member

ahoarau commented Sep 20, 2018

I'm thinking about having 2 functions in orca::robot::RobotModel to differenciate fixed base and floating robots:

robot->setFixedBaseFrame("base_of_the_manipulator"); // robot is fixed somewhere in the world.
// and
robot->setFloatingFrame("pelvis"); // robot can move in the world

@rlober , @iadev , @vpadois ?

@iadev
Copy link
Collaborator

iadev commented Sep 20, 2018

TL;DR: Yes

To me this is much clearer indeed than inferring it from whether or not tasks are defined on 6+ndof.
Question though: what's the point of explicitly specifying which frame is the base ?
Is that just to have a "default" base frame for all tasks ?

@ahoarau
Copy link
Member Author

ahoarau commented Sep 20, 2018

Is that just to have a "default" base frame for all tasks ?

That and when setting the robot state at every timestep, you need to specify the World to Base transform (and twist).

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

No branches or pull requests

2 participants