Open buntonj opened 1 year ago
DLIO-M keeps track of int indices for the map point clouds, so we can summarize over those as long as the cost function can dig into the map details to compute overlaps and stuff. Can take some inspiration from their compute_overlap
function.
If I want to exclusively use their compute_overlap
function, I need to resort to pair-wise
evaluations. Otherwise, I may have to open up the hood of their function a bit more to do overlap computations with larger subsets of point clouds.
Develop a reasonable cost function for DLIO-M interface (will need to operate on pointers to point cloud objects, potentially handled in ~ROS2~ ROS Noetic).