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

JointName Proposal #7

Open
xwavex opened this issue Jun 21, 2016 · 2 comments
Open

JointName Proposal #7

xwavex opened this issue Jun 21, 2016 · 2 comments

Comments

@xwavex
Copy link
Collaborator

xwavex commented Jun 21, 2016

Proposed API calls

setForce(joint_names[i], torque[i]);

joints[joint_names[i]]->setForce(torque[i]);

Requirements:

  • Iterating over a list of joint names and fitting it in a specific format to another library
  • Know the format of the vector you get from the simulation
  • Format of vector should be defined in preface based on SRDF
  • Address the vector with the joint names in case of using Gazebo's API
  • Use a common IF in the robot simulation components as well as in the view components
  • Minimum configuration overhead in .ops
  • Take care that only valid joints can be addressed in certain scopes (perhaps retrieve joints depending on the "used" kinematic chain?)
@xwavex
Copy link
Collaborator Author

xwavex commented Jun 21, 2016

Read specific std::vector<std::string> from SRDF for a particular kinematic chain. The order in this case specifies the associated index.

I guess there is no need to include the joint names in a particular data type...

@xwavex
Copy link
Collaborator Author

xwavex commented Jun 22, 2016

TODO provide sequence diagram with interface definition

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

1 participant