You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Slicer does not properly open 2D transforms, which are meant to transform 2D images.
Describe the solution you'd like
I assume it would be too much work to have internal support for 2D transforms, so I suggest the following: Convert 2D transforms to 3D transforms upon loading. The transformation along the 3rd axis should be set to zero. When such a transform gets applied to 2D images, they get deformed the same way as when the original 2D transform is applied to them (e.g. ITK's resample filter). I envision no special handling on saving, so they get saved as regular 3D transforms. In the future, we might consider special checks to recognize 2D transforms and convert them to 2D upon saving.
Describe alternatives you've considered
For debugging purposes, 2D affine transforms can be converted to 3D affines without much trouble. ITK-based code from here (in case of link rot):
But this only benefits the one project in which it exists. It would be much better to have this inside Slicer.
Doing the equivalent for displacement field (DF) transforms is more involved. Also, if DF transforms are converted to 3D upon saving to disk, they result in files which are ~33% bigger.
Is your feature request related to a problem? Please describe.
Slicer does not properly open 2D transforms, which are meant to transform 2D images.
Describe the solution you'd like
I assume it would be too much work to have internal support for 2D transforms, so I suggest the following: Convert 2D transforms to 3D transforms upon loading. The transformation along the 3rd axis should be set to zero. When such a transform gets applied to 2D images, they get deformed the same way as when the original 2D transform is applied to them (e.g. ITK's resample filter). I envision no special handling on saving, so they get saved as regular 3D transforms. In the future, we might consider special checks to recognize 2D transforms and convert them to 2D upon saving.
Describe alternatives you've considered
For debugging purposes, 2D affine transforms can be converted to 3D affines without much trouble. ITK-based code from here (in case of link rot):
But this only benefits the one project in which it exists. It would be much better to have this inside Slicer.
Doing the equivalent for displacement field (DF) transforms is more involved. Also, if DF transforms are converted to 3D upon saving to disk, they result in files which are ~33% bigger.
Additional context
Here are some sample transforms: 2D_transform_examples.zip
The sample transforms can be applied to these images:
https://github.com/ntustison/TemplateBuildingExample/tree/master/Faces
Associated forum thread.
The text was updated successfully, but these errors were encountered: