FIX: Immediately fix headers of AFNI outputs #818
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
effigies
force-pushed
the
fix/afni_shield
branch
from
5d7e531
to
828d42a
Compare
effigies
force-pushed
the
fix/afni_shield
branch
from
94dea67
to
e10ea77
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.
As noted in #743, AFNI doesn't believe in NIfTI headers. #807 introduced a bug by targeting an antsApplyTransform at an image with an AFNI-corrupted header.
Fortunately, every AFNI tool we use doesn't change the affine space, so we can overwrite the qform/sform with the original affine. This change adds/moves header correction to immediately after each AFNI process.