Skip to content

[multirobot - Part2] Add namespacing to nav stack#1147

Merged
orduno merged 1 commit intomasterfrom
multi-robot/namespace_stack
Sep 25, 2019
Merged

[multirobot - Part2] Add namespacing to nav stack#1147
orduno merged 1 commit intomasterfrom
multi-robot/namespace_stack

Conversation

@orduno
Copy link
Copy Markdown
Contributor

@orduno orduno commented Sep 20, 2019


Basic Info

Info Please fill out this column
Ticket(s) this addresses #
Primary OS tested on Ubuntu 18.04
Robotic platform tested on Gazebo simulation of TB3

Description of contribution in a few bullet points

Extends #1146 adding capability of namespacing the stack (nodes and topics).

  • Extending rewritten_yaml to also replace keys
  • Adding a node launcher that puts a condition to applying the remappings.
  • Add namespacing to launch files
  • Update namespace of costmap. Planner and controller now pass the correct namespace to use.

Copy link
Copy Markdown
Member

@SteveMacenski SteveMacenski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Side note there appears to be a rebasing problem, I'm seeing some other PRs stuff leaking into the github view.

@orduno
Copy link
Copy Markdown
Contributor Author

orduno commented Sep 22, 2019

Side note there appears to be a rebasing problem, I'm seeing some other PRs stuff leaking into the github view.

@SteveMacenski Yes, I'm working on rebasing with master and it's taking longer than I anticipated. Some recent change in nav2 breaks my multi-robot example and I haven't found the source of the problem. Will let you know once I'm done so you can continue reviewing.

@SteveMacenski
Copy link
Copy Markdown
Member

I also wouldn't spend too much time trying to fix just the rebase, what's an unideal commit or two between colleagues 😉

@orduno orduno force-pushed the multi-robot/spawn_robot branch from 072bcfc to f592145 Compare September 23, 2019 20:20
@orduno orduno force-pushed the multi-robot/namespace_stack branch from be4a43f to eebdc8a Compare September 23, 2019 20:21
@orduno
Copy link
Copy Markdown
Contributor Author

orduno commented Sep 24, 2019

I agree on an upstream change to add a prefix to the tf broadcaster/listener. The broadcaster could even take the namespace off the node if not adding a separate constructor argument.

@bpwilcox Prefixing the transforms was actually previously supported and deprecated.

There is an ongoing discussion on a replacement:
ros/geometry2#32

@orduno orduno force-pushed the multi-robot/spawn_robot branch from 03f84fa to 9cb8638 Compare September 25, 2019 21:45
@orduno orduno changed the base branch from multi-robot/spawn_robot to master September 25, 2019 21:48
Adding a node launcher that put a condition to
applying the remappings.
Add namespacing of launch files
Update namespace of costmap and passing of correct
namespace by planner & controller.
@orduno orduno force-pushed the multi-robot/namespace_stack branch from eebdc8a to 0dc160d Compare September 25, 2019 21:58
@orduno orduno merged commit 226f06c into master Sep 25, 2019
@SteveMacenski SteveMacenski deleted the multi-robot/namespace_stack branch September 25, 2019 22:06
@mkhansenbot
Copy link
Copy Markdown
Collaborator

It looks like this PR introduced an uncrustify failure that broke the build on master. Can you submit a PR to fix? The details are here:
https://travis-ci.org/ros-planning/navigation2/builds/589669928

savalena pushed a commit to savalena/navigation2 that referenced this pull request Jul 5, 2024
* Extending `rewritten_yaml` to also replace keys.

* Adding a node launcher that puts a condition to
applying the remappings.

* Add namespacing of launch files.

* Update namespace of costmap and passing of correct
namespace by planner & controller.
danmartinez78 pushed a commit to danmartinez78/shadowhound that referenced this pull request Oct 26, 2025
- Nav2 bringup_launch.py already includes TF remappings internally
- Remappings keep /tf and /tf_static global while frames remain namespaced
- This is the correct ROS2 multi-robot architecture (not a workaround)
- Issue: Nav2 nodes still subscribing to /robot0/tf instead of /tf
- Need to investigate why Nav2's built-in remappings aren't working

References:
- ros/geometry2#32
- ros-navigation/navigation2#1147
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 this pull request may close these issues.

4 participants