Andrew Berger
Andrew Berger
antspy 0.3.3, the latest as of time writing installed via PyPI cc #86
I've noticed that: ``` aff = ants.registration(fix, mov, type_of_transform='Affine') # true aff['fwdtransforms'][0] == aff['invtransforms'][0] ``` Is this intentional? Affine transforms are easy to invert of course but this behavior seems...
not sure if I'm missing something or if there is a bug here ``` # f: image with shape (200, 200, 200) # aff: nonzero affine w = ants.transform_from_displacement_field( ants.from_numpy(...
the following cause segfaults: `ants.transform_from_displacement_field(ants.from_numpy(np.random.randn(200, 200, 200)))` `ants.transform_from_displacement_field(ants.from_numpy(np.random.randn(200, 200, 200, 3)))`
Calling it with a list of floats yields: ``` TypeError: TransformIndexToPhysicalPointF3(): incompatible function arguments. The following argument types are supported: 1. (arg0: capsule, arg1: List[List[int]]) -> List[List[float]] ``` However it...
`image.direction` is not updated after I apply an affine transform to `image`. This could be argued to be reasonable behavior, were the affine transform tracked behind the scenes. But evidently...
Could you clarify whether the input and output spaces for `ANTsTransform.apply_to_point` are index or physical? I couldn't find anything about this in the documentation for ANTsPy or ANTs
`ants.transform_index_to_physical_point` and `ants.transform_physical_point_to_index` are not present in the published antspy documentation. I was not aware of these extremely useful methods until I happened upon #159
Thoughts on creating the aliases `read_image` and `write_image` for `image_read` and `image_write` respectively? I find myself accidentally using `read_image` all of the time, and it feels like the more pythonic...
Readability could be improved by conforming to PEP-8. Very easy to do with a formatter such as [black](https://github.com/psf/black) before commiting and also as a build step in github's CI tool.