[MINC-development] MINC 2 - re transitioning from MINC 1

[Jason Lerch]

.  I'm
> curious if anyone out there actually writes code for libminc2?  Are  
> they
> expecting that people will happily go convert all their data?

Yup. And yup. Begone, ICVs!. The transition is quite painless - a  
single command during which no data or headers are lost - and since  
all the tools can work on minc2 files after a simple recompile (or  
so's the theory, which so far is holding true in practice), this  
really isn't that bad a deal.

> We have
> terabytes of data - converting it all would be fairly complicated, to
> put it mildly.  Not to mention, that even had we converted it all, as
> soon as someone runs a minc tool, odds are we'll have minc1 files  
> again

That default is easily changed. Moreover, the minc tools produce  
output files based on what the inputs where. So, given two input  
minc2 files, for example, mincmath should produce an output minc2  
file as well.

I'll let Bert and/or Leila speak to the design decisions ...

Jason

>
>
> I have to wonder what prompted these design decisions - am I missing
> some fundamental truth, or is libminc2 really meant to look good  
> but not
> be used?  Are there any sites actually using minc2?  Are they actually
> adding -2 options to *every* command, or are they really just running
> MINC 2.x but only using the minc1 file format?  If the latter, then
> what's the point of MINC 2.x?
>
> Cheers,
> J
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development