Repository navigation
BUG: Compute displacement exponential scale without undefined shift (B35, split of #6669) - #6673
Merged
hjmjohnson merged 1 commit intoJul 23, 2026
Conversation
The first-order scale 2^numiter was computed as 1 << numiter, which is undefined behavior for 31 or more iterations and reachable through SetMaximumNumberOfIterations with automatic iterations off. Use ldexp. Also select zero squaring iterations for a zero field: the previous sentinel, NumericTraits::min(), is a tiny positive value, so the keep-zero branch was unreachable, and integral iteration estimates overshot the documented ceil by one. Issue InsightSoftwareConsortium#6575, items B35 and Q31.
hjmjohnson
marked this pull request as ready for review
July 21, 2026 15:40
Contributor
dzenanz
approved these changes
Jul 23, 2026
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
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.
B35 —
ExponentialDisplacementFieldImageFilterdivided the field by1 << numiter, undefined behavior fornumiter >= 31. Split out of #6669 as an independent bug fix (#6669 closed in favor of focused PRs).Unreachable by default (automatic cap 20), but an explicit
SetMaximumNumberOfIterations(>= 31)made it live. The scale is now computed in floating point.New GTests
ThirtyOneIterationsScaleCorrectlyandZeroFieldStaysZero.Local testing
Cherry-picked onto current
upstream/main(37ecafc); builtITKDisplacementFieldGTestDriverand ran both new tests — PASSED.pre-commit run --all-filesclean.Fixes item B35 from the #6575 audit. Companion PRs (split from #6669): STYLE/DOC dispositions and the WarpImageFilter B34 fix.