Fix get slice range #3325
Merged
Fix get slice range #3325
Conversation
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
…lume VolumeMapper is expecting getProperties() to return a non-empty array
…orientation matrix getBounds() rotates the extent, however it produces new corner points. Those new corner points were used to compute the slice range along the slice normal . Instead we keep the original extent corner points to apply the image direction along the slice normal.
finetjul
force-pushed
the
fix-getSliceRange
branch
from
406afd8 to
3809dd2
Compare
|
🎉 This PR is included in version 34.11.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Context
When a vtkImageData had a rotation/direction matrix, getSliceRange was "too wide".
Results
getSliceRange is now better fitting the image data bounds.
Changes
PR and Code Checklist
npm run reformatto have correctly formatted codeTesting