Skip to content
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

Inputs do not occupy the same physical space! #26

Closed
chapmanbe opened this issue May 18, 2016 · 0 comments
Closed

Inputs do not occupy the same physical space! #26

chapmanbe opened this issue May 18, 2016 · 0 comments

Comments

@chapmanbe
Copy link

I am seeing the same problem as a previously reported issue. I am testing ShapeWorks on a set of four binary images (segmentations of the pulmonary arteries). Following the documentation here on GitHub I creates a *.groom.xml file and *.run.xml file modeled after the torus example. I then run ShapeWorksGroom as follows:

ShapeWorksGroom pah_pos.groom.xml isolate hole_fill center auto_crop antialias fastmarching blur.

When I then run ShapeWorksRun as follows:

ShapeWorksRun pah_pos.run.xml

I get the following error:

itk::ExceptionObject (0x7fa91520f978)
Location: "unknown"
File: /Users/brighambagley/ITK/Modules/Core/Common/include/itkImageToImageFilter.hxx
Line: 248
Description: itk::ERROR: MaximumEntropyCorrespondenceSampler(0x7fa913d2e950): Inputs do not occupy the same physical space!
InputImage Origin: [-1.6199988e+02, -1.6199988e+02, -1.3750000e+02], InputImage_1 Origin: [-1.5050009e+02, -1.5050009e+02, -1.3000000e+02]
Tolerance: 2.5312481e-06
InputImage Spacing: [2.5312481e+00, 2.5312481e+00, 5.0000000e+00], InputImage_1 Spacing: [2.3515639e+00, 2.3515639e+00, 5.0000000e+00]
Tolerance: 2.5312481e-06

My origins, spacing, and sizes are all different between my input images and the groomed (DT) images.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants