-
Notifications
You must be signed in to change notification settings - Fork 580
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
srdf publisher node #2682
srdf publisher node #2682
Conversation
dc86a47
to
7a5d0ad
Compare
5f6d030
to
58fd791
Compare
for (auto const& parameter : parameters) | ||
{ | ||
if (parameter.get_name() == "robot_description_semantic") |
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.
Can there be multiple robot_description_semantic
parameter? or should if the get_name( ) == then should this function return?
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.
Adding a break here instead of a return because we need to return success through the result for now.
rcl_interfaces::msg::SetParametersResult result; | ||
result.successful = true; | ||
return result; |
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.
is this callback always suppose to return success or should it return success in the if, and false otherwise?
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.
I'm adding a comment about this. In humble the only callback we have for parameters is the validation one. You may ask, why don't I validate this is a valid srdf? I considered that until I realized the srdf parser requires a urdf as a parameter which I don't want to make this node get the urdf just to validate the srdf. This node is just a relay anyway and if you use it to set an invalid srdf the nodes that depend on it will blow up.
After humble is eol we can use add_post_set_parameters_callback which is only in rolling now. I'm adding a comment explaining this.
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2682 +/- ##
==========================================
- Coverage 50.74% 41.50% -9.24%
==========================================
Files 392 691 +299
Lines 32553 56255 +23702
Branches 0 7288 +7288
==========================================
+ Hits 16517 23341 +6824
- Misses 16036 32752 +16716
- Partials 0 162 +162 ☔ View full report in Codecov by Sentry. |
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.
thanks for the clarification comment
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.
Nice work! Should we add that node to the move_group launch files?
This pull request is in conflict. Could you fix it @tylerjw? |
7d4be87
to
1662647
Compare
Description
Similar to how robot_state_publisher publishes a string to
/robot_description
for the URDF this publishes to/robot_description_semantic
controlled by a parameter of the same name.MoveIt already subscribes to the topic
/robot_description_semantic,
so this node could be useful in a system using MoveIt.