BUG: Quick-fix ContourSpatialObject::Update(), LINEAR_INTERPOLATION case #3225
Conversation
This file contains 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
`ContourSpatialObject::Update()` appears to have an assignment to `newPoint`, in the `case InterpolationMethodEnum::LINEAR_INTERPOLATION` section, which was meant to assign just a single element `newPoint[d]`. As was confirmed by Stephen Aylward at issue InsightSoftwareConsortium#3222, "`ContourSpatialObject<TDimension>::Update()` LINEAR_INTERPOLATION case may need some adjustment". Some more adjustment may still be needed, as `newPoint` now still gets modified multiply times (rather than just once), before it eventually gets used.
github-actions
bot
added
area:Core
N-Dekker
added a commit
to N-Dekker/ITK
that referenced
this pull request
Feb 27, 2022
Prevented implicit conversion of a value to `Point`. Aims to avoid possible flaws, like the ones addressed by: Pull request InsightSoftwareConsortium#3225 commit 5b71d63 "BUG: Quick-fix ContourSpatialObject::Update(), LINEAR_INTERPOLATION case" Pull request InsightSoftwareConsortium#3228 commit 12a501c "BUG: Fix `SetCenterInObjectSpace` calls in Registration test" Pull request InsightSoftwareConsortium#3231 commit e4841aa "STYLE: Clarify estimation ray position `RayCastInterpolateImageFunction`" Deleted `Point(nullptr_t)`, especially to avoid `PointType p = 0`.
N-Dekker
added a commit
to N-Dekker/ITK
that referenced
this pull request
Feb 28, 2022
Prevented implicit conversion of a value to `Point`. Aims to avoid possible flaws, like the ones addressed by: Pull request InsightSoftwareConsortium#3225 commit 5b71d63 "BUG: Quick-fix ContourSpatialObject::Update(), LINEAR_INTERPOLATION case" Pull request InsightSoftwareConsortium#3228 commit 12a501c "BUG: Fix `SetCenterInObjectSpace` calls in Registration test" Pull request InsightSoftwareConsortium#3231 commit e4841aa "STYLE: Clarify estimation ray position `RayCastInterpolateImageFunction`" Deleted `Point(nullptr_t)`, especially to avoid `PointType p = 0`.
hjmjohnson
pushed a commit
that referenced
this pull request
Feb 28, 2022
Prevented implicit conversion of a value to `Point`. Aims to avoid possible flaws, like the ones addressed by: Pull request #3225 commit 5b71d63 "BUG: Quick-fix ContourSpatialObject::Update(), LINEAR_INTERPOLATION case" Pull request #3228 commit 12a501c "BUG: Fix `SetCenterInObjectSpace` calls in Registration test" Pull request #3231 commit e4841aa "STYLE: Clarify estimation ray position `RayCastInterpolateImageFunction`" Deleted `Point(nullptr_t)`, especially to avoid `PointType p = 0`.
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.
ContourSpatialObject::Update()appears to have an assignment tonewPoint, in thecase InterpolationMethodEnum::LINEAR_INTERPOLATIONsection, which was meant to assign just a single element
newPoint[d].As was confirmed by Stephen Aylward (@aylward) at issue #3222,
"
ContourSpatialObject<TDimension>::Update()LINEAR_INTERPOLATION casemay need some adjustment".
Some more adjustment may still be needed, as
newPointnow still getsmodified multiply times (rather than just once), before it eventually
gets used.