<div dir="ltr"><div>And few more details copied from <a href="http://www.kitware.com/blog/home/post/184">http://www.kitware.com/blog/home/post/184</a><br><br>"What You Can Find on a Migration Post<br><br>Each change made by a developer is linked to a file explaining the change. The Migration Guide formats this file and displays the following information:<br>
<br> A detailed description of the API change<br> Examples of the previous and the new way to use the API<br> A list of the modified files in the ITK Library and related changes<br> A link to the Gerrit patch which contains additional information regarding the validation of the change, and the development discussion that led to the modification<br>
"<br><br>"The Migration Guide uses a powerful search system that enables users to
find the information they need. The website also uses dynamic tools for
communicating with the search engines, allowing the information to be
available in their search results."<br><br></div><div>Hth<br></div><div>Jc<br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Nov 15, 2013 at 3:30 AM, Jean-Christophe Fillion-Robin <span dir="ltr"><<a href="mailto:jchris.fillionr@kitware.com" target="_blank">jchris.fillionr@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi Harri, <br><br></div>In case you didn't see it, you should consider reading the migration guide. <br>
<br>See <a href="http://itk.org/migrationv4/" target="_blank">http://itk.org/migrationv4/</a><br><br>
</div>Hth<br></div>Jc<br><div><div><br> <br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Fri, Nov 15, 2013 at 3:17 AM, Harri Pölönen <span dir="ltr"><<a href="mailto:hapapo@gmail.com" target="_blank">hapapo@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><br><div>Hi all!</div><div><br></div><div>We have a pretty big medical software which is originally created using ITK 3.20. Now we are interested in upgrading it to use the newest ITK version. We mainly use functions related to 3D volume processing (affine transformation etc) and data input/output. There are some new nice features in ITK4 that we want to use, such as MRI bias correction.</div>
<div><br></div><div>I already tried simply replacing the old ITK with the current one (4.4.2) and rebuilding everything from the source codes, but that didn't work (not that I even expected it to work this way). There seem to be some now obsolete functions/methods in ITK 3.2 and other issues I just need go through and fix one by one manually. </div>
<div><br></div><div>However, before I start editing our software I would be grateful to hear any advice and other experiences about similar job. Our software contains about 400 C++ files and 200 000+ lines of code (not including ITK code), so there will be a lot of work to do with this upgrade. Specifically I would like to hear comments on the following questions:<br>
</div><div><br></div><div> x How much work is expected? I mean, are there many functions/methods in ITK 3.2 that do not exist anymore in the modern ITK releases or are called in a different way? Would it be possible to perform the upgrade in just a few days or should I book several weeks for the job (obviously this depends heavily on how our software is built internally)?<br>
<br></div><div> x What are the main known differences between those ITK versions that I should be aware of? Where will I face the biggest problems?<br></div><div><br></div><div> x Are there any functions that are protected by patents in ITK 4 but are free-for-all in ITK 3.2? Our software is commercial, so we don't and won't use any patented components.<br>
</div><div><br></div><div>I know there's a backward compatibility option in building ITK 4 but we don't really want to use it. We prefer to rewrite our code to work directly with ITK 4 instead.</div><div><br></div>
<div>Thanks!</div><span><font color="#888888"><div><br></div><div>/ Harri<br><br></div></font></span></div>
<br></div></div>_____________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Kitware offers ITK Training Courses, for more information visit:<br>
<a href="http://www.kitware.com/products/protraining.php" target="_blank">http://www.kitware.com/products/protraining.php</a><br>
<br>
Please keep messages on-topic and check the ITK FAQ at:<br>
<a href="http://www.itk.org/Wiki/ITK_FAQ" target="_blank">http://www.itk.org/Wiki/ITK_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.itk.org/mailman/listinfo/insight-users" target="_blank">http://www.itk.org/mailman/listinfo/insight-users</a><br>
<br></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><a href="tel:%2B1%20919%20869%208849" value="+19198698849" target="_blank">+1 919 869 8849</a><br>
</font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br>+1 919 869 8849<br>
</div>