Skip to content

Adding ROS namespace manipulation operations#141

Open
meyerj wants to merge 7 commits intoorocos:toolchain-2.9from
jhu-lcsr-forks:ros-ns-manip
Open

Adding ROS namespace manipulation operations#141
meyerj wants to merge 7 commits intoorocos:toolchain-2.9from
jhu-lcsr-forks:ros-ns-manip

Conversation

@meyerj
Copy link
Member

@meyerj meyerj commented Jan 6, 2020

Copy of jhu-lcsr-forks#59 by @jbohren:

This aims to resolve issues mentioned in #35

This allows us to do the following (in ops for example):

ros.setNS("/controllers/left")
// call function which creates other components
// all ROS names will be scoped to "/controllers/left"

ros.setNS("/controllers/right")
// call same function which creates other components
// all ROS names will be scoped to "/controllers/right"

ros.resetNS()

Or, if you have multiple deployers, you could run this code in each of them, without having ROS namespace collisions (unless you do something with an absolute namespace):

ros.pushNS("deployer_1")
// create a bunch of components
// all ROS names will be scoped to "deployer_1"
ros.popNS()

@smits @meyerj @konradb3 @cpaxton What do you guys think?

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.

2 participants