-
-
Notifications
You must be signed in to change notification settings - Fork 661
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
Tolerance in image size in regression comparison #4613
Comments
In implementing this, the images could be cropped to the common region, or expanded to the largest containing region. For expansion, we would need to decide how to fill the padding. Perhaps go for the most convenient NearestNeighborExtrapolateImageFunction? |
The current implementation assumes that the image are "congruent"? Aside from a different size, would this proposal allow for any other variations in geometry metadata? Are we comparing values physical or pixel space? P.S.: If we are comparing image A and B, then a perhaps new flexible comparison option is to resample image B onto the grid of image A, then proceed with the existing comparison. This essentially remove the requirement for image B to be congruent with image A. |
For For the resampling approach, we should probably do it symmetrically, so both resample A to B, and B to A, and do existing comparison twice (in case one image a significantly bigger than the other). And do this only if the images are not congruent and the size tolerance was specified, otherwise do the classic comparison as before. Are you willing to take this up this issue Brad? |
It would be nice to clean up this flag in Montage: |
Description
Currently, the test image and its regression baseline must have the exact same size, as per:
ITK/Modules/Core/TestKernel/src/itkTestDriverInclude.cxx
Lines 508 to 514 in e41c458
Which causes this sort of failure:
This makes the regression test fail even if it would pass otherwise (with e.g.
--compareRadiusTolerance 1
and other tolerances).Expected behavior
Use
compareRadiusTolerance
for comparing image sizes (which would have backwards compatibility problems), or use a new flag for that purpose (which would not disturb existing comparisons).Actual behavior
There is no way to specify that image sizes could differ even a little.
The text was updated successfully, but these errors were encountered: