Skip to content

[fix] Correct nb of laser rings detection

Nicolas Cadart requested to merge fix/KRGetPerRingLineNeighbors into master

Since 0210594d, the number of laser ids in the current neighborhood needs to be computed, as the keypoints extractor is not accessible anymore.

If max and min laser ids where equal, the computed number of laser rings was 0, but should be 1. Otherwise, this lead to segfaults when EgoMotion registration was used.

This commit fixes this number of scan lines estimation.

@julia.sanchez @nick.laurenson PTAL

Merge request reports

Loading