[Spawner] Allow parsing the parameter files parsed from spawner to controllers#3136
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #3136 +/- ##
==========================================
- Coverage 89.35% 89.34% -0.01%
==========================================
Files 158 158
Lines 19392 19441 +49
Branches 1573 1583 +10
==========================================
+ Hits 17327 17369 +42
- Misses 1419 1421 +2
- Partials 646 651 +5
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
I have to say that I find it mildly confusing that --ros-args --params-file <filename> != --param-file <filename>.
Maybe it would be worth mentioning explicitly, that --param-file can be replaced by --ros-args --params-file or more importantly that in a launchfile
arguments=[
"my_controller_name",
"--param-file",
PathSubstitution(FindPackageShare("my_config_pkg"))
/ "config"
/ "controllers.yaml",
],can be written as
parameters=[
ParameterFile(
PathSubstitution(FindPackageShare("my_config_pkg"))
/ "config"
/ "controllers.yaml",
),
],
arguments=[
"my_controller_name",
],Or maybe put more simply: Controller parameters can either be specified by loading a parameter file using --param file or through the spawner's ROS node parameters when running as a ROS node.
But this PR definitively solves my issue.
I'll try to update the docs tonight. However, I think it is better I don't say it generic that --param-file can be replaced by this, just because then when you try to load multiple controllers with multiple param files with some wildcard entries, it won't work. Thank you for testing it 👏🏾 |
a583699
into
ros-controls:master
Fixes #3135
Tested with ros-controls/ros2_control_demos#1079
@urfeex FYI