Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add support for deploying an experiment to an existing ROS network #160

Closed
finger563 opened this issue Aug 8, 2017 · 0 comments
Closed

Comments

@finger563
Copy link
Member

If the user provides (in the configuration dialog) the ip address and port number of a running roscore, then we should not spawn a roscore and should instead point the newly deployed nodes to it. Then the stop experiment will automatically not find a node running roscore and will handle it fine.

This enables users to break up their experiments into long-running, stable components that can be left on the system and deployments containing component-under-test. It also allows deploying onto an already existing system and further mixing of ROSMOD and non-ROSMOD executables.

@finger563 finger563 added this to the Version 1.1.0 milestone Aug 8, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant