What would you like to see added in fMRIPrep?
bbregister strongly assumes that there is a subject directory to look up white matter surfaces, thickness metrics, and possibly other files. We should enumerate which files are actually used, and create these in the scratch directory. This allows us to accept pre-computed GIFTI files and still perform boundary-based registration, which is better than the FSL approximation. Thus instead of threading subject directory/id through functional workflows, we only need to pass the actual GIFTIs.
Another approach being explored by @HippocampusGirl is to convert GIFTI to the format expected by FLIRT's bbregister implementation.
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
No response
What would you like to see added in fMRIPrep?
bbregister strongly assumes that there is a subject directory to look up white matter surfaces, thickness metrics, and possibly other files. We should enumerate which files are actually used, and create these in the scratch directory. This allows us to accept pre-computed GIFTI files and still perform boundary-based registration, which is better than the FSL approximation. Thus instead of threading subject directory/id through functional workflows, we only need to pass the actual GIFTIs.
Another approach being explored by @HippocampusGirl is to convert GIFTI to the format expected by FLIRT's bbregister implementation.
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
No response