[ENH] New WarpPoints interface in algorithms.mesh #889
Conversation
| class WarpPointsInputSpec(BaseInterfaceInputSpec): | ||
| points = File(exists=True, mandatory=True, | ||
| desc=('file containing the point set')) | ||
| warp = File(exists=True, mandatory=True, |
There was a problem hiding this comment.
where does this field come from? different nonlinear registration algorithms store this field in different ways. we should specify which types of fields this tool supports.
There was a problem hiding this comment.
I'm getting satisfactory results using fields generated with FSL and convertwarp. Therefore, I guess any field written by FSL (fields, not coefficients) should work out. But true, we should specify this.
I'll be checking what other interfaces generate compatible fields (and/or implement filters for those that are somehow direct). Basically, any 4D image with 3 components should be enough.
Points that fall outside the FoV of the image will experiment zero-displacement.
|
@oesteban - could you please update this PR to be ready for merge or change the title to a WIP? we are going to try and release soon. |
oesteban
changed the title
Conflicts: CHANGES nipype/algorithms/mesh.py
Conflicts: CHANGES
|
I have added a more detailed docstring for the interface. I hope this fulfills the need for a more detailed description of compatible warping fields. |
Conflicts: CHANGES
Conflicts: CHANGES
oesteban
changed the title
An interface to Warp vtk meshes from a displacement field. Uses scipy.map_coordinates interpolation.
EDIT: this interface is much faster than fsl.WarpPoints in the sense that the coefficients (for bspline interpolation) are computed only once. Conversely to fsl.WarpPoints, this interface only accepts points in physical space coordinates