Difference between revisions of "Developer Meetings/20140422"
From Slicer Wiki
m |
m (→Conclusion) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 11: | Line 11: | ||
** vtkITK: Implemented a long time ago and not robust to compute inverse BSpline transform | ** vtkITK: Implemented a long time ago and not robust to compute inverse BSpline transform | ||
** TFM files can store inverse transform but ITK can not read it | ** TFM files can store inverse transform but ITK can not read it | ||
− | ** VTK implementation | + | ** ITK implementation ... |
+ | *** of BSpline transform doesn't include smooth boundary condition | ||
+ | *** GetInverseTransform() methods in ITK have not been implemented for non-linear transforms yet | ||
+ | ** VTK implementation provides robust support to computing inverse transform | ||
** CLILogic would have to convert the transform before execution | ** CLILogic would have to convert the transform before execution |
Latest revision as of 19:07, 22 April 2014
Home < Developer Meetings < 20140422To discuss
- The 4.4 Roadmap is at 32% for an end of May release, do we need to re-target some bugs?
- Non-linear transform discussions
- In memory
- On disk
Conclusion
- Transform discussion
- vtkITK: Implemented a long time ago and not robust to compute inverse BSpline transform
- TFM files can store inverse transform but ITK can not read it
- ITK implementation ...
- of BSpline transform doesn't include smooth boundary condition
- GetInverseTransform() methods in ITK have not been implemented for non-linear transforms yet
- VTK implementation provides robust support to computing inverse transform
- CLILogic would have to convert the transform before execution