-
Notifications
You must be signed in to change notification settings - Fork 80
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
does this tool support "relay" mode? #71
Comments
Hi @asimay, |
hi, @mikaelarguedas , dear, yes. I used topic_tools before, and find your tools, topic_tools has "relay" mode, and I want to know your package has this kind of mode or not? because I need to defined this kind of mode across files. but 1 disadvantage of topic_tools relay mode is: it also copy the topic data, this will waste the resources of PC. |
Thanks for clarifying. It could be fairly easily implemented by providing a nodelet templated on the message type and taking input and output topic names as parameters (you can look at nodelet_mux.h or nodelet_throttle.h for examples of nodelets templated on message types. Though it is recommended to remap topics (if it makes sense in the case of your application) rather than subscribing and republishing them, this allow to avoid serialization/deserialization put as well as unnecessary copies. Please see ros/roscpp_core#31 for more information of cases where copies will be performed anyway. |
http://wiki.ros.org/cras_topic_tools provides a relay nodelet. The package is released, so simply |
does this tool support "relay" mode?
if not, and can you add it?
The text was updated successfully, but these errors were encountered: