Closed
Conversation
…lation, rigid, and full affine transforms.
Contributor
Author
|
Superseded by #81 |
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
1 participant
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 expands our QuadDIRECT registration backend to include translations (sub-pixel) and general affine transformations in addition to rigid transforms. This gets us closer to feature parity with registration packages such as ANTs. Optimization of the full affine transform in 3D (12 parameters) is quite slow but still may be useful. Note that the tests sometimes fail, and it's usually due to one of the errors I reported in timholy/QuadDIRECT.jl#8.
As an aside, two other features that would get us pretty close to feature parity with ANTs are the ability to use restriction "pyramids" with any algorithm and the ability to choose a mutual information-based metric in addition to our intensity-based metric.