-
Notifications
You must be signed in to change notification settings - Fork 310
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
Set chained controller interfaces as available for activated controllers #1098
Set chained controller interfaces as available for activated controllers #1098
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #1098 +/- ##
==========================================
+ Coverage 47.65% 47.79% +0.14%
==========================================
Files 40 40
Lines 3448 3450 +2
Branches 1867 1869 +2
==========================================
+ Hits 1643 1649 +6
+ Misses 480 457 -23
- Partials 1325 1344 +19
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as far as I understand the chainable controllers.
This pull request is in conflict. Could you fix it @saikishor? |
10bc21c
to
00f29cc
Compare
This pull request is in conflict. Could you fix it @saikishor? |
94361ba
to
4ed6bf8
Compare
@bmagyar I think the rebase I've done after the conflict has invalidated the review of @destogl and @christophfroehlich. In this case, do they have to review again? or what's the exact process to follow? Thank you |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LstillGTM, and please don't forget to update docs with details on that. E.g. here: https://control.ros.org/master/doc/ros2_control/controller_manager/doc/controller_chaining.html#debugging-outputs
@christophfroehlich I've updated the docs now. Please review and let me know your opinion. Thank you |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
333e0bf
This PR addresses the issue with the current
list_hardware_interfaces
service which lists the interfaces exposed by the chainable controllers asunavailable
instead ofavailable
until they are in chained modeCurrent behavior:
unavailable
andunclaimed
unavailable
andunclaimed
available
andclaimed
New behavior:
unavailable
andunclaimed
available
butunclaimed
available
andclaimed