Documentation/4.2/Developers/Tutorials/PortingCLIToITKv4 - Revision history

UpdateBot: Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-06-14T07:44:21Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-02-12T21:31:45Z

2012-12-06T20:33:30Z

ITKv4

2012-12-06T20:29:32Z

Introduction

2012-12-06T20:25:14Z

Introduction

2012-12-06T20:24:41Z

ITKv4

2012-12-06T20:18:45Z

ITKv4

2012-12-06T20:16:36Z

ITKv4

2012-12-06T20:12:02Z

My filter doesn't run.

2012-12-06T20:06:11Z

My filter doesn't run.

← Older revision		Revision as of 07:44, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	== Introduction ==		== Introduction ==

← Older revision		Revision as of 21:31, 12 February 2013
Line 32:		Line 32:
	=== DICOM/GDCM ===		=== DICOM/GDCM ===
	ITKv4 updated the version of GDM used to version 2. GDCM version 2 has many API changes from version 1. If your CLI used GDCM directly, you will need to port your CLI to ITKv4. If you used ITK abstractions to access DICOM, then the changes to GDCM will not affect your CLI.		ITKv4 updated the version of GDM used to version 2. GDCM version 2 has many API changes from version 1. If your CLI used GDCM directly, you will need to port your CLI to ITKv4. If you used ITK abstractions to access DICOM, then the changes to GDCM will not affect your CLI.
		+
		+	=== Differences in test baselines for algorithms that use RecursiveGaussian filters ===
		+
		+	A correction was made to how the sigma/spacing/scales are computed for the RecursiveGaussian filters. For more details, see [http://itk.org/gitweb?p=ITK.git;a=commit;h=b54b8f664c377310c2ff8b3c4e6f704c819490f6 the commit].

@@ Line 5: / Line 5: @@
 ITKv4 is the result of an effort to retool ITK after 10 years of continuous development.  Preserving APIs was concern.  But there were circumstances where the APIs changed or were eliminated. Porting CLIs that utilized these components will require a bit more work.  The [http://itk.org/migrationv4/index.php?action=news&newsid=2&newslang=en ITKv4 Migration Guide] is a valuable reference to track known issues and the suggested remediations.
-== ITKv4 ==
+== ITKv4 Resources ==
 [http://www.itk.org/Wiki/ITK/Getting_Started Getting started with ITKv4] - has general information on ITKv4

← Older revision		Revision as of 20:29, 6 December 2012
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
		+
		+	Many CLIs are essentially ITK programs. Porting to ITKv4 usually just involves recompilation.
		+
	ITKv4 is the result of an effort to retool ITK after 10 years of continuous development. Preserving APIs was concern. But there were circumstances where the APIs changed or were eliminated. Porting CLIs that utilized these components will require a bit more work. The [http://itk.org/migrationv4/index.php?action=news&newsid=2&newslang=en ITKv4 Migration Guide] is a valuable reference to track known issues and the suggested remediations.		ITKv4 is the result of an effort to retool ITK after 10 years of continuous development. Preserving APIs was concern. But there were circumstances where the APIs changed or were eliminated. Porting CLIs that utilized these components will require a bit more work. The [http://itk.org/migrationv4/index.php?action=news&newsid=2&newslang=en ITKv4 Migration Guide] is a valuable reference to track known issues and the suggested remediations.

@@ Line 1: / Line 1: @@
 == Introduction ==
-ITKv4 is the result of an effort to retool ITK after 10 years of continuous development.  Preserving APIs was concern.  But there were circumstances where the APIs changed or were eliminated. Porting CLIs that utilized these components will require a bit more work.  The [http://itk.org/migrationv4/index.php?action=news&newsid=2&newslang=en ITKv4 Migration Guide] is a valuable reference to track down how to fix issues.
+ITKv4 is the result of an effort to retool ITK after 10 years of continuous development.  Preserving APIs was concern.  But there were circumstances where the APIs changed or were eliminated. Porting CLIs that utilized these components will require a bit more work.  The [http://itk.org/migrationv4/index.php?action=news&newsid=2&newslang=en ITKv4 Migration Guide] is a valuable reference to track known issues and the suggested remediations.
 == ITKv4 ==

← Older revision		Revision as of 20:24, 6 December 2012
Line 1:		Line 1:
		+	== Introduction ==
		+	ITKv4 is the result of an effort to retool ITK after 10 years of continuous development. Preserving APIs was concern. But there were circumstances where the APIs changed or were eliminated. Porting CLIs that utilized these components will require a bit more work. The [http://itk.org/migrationv4/index.php?action=news&newsid=2&newslang=en ITKv4 Migration Guide] is a valuable reference to track down how to fix issues.
		+
	== ITKv4 ==		== ITKv4 ==

@@ Line 7: / Line 7: @@
 === My filter doesn't run. ===
-The API to ThreadedGenerateData() changed in ITKv4 (use of a defined type ThreadIdType).  This can result in your implementation of ThreadedGenerateData() defining a new function instead of overriding the version called by the pipeline.  ITKv4 attempts to emit a run-time exception but there are circumstances where the exception cannot be thrown (for instance, if the superclass already provided a valid version of ThreadedGenerateData()).  If your filter is not executing in ITKv4, check the declaration of ThreadedGenerateData().
+The API to ThreadedGenerateData() changed in ITKv4.
 ITKv3 version of ThreadedGenerateData()
        virtual  void ThreadedGenerateData(const OutputImageRegionType& outputRegionForThread,  int threadId );
 ITKv4 version of ThreadedGenerateData()
       virtual  void ThreadedGenerateData(const OutputImageRegionType & outputRegionForThread, ThreadIdType threadId);
 === DICOM/GDCM ===
 ITKv4 updated the version of GDM used to version 2. GDCM version 2 has many API changes from version 1. If your CLI used GDCM directly, you will need to port your CLI to ITKv4.  If you used ITK abstractions to access DICOM, then the changes to GDCM will not affect your CLI.