-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove ITKv3Compatibility from list of ITK components #4
Comments
@hjmjohnson : Here are suggestions to update DTIPrep, so it can be built with ITKV3_COMPATIBILITY OFF. |
Martin and Francois, We were going to just fix DTIPrep so that it works with ITKv4, but it appears to be a bigger issue than we expected. I am guessing that some of this code is not in use, and is perhaps a testing ground for incomplete or no longer used features. We are willing to assist with advice and perhaps even some changes. At this point we just wanted to let you know that we need to drop DTIPrep from our superbuild system due to these incompatibilities, and we will not be able to supply the level of support that we have in the past. Regards, |
Thanks Hans Martin Martin Styner, PhD. MS ETH On Dec 4, 2014, at 2:16 PM, hjmjohnson <notifications@github.commailto:notifications@github.com> wrote: @fbudin69500https://github.com/fbudin69500 @stynerhttps://github.com/styner Martin and Francois, We were going to just fix DTIPrep so that it works with ITKv4, but it appears to be a bigger issue than we expected. I am guessing that some of this code is not in use, and is perhaps a testing ground for incomplete or no longer used features. We are willing to assist with advice and perhaps even some changes. At this point we just wanted to let you know that we need to drop DTIPrep from our superbuild system due to these incompatibilities, and we will not be able to supply the level of support that we have in the past. Regards, — |
I believe this was fixed by #45 |
Closing the issue. ITKv3 compatibility is currently on. |
Slicer is going to stop support for ITKv3 compatibility; therefore, changes suggested in this issue are needed for future compatibility.
I already started a patch to address this issue:
aghayoor@cde440f
However, DTIPrep still needs to go under a drastic refactoring in its registration framework. Here are some suggestions to start these changes:
"MultiResolutionMultiImageRegistrationMethod" class is not needed anymore, since "itkImageRegistrationMethodv4" provides multi-resolution and multi-metric/image registration capabilities.
"GradientDescentLineSearchOptimizer" class can be removed, since ITKv4 registration framework has the same optimizer: "itkGradientDescentLineSearchOptimizerv4".
"MultiImageMetric" class can be removed from the src directory, and the ITK class (itkObjectToObjectMultiMetricv4) can be used as the base class for multi-metric registration process.
The "UnivariateEntropyMultiImageMetric" and "VarianceMultiImageMetric" classes should be modified to be compatible with the new multi-metric base class.
"MultiImageRegistrationFilter" should be re-written in a way to run ITKv4 registration. Begin with:
MultiResolutionMultiImageRegistrationMethod.h --> itkImageRegistrationMethodv4.h
GradientDescentLineSearchOptimizer.h --> itkGradientDescentLineSearchOptimizerv4.h
itkBSplineDeformableTransform.h --> itkBSplineTransform.h
itkBSplineDeformableTransformInitializer.h --> itkBSplineTransformInitializer.h
...
Other registration classes in the src directory (like IntraGradientRigidRegistration, RigidRegistration and itkVectorImageRegisterAffineFilter) are also needed to be changed to use "itkImageRegistrationMethodv4" for their registration process.
The text was updated successfully, but these errors were encountered: