[MINC-users] MINC and ITK

[Rupert Brooks]

Hi Leila,

It would be great to bring ITK support for MINC into the mainstream.
Back in 2008 Andrew Janke and I looked at tests for this class - there
were a number of issues relating to orientation, etc, detailed here.
This might make a good start for a solid unit test.

http://public.kitware.com/Bug/view.php?id=6038

Regards,
Rupert




--------------------------------------------------------------
Rupert Brooks
rupert.brooks at gmail.com




On Sun, Jun 5, 2011 at 09:12, Luis Ibanez <luis.ibanez at kitware.com> wrote:
> Hi Leila,
>
> As you already pointed out,
> the MINCImageIO code is currently in
>
>             ITK/Modules/Nonunit/Review
>
> Here are the ITK plans for relocating the
> code that is currently in the Review directory:
> https://spreadsheets.google.com/a/kitware.com/spreadsheet/ccc?key=0ApfVzIsZe0VFdFUxdE95WE5kMVE4LTJ6b3ZYQnpRalE&hl=en_US#gid=0
>
> Should you provide an updated version
> of the MINCImageIO classes, it will replace
> the one currently in Nonunit/Review, and
> later this year will be moved to IO/MINC.
>
> Depending on how extensive the changes are,
> you could use the IJ mechanism or a Gerrit
> patch mechanism.
>
> The Gerrit patch is the easiest way to bring
> the changes into ITK if they happen to be
> rather small changes on existing code.
>
> The Insight Journal will be more appropriate
> for large modifications or for fully new code.
>
>
> Thanks for contributing this code to ITK.
>
>
>    Luis
>
>
> ---------------------------------------------------------------
> On Fri, Jun 3, 2011 at 1:23 PM, Leila Baghdadi <baghdadi at phenogenomics.ca>wrote:
>
>> Hi Michel
>>
>> not sure I follow?
>> I got a recent version of itk tree and noticed that the code was in nonunit
>> directory, I was under the assumption that it will be either removed or
>> replaced with a new version from insight journal (not correct?)
>>
>> Leila
>>
>> ----- Original Message -----
>> From: Michel Audette <michel.audette at kitware.com>
>> Sent: Fri, 6/3/2011 1:03pm
>> To: MINC users mailing list <minc-users at bic.mni.mcgill.ca>
>> Subject: Re: [MINC-users] MINC and ITK
>>
>> Hi Leila,
>>
>> just checking whether you've discussed this on the ITK users list. If you
>> need help with the Insight Journal entry, which is the usual method for ITK
>> acceptance, let me know.
>>
>> Best wishes,
>>
>> Michel
>>
>> On Fri, Jun 3, 2011 at 12:12 PM, Leila Baghdadi
>> <baghdadi at phenogenomics.ca>wrote:
>>
>> >
>> >
>> > ----- Original Message -----
>> > From: Leila Baghdadi <baghdadi at phenogenomics.ca>
>> > Sent: Fri, 6/3/2011 12:00pm
>> > To: MINC development discussion & planning <
>> > minc-development at bic.mni.mcgill.ca>
>> > Subject: Re: [MINC-development] MINC and ITK
>> >
>> > Hi everyone,
>> >
>> > Just thought of sending an update to the minc community regarding support
>> > for MINC in ITK.
>> >
>> > My code (ITKMINC2IO) (originally written in 2008 and not maintained,
>> blame
>> > it on maternity leave(s)!), can only support MINC2 files and right now
>> > requires work as various things have changed in ITK since then,
>> >
>> > I am in the process of rewriting some parts of the above, and will
>> resubmit
>> > a new version to the ITK-journal once I have it completed! (I do want to
>> > resubmit this code as it makes exclusive minc2 api calls )
>> >
>> > meanwhile,
>> >
>> > The code of Vladimir (EZminc), can read both formats and is much more
>> > up-to-date,
>> >
>> > Please send me any questions or concerns
>> >
>> > Leila
>> >
>> > ----- Original Message -----
>> > From: Andrew Janke <a.janke at gmail.com>
>> > Sent: Sun, 5/15/2011 8:29pm
>> > To: MINC development discussion & planning <
>> > minc-development at bic.mni.mcgill.ca>
>> > Subject: Re: [MINC-development] MINC and ITK
>> >
>> > > That's my understanding as well - we (us Toronto folks, that is), seem
>> to
>> > be the happiest in the MINC community to discard MINC1 compatibility,
>> >
>> > Pick me too!  I have been MINC2 only for at least the last 3 years,
>> > the impending MINC2.2 release will finally drive the final nail in the
>> > MINC1 coffin. The default will be to write out MINC2 files
>> > irrespective of what the input was.  I don't plan to add a -1 flag to
>> > all the binaries to write out MINC1 and instead will only add a -1
>> > flag to mincconvert for the sticklers.
>> >
>> > For those asking why, I have had requests for this from users none of
>> > whom were from the BIC!  Perhaps I should open a separate thread about
>> > this on minc-dev but expect to see my commits for this on github
>> > shortly.
>> >
>> >
>> > a
>> > _______________________________________________
>> > MINC-development mailing list
>> > MINC-development at bic.mni.mcgill.ca
>> > http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>> > _______________________________________________
>> > MINC-development mailing list
>> > MINC-development at bic.mni.mcgill.ca
>> > http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>> > _______________________________________________
>> > MINC-users at bic.mni.mcgill.ca
>> > http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
>> >
>>
>>
>>
>> --
>> Michel Audette, Ph.D.
>> R & D Engineer,
>> Kitware Inc.,
>> Chapel Hill, N.C.
>> _______________________________________________
>> MINC-users at bic.mni.mcgill.ca
>> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
>> _______________________________________________
>> MINC-users at bic.mni.mcgill.ca
>> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
>>
> _______________________________________________
> MINC-users at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
>