Open tsalo opened 4 years ago
@marcelzwiers wrote:
This information is already stored in the NIfTI header
You mean in pixdim4? True but kind of cumbersome to read, and the standard tools and libraries can't do it
@effigies wrote:
I would recommend entirely removing this field in order to minimize ambiguity.
I would oppose this on the grounds that TR may not be constant (see VolumeTiming), in which case pixdim4 is insufficient metadata.
RepetitionTime is mutually exclusive with VolumeTiming, so I don't see that as problematic.
Also, what tools have problems with pixdim4?
In general, the NIfTI and BIDS headers store mutually independent information, which prevents issues of precedence for conflicting information.For most MR sequences, RepetitionTime and pixdim4 are the same. I also commented on this during the development of BIDS. One major reason for storing this is that SPM would not retain pixdim4. Therefore, if SPM was used at any time to modify a NIfTI image, the resulting image would no longer include pixdim4. Therefore, the inclusion of RepetitionTime for BIDS had strong pragmatic motivation.
This information is already stored in the NIfTI header (as the current field description seems informed of). Apparently this field isn't intended to override the header either (which would have been a bad idea anyway), so it's basically useless data duplication, with all the potential inconsistency issues that brings. I would recommend entirely removing this field in order to minimize ambiguity.
Original authors: Unknown