[IJRR 2026] Commerge: Communication-Efficient, Robust, and Fast LiDAR Map Merging Framework
for Multi-Robot Coordination in Resource-Constrained Scenarios
Robots that map on their own must exchange scans to merge their maps, and over a weak link that exchange is the bottleneck. Commerge picks the few scans that carry the overlap and sends only those, in three steps:
- 🤖 Before the steps, each robot runs its own SLAM with SOLiD: keyframe scans, poses and SOLiD descriptors, saved as a session.
- 🔗 Step (A) Sequential matching: regions of the inter-robot affinity matrix where both robots saw the same places in sequence.
- ⚖️ Step (B) Balanced minimum vertex cover: the fewest keyframes that still touch every candidate match, shared fairly between the robots.
- 💎 Step (C) Maximum edge-weighted clique: among those, only the pairs that agree with each other geometrically.
- 🤝 Exchange and merge: the robots exchange the scans of the most consistent region only; their submaps are registered (KISS-Matcher + GICP) and the transform merges the whole maps.
- 📦 MB, not GB: up to 99.98 % less data exchanged (7,000 MB → 1.3 MB on HeLiPR) with comparable alignment, also on a Jetson Nano.
📦 Prerequisites
- Python 3.9+.
pip install commergebrings NumPy, SciPy, Matplotlib and the registration (KISS-Matcher, wheels for Python 3.9-3.12, and small_gicp). - Solver: Gurobi, free for academic use, as in the paper (
pip install gurobipy, thengrbgetkey <key>). No license? HiGHS ships with SciPy and returns the same selection, only slower on the largest regions (--solver highs;auto, the default, picks Gurobi when it is licensed). - One session per robot from SOLiD (
thirdparty/SOLiD): keyframe scans, poses and SOLiD descriptors.
🛠️ Installation
pip install commerge # + "commerge[gurobi]" for gurobipy, "commerge[compare]" for the AutoMerge comparison
# or from a clone, with SOLiD and KISS-Matcher as submodules:
git clone --recursive https://github.com/sparolab/Commerge.git && cd Commerge && pip install .
# KISS-Matcher from the submodule instead of the wheel: pip install thirdparty/KISS-Matcher/python
commerge --version
Ubuntu and macOS (Python only, no ROS needed for Commerge itself).
Docker
docker pull ghcr.io/sparolab/commerge # or: docker build -f docker/Dockerfile -t ghcr.io/sparolab/commerge .
docker run --rm -v $HOME/robot_a:/a -v $HOME/robot_b:/b -v $PWD/merged:/out ghcr.io/sparolab/commerge \
commerge /a /b --threshold 0.96 --min-area 2000 --out /out --plot
# Gurobi: add -v $HOME/gurobi.lic:/opt/gurobi/gurobi.lic (otherwise HiGHS)
🚀 Run
1. One session per robot with SOLiD, with any odometry it supports (FAST-LIO, KISS-ICP, GeoRIO, …) or without ROS:
cd thirdparty/SOLiD
roslaunch solid_ros run.launch odometry:=fast_lio save_dir:=$HOME/robot_a # ROS 1, while the bag of robot A plays
ros2 launch solid_ros run.launch.py odometry:=kiss_icp save_dir:=$HOME/robot_b # ROS 2
python slam/common/mac/solid_loops.py --kitti <sequence> --config slam/config/kitti.yaml --out $HOME/robot_a # no ROS
2. Select the scans to exchange, register them and merge:
commerge $HOME/robot_a $HOME/robot_b --threshold 0.96 --min-area 2000 --out merged/ --plot [--gt-a gt_a.txt --gt-b gt_b.txt]
[commerge] kitti00_a: 1011 keyframes | kitti00_b: 1701 keyframes
[commerge] steps (A)+(B)+(C), solver gurobi: (A) 4 region(s) (threshold 0.96, min area 2000) in 0.021 s
[commerge] region 2: A 250-381 x B 899-1027: (A) 1077 candidate pairs -> (B) 66+66 keyframes -> (C) 24 pairs = 14 A + 17 B scans, (B) 0.34 s, (C) 0.13 s
...
[commerge] registered B to A: 540 KISS-Matcher inliers, GICP in 1.3 s; vs ground truth: 0.35 m, 0.06 deg (B keyframes 0.15 m off on average)
[commerge] exchanged 14 A + 17 B scans (1.1 % of 2712, 4.6 MB) from region(s) [2] of 4 -> merged/
All outputs, options and the Python API: docs/GUIDE.md.
📊 Compare
commerge-compare runs Commerge, its ablations and AutoMerge on the same sessions. On KITTI 00 split into two robots, Commerge sends 31 of 2,712 scans (4.6 MB) and merges the maps within 0.35 m; AutoMerge's region sends 156 scans and merges within 1.05 m. Details and the ablations: docs/GUIDE.md.
🤖 Run with your agent
Open Claude Code or Codex in an empty folder and paste:
Clone https://github.com/sparolab/Commerge, read its AGENTS.md, and follow it to install Commerge and merge KITTI 00 split into two robots on this machine. Ask me what you need along the way.
The agent follows AGENTS.md: it installs Commerge with Gurobi or HiGHS, makes one SOLiD session per robot, selects and exchanges the scans, merges the maps, and checks the result.
⚠️ Limitation: heterogeneous LiDARs
Commerge selects scans from the affinity of the two robots' descriptors. With the same LiDAR on both robots, SOLiD gives an affinity whose overlapping regions stand out. With different LiDARs (a spinning Ouster and a Livox Avia with a 70° field of view, for instance), SOLiD describes the same place differently and step (A) finds hundreds of regions with no structure. A descriptor made for heterogeneous LiDARs, such as InLiER, passed with --affinity (and --enhance), brings the right region back; registering the few scans exchanged across such different fields of view is still unreliable (--registration grid is experimental). Contributions are welcome.
Citation
If you use Commerge in your research, please cite our paper.
See bibtex
@article{kim2026commerge,
author = {Kim, Hogyun and Choi, Jiwon and Kim, Juwon and Yang, Geonmo and Jeong, Seokhwan and Lim, Hyungtae and Cho, Younggun},
title = {Commerge: Communication-Efficient, Robust, and Fast LiDAR Map Merging Framework for Multi-Robot Coordination in Resource-Constrained Scenarios},
journal = {International Journal of Robotics Research (IJRR)},
year = {2026}
}
Contributing
Issues and pull requests are welcome.
Acknowledgements
Commerge uses SOLiD for inter-robot place recognition. The comparison re-implements the region selection of AutoMerge, which builds on SeqSLAM. Related research: KISS-Matcher, SKiD-SLAM.
Special Thanks
We thank Minwoo Jung for the HeLiPR dataset, and Nikolaos Stathoulopoulos for InLiER, learning-free heterogeneous LiDAR place recognition.
Metadata
Release files for commerge 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| commerge-2.0.0.tar.gz | 35.4 kB | With provenance | Details for commerge-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| commerge-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for commerge-2.0.0-py3-none-any.whl |
Total release size: 68.3 kB
Release files / commerge-2.0.0.tar.gz
| Download URL | commerge-2.0.0.tar.gz |
|---|---|
| Size | 35.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af4219420b0a27cb94c235657f3a3c9c508759302e082fd27b7b67d9fe52bae8
|
|
BLAKE2b-256 checksum How to use checksums |
5cca546dffc73ab53972544d53c8e487feb4b8d5b4bebc269ca5ad39a93772f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logRelease files / commerge-2.0.0-py3-none-any.whl
| Download URL | commerge-2.0.0-py3-none-any.whl |
|---|---|
| Size | 32.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de0f44b0fbdae4ac0ac3edfe2df7dbdc773e52283b7d3d1c97c89371701352ef
|
|
BLAKE2b-256 checksum How to use checksums |
7b97ca0a61245274e39def052459feb1387b87caa21c98aeedada87f5bbe6294
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logSecurity for commerge 2.0.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for commerge-2.0.0.tar.gz
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 Nov 10, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.