[MINC-development] MINC 2.0 draft

[Leila Baghdadi]

Hi everyone

Peter I read your mail and I believe you have actually explained some of 
the very important points infact believe it or not a couple of points are now 
clear to me


1) NetCDF versus HDF, I agree that it is at least worth investigating and 
because I myself am very curios to understand how it works (at least on an 
abstract level), I will look into it myself. I know that in 98 they 
introduced HDF5 which was motivated by some of the limitations of HDF 
itself such as no support for files larger than 2 GB.

2) as for compression and NetCDF, they have made a point that it is 
possible and not optimal but no reasons at least to the extend of my 
readings. mysterious NetCDF In or out?


3) I believe you have raised an important issue and explained it very 
clearly. Perhaps, the option of lots of memory is infact something we are 
trying to avoid to begin with so we have to come up with a good strategy 
for file-writing.

4) My understanding is that 2N-1 is the number we found out for the 
blocking scheme. Apart from less number of pointers in C , I am not 
sure what else I can comment on right now. maybe john can come up with a 
better explanation.


5) Believe it or not, we have been having the same discussion about 
SetVoxel() using the wavelet compression and came up with some ridiculously 
huge number. We are still not sure if wavelets are worth pursuing!!


6) This is also one of those points where further investigation might be a 
good idea.  I am specially very curious about the computation cost.



7) I was not aware that volume_io does not handle vector data very well 
but I think maybe it is not a bad idea to have a new version of volume_io 
without this limitations. 


I also like the idea of an API definition. I think it will simplify things 
and make our development process faster which is one of our main 
priorities. Hopefully we can come up with a rough draft before the 
meeting!



Thanks


Leila