Some fMRI studies will not acquire one SBRef for every multiband BOLD scan (this is probably true for DWI too, and thus bids-standard/bids-specification#239).
Currently, the task-Name entity needs to be defined for SBRefs. Doing it optional, would allow the following:
Where, by the inheritance principle, sub-3010_sbref.nii.gz is intended for all tasks but rest because a particular sbref exists for that one.
Additionally, I propose to allow defining the IntendedFor metadata for SBRefs, so the same behavior can be implemented without missing the provenance about what task was acquired closest to the sbref, e.g.:
Related to bids-standard/bids-specification#239.
Some fMRI studies will not acquire one SBRef for every multiband BOLD scan (this is probably true for DWI too, and thus bids-standard/bids-specification#239).
Currently, the
task-Name
entity needs to be defined for SBRefs. Doing it optional, would allow the following:Where, by the inheritance principle,
sub-3010_sbref.nii.gz
is intended for all tasks butrest
because a particularsbref
exists for that one.Additionally, I propose to allow defining the
IntendedFor
metadata for SBRefs, so the same behavior can be implemented without missing the provenance about what task was acquired closest to the sbref, e.g.:where
sub-3010_task-discountFix_run-1_sbref.json
has anIntendedFor
field: