-
Notifications
You must be signed in to change notification settings - Fork 47
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
Support for multiple machines #26
Comments
Support for multiple machines is currently not planned. I'd be happy to receive PRs, though. rosmon is mostly used in our lab in multi-master systems connected using nimbro_network - over lossy / intermittent WiFi networks. In this situation, central launching is not very useful, that's why we did not implement it so far. We usually Do you have a particular use case in mind? Do you start multiple robots at once? Or do you just distribute nodes over machines inside one robot? I'm just curious ;-) |
Typically, in our lab we distribute nodes over multiple machines, so that each machine runs a set of functionalities of the robot. For example, one machine takes care of reading from the sensors, another one processes the data, etc. This allows to distribute computational resources, but also to avoid that changing something on a central machine might affect some basic functionalities of the robot. Thus, we run the robot by I like rosmon :) so I'd like to put some effort to make it work over multiple machines. |
I see. In that case, it might be as easy as putting |
or you could try node_manager_fkie |
At our lab, we would like to use your tool to monitor ROS on multiple machines.
However, it doesn't look to be possible at the moment as the
<machine>
tag is not supported yet.Are you planning to keep developing the tool to make it work on multiple machines in the next future?
Otherwise, we may consider to implement this functionality ourselves.
If someone else is interested or planning to implement it, please comment here, so we can put some effort together and avoid to replicate the work.
Thanks!
The text was updated successfully, but these errors were encountered: