-
Notifications
You must be signed in to change notification settings - Fork 0
WIP Flexible actuator interfaces #6
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
base: melodic-devel
Are you sure you want to change the base?
Conversation
Not at all. In fact was kind of expected given the nature of the changes required. |
|
@jordan-palacios it was super tricky to figure out the right way of these changes. Please have a look, but keep in mind I'm not done yet |
… from base classes
…missions only use the relevant interface in relevant functions
e1262ec to
da86026
Compare
|
I've rebased this branch to the latest melodic-devel to get Travis up'n'running |
da86026 to
12c86ee
Compare
5cabd14 to
373a871
Compare
373a871 to
543d2ac
Compare
06c1058 to
088bb38
Compare
Supersedes #3 .
Note that these changes break API for all transmissions. Please let me know if you think this is a show-stopper.
Todo list includes:
ActuatorDatatemplated on interface typesActuatorStateHandletemplated on interface typesTransmissionHandlewill become templated on the components ofActuatorData, instead of holding a fixedActuatorData actuator_data_;field. That will come with new tests.ActuatorStateHandlein business logic, ideally should be defined / used by RobotHW.ActuatorData((likewise forJointDatain the future).