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