Fix profile access in groupwise registration #444
Merged
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
Update profile access for the registration group to use the b-spline registration parameter map.
Only crop the input images if truncation images are loaded.
- Update docstring - Trim trailing spaces
The direction may not be transferable, such as directions generated from groupwise registration. Simply catch these exceptions and leave the default direction.
yoda-vid
force-pushed
the
fix_groupwise_reg
branch
from
b091b6b to
623976c
Compare
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.
This PR fixes groupwise registration for updates to the atlas profile structure. Cropping is also now optional since it was for a specialized case, now only applied when a truncated labels image is present.
As mentioned in #438, the current SimpleITK/SimpleElastix release lost support for groupwise registration. See #438 (comment) for a potential workaround.