-
Notifications
You must be signed in to change notification settings - Fork 150
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
add topicname args to navigation launch #137
add topicname args to navigation launch #137
Conversation
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.
SRTM
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.
SRTM
@@ -11,6 +11,12 @@ | |||
<arg name="move_base_include" default="$(find fetch_navigation)/launch/include/move_base.launch.xml" /> | |||
<arg name="amcl_include" default="$(find fetch_navigation)/launch/include/amcl.launch.xml" /> | |||
|
|||
<!-- set topics --> | |||
<arg name="scan_topic" default="base_scan" /> |
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.
remove tab
@@ -11,6 +11,12 @@ | |||
<arg name="move_base_include" default="$(find fetch_navigation)/launch/include/move_base.launch.xml" /> | |||
<arg name="amcl_include" default="$(find fetch_navigation)/launch/include/amcl.launch.xml" /> | |||
|
|||
<!-- set topics --> | |||
<arg name="scan_topic" default="base_scan" /> |
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.
remove tab
A question for others in general (incl. @cjds @narora1 ): Does it make sense to be parameterizing everything in the base launch files? Where I'm coming from: My impression is that the launch files originally captured best practices (5 years ago), but I'm not personally familiar with other robots' equivalent launch files or changes in practice in the past 5 years. I am wondering if these changes (including similar in previous PRs) match the spirit of current best/common practices. That said, this generally LGTM 👍 . I just could imagine a fully parameterized launch file being a bit less readable... |
@erelson I think it makes sense that as you have more people doing more use-cases, you'll end up with a few more parameters. I can certainly understand scan and odom getting parameterized (since you might install a better/different set of sensors). Parameterizing the default map seems kind of unnecessary (I'm not aware of any other robot platform that uses a default map not named "map" - it's pretty much the standard). Same goes for cmd_vel - while different robots may have a different name for this, the entire fetch/freight research system uses a consistent naming convention throughout the real robot config (that's apps like nav here, as well as drivers/bringup) and the simulation. |
In our lab, |
kindly ping. |
Thanks for the ping. Merged both indigo and melodic PRs 👍 |
I have added topic name arguments to navigation launch files so that navigation topics can be remapped to other topics. ( like remapping /odom to /odom_visual )