[MINC-users] Determining memory usage for minctracc calls

[Gabriel A. Devenyi]

I can't offer an answer, but I wonder whether Valgrind (http://valgrind.org/)
could be used to analyze the memory usage as a function of the input
parameters to create some kind of lookup table?

-- 
Gabriel A. Devenyi B.Eng. Ph.D.
Research Computing Associate
Computational Brain Anatomy Laboratory
Cerebral Imaging Center
Douglas Mental Health University Institute
McGill University
t: 514.761.6131x4781
e: gdevenyi at gmail.com

On Mon, Jun 8, 2015 at 3:45 PM, Matthijs van Eede <matthijs at mouseimaging.ca>
wrote:

> Hi all,
>
> We are trying to determine/estimate how much memory a minctracc call will
> use depending on the file resolution, number of voxels and the step size
> used in the minctracc call. So far we have not been able to fit the memory
> data we've gathered in a way that can predict memory usage for a wide range
> of input resolutions.
>
> One of the things we realized is that minctracc uses (at least one) memory
> saving strategy: if a mask is provided for the registration, the bounding
> box for the region of interest is determined, and only that volume is used
> for the actual registration. Does any know of any other memory saving
> strategies that minctracc uses? Or is there anyone who might have an
> intuition on how the memory usage should vary on file size and step size /
> resolution?
>
> Thanks in advance,
> Matthijs
> _______________________________________________
> MINC-users at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
>