ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
![]() | 1 | initial version |
I just found out the answer to my problem. It is due to a very strange way these things work.
When I dump ALL the parameters
rosparam load dump4.yaml
I got the correct ways such as
keys_to_twist: {angular_scale: 0.4, linear_scale: 0.5}
but when I do rosparam load dump5.yaml
I got
{angular_scale: 0.4, linear_scale: 0.5}
so when I load this file, another set of parameters get added! So I have the original keys_to_twist/angular_scale
and another angular_scale
and therefore the correct values are not set in the parameters it should go.
the solution is to set the yaml file as
keys_to_twist: {angular_scale: 0.3, linear_scale: 0.6}
![]() | 2 | No.2 Revision |
I just found out the answer to my problem. It is due to a very strange way these things work.
When I dump ALL the parameters
rosparam load dump4.yaml
I got the correct ways such as
keys_to_twist: {angular_scale: 0.4, linear_scale: 0.5}
but when I do rosparam load dump5.yaml
I got
{angular_scale: 0.4, linear_scale: 0.5}
so when I load this file, another set of parameters get added! So I have the original keys_to_twist/angular_scale
and another angular_scale
and therefore the correct values are not set in the parameters it should go.
the solution is to set the yaml file as
keys_to_twist: {angular_scale: 0.3, linear_scale: 0.6}
The funny thing I found out even later is that the loading of parameters from a launch file does not work at all like this
If you load the parameters from a launch file you have to go again to
{angular_scale: 0.4, linear_scale: 0.5}
otherwise you would have two times the "key_to_twist" part.