Julien Sein
Julien Sein
Hi, I tried the "Syn" procedure for the first time with fmriprep v21.0.2 and couldn't make it work for the 3 subjects I tested. - For these subjects we have...
A test on another dataset with the same command (with other acquisition parameters and less distorsion than the one I presented above) with "Syn" option didn't fail with fmriprep v21.0.2:
Hi again, I went on trying to understand what is going on and I believe that there is a weird interaction between the SBref volume taken as the reference for...
To summarize: the mcflirt behavior (giving a lot of 0 in the motion parameters) seems to be coming from three factors: - subject with actually very low motions: looping through...
I went to plan B for this case of low movers where obviously the motion estimation with the combo mcflirt - SBref - cost function (normcorr) was wrong (too many...
As this strange behavior during HMC seems to be related to mcflirt, data were sent to the FSL mailing list. FSL developers reproduced the bug internally, they are investigating. Meanwhile...
EDIT: qform and sform matrices are fine in my case. Orientation information is totally identical between SBref images and corresponding bold run.
EDIT: FSL team is well aware of this problem, they were able to reproduce the mcflirt behavior with sbref images as target file for motion correction but no solution is...
Must be related to : #1684
I just checked: the problem with mcflirt is not only related to a mismatch between orientation header between the SBref image and the related multiband serie , as it is...