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

Adding ROS namespace manipulation operations #59

Closed
wants to merge 2 commits into from

Conversation

jbohren
Copy link
Member

@jbohren jbohren commented Oct 8, 2014

This aims to resolve issues mentioned in orocos#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?


This change is Reviewable

Conflicts resolved:
	rtt_ros/src/rtt_ros_service.cpp
@ahoarau
Copy link

ahoarau commented Jul 21, 2016

@meyerj To my opinion, this would be a very useful addition to rtt_ros.

@meyerj
Copy link

meyerj commented Jan 6, 2020

Re-opened as orocos#141.

@meyerj meyerj closed this Jan 6, 2020
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.

3 participants