You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both AdvancedImageToImageMetric::Initialize() and AdvancedImageToImageMetric::InitializeLimiters() use ComputeImageExtremaFilter to estimate the minimum and the maximum pixel value of the fixed and the moving image. Now the first member function also calls the second one, indirectly, causing the expensive ComputeImageExtremaFilter to be executed more than necessary.
Looking back at commit 592608c (January 15, 2018), it looks like it it that way already for a while:
Both
AdvancedImageToImageMetric::Initialize()
andAdvancedImageToImageMetric::InitializeLimiters()
useComputeImageExtremaFilter
to estimate the minimum and the maximum pixel value of the fixed and the moving image. Now the first member function also calls the second one, indirectly, causing the expensiveComputeImageExtremaFilter
to be executed more than necessary.Looking back at commit 592608c (January 15, 2018), it looks like it it that way already for a while:
elastix/Common/CostFunctions/itkAdvancedImageToImageMetric.hxx
Lines 276 to 277 in 592608c
elastix/Components/Metrics/AdvancedMeanSquares/itkAdvancedMeanSquaresImageToImageMetric.hxx
Lines 94 to 95 in 592608c
While
AdvancedMeanSquaresImageToImageMetric::Initialize()
also callingAdvancedImageToImageMetric::Initialize()
:elastix/Components/Metrics/AdvancedMeanSquares/itkAdvancedMeanSquaresImageToImageMetric.hxx
Line 68 in 592608c
The text was updated successfully, but these errors were encountered: