ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2020-04-03 15:05:50 -0500 | received badge | ● Nice Question (source) |
2020-02-08 07:55:53 -0500 | received badge | ● Guru (source) |
2020-02-08 07:55:53 -0500 | received badge | ● Great Answer (source) |
2019-03-13 10:43:16 -0500 | received badge | ● Enlightened (source) |
2019-03-13 10:43:16 -0500 | received badge | ● Good Answer (source) |
2018-11-16 03:30:30 -0500 | received badge | ● Student (source) |
2018-03-23 06:44:38 -0500 | received badge | ● Nice Answer (source) |
2018-02-11 09:52:12 -0500 | received badge | ● Famous Question (source) |
2018-02-11 09:52:12 -0500 | received badge | ● Notable Question (source) |
2018-02-11 09:52:12 -0500 | received badge | ● Popular Question (source) |
2018-01-28 04:26:25 -0500 | received badge | ● Famous Question (source) |
2017-04-07 09:20:55 -0500 | received badge | ● Famous Question (source) |
2017-02-17 08:16:30 -0500 | received badge | ● Notable Question (source) |
2017-02-12 06:34:46 -0500 | received badge | ● Teacher (source) |
2016-07-27 21:25:56 -0500 | received badge | ● Notable Question (source) |
2015-12-04 00:31:49 -0500 | received badge | ● Popular Question (source) |
2015-12-03 12:49:53 -0500 | asked a question | yaml serialization for messages Is it possible to serialize ROS messages to and from YAML files directly? I want to save some config data and a piece of this data is a geometry_msgs/Pose data type. I realized that you can publish to a node using YAML syntax in the command line and so I know they are serializable I just don't know of an API for doing so in C++. |
2015-11-06 07:24:33 -0500 | received badge | ● Enthusiast |
2015-10-29 14:47:32 -0500 | received badge | ● Popular Question (source) |
2015-10-29 13:54:07 -0500 | received badge | ● Scholar (source) |
2015-10-29 13:53:58 -0500 | received badge | ● Supporter (source) |
2015-10-29 13:53:54 -0500 | commented answer | Get apt-get dependencies given rosdep key Thanks for explaining the difference between these commands. The rosdep documentation is rather slim and vague. |
2015-10-29 13:53:30 -0500 | commented answer | Get apt-get dependencies given rosdep key Exactly what I needed. Thanks! Recursion can be done using a simple bash script. |
2015-10-29 12:46:52 -0500 | asked a question | Get apt-get dependencies given rosdep key So I know using i.e the Is there a command that will return |
2015-10-08 06:50:50 -0500 | answered a question | How to publish a ROS msg on Linux terminal The ROS wiki gives this as an answer example. Depending on your message type you can simply follow the pattern given above; in which case you won't need |
2015-10-07 13:44:52 -0500 | asked a question | Generic Ros Service Clients I'm currently trying to use the topic_tools/mux node to multiplex multiple topics using the same selector (which is implemented as a ROS service). Now, I've recently discovered that ROS Services cannot be created with the same name, and if they are then the most recent Services gets created and the ones before are destroyed (without notification to the user by the way which is not good in the sense that it may not be intended by the user). So then, another solution would be to create the multiplexer each with a different service name. Then I would create another node that broadcasted to these services. Now, I would like to make this generic (as it would be very useful for later use) such that this node would:
My current problem is that I can't find a way to determine the Service type based on the given qualified service name using the current roscpp API. I may be missing something however, it appears that the only way to create a ROS Service client is to know the Request and Respond types first; there is no generic wrapper around this so that applications - such as mine - can forward client requests to services without regard to the type. This seems to be possible as I would assume that there is some class that the roscpp API is using to bind a service's name with its service type - that and the topic_tools/mux node seems to be able to do this for topics (that is forwarding the messages from one topic to another without regard to the topic message types). And though services are different than topics they both seem to be based on message types. |