[MINC-users] mincaverage -avgdim result header

[Leila Baghdadi]

Hi guys,

To my knowledge there is no need to make HDF5 calls to "use" minc2, as the minc2 API functions will take care of that for you. I have written different software that uses minc2 and never had to go down to hdf5 layer, however, I have added more functionality to minc2 (HDF5 calls) if I discovered there was a need for a functionality which was not accounted for but this was one or two cases.
I would say that we certainly meant to keep the level of encapsulation of minc2 to be very similar to minc1.
 If you are referring to backward compatibility, last I recall, it is provided by a module which emulates a restricted subset of NETCDF calls.

and finally, I am sorry to say that documentation is nowhere near what it should be!
perhaps one day :)

one of the minc2 souls

----- Original Message -----
From: Peter Neelin <peter.neelin at gmail.com>
Sent: Tue, 3/27/2012 12:45am
To: MINC users mailing list <minc-users at bic.mni.mcgill.ca>
Subject: Re: [MINC-users] mincaverage -avgdim result header

On Mar 26, 2012 11:02 PM, "Peter Neelin" <peter.neelin at gmail.com> wrote:
> As I understand it, HDF5 provides a netcdf interface. That's how minc
works with it.

Looks like I got that wrong. HDF3 provided a netcdf interface. Looks like
they took it out in HDF4 and HDF5 and some kindly soul (Leila?) wrote a
complete wrapper layer. Perhaps someone with some knowledge can provide
details. So I don't know if the netcdf concepts are reflected in the HDF5
format or only in the wrapper layer... Is there any documentation for this
stuff now?

Peter
--
Peter Neelin
peter.neelin at gmail.com
_______________________________________________
MINC-users at bic.mni.mcgill.ca
http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users