Thank you for your explanation. I have a little bit confused. As the third
way of registration you mentioned, why could we simply apply the motion
correction for fMRI volume data and align to T1 image with bbr, then
project to fs32k native surface as one step registration, couldn't we? If
not, how
This is a good point and something we thought about at the time. The reason we did it this way was to avoid having to generate two separate volume timeseries files (making these is by far the most time-consuming part of the fMRIVolume pipeline). We would
have had to make one that was fully
