Deep learning has shown promising results for multiple 3D point cloud registration datasets. However, in the underwater domain, most registration of multibeam echo-sounder (MBES) point cloud data are still performed using classical methods in the iterative closest point (ICP) family. In this work, we curate and release DotsonEast Dataset, a semi-synthetic MBES registration dataset constructed from an autonomous underwater vehicle in West Antarctica. Using this dataset, we systematically benchmark the performance of 2 classical and 4 learning-based methods. The experimental results show that the learning-based methods work well for coarse alignment, and are better at recovering rough transforms consistently at high overlap (20-50%). In comparison, GICP (a variant of ICP) performs well for fine alignment and is better across all metrics at extremely low overlap (10%). To the best of our knowledge, this is the first work to benchmark both learning-based and classical registration methods on an AUV-based MBES dataset.
The data presented in this paper was collected using RAN - Gothenburg University’s Kongsberg Hugin AUV equipped with a Kongsberg EM2040 multibeam echo sounder during the 2022 ITGC cruise. The survey site was close to the eastern side of Dotson ice shelf in West Antarctica. As such, the data has unusually large elevation changes.
To construct a dataset with groundtruth, we perform the following steps:
We evaluate the tested methods on three sets of metrics:
Using the above metrics, we evaluate the following methods. The code and pretrained models for DotsonEast dataset will be released shortly.
We benchmark the evaluated methods using submap pairs with between 10-50% of overlap. Amongst others, we notice the following:
@inproceedings{ling2024benchmarking,
title={Benchmarking Classical and Learning-Based Multibeam Point Cloud Registration},
author={Ling, Li and Zhang, Jun and Bore, Nils and Folkesson, John and Wåhlin, Anna},
booktitle={2024 IEEE International Conference on Robotics and Automation (ICRA)},
year={2024},
organization={IEEE}
}