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

ActuatorStateInterface to be aggregator of multiple smaller interfaces? #2

Open
bmagyar opened this issue Mar 7, 2019 · 1 comment

Comments

@bmagyar
Copy link
Member

bmagyar commented Mar 7, 2019

Fully depicting what I mean by a UML:

actuatorstateinterface

This'd allow for one to actually implement the actuator state interface they want in their RobotHW while clients could specify only the interfaces they require from an actuator handle.

@bmagyar bmagyar changed the title ActuatorInterface to be aggregator of multiple smaller interfaces? ActuatorStateInterface to be aggregator of multiple smaller interfaces? Mar 7, 2019
@jordan-palacios
Copy link

jordan-palacios commented Mar 7, 2019

Great representation.

This is how I exactly how I envisioned the new ActuatorStateInterface (see #1). My concern is how we couple this with the JointStateInterface and Transmission.

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

No branches or pull requests

2 participants