Support repetition time stored in BIDS AFI B1-mapping sidecar file #62
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
Warning: this also requires giving the input AFI data in the opposite order for the legacy method (the order is now more logical and matches the order of TRs in the alTR array)
added 8 commits
June 2, 2023 23:09
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.
Added support for BIDS-ified data which specifies separate
RepetitionTimes in the sidecar metadata of each AFI volume.The toolbox was written based on data where (because of sequence restrictions) the
RepetitionTimemetadata fields were always the same for the two separate AFI volumes, which were really recorded with two differentRepetitionTimes. The legacy solution to this was to read theRepetitionTimes from a Siemens DICOM field (alTR), which is preserved if the hMRI toolbox conversion is used.Under the assumption that BIDS will drive solutions to enable saving two separate
RepetitionTimes (either in the sequence or during the DICOM to NIfTI conversion), the toolbox now checks whether the two TRs are different, and if they are, uses them rather than the legacy method.Backwards compatibility warning
This pull request will break backwards compatibility with some scripts. It requires the input AFI data to be given in the opposite order to previously when using the legacy method. Note that this new order is more logical and matches the order of
RepetitionTimes in thealTRarray.Following a previous pull request, a warning should be printed if the toolbox detects that reversing the data order would improve the quality of the B1 map.
If the data are BIDS-compliant and specify a different
RepetitionTimein each sidecar file, then the order will not matter.