8000 Deserialize messages in bag using the message definitions in the bag · Issue #1603 · ros2/ros2 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Deserialize messages in bag using the message definitions in the bag #1603

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
jackiescanlon opened this issue Sep 18, 2024 · 0 comments
Open

Deserialize messages in bag using the message definitions in the bag #1603

jackiescanlon opened this issue Sep 18, 2024 · 0 comments
Assignees
@wjwwood

Comments

@jackiescanlon
Copy link

Feature request

(Ported from ros2/rosbag2#1801)

Feature description

Right now with rosbag2_py it seems that its possible to:

  1. Get the message definitions stored in an .mcap in string format (source)
  2. Get the messages stored in an .mcap by deserializing with the associated message definition (example)

However, I cannot find a way to connect the two things, i.e., deserialize the messages via the definitions in the bag. There doesn't seem to be a (simple) way to turn the string message definitions into actual message defs that the deserializer can use. All the examples I can find for deserialization in python involve using the message definitions available in the local environment, not the ones in the bag.

Let me know if I am overlooking some part of the API that does do this currently.

Related Issues

  1. I found Store message definition in bag rosbag2#782 which seems to have covered the problem of the message definitions not being stored in bag files at all in ROS 2, but using the stored definitions for deserialization does not appear to be covered by that ticket.
  2. There's some comments on Type Description Distribution (REP-2011 subset / REP-2016) - formerly "message definitions on-the-wire" #1159 (comment) requesting this also, but as far as I can tell no separate ticket was ever created for this.
  3. Those comments reference Dynamic Subscription (REP-2011 subset) #1374. I didn't see anything obvious in there that seems to cover the issue I'm describing but perhaps I overlooked it? Not sure.

Implementation considerations

@MichaelOrlov mentioned in ros2/rosbag2#1801 that:

There is nothing to do from the Rosbag2 side. We just don't have API from the underlying ROS 2 core packages to be able to deserialize messages using saved type description from the #1159
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wjwwood wjwwood

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wjwwood @jackiescanlon
0