Hi
No this is unrelated to these options. This suggests that probably some slices haven’t been processed successfully (e.g. due to memory requirements). If you look into the log files you should be able to find this information. If you are unsure, feel free to zip the files and send it to us to have a look.
Cheers
Stam
> On 20 Apr 2016, at 21:43, Amy Zheng <[log in to unmask]> wrote:
>
> Hi all,
>
> For those of you who use the HCP dataset and have run bedpostx with -n 3 -model 3 -g --rician options as recommended by the HCP tutorial, have you encountered the problem where the bedpostx outputs result in a different image size as the input data? In my case, dim3 is changed.
>
> For example:
> fslinfo subject.Bedpostx/merged_f1samples.nii.gz
> dim1 145
> dim2 174
> dim3 140
>
> Whereas, fslinfo subject.Bedpostx/nodif_brain_mask.nii.gz
> dim1 145
> dim2 174
> dim3 145
>
> This issue is seen in a majority of the subjects I have run. I wonder if it has to do with the -g or --rician options? I guess reslicing the bedpostx outputs to match the original dimensions is the way to correct for this now?
>
> Thanks,
> Amy
|