yes, the easiest thing to do would be to reslice one like the other then
register and average them (-rl in mri_convert)
On Wed, 18
Jan 2017, Alex Cohen wrote:
yes. If you try to feed them both to recon-all, it errors out due to
dimension mismatch (lines 939+) so I presume I'd have to do it fi
yes. If you try to feed them both to recon-all, it errors out due to
dimension mismatch (lines 939+) so I presume I'd have to do it first,
unless there is an expert-pref to do this.
-Alex
Alexander Li Cohen, M.D., Ph.D.
E-mail: ale
average what? The different voxel size images?
On Wed, 18 Jan 2017, Alex Cohen wrote:
I will likely end up running each separately on several subjects to get a
handle on how they're behaving; however assuming I did what to average them,
have you all found a particular method more useful than a
I will likely end up running each separately on several subjects to get a
handle on how they're behaving; however assuming I did what to average
them, have you all found a particular method more useful than another for
this?
i.e., mri_robust_register, bbregister, etc...
-Alex
--
Hi Alex
you get to decide whether to average your data or not. It's a totally
empirical question which one is better - why don't you run them each and
visually inspect the results?
cheers
Bruce
On Wed, 18 Jan 2017, Alex Cohen wrote:
Hi all, What is the current best practice recommendation f
Hi all,
What is the current best practice recommendation for using multiple T1s
and/or T2s for recon-all where the sizes of the images are slightly
different.
For instance: two T1w images of 0.9x0.9x0.9 and 1x1x1 resolution, however
the 1x1x1 image seems to have better grey-white separation, etc.
