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
The current use of itkAssertOrThrowMacro to report errors, such as inputs that cannot be processed, is not caught by a Python try-except block. We want a solution where the Python program can recover from these errors.
That would be a great feature. I was looking into using ITKColorNormalization in my DP workflows, but I was unable to as it seemed to crash too often, with no simple way to catch these errors, as fair as I remember.
I could test a proposed solution in a typical workflow when it is ready.
InsightSoftwareConsortium/ITK#3479 should fix this issue. However, I nonetheless recommend that we use if (!success) { itkGenericExceptionMacro(message); } to replace itkAssertOrThrowMacro(success, message); in ITKColorNormalization code.
Activity
andreped commentedon Jun 6, 2022
That would be a great feature. I was looking into using ITKColorNormalization in my DP workflows, but I was unable to as it seemed to crash too often, with no simple way to catch these errors, as fair as I remember.
I could test a proposed solution in a typical workflow when it is ready.
Leengit commentedon Jul 4, 2022
InsightSoftwareConsortium/ITK#3479 should fix this issue. However, I nonetheless recommend that we use
if (!success) { itkGenericExceptionMacro(message); }to replaceitkAssertOrThrowMacro(success, message);in ITKColorNormalization code.