Python package for the evaluation of odometry and SLAM
Python package for the evaluation of odometry and SLAM
Linux / macOS / Windows / ROS / ROS2 |
---|
This package provides executables and a small library for handling, evaluating and comparing the trajectory output of odometry and SLAM algorithms.
Supported trajectory formats:
geometry_msgs/PoseStamped
, geometry_msgs/TransformStamped
, geometry_msgs/PoseWithCovarianceStamped
, geometry_msgs/PointStamped
or nav_msgs/Odometry
topics or TF messagesSee here for more infos about the formats.
evo has several advantages over other public benchmarking tools:
core
and tools
libraries for custom extensionsWhat it’s not: a 1-to-1 re-implementation of a particular evaluation protocol tailored to a specific dataset.
Installation is easy-peasy if you’re familiar with this: https://xkcd.com/1987/#
evo supports Python 3.8+.
You might also want to use a virtual environment.
If you just want to use the executables of the latest release version, the easiest way is to run:
pip install evo
This will download the package and its dependencies from PyPI and install or upgrade them. If you want, you can subscribe to new releases via https://libraries.io/pypi/evo.
Run this in the repository’s base folder:
pip install --editable .
Tab completion is supported via the argcomplete package. Run activate-global-python-argcomplete
after the installation to use it.
Python packages
evo has some required dependencies that are automatically resolved during installation with pip.
See the pyproject.toml
file for all details.
PyQt5 (optional)
PyQt5 will give you the enhanced GUI for plot figures from the “Qt5Agg” matplotlib backend (otherwise: “TkAgg”). If PyQt5 is already installed when installing this package, it will be used as a default (see evo_config show
). To change the plot backend afterwards, run evo_config set plot_backend Qt5Agg
.
ROS (optional)
Some ROS-related features require a ROS installation, see here. We are testing this package with ROS Noetic and Iron. Previous versions (<= 1.12.0
) work with Melodic, Kinetic and Indigo.
Note: reading ROS bag files works also without a ROS installation thanks to the great rosbags package that is installed together with evo. This allows you also to read ROS 1 & 2 bags even if you don’t have one of those ROS distros installed. (except for reading /tf
topics, because there we need the buffer implementation from ROS)
contextily (optional)
contextily is required for adding map tiles to plots of geo-referenced data.
After installation with pip, the following executables can be called globally from your command-line:
Metrics:
evo_ape
- absolute pose errorevo_rpe
- relative pose errorTools:
evo_traj
- tool for analyzing, plotting or exporting one or more trajectoriesevo_res
- tool for comparing one or multiple result files from evo_ape
or evo_rpe
evo_fig
- (experimental) tool for re-opening serialized plots (saved with --serialize_plot
)evo_config
- tool for global settings and config file manipulationCall the commands with --help
to see the options, e.g. evo_ape --help
. Tab-completion of command line parameters is available on UNIX-like systems.
More documentation
Check out the Wiki on GitHub.
There are some example trajectories in the source folder in test/data
.
Here, we plot two KITTI pose files and the ground truth using evo_traj
:
cd test/data
evo_traj kitti KITTI_00_ORB.txt KITTI_00_SPTAM.txt --ref=KITTI_00_gt.txt -p --plot_mode=xz
For example, here we calculate the absolute pose error for two trajectories from ORB-SLAM and S-PTAM using evo_ape
(KITTI_00_gt.txt
is the reference (ground truth)) and plot and save the individual results to .zip files for evo_res
:
First trajectory (ORB Stereo):
mkdir results
evo_ape kitti KITTI_00_gt.txt KITTI_00_ORB.txt -va --plot --plot_mode xz --save_results results/ORB.zip
Second trajectory (S-PTAM):
evo_ape kitti KITTI_00_gt.txt KITTI_00_SPTAM.txt -va --plot --plot_mode xz --save_results results/SPTAM.zip
evo_res
can be used to compare multiple result files from the metrics, i.e.:
Here, we use the results from above to generate a plot and a table:
evo_res results/*.zip -p --save_table results/table.csv
For an interactive source code documentation, open the Jupyter notebook metrics_tutorial.ipynb
in the notebooks
folder of the repository. More infos on Jupyter notebooks: see here
If you have IPython installed, you can launch an IPython shell with a custom evo profile with the command evo_ipython
.
A few “inoffical” scripts for special use-cases are collected in the contrib/
directory of the repository. They are inofficial in the sense that they don’t ship with the package distribution and thus aren’t regularly tested in continuous integration.
“😱, this piece of 💩 software doesn’t do what I want!!1!1!!”
First aid:
-h
/ --help
to your commandPatches are welcome, preferably as pull requests.
If you use this package for your research, a footnote with the link to this repository is appreciated: github.com/MichaelGrupp/evo
.
…or, for citation with BibTeX:
@misc{grupp2017evo,
title={evo: Python package for the evaluation of odometry and SLAM.},
author={Grupp, Michael},
howpublished={\url{https://github.com/MichaelGrupp/evo}},
year={2017}
}