[MINC-development] nu-correct produces incorrect results, sometimes

[Andrew Janke]

I seem to remember something about N3 having strife with some
combinations of slice scaling...

try this:

mincreshape -float in.mnc out.mnc

nu_correct out.mnc fred.mnc


a

On 5/11/07, Vladimir FONOV <vladimir.fonov at gmail.com> wrote:
> Hello,
>
> On 5/10/07, Andrew Janke <a.janke at gmail.com> wrote:
> > Looks like stratified background noise and/or poor slice normalization to me.
> >
> > Meaning the file conversion is probably off.
>
> So, is there any way of automatically detecting this ? As you can
> imagine this is one of the scans of the young kids. This is how it
> looks after fitting to a model:
> http://www.bic.mni.mcgill.ca/~vfonov/broken_nuc/fitted.jpg
>
>
> --
> Best regards,
>  Vladimir S. Fonov ~ vladimir.fonov <at> gmail.com
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>


-- 
Andrew Janke   (a.janke at gmail.com || http://a.janke.googlepages.com/)
Canberra->Australia    +61 (402) 700 883