ITK/Release 4/Why Switch to ITKv4: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
| Line 7: | Line 7: | ||
* Makes it '''easy to associate''' and build auxiliary '''community projects''' with the [[ITK_Release_4/Modularization/Add an external module (external module)| External module]]. | * Makes it '''easy to associate''' and build auxiliary '''community projects''' with the [[ITK_Release_4/Modularization/Add an external module (external module)| External module]]. | ||
* Find the quality control per module by performing code coverage testing per module. | * Find the quality control per module by performing code coverage testing per module. | ||
=== New Registration Framework === | === New Registration Framework === | ||
Revision as of 21:44, 1 September 2011
Modularization
- Easier to find what you are looking for.
- Easier to understand how to use the toolkit.
- Build only the parts of the toolkit that you need.
- Extend bridging of the toolkit to other toolkit and libraries.
- Makes it easy to associate and build auxiliary community projects with the External module.
- Find the quality control per module by performing code coverage testing per module.
New Registration Framework
New LevelSets Segmentation Framework
SimpleITK
- Ease of Use
- Rapid development
- Interactive processing
