[MINC-development] MINC2 file with floating-point voxels and slice normalization
Vladimir S. FONOV
vladimir.fonov at gmail.com
Sat Jan 19 09:13:28 EST 2013
Hello,
I think these relics of the past have to go, right now it takes much more
time to extract the right slice from the dataset (especially if it is a
histological volume located on NFS server) then actually dynamically
calculating min and max range of the memory buffer.
On Sat, Jan 19, 2013 at 12:06 AM, Peter Neelin <peter.neelin at gmail.com>wrote:
> On Jan 18, 2013 4:48 PM, "Andrew Janke" <a.janke at gmail.com> wrote:
>
> > Isn't this done by the valid min and max for the file? I'll have to
> look at the register and Display code again.
>
> The valid min/max give the range for the entire file. The image min/max
> variables allow it to be specified by image (or frame, or other dimensions
> of interest).
>
> Peter
> --
> Peter Neelin
> peter.neelin at gmail.com
>
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>
>
--
Best regards,
Vladimir S. Fonov ~ vladimir <dot> fonov <at> gmail <dot> com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.bic.mni.mcgill.ca/pipermail/minc-development/attachments/20130119/e82cd446/attachment.html>
More information about the MINC-development
mailing list