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
This discussion was converted from issue #397 on December 16, 2022 05:52.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I downloaded a ROS 2 db3 file from Autoware here.
I tried to convert it to MCAP using
mcap convert
. I ran this inside a docker container with the message definitions available:It turns out that these schemas are specified using
.idl
instead of.msg
:root@b89cf3a30f2a:/bags/autoware# find / | grep -i ControlModeReport /autoware/build/autoware_auto_vehicle_msgs/ament_cmake_core/stamps/ControlModeReport.idl.stamp /autoware/src/core/external/autoware_auto_msgs/autoware_auto_vehicle_msgs/msg/ControlModeReport.idl /autoware/install/autoware_auto_vehicle_msgs/share/autoware_auto_vehicle_msgs/msg/ControlModeReport.idl
.idl
is supported by ROS 2 as an alternative to.msg
.mcap convert
doesn't appear to support db3 files with.idl
message definitions, and the MCAP spec appendix doesn't document a way to store these.Even if
mcap convert
supported.idl
schemas, Foxglove Studio apparently does not support rendering them.Pre-requisites:
mcap convert
should support db3 files with IDL schemas mcap#496Related:
Beta Was this translation helpful? Give feedback.
All reactions