[MINC-development] Draft API for MINC 2.0

[Leila Baghdadi]

Hi Rick

Perhaps you are right about the naming convention but we are trying very 
hard to keep everything backwards compatible with original minc1.0 so we 
thought it is best to call it minc still so people have no confusion about 
what happens to minc1.0 file format once minc2.0 is in use.

thanks

Leila

 
On Tue, 17 Jun 2003, Rick Hoge wrote:

> 
> >> Is there a gentler introduction that outlines the concepts and
> >> data types?  For instance, what is a "group"?  What is the "path"
> >> argument that many functions take?  Is this api layered on top of
> >> hdf5?  If so, is it necessary to understand it to read the new api
> >> document?
> >
> > The plan is to have a top level document explaining the concepts, but
> > it hasn't been written yet -- partly because some of the concepts are
> > still fluid.  With respect to layering, the plan is as follows.
> >
> > HDF5 is the bottom level layer which the programmer never sees or
> > requires the documentation.  The old libminc API is present with as 
> > much
> > of its functionality retained as is consistent with the new libminc
> > API (i.e. almost all of it).  The new libminc API is what our new
> 
> Will it still make sense to call it Medical Image NetCDF (MINC) when 
> it's based on HDF?
> 
> ______________________________________
> Richard D. Hoge, Ph.D.
> Instructor, HMS Department of Radiology
> A. A. Martinos Center for Biomedical Imaging
> 149 13th St.
> Charlestown MA 02129
> phone 617-726-6598
> fax    617-726-7422
> ______________________________________
> 
> _______________________________________________
> MINC-development mailing list
> MINC-development@bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
> 
>