Fix ICP viewpoint adaptation issue by aligning sensor coordinates #6280
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
This is a quick fix for issue #6279.
When performing ICP registration, if the
input_point cloud and the reference (i.e.,target_) point cloud come from different viewpoints (i.e., differentsensor_origin_andsensor_orientation_), the output point cloud may retain inconsistent coordinate frame information, potentially leading to downstream processing errors.Since
input_is being registered to the reference cloud, it is reasonable to directly assign the output cloud’ssensor_origin_andsensor_orientation_to those of the reference (target) cloud, ensuring consistent frame alignment.This change updates the
align()method to apply this correction, and issues a warning if such a transformation occurs.