Skip to content

Fix operator precedence bug in interpolation grid max#125

Open
CodeReclaimers wants to merge 1 commit intodavideberly:masterfrom
CodeReclaimers:fix/interp-grid-max-precedence
Open

Fix operator precedence bug in interpolation grid max#125
CodeReclaimers wants to merge 1 commit intodavideberly:masterfrom
CodeReclaimers:fix/interp-grid-max-precedence

Conversation

@CodeReclaimers
Copy link
Contributor

Operator precedence causes mXMax = xMin + xSpacing * xBound - 1 to evaluate as (xMin + xSpacing*xBound) - 1 instead of xMin + xSpacing*(xBound - 1). Affects IntpBilinear2, IntpBicubic2, IntpTrilinear3, and IntpTricubic3.

Test: tests/issue_6_2_3_4_interp_grid_max/

🤖 Generated with Claude Code

mXMax = xMin + xSpacing * xBound - 1 evaluates as (xMin + xSpacing*xBound) - 1
instead of xMin + xSpacing*(xBound - 1). Affects IntpBilinear2, IntpBicubic2,
IntpTrilinear3, and IntpTricubic3.

Test: tests/issue_6_2_3_4_interp_grid_max/

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.

1 participant