I was using the Python version of the Rosbag Code API:<br><meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://www.ros.org/wiki/rosbag/Code%20API#py_api">http://www.ros.org/wiki/rosbag/Code%20API#py_api</a><br>

and I could not get the topics to print from my bag I recored on our robot.  After looking around, I realized the example for recording a bag has:<br><br>bag.write(&#39;chatter&#39;, str);<br><br>and the example for reading has:<br>

<br>bag.read_messages(topics=[&#39;chatter&#39;, &#39;numbers&#39;]):<div><br></div><div>I tried reading in my message as: bag.read_messages(topics=[&#39;odom&#39;]): but it did not work until I used bag.read_messages(topics=[&#39;/odom&#39;]):</div>

<div><br></div><div>When NOT using the slash, I received a stop iterator:</div><div><div>&gt;&gt;&gt; g.next()</div><div>Traceback (most recent call last):</div><div>  File &quot;&lt;stdin&gt;&quot;, line 1, in &lt;module&gt;</div>

<div>StopIteration</div></div><div><br></div><div>So it appears the Rosbag Code API does not handle the topic names like the other ROS tools regarding the first &#39;/&#39;.</div><div><br></div><div>Is this an intentional design decision or just some checks that were left out? </div>

<div><br></div><div>Thanks,</div><div> - Chad</div><meta http-equiv="content-type" content="text/html; charset=utf-8"><meta http-equiv="content-type" content="text/html; charset=utf-8">