fix(autoware_image_projection_based_fusion): modify incorrect index access in pointcloud filtering for out-of-range points #10087
+4
−2
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.
Description
Before
In this line, the point cloud filtering process for out-of-range points increments output variables (such as "iter_painted_x") at the same time as "iter_x".
However, in the following process, these output variables are used until "j", which is the size of points within the range.
As a result, data is stored at indices beyond "j", leading to incorrect index access.
After
I modified the timing of the increments for "iter_painted_x" so that points within the range are stored correctly until "j".
Related links
Parent Issue:
How was this PR tested?
Notes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.