Skip to content

BUG: TubeSpatialObject normals not unit vectors - #1972

Merged
aylward merged 2 commits into
InsightSoftwareConsortium:masterfrom
aylward:PointBasedSpatialObjects
Sep 1, 2020
Merged

BUG: TubeSpatialObject normals not unit vectors#1972
aylward merged 2 commits into
InsightSoftwareConsortium:masterfrom
aylward:PointBasedSpatialObjects

Conversation

@aylward

@aylward aylward commented Aug 31, 2020

Copy link
Copy Markdown
Member

TubeSpatialObject::ComputeTangent(s)AndNormals() would result in
certain normals not being unit vectors. This fixes and tests for
those errors.

COMP: Fixes a spelling mistake in ComputeTangentAndNormals by
making Tangents plural, as it should be. This function is primarily
used by internal methods so chances of breaking backward compartibility
are slim.

PR Checklist

  • No API changes were made (or the changes have been approved)
  • No major design changes were made (or the changes have been approved)
  • Added test (or behavior not changed)
  • Updated API documentation (or API not changed)
  • Added license to new files (if any)
  • Added Python wrapping to new files (if any) as described in ITK Software Guide Section 9.5
  • Added ITK examples for all new major features (if any)

Refer to the ITK Software Guide for
further development details if necessary.

TubeSpatialObject::ComputeTangent(s)AndNormals() would result in
certain normals not being unit vectors.  This fixes and tests for
those errors.

COMP: Fixes a spelling mistake in ComputeTangentAndNormals by
making Tangents plural, as it should be.  This function is primarily
used by internal methods so chances of breaking backward compartibility
are slim.

@dzenanz dzenanz left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good on a glance. I guess you forgot to rename one invocation place:

Examples/SpatialObjects/TubeSpatialObject.cxx:138:9: error: no member named 'ComputeTangentAndNormals' in 'itk::TubeSpatialObject<3, itk::TubeSpatialObjectPoint<3> >'; did you mean 'ComputeTangentsAndNormals'?

Examples/SpatialObjects/TubeSpatialObject.cxx:138:9: error: 'using ObjectType = class itk::TubeSpatialObject<3u> {aka class itk::TubeSpatialObject<3u>}' has no member named 'ComputeTangentAndNormals'; did you mean 'ComputeTangentsAndNormals'?

Missed one call that needed to be updated to use the corrected spelling.
@aylward

aylward commented Sep 1, 2020

Copy link
Copy Markdown
Member Author

@dzenanz - thanks for catching that! Fixed! If approved, I would squash and merge.

@dzenanz

dzenanz commented Sep 1, 2020

Copy link
Copy Markdown
Member

Yes, please squash.

@aylward
aylward merged commit bc0d6ad into InsightSoftwareConsortium:master Sep 1, 2020
hjmjohnson pushed a commit to hjmjohnson/ITK that referenced this pull request May 6, 2026
…rtium#1972)

* BUG: TubeSpatialObject normals not unit vectors

TubeSpatialObject::ComputeTangent(s)AndNormals() would result in
certain normals not being unit vectors.  This fixes and tests for
those errors.

COMP: Fixes a spelling mistake in ComputeTangentAndNormals by
making Tangents plural, as it should be.  This function is primarily
used by internal methods so chances of breaking backward compartibility
are slim.
hjmjohnson pushed a commit to hjmjohnson/ITK that referenced this pull request May 12, 2026
…rtium#1972)

* BUG: TubeSpatialObject normals not unit vectors

TubeSpatialObject::ComputeTangent(s)AndNormals() would result in
certain normals not being unit vectors.  This fixes and tests for
those errors.

COMP: Fixes a spelling mistake in ComputeTangentAndNormals by
making Tangents plural, as it should be.  This function is primarily
used by internal methods so chances of breaking backward compartibility
are slim.
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