Ask Your Question
0

Does the ros publisher publish in bytes?

asked 2013-05-27 15:56:40 -0500

aswin gravatar image

updated 2014-01-28 17:16:40 -0500

ngrennan gravatar image

Hi all, Following is a simple publishing example I copied from the ROS tutorials. Is msg transmitted over TCP as bytes? or as string? For efficient transfer, I would like to know if I need to convert 'count' into bytes before publishing.

std_msgs::String msg;
double count = 12.76578589776736376983983231112;
std::stringstream ss;
ss << "hello world " << count;
msg.data = ss.str();

ROS_INFO("%s", msg.data.c_str());

/**
 * The publish() function is how you send messages. The parameter
 * is the message object. The type of this object must agree with the type
 * given as a template parameter to the advertise<>() call, as was done
 * in the constructor above.
 */
chatter_pub.publish(msg);
edit retag flag offensive close merge delete

Comments

Not quite sure what you mean by converting "hello world" into bytes before publishing. You can only publish the msg in the correct format (http://www.ros.org/doc/api/std_msgs/html/msg/String.html), which in this case is a string

weiin gravatar image weiin  ( 2013-05-27 20:33:27 -0500 )edit

I am sorry. I meant how many bytes is 'count' converted to? Or in short, how many bytes are published in total?

aswin gravatar image aswin  ( 2013-05-27 20:41:49 -0500 )edit

strlen(msg.data.c_str()) + 1 + some amount of network headers

Bill Smart gravatar image Bill Smart  ( 2013-05-28 18:31:34 -0500 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2013-05-28 06:46:55 -0500

Bill Smart gravatar image

Not sure what you mean by converting to bytes, since everything is represented as bytes internally. You're constructing a string on the line

ss << "hello world " << count;

so that's what you're sending. The string stream operator will take count, turn it into a string, append it to "hello world " and return it through the c_str() call. If you want to know how long that string is, then use strlen(). The double needs sizeof(double) bytes (probably 8, if your machine is like mine). Any string representation of a double with more than 8 characters will use more space. If you really want to send a double, create a message type with a double field.

More than that is getting sent, though, since the underlying networking layers are adding protocol wrappers to everything that gets sent out. In general, I'd advise against trying to optimize things at this level, unless you're seeing a performance problem. Unless you understand linux networking and how ROS uses it at a pretty fine-grained level, you might end up doing a lot of work for little gain.

edit flag offensive delete link more

Comments

I later realized that this was not a ROS question. Anyway, as you mentioned there are more than 8 bytes that are sent for "count". A message field with double field is good, but when the message includes bool, int, string etc, this leads to more messages unnecessarily.

aswin gravatar image aswin  ( 2013-05-28 15:39:59 -0500 )edit

The key is to convert double, short etc... into a hex byte representation before appending to string stream, and then sending it. In this case count will always occupy 8 bytes. For people working on intel architecture this will not cause latency. I use a single core ARM

aswin gravatar image aswin  ( 2013-05-28 15:43:06 -0500 )edit

I'm not sure why you're packing things into a string, since defining a new message with all of the fields you need will accomplish the same thing at the same storage cost, but without you having to do the packing yourself.

Bill Smart gravatar image Bill Smart  ( 2013-05-28 18:30:42 -0500 )edit

Agree that it has the same storage cost. However, with a different message for each datatype, this would mean I will have to maintain 5 to 6 times the number of messages & topics I have in a distributed system. There is also slight overhead due to extra headers and checksum.

aswin gravatar image aswin  ( 2013-05-29 16:02:43 -0500 )edit

I understand now: you're looking to send a message with a dynamic data type, right? There's a strong typing in ROS messages, so you're going to have to pull some tricks to do this (like the one you suggest above).

Bill Smart gravatar image Bill Smart  ( 2013-05-30 09:02:35 -0500 )edit

On another note, one should not use stringstream for packing in such applications i.e. at byte level. Presence of bytes such as 0x0A in the stream screws up the unpacking process

aswin gravatar image aswin  ( 2013-05-30 21:08:10 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2013-05-27 15:56:40 -0500

Seen: 790 times

Last updated: May 28 '13