ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2014-07-28 08:40:17 -0500 | received badge | ● Famous Question (source) |
2014-07-27 15:00:08 -0500 | received badge | ● Notable Question (source) |
2014-07-27 14:27:25 -0500 | received badge | ● Famous Question (source) |
2014-07-25 09:41:22 -0500 | received badge | ● Popular Question (source) |
2014-07-25 02:18:35 -0500 | asked a question | How to compile ROS messages "by hand"? In our project, we use Now I need a custom message type and wonder, how the language-specific code is compiled from a |
2014-06-02 04:25:08 -0500 | received badge | ● Notable Question (source) |
2014-06-02 01:14:57 -0500 | received badge | ● Student (source) |
2014-06-02 00:57:04 -0500 | commented answer | How to implement the "pipeline pattern" in ROS? Thank you, this makes it very clear! |
2014-06-02 00:56:03 -0500 | received badge | ● Scholar (source) |
2014-05-30 03:44:49 -0500 | received badge | ● Popular Question (source) |
2014-05-29 10:54:11 -0500 | received badge | ● Editor (source) |
2014-05-29 10:50:33 -0500 | asked a question | How to implement the "pipeline pattern" in ROS? Hi, as far as I understand in ROS the connections between nodes are implicitely given by topic names. So for example node A provides "camera_image", and node B subscribes to "camera_image", and provides "edge_detections". Now, A and B are connected. The names are hard-coded in the nodes source files. But what if I want to install a node C between A and B, which takes "camera_image", provides "black_and_white_image"? Node B now should no longer subscribe to "camera_image", but to "black_and_white_image". Of course I don't want to change the source of B. Should I pass the topic name as command line argument? What is my fundamental misunderstanding here? |