Any pre-made msg migration rules? (eg. tf/tfMessage)
I received a rosbag, which I think, but can't be sure was recorded with Kinetic and I need to migrate it to Melodic. I've tried rosbag check and rosbag fix but it seems there are no existing rules and I need to write my own. I have a hard time believing that no one has already made scripts to migrate most of the standard ROS messages.
zac@zac-prodesk:~$ rosbag check my_old_bag.bag
WARNING: For type [tf/tfMessage] stored md5sum [94810edda583a504dfda3829e70d7eec] does not match message definition [d41d8cd98f00b204e9800998ecf8427e].
Try: "rosrun rosbag fix_msg_defs.py old_bag new_bag."
The following migrations need to occur:
* From: tf/tfMessage [d41d8cd98f00b204e9800998ecf8427e]
To: tf/tfMessage [94810edda583a504dfda3829e70d7eec]
1 rules missing:
* From: tf/tfMessage [d41d8cd98f00b204e9800998ecf8427e]
To: tf/tfMessage [94810edda583a504dfda3829e70d7eec]
To generate rules, please run with -g <rulefile>
I've generated the blank rulefile, but it seems like I still need to write it all myself. Is there no easier way?
As far as I can tell, the TF message hasn't changed for a _long_ time. See here (http://docs.ros.org/melodic/api/tf/ht...) for Melodic and here (http://docs.ros.org/diamondback/api/t...) for diamond back, they're identical down to their parts.
Did you modify that message or anything in geometry msgs and recompile?
I would tend to agree with @stevemacenski. TF hasn't changed in a very long time, so I'd be more inclined to believe something else is going wrong here.
A quick google shows that
d41d8cd98f00b204e9800998ecf8427eis the MD5 sum of an empty string.That does not seem right.
Is there any chance you could provide us with the
.bag, or an extract of it?Can you provide more information on the circumstances in which it was recorded?