Specifically, it provides a common interface for connecting LIO datasets and LIO pipelines. This allows for easy addition of new datasets and pipelines, as well as a common location to evaluate them making benchmarks significantly easier to run. It features,
- No ROS dependency! (though it can still load rosbag datasets using the wonderful rosbags package)
- 8 compiled in LIO pipelines and 12 configured datasets.
- Easy to add new datasets and pipelines, see the example
- Unified representation of lidar scan, e.g. row (scan-line) major order, stamped at the start of the scan, point stamps are relative from the start of the scan.
- Download and manage datasets via the CLI interface
- Simple to use API for friction-free access to data
- Run pipelines via the CLI interface and yaml config files
- Compute statistics for resulting trajectory runs
Installation
evalio is available on PyPi (with all pipelines compiled in!), so simply install via your favorite python package manager,
uv add evalio # uv
pip install evalio # pip
Basic Usage
evalio can be used both as a python library and as a CLI for both datasets and pipelines. We cover just the tip of the iceberg here, so please check out the docs for more information.
Datasets
Once evalio is installed, datasets can be listed and downloaded via the CLI interface. For example, to list all datasets and then download a sequence from the hilti-2022 dataset,
evalio ls datasets
evalio dl hilti_2022/basement_2
Once downloaded, a trajectory can then be easily used in python,
from evalio import datasets as ds
# for all data
for mm in ds.Hilti2022.basement_2:
print(mm)
# for lidars
for scan in ds.Hilti2022.basement_2.lidar():
print(scan)
# for imu
for imu in ds.Hilti2022.basement_2.imu():
print(imu)
Pipelines
The other half of evalio is the pipelines that can be run on various datasets. All pipelines and their parameters can be shown via,
evalio ls pipelines
For example, to run KissICP on a dataset,
evalio run -o results -d hilti_2022/basement_2 -p kiss
This will run the pipeline on the dataset and save the results to the results folder. The results can then be used to compute statistics on the trajectory,
evalio stats results
More complex experiments can be run, including varying pipeline parameters, via specifying a config file,
output_dir: ./results/
datasets:
# Run on all of hilti trajectories
- hilti_2022/*
# Run on first 1000 scans of multi campus
- name: multi_campus/ntu_day_01
length: 1000
pipelines:
# Run vanilla kiss with default parameters
- kiss
# Tweak kiss parameters
- name: kiss_tweaked
pipeline: kiss
deskew: true
# Sweep over voxel size parameter
sweep:
voxel_size: [0.1, 0.5, 1.0]
This can then be run via
evalio run -c config.yml
Contributing
Contributions are always welcome! Feel free to open an issue, pull request, etc. The documentation has a more details on developing new datasets and pipelines.
Citation
If you use evalio in your research, please cite the following paper,
@misc{potokar2025_evaluation_lidar_odometry,
title={A Comprehensive Evaluation of LiDAR Odometry Techniques},
author={Easton Potokar and Michael Kaess},
year={2025},
eprint={2507.16000},
archivePrefix={arXiv},
primaryClass={cs.RO},
url={https://arxiv.org/abs/2507.16000},
}
Metadata
Release files for evalio 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| evalio-0.6.1-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.14 | CPython 3.14 | Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 | Details |
| evalio-0.6.1-cp314-cp314-macosx_11_0_arm64.whl | CPython 3.14 | CPython 3.14 | macOS 11.0+ ARM64 | Details |
| evalio-0.6.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
| evalio-0.6.1-cp313-cp313-macosx_11_0_arm64.whl | CPython 3.13 | CPython 3.13 | macOS 11.0+ ARM64 | Details |
| evalio-0.6.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
| evalio-0.6.1-cp312-cp312-macosx_11_0_arm64.whl | CPython 3.12 | CPython 3.12 | macOS 11.0+ ARM64 | Details |
| evalio-0.6.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
| evalio-0.6.1-cp311-cp311-macosx_11_0_arm64.whl | CPython 3.11 | CPython 3.11 | macOS 11.0+ ARM64 | Details |
Total release size: 35.7 MB
Release files / evalio-0.6.1-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | evalio-0.6.1-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 4.8 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ed8c2fa3732c15bcc9661640062ea136d0849bfcfc0e50f8af72f47f16df1149
|
|
BLAKE2b-256 checksum How to use checksums |
e2e4a19a896fd295ab0d7d2c7868f04c0fc7cd2e44b3e34a7aa29f9448368a32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / evalio-0.6.1-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | evalio-0.6.1-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6071c26b33060dc56ed1522c7ddf53e7398793d07828b7b50bff69157218b7df
|
|
BLAKE2b-256 checksum How to use checksums |
70038d164651c7a01fb52325e130623763cac44cec3ea498a4f85b0e8ced3635
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / evalio-0.6.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | evalio-0.6.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 4.8 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b1ae5df061d1c9a4be83a0eff23d90d28a990c28d027c3efe6d66b02885d2811
|
|
BLAKE2b-256 checksum How to use checksums |
014b25e926509efd8aae01e41af822d557d512f2e8776aa29795bea1a98ede76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / evalio-0.6.1-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | evalio-0.6.1-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
cfe0df068997b0abd8de2e71406be654b174f0260366e16e8966301638bc119b
|
|
BLAKE2b-256 checksum How to use checksums |
18bdc1f2329e5727c8e342329ebc47972d920361945803301c4efbcc28761907
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / evalio-0.6.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | evalio-0.6.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 4.8 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
272bb3aef236612276342405e30bbfa5d841b4612cfec3932185865376c3cb63
|
|
BLAKE2b-256 checksum How to use checksums |
d4218dca2e7552b45e320e4ef9d90f72f3320c5b9da2d125a417e2d44fa1fd34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / evalio-0.6.1-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | evalio-0.6.1-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
96c36fd84d5ce021df74d2785578328e9d27851fe9a9d3b152f7497f2e348788
|
|
BLAKE2b-256 checksum How to use checksums |
b06d746282104665e8c3389088853ecfe3afd61dffad75d70bda31797d204a5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / evalio-0.6.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | evalio-0.6.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 4.8 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
eb4bd13291f01d80a5c42023f01cf8284036502edd8b0f76dcb2ef1bddd4e8df
|
|
BLAKE2b-256 checksum How to use checksums |
37b82e1e84633a105a9dd3334a6bf997cf0065443a792a9469c25c05abeec91a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / evalio-0.6.1-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | evalio-0.6.1-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b49a558e8ee7f840ec2e2986b03f5f93ebb188fcb1b7c2533e4ed72a84f73d1c
|
|
BLAKE2b-256 checksum How to use checksums |
3b8ba64934aebf02c87f93b7f44984fa619526154fb2a3c8afde6278a93ea8f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency log