[WIP] ENH: Apply 9 DOF alignment in T1 merge #473
Closed
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
|
This is interesting: which of the two T1s is the reference? While the first 6 parameters are equivalent between registration directions (i.e. which T1 is the reference), the scaling parameters (the 3 between 6 and 9) are not. Maybe we need a subject-template space at the midpoint of all transforms. |
|
So we're not actually using 9-DOF, we moved to #481 put in machinery that I think shouldn't be too hard to adapt to an unbiased template (see discussion). |
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.
Moves to using merged and conformed T1 as basis for FreeSurfer reconstruction, rather than raw T1w images.
Fixes #439.