You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For derivatives, I think it makes sense to introduce CIFTI-2 and GIFTI files, along with their extensions (e.g., .dtseries.nii, .surf.gii) to establish these as acceptable file types. We could use a limited subset, if there are some that are never seen in practice and we don't want to endorse without a use-case, or we could just say "If it follows these specs, then it must be fine".
Thoughts? Any other file types to consider?
The text was updated successfully, but these errors were encountered:
Your idea
In https://bids-specification.readthedocs.io/en/stable/02-common-principles.html#file-formation-specification we define NIfTI, TSV and JSON as generally valid extensions.
For derivatives, I think it makes sense to introduce CIFTI-2 and GIFTI files, along with their extensions (e.g.,
.dtseries.nii
,.surf.gii
) to establish these as acceptable file types. We could use a limited subset, if there are some that are never seen in practice and we don't want to endorse without a use-case, or we could just say "If it follows these specs, then it must be fine".Thoughts? Any other file types to consider?
The text was updated successfully, but these errors were encountered: