Skip to content
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

rosparam with inline yaml and argument substitution not working #83

Closed
matawed opened this issue May 25, 2019 · 1 comment · Fixed by #85
Closed

rosparam with inline yaml and argument substitution not working #83

matawed opened this issue May 25, 2019 · 1 comment · Fixed by #85

Comments

@matawed
Copy link

matawed commented May 25, 2019

problem

mon launch reports Substitution error: $(arg traffic_topic_name_generic ): Unknown arg

input

for the following launch file:

<launch>
    <!--****************************************
    **********   Program Parameters   **********
    *****************************************-->

    <arg name="traffic_topic_name_generic" default="example_name"/>


    <!--*********************************
    **********   Launch Node   **********
    **********************************-->
        <node pkg="package" type="type" name="name" output="screen" >
            <rosparam param="topic_names" subst_value="true" command="load">
                traffic_topic_name_generic:        $(arg traffic_topic_name_generic       )
            </rosparam>
        </node>
</launch>

workaround

It seems that the trailing whitespaces after the arg name cause the problem, since the following line works
traffic_topic_name_generic: $(arg traffic_topic_name_generic)

rosmon version

2.0.2 ubuntu 18.04. ros melodic

@xqms
Copy link
Owner

xqms commented May 27, 2019

Thanks for the report, I'll look into it. I guess this is one of the cases were roslaunch is more lenient than the spec, so we'll have to adapt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants