Rewire maps these ROS 2 message types to Rerun archetypes automatically. No configuration needed.
Rewire aims to align its mappings with the conventions Rerun uses for MCAP ingestion, so data
recorded with Rewire should look familiar if you've used Rerun's built-in MCAP loader. That said,
full parity is not guaranteed — some mappings may differ where Rewire optimizes for live streaming
or supports ROS 2-specific semantics that don't have a direct MCAP equivalent.
You can always check the latest list by running rewire types.
Some types log their reported uncertainty as an extra Scalars series alongside the measurement:
Temperature, FluidPressure, RelativeHumidity, Illuminance, Range — variance
Imu — orientation, angular velocity and linear acceleration covariance diagonals
Newer ROS 2 distributions publish their demo topics with these types instead of the deprecated
std_msgs primitives. They are wire-identical, and Rewire maps them the same way.
The VoxelGrid converter is marked unstable while Rerun's VoxelGridMap archetype is itself
experimental. Occupied voxels are colored by value through the Turbo colormap.
String on a topic ending in /robot_description is loaded as a URDF instead, which produces
Asset3D, Transform3D, CoordinateFrame and InstancePoses3D.
See URDF Loading.
