-
Notifications
You must be signed in to change notification settings - Fork 2
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
Elastix compatibility "Too many samples map outside moving image buffer" #8
Comments
Hi @young-oct, Thank you for bringing this to my attention. I've tested the module and was able to reproduce this issue. It seems the Elastix module has changed the way it processes image registrations or the error handling it does since I last worked on this portion of the module. It seems a step has been removed that prevents an error that occurs when images are too far apart. There is a metric that Elastix computes that requires the images to reasonably close. A fiducial registration solves this, as it will register the images so that they are close enough for the rigid registration. Although, that is not working anymore. I see in the screenshot above that you posted, you began to process the Step 1. Fiducial Registration, but did not Harden the change. In this way, the registration was not applied. Please see that once applied, the Moving Volume's name will have "_fiducial" appended to it. Give this a try. Otherwise, the code will have to be updated to ensure additional checks or actions are performed before the Rigid Registration takes place. As a last resort (no programming involved), you could potentially revert Slicer, Elastix Slicer Extension, and this module's primary Python dependencies (vtk, ctk, SimpleITK, and sitkUtils) to the versions that were available on Sep 1. 2020 (the last date I ensured the module was tested and working). To do this, you would need to get a custom python environment going and select the versions using python's PIP as well as installing a local copy of the Elastix slicer extension that was available on that day. This issue has also been referenced in the following places: |
Python error:
|
I was excited when I found out about this module, and thank you for all your work. Currently I'm stuck at step 2 and I got the error message saying:
"command elsatix return to non-zero exit status 1 error."
Any help is greatly appreciated.
@ben-connors @jamesobutler @e-simpson
The text was updated successfully, but these errors were encountered: