[Insight-users] ANNOUNCEMENT: ITK 3.20 RELEASED !
Andriy Fedorov
fedorov at bwh.harvard.edu
Mon Jul 19 09:33:36 EDT 2010
Luis,
Thank you for the explanation! I will follow this procedure in the future.
For now, I set up monitoring for the bug you submitted, and will fix
Slicer code once it is closed (ie the commit is propagated to 3.20)
AF
On Mon, Jul 19, 2010 at 00:58, Luis Ibanez <luis.ibanez at kitware.com> wrote:
>
> Hi Andriy,
>
>
> You are always welcome to fix bugs in ITK :-)
>
>
> However,
> only the "gatekeeper" can commit code
> to ITK Release Branches.
>
>
> You can certainly commit bug fixes in the
> CVS HEAD.
> (Please do so as often as you can....)
>
> ---
>
> The procedure to do fixes in Release branches
> is the following:
>
> 1) Report bug in MANTIS
> 2) Fix it in ITK CVS HEAD
> 3) Open another but report in MANTIS
> specific to ITK 3.20.
> 4) Assign the bug in (3) to the branch
> gatekeeper (currently me...)
> 5) Gatekeeper checks the fix
> in to the Branch.
> 6) Close but in (3)
>
>
> BTW, currently the bug report described
> in Item (3) is
> http://public.kitware.com/Bug/view.php?id=11008
>
>
>
> This workflow will change as soon
> as we move to Git.
>
> It will actually be a lot more agile and
> distributed. We are counting on Git
> workflows to help us harvest better the
> brainpower of the larger ITK community.
>
>
> Luis
>
>
> -------------------------------------------------------
> On Mon, Jul 19, 2010 at 12:46 AM, Andriy Fedorov <fedorov at bwh.harvard.edu>
> wrote:
>>
>> Luis,
>>
>> Thank you for the quick response! I guess I could fix this myself, but
>> I was not sure what are the rules of committing to the release
>> branch....
>>
>> If you don't forget, please let me know when the update is propagated
>> to 3.20, so that I can update the Slicer code accordingly.
>>
>> AF
>>
>>
>>
>> On Mon, Jul 19, 2010 at 00:42, Luis Ibanez <luis.ibanez at kitware.com>
>> wrote:
>> >
>> > Hi Andi,
>> >
>> > Thanks for reporting this oversight.
>> >
>> > I just committed a fix to the CVS HEAD:
>> >
>> >
>> > http://public.kitware.com/cgi-bin/viewcvs.cgi/Code/Common/itkTransformFactoryBase.cxx?root=Insight&r1=1.7&r2=1.8&sortby=date
>> >
>> >
>> > I will wait to see it Green in the continuous
>> > builds tomorrow, before I commit the same
>> > patch to the ITK 3.20 branch.
>> >
>> > No need to wait until a new release...
>> >
>> > All bug fixes will go into the ITK 3.20 branch,
>> > as we focus on ITKv4.
>> >
>> >
>> > Please let us know if you find any
>> > other problems,
>> >
>> >
>> > Thanks
>> >
>> >
>> > Luis
>> >
>> >
>> > ------------------------------------------------------------
>> > On Fri, Jul 16, 2010 at 2:25 PM, Andriy Fedorov
>> > <fedorov at bwh.harvard.edu>
>> > wrote:
>> >>
>> >> Luis,
>> >>
>> >> It appears that while the new release includes ScaleVersor3DTransform
>> >> in stable Code, this transform is not registered with the
>> >> TransformFactoryBase.
>> >>
>> >> Is this a bug? If yes, can we fix this in 3.20, or this has to wait
>> >> until the next release?
>> >>
>> >> We are using this type of transform in Slicer, and right now we need
>> >> to manually register the transform with the factory, we would like to
>> >> avoid this, since we also need to re-register all the rest of the
>> >> transforms when we add a new one.
>> >>
>> >> Please advice
>> >>
>> >> Andrey Fedorov
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, Jul 15, 2010 at 12:00, <insight-users-request at itk.org> wrote:
>> >> > Message: 2
>> >> > Date: Thu, 15 Jul 2010 09:18:09 -0400
>> >> > From: Luis Ibanez <luis.ibanez at kitware.com>
>> >> > Subject: [Insight-users] ANNOUNCEMENT: ITK 3.20 RELEASED !
>> >> > To: itk <Insight-users at itk.org>, Insight Developers
>> >> > <Insight-developers at itk.org>
>> >> > Message-ID:
>> >> > <AANLkTinR1hYeqYo2bzrMjNIDQ2S4GBbNS59ZxrKd1J1E at mail.gmail.com>
>> >> > Content-Type: text/plain; charset="iso-8859-1"
>> >> >
>> >> > We are pleased to announce the release of
>> >> >
>> >> >
>> >> > ITK 3.20
>> >> >
>> >> >
>> >> > Source files and download instructions are available at
>> >> > http://itk.org/ITK/resources/software.html
>> >> >
>> >> >
>> >> > The list of new files can be found at:
>> >> > http://www.itk.org/Wiki/ITK_Release_3.20
>> >> >
>> >> >
>> >> > The list of changed files can be found at:
>> >> > http://www.itk.org/Wiki/ITK_Release_3.20_Changed_From_Previous
>> >> >
>> >> >
>> >> >
>> >> > Please let us know if you find any problems.
>> >> >
>> >> >
>> >> > Thanks
>> >> >
>> >> >
>> >> > Luis
>> >> > -------------- next part --------------
>> >> > An HTML attachment was scrubbed...
>> >> > URL:
>> >> >
>> >> > <http://www.itk.org/pipermail/insight-users/attachments/20100715/936af08b/attachment-0001.htm>
>> >> >
>> >> > ------------------------------
>> >> >
>> >> > Message: 3
>> >> > Date: Thu, 15 Jul 2010 09:46:15 -0400
>> >> > From: Luis Ibanez <luis.ibanez at kitware.com>
>> >> > Subject: [Insight-users] ITK 3.20 --> ITK 4.0 Transition Plan : ITK :
>> >> > CVS --> Git
>> >> > To: itk <Insight-users at itk.org>, Insight Developers
>> >> > <Insight-developers at itk.org>
>> >> > Message-ID:
>> >> > <AANLkTin1AHPsPB9PKJhqdmD5BplfOeLBy9AqEfZLxfP6 at mail.gmail.com>
>> >> > Content-Type: text/plain; charset="iso-8859-1"
>> >> >
>> >> > As many of you may know, we are working on
>> >> > a major new version of ITK:
>> >> >
>> >> >
>> >> > This will be ITKv4.
>> >> >
>> >> >
>> >> >
>> >> > The main goals for ITKv4 are:
>> >> >
>> >> > (1) Revising,
>> >> > (2) Accelerating,
>> >> > (3) Simplifying and
>> >> > (4) Improving DICOM support in ITK.
>> >> >
>> >> >
>> >> > To that end we have drafted a Transition Plan to go
>> >> > from ITK 3.20 to ITKv4. The current form of this plan
>> >> > is available in the Wiki page:
>> >> >
>> >> > http://www.itk.org/Wiki/ITK_Release_4/Migration_Plan
>> >> >
>> >> >
>> >> > A schematic representation of th plan is available at:
>> >> >
>> >> > http://www.itk.org/Wiki/File:ITKv4-TransitionPlanProposal.png
>> >> >
>> >> >
>> >> >
>> >> > The intermediate Phases of the Transition Plan
>> >> > have been sketched out in
>> >> >
>> >> > http://www.itk.org/Wiki/ITK_Release_4/Migration_Plan/Phases
>> >> >
>> >> > an equivalent document is available at:
>> >> > http://www.itk.org/Wiki/images/5/5c/ITKv4-TransitionPlan-Draft.pdf
>> >> >
>> >> >
>> >> >
>> >> > Please share with us your impression on how
>> >> > the current transition plan may impact your use
>> >> > of ITK.
>> >> >
>> >> >
>> >> > ---
>> >> >
>> >> >
>> >> > At this point, we have executed:
>> >> >
>> >> > * Release of ITK 3.20 : July 15th
>> >> >
>> >> > We are now in the process of:
>> >> >
>> >> > * Porting ITK from CVS to Git.
>> >> >
>> >> > As we move to Git, a lot of effort is being invested
>> >> > in preserving the CVS history.
>> >> >
>> >> > We anticipate that ITK-Git will be settle by the end of July.
>> >> >
>> >> >
>> >> > It is therefore a good moment for you to start learning Git. :-)
>> >> >
>> >> > Resources are available at:
>> >> > http://git-scm.com/documentation
>> >> >
>> >> > We recommend that you start by watching this talk
>> >> > that Linus Torvals gave at Google:
>> >> >
>> >> > http://www.youtube.com/watch?v=4XpnKHJAok8
>> >> >
>> >> > Then follow up with the official Git tutorial
>> >> >
>> >> > http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html
>> >> >
>> >> > ( but, please note that there are many other
>> >> > resources available for learning Git )
>> >> >
>> >> >
>> >> > --
>> >> >
>> >> >
>> >> > We will appreciate any suggestions on how to
>> >> > improve the Transition Plan, and how to minimize
>> >> > the effort that users will have to invest for migrating
>> >> > to ITKv4.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > Thanks
>> >> >
>> >> >
>> >> >
>> >> > Luis
>> >> > -------------- next part --------------
>> >> > An HTML attachment was scrubbed...
>> >> > URL:
>> >> >
>> >> > <http://www.itk.org/pipermail/insight-users/attachments/20100715/7184d3d1/attachment-0001.htm>
>> >> >
>> >> > ------------------------------
>> >> >
>> >> > Message: 4
>> >> > Date: Thu, 15 Jul 2010 15:06:06 +0000 (UTC)
>> >> > From: Matt McCormick <matt at mmmccormick.com>
>> >> > Subject: Re: [Insight-users] ITK 3.20 --> ITK 4.0 Transition Plan
>> >> > :
>> >> > ITK : CVS --> Git
>> >> > To: insight-users at itk.org
>> >> > Message-ID: <loom.20100715T170213-434 at post.gmane.org>
>> >> > Content-Type: text/plain; charset=us-ascii
>> >> >
>> >> > Luis Ibanez <luis.ibanez at ...> writes:
>> >> > Porting ITK from CVS to Git.As we move to Git, a lot of effort is
>> >> > being
>> >> > invested
>> >> > in preserving the CVS history.We anticipate that ITK-Git will be
>> >> > settle
>> >> > by the
>> >> > end of July.
>> >> >
>> >> > Huge commendations for making this change! It is very exciting. It
>> >> > will make
>> >> > doing development with and for ITK much easier.
>> >> >
>> >> > Matt
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------
>> >> >
>> >> > Message: 5
>> >> > Date: Thu, 15 Jul 2010 08:29:37 -0700 (PDT)
>> >> > From: yasser salman <yass71 at yahoo.com>
>> >> > Subject: [Insight-users] Fw: Mesh generation
>> >> > To: Luis Ibanez <luis.ibanez at kitware.com>
>> >> > Cc: insight-users at itk.org
>> >> > Message-ID: <594694.20826.qm at web50601.mail.re2.yahoo.com>
>> >> > Content-Type: text/plain; charset="iso-8859-1"
>> >> >
>> >> >
>> >> >
>> >> > Hi Luis,
>> >> >
>> >> > I have a MRI brain volume, i wanna to do that:
>> >> > 1- Extract the Brain only from the volume.??
>> >> > 2- Segment Brain to Gray / White matter/ ?CFS.? (may be tumor in the
>> >> > future will
>> >> > be considered)
>> >> > 3- Output this segmented volume to FEM (Ansys) .??
>> >> > Could you please let me know the shortcut to do that
>> >> > Regards,
>> >> > Yasser
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > ________________________________
>> >> > From: Luis Ibanez <luis.ibanez at kitware.com>
>> >> > To: yasser salman <yass71 at yahoo.com>
>> >> > Cc: itk <Insight-users at itk.org>
>> >> > Sent: Sun, July 11, 2010 8:27:18 AM
>> >> > Subject: Re: [Insight-users] Mesh generation
>> >> >
>> >> >
>> >> > Hi Yasser,
>> >> >
>> >> > Do you need something more detailed than Skull-removal ?
>> >> >
>> >> > The first thing in MRI will be to evaluate whether
>> >> > you need bias-field correction or not.
>> >> >
>> >> > Please provide more details on what you are trying to achieve.
>> >> >
>> >> >
>> >> > ???? Thanks
>> >> >
>> >> >
>> >> > ?????????? Luis
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------------------------------------------------------
>> >> >
>> >> > On Sun, Jul 11, 2010 at 11:20 AM, yasser salman <yass71 at yahoo.com>
>> >> > wrote:
>> >> >
>> >> > Hi Luis
>> >> >>
>> >> >>?MRI
>> >> >>Yasser
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> > ________________________________
>> >> > From: Luis Ibanez <luis.ibanez at kitware.com>
>> >> >>To: yasser salman <yass71 at yahoo.com>
>> >> >>Cc: itk <Insight-users at itk.org>
>> >> >>Sent: Sat, July 10, 2010 1:08:26 PM
>> >> >>Subject: Re: [Insight-users] Mesh generation
>> >> >>
>> >> >>
>> >> >>?Hi Yasser,
>> >> >>
>> >> > >From what image modality ?
>> >> >>
>> >> >>
>> >> >>????? Luis
>> >> >>
>> >> >>
>> >> >>----------------------------------------
>> >> >>
>> >> >>On Fri, Jul 9, 2010 at 6:43 PM, yasser salman <yass71 at yahoo.com>
>> >> >> wrote:
>> >> >>
>> >> >>Dear Luis,
>> >> >>>i asking for an easy way to segment /extract the whole brain from
>> >> >>> head,
>> >> >>>is it by using threshold tech., depending on histogram?
>> >> >>>Regards ,
>> >> >>>Yasser
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > -------------- next part --------------
>> >> > An HTML attachment was scrubbed...
>> >> > URL:
>> >> >
>> >> > <http://www.itk.org/pipermail/insight-users/attachments/20100715/5024a9ce/attachment-0001.htm>
>> >> >
>> >> > ------------------------------
>> >> >
>> >> > _______________________________________________
>> >> > Insight-users mailing list
>> >> > Insight-users at itk.org
>> >> > http://www.itk.org/mailman/listinfo/insight-users
>> >> >
>> >> >
>> >> > End of Insight-users Digest, Vol 75, Issue 26
>> >> > *********************************************
>> >> >
>> >
>> >
>
>
More information about the Insight-users
mailing list