Fix bounds check for FAST Nonmax by jlaxson · Pull Request #3357 · arrayfire/arrayfire
This bounds check was broken in two ways:
- It happened after memory access already occurred, meaning it didn't really protect anything
- It swapped x/y checks in the dimension order.
The result was fast (and orb) features would not be returned for the entire image if the input image wasn't square.
Checklist
- Rebased on latest master
- Code compiles
- Tests pass
- Functions added to unified API
- Functions documented