Revision history [back]

You're having problems with 'rosbag fix' only right? I'm assuming that your bags are properly indexed and if they aren't you can run rosbag reindex on them.

In order to migrate, you'll likely have to first split the topics into two separate bags. The tool to use for this is rosbag filter. For example try:

rosbag filter original.bag PNI.bag "topic == '/pni_imu'"


Now that you have bags with only one of the problematic types, you should be able to set up your environment so that you can migrate. This is pretty complicated, so I can't give you a complete list of steps to take, but here's some things to check:

• Make sure your new messages don't have this same problem (identical datatypes in the definition).
• Make sure you only don't have the old messages built currently.
• Make sure you only have one migration rule exported at a time.

You probably don't have to make sure all of these are true, but if you keep having problems, if I didn't forget anything, that should be all you need to resolve this migration.

Good luck! :D

This problem means that your message definitions are the same. Likely you have the same message in two different packages with different filenames.

You're having problems with 'rosbag fix' only right? I'm assuming that your bags are properly indexed and if they aren't you can run rosbag reindex on them.

In order to migrate, you'll likely have to first split the topics into two separate bags. The tool to use for this is rosbag filter. For example try:

rosbag filter original.bag PNI.bag "topic == '/pni_imu'"


Now that you have bags with only one of the problematic types, you should be able to set up your environment so that you can migrate. This is pretty complicated, so I can't give you a complete list of steps to take, but here's some things to check:

• Make sure your new messages don't have this same problem (identical datatypes in the definition).
• Make sure you only don't have the old messages built currently.
• Make sure you only have one migration rule exported at a time.

You probably don't have to make sure all of these are true, but if you keep having problems, if I didn't forget anything, that should be all you need to resolve this migration.

Good luck! :D

This problem means that your message definitions are the same. Likely you have the same message in with two different packages with different filenames.

You're having problems with 'rosbag fix' only right? I'm assuming that your bags are properly indexed and if they aren't you can run rosbag reindex on them.

In order to migrate, you'll likely have to first split the topics into two separate bags. The tool to use for this is rosbag filter. For example try:

rosbag filter original.bag PNI.bag "topic == '/pni_imu'"


Now that you have bags with only one of the problematic types, you should be able to set up your environment so that you can migrate. This is pretty complicated, so I can't give you a complete list of steps to take, but here's some things to check:

• Make sure your new messages don't have this same problem (identical datatypes in the definition).
• Make sure you only don't have the old messages built currently.
• Make sure you only have one migration rule exported at a time.

You probably don't have to make sure all of these are true, but if you keep having problems, if I didn't forget anything, that should be all you need to resolve this migration.

Good luck! :D