Skip to content

cpu: fix the FAST non-max bounds check - #3720

Draft
melonakos wants to merge 1 commit into
masterfrom
fix/3357-fast-nonmax-bounds
Draft

melonakos wants to merge 1 commit into
masterfrom
fix/3357-fast-nonmax-bounds

Conversation

@melonakos

@melonakos melonakos commented Sep 10, 2026

Copy link
Copy Markdown
Member

The FAST non-max check ran after the neighbourhood reads and compared y against dims[1] and x against dims[0], so on non-square images it read out of bounds and rejected every keypoint. This is @jlaxson's commit from #3357, authorship kept. The SUSAN and Harris changes @syurkevi added on top in that PR swap the reported x/y coordinates and fail the SUSAN test suite against the current gold data, so they are left out until that convention is settled.

The check ran after the neighbourhood reads and compared y against dims[1] and x against dims[0], so on non-square images it read out of bounds and rejected every keypoint. Move it before the reads and use the right dimension for each axis. Extracted from #3357.
@melonakos
melonakos force-pushed the fix/3357-fast-nonmax-bounds branch from eb8d767 to 567fe34 Compare September 10, 2026 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants