-
Notifications
You must be signed in to change notification settings - Fork 493
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
Fix psm/servo parameter conflict #266
Fix psm/servo parameter conflict #266
Conversation
Codecov Report
@@ Coverage Diff @@
## master #266 +/- ##
==========================================
+ Coverage 46.63% 47.87% +1.24%
==========================================
Files 122 155 +33
Lines 12740 15750 +3010
==========================================
+ Hits 5941 7541 +1600
- Misses 6799 8209 +1410
Continue to review full report at Codecov.
|
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.
In general not sure how to make different things sharing a node handle the parameters nicely, but using the private node seems reasonable to me.
Thanks for catching and fixing the intra-process communications in moveit_servo!
@@ -73,7 +73,8 @@ def generate_servo_test_description(*args, | |||
package='moveit_servo', | |||
plugin='moveit_servo::ServoServer', | |||
name='servo_server', | |||
parameters=[servo_params, robot_description, robot_description_semantic]) | |||
parameters=[servo_params, robot_description, robot_description_semantic], | |||
extra_arguments=[{'use_intra_process_comm': True}]) |
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.
Oops! Definitely meant to do this for the tests and forgot, thanks Henning!
Sorry to comment on this closed issue. But how should one set the parameters moved to the private node? Shouldn't we set these values to the values of the current Node when declaring them? |
All parameters are triggering the parameter callback in the PSM node, which results in the PSM rejecting parameters from moveit_servo. I'm not sure if this fix is a good long-term solution, but for now exclusive parameters in the PSM are declared for the private node. Eventually, we might want to reimplement the PSM as a composable node which would allow a cleaner separation.
Additionally, 0a98d55 should fix some warnings with the moveit_servo tests, @AdamPettinger does this make sense to you?