[MINC-development] Latest MINC 2.0 API documentation

[Leila Baghdadi]

Andrew

The answer to your first question:

we just decided from the beginning to always pass the array length (size) 
along with the array whose bounds are not specified.
If you check other functions in the API, you will see similar structure.

As for getting voxels for dummies, I can not recall if we had any plans, 
perhaps Bert or John can correct me if otherwise but I will add your 
suggestion to the "to discuss list".


Leila


On Mon, 16 Feb 2004, Andrew Janke wrote:

> On Mon, 16 Feb 2004, Robert VINCENT wrote:
> 
> > The latest MINC 2.0 API document is now available at:
> > http://www.bic.mni.mcgill.ca/software/minc2/api_doc/index.html
> >
> > Comments and questions are encouraged, please direct them to me or to the
> > list.
> 
> What's the array_length argument do in miset_real_value?  I can guess but am
> unsure.
> 
> Also are there any plans to support a "getting voxels for dummies" type
> function? (that doesn't require setting up a location[] array with indicies and
> the likes?)
> 
> ie:
> 
>   value = miget_real_value_3D(volume, x, y, z);
> 
> ?  The current implementation whilst nice and general isn't that easy for
> newbies to grok IMHO.
> 
> 
> --
> Andrew Janke   ( rotor@cmr.uq.edu.au || www.cmr.uq.edu.au/~rotor )
> Australia->University of Queensland->Centre for Magnetic Resonance
> W: +61 7 3365 4100  ||  H: +61 7 3800 4042  ||  M: +61 4 2138 8581
> 
> _______________________________________________
> MINC-development mailing list
> MINC-development@bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
> 
>