rerun could be a nice visualization option as an alternative to the matplotlib-based plotting features of evo. They seem to complement each other quite well:
- matplotlib: static, focus on high-quality plots suitable for print, terrible 3D view
- rerun: dynamic timeline replay, focus on live visualization/interaction, nice 3D view
bridge
The Rerun archetypes should allow to log most of the things that are also added to plots right now:
- trajectory visualization (pose axes, lines, correspondences, color-mapped trajectories...)
- scalar visualization (errors, speeds, XYZ, orientations...)
Missing / unclear:
Probably useless:
PosePath3D support: probably makes no sense without timestamps, only support PoseTrajectory3D- 2D view support: doesn't seem to be worth the effort, evo data is 3D and matplotlib is fine for 2D
CLI
CLI integration into the existing commands would be nice. E.g. something like evo_traj bag ... --rerun to cover common use cases without scripting.
Dependency
rerun should be only an optional dependency in pyproject.toml.
rerun could be a nice visualization option as an alternative to the matplotlib-based plotting features of evo. They seem to complement each other quite well:
bridge
The Rerun archetypes should allow to log most of the things that are also added to plots right now:
Missing / unclear:
sharexin mpl), coming soon: Add option to link the X-axis of multiple time plots rerun-io/rerun#10146Probably useless:
PosePath3Dsupport: probably makes no sense without timestamps, only supportPoseTrajectory3DCLI
CLI integration into the existing commands would be nice. E.g. something like
evo_traj bag ... --rerunto cover common use cases without scripting.Dependency
rerun should be only an optional dependency in
pyproject.toml.