<br>Hi Alex,<br><br>Your point is well taken.<br><br>We certainly rely on user's feedback in order to <br>move contributions from the Insight Journal into<br>the toolkit.<br><br>The process is describe here:<br><a href="http://www.itk.org/Wiki/ITK_Procedure_for_Contributing_New_Classes_and_Algorithms">http://www.itk.org/Wiki/ITK_Procedure_for_Contributing_New_Classes_and_Algorithms</a><br>
<br><br>The first thing you can do to help is to write<br>a review for this paper, and emphasize that<br>you found the code to be useful.<br><br><br>Yet another way to help is to join the developers<br>team, by signing up for:<br>
<br><a href="http://www.itk.org/Wiki/ITK#Adopt-A-Bug_2.0">http://www.itk.org/Wiki/ITK#Adopt-A-Bug_2.0</a><br><br>At which point you could move this algorithm<br>into ITK by yourself (in coordination with other<br>developers, of course).<br>
<br><br>We are actively looking for new developers <br>and we appreciate all the help that we can get.<br><br><br>See "Opening Open Source"<br><a href="http://www.kitware.com/blog/home/post/13">http://www.kitware.com/blog/home/post/13</a><br>
<br><br>By getting involved as a developer you help <br>ensure that ITK will continue providing the <br>functionalities that you need.<br><br>Give it a try !<br><br>Joining is easy:<br><a href="http://www.itk.org/Wiki/ITK_10th_Anniversary_Activities/Adopt-A-Bug_2.0#Adoption_Paper_Work">http://www.itk.org/Wiki/ITK_10th_Anniversary_Activities/Adopt-A-Bug_2.0#Adoption_Paper_Work</a><br>
<br><br> Regards,<br><br><br> Luis<br> <br><br>----------------------------------------------------------------<br><div class="gmail_quote">On Tue, Apr 27, 2010 at 3:05 PM, Oleksandr Dzyubak <span dir="ltr"><<a href="mailto:adzyubak@gmail.com">adzyubak@gmail.com</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;"><br>
Dear colleagues,<br>
<br>
This email was inspired by my recent upgrade to ITK 3.18<br>
that caused some my algorithms stopped working<br>
whereas the other started working incorrectly.<br>
<br>
Ultimately I figured out that partly the reason for this is that<br>
whenever the community and developers find some<br>
work around or the bug fix, I just overwrite the headers and templates<br>
and still keep "old" release. Bad practice.<br>
<br>
That is exactly what happened to the "BinaryThinning" algorithm.<br>
Couple years ago I tested the "Implementation of a 3D thinning algorithm"<br>
by Hanno Homann (<a href="http://hdl.handle.net/1926/1292" target="_blank">http://hdl.handle.net/1926/1292</a>).<br>
It worked so great that I just carelessly overwrote<br>
the release in-stock "BinaryThinning" algorithm<br>
and happily used that algorithm for couple years.<br>
<br>
Since I did not have any doubts that this algorithm is now<br>
a native part of the ITK library, I was surprised very much<br>
when found that my programs do not work anymore after<br>
I made upgrade to ITK-3.18. And it took a while before I understood why.<br>
<br>
Surprisingly the algorithm by Hanno Homman did not get into 3.18.<br>
Which is more, still there is no even a review /request for that algorithm.<br>
<br>
How do the algorithms get into the ITK library?<br>
Is that the review which initializes the process?<br>
Can I promote the algorithm by writing a review?<br>
<br>
Regards,<br>
<br>
Alex<br>
<br>
</blockquote></div><br>