You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I am launching this script (Ubuntu 16.04 - ROS Kinetic):
import rosbag
with rosbag.Bag('2019-05-24-09-53-28-high-density-imurenamed.bag', 'w') as outbag:
for topic, msg, t, conn_header in rosbag.Bag('2019-05-24-09-53-28-high-density.bag').read_messages(return_connection_header=True):
if topic == "/f746zg_imu/data_raw" or topic == "/f746zg_imu/mag":
msg.header.frame_id = "nucleo_imu"
outbag.write(topic, msg, t, connection_header=conn_header)
and I obtain the following error:
Traceback (most recent call last):
File "rename_imu.py", line 4, in <module>
for topic, msg, t, conn_header in rosbag.Bag('2019-05-24-09-53-28-high-density.bag').read_messages(return_connection_header=True):
TypeError: read_messages() got an unexpected keyword argument 'return_connection_header'
The text was updated successfully, but these errors were encountered:
ricber
changed the title
Python rosbag::Bag read_messages function does not accept return_connection_header
Python rosbag::Bag.read_messages() does not accept return_connection_header
Sep 3, 2019
ricber
changed the title
Python rosbag::Bag.read_messages() does not accept return_connection_header
Python rosbag::Bag.read_messages() does not accept return_connection_header parameter
Sep 3, 2019
The "return_connection_header" parameter is not available in the kinetic branch. Why this? In my case, if I don't copy the connection header, the /tf_static topic will not be published in the new bag.
ricber
changed the title
Python rosbag::Bag.read_messages() does not accept return_connection_header parameter
rosbag::Bag.read_messages() does not provide return_connection_header parameter on kinetic branch
Sep 3, 2019
Hi,
I am launching this script (Ubuntu 16.04 - ROS Kinetic):
and I obtain the following error:
The text was updated successfully, but these errors were encountered: