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
Some ImageMath functions have type issues that are revealed by haddock documents. Like, findMinMaxMask uses BareImage. It is also dubious which images can (or should) be called with D8 images. In my documentation commit, I have already changed some functions (like sqrt) to accept D32 image only. Then addS is now for D32 only while it might be possible to use it for D8 - but there could be overflow problems. Suggest deciding this matter for every function.
As a side note, should we have a BinaryImage type (perhaps newtype of Image GrayScale D8) that would be the only image type accepted for masks and such, and could be produced by comparison operators?
The text was updated successfully, but these errors were encountered:
Some ImageMath functions have type issues that are revealed by haddock documents. Like, findMinMaxMask uses BareImage. It is also dubious which images can (or should) be called with D8 images. In my documentation commit, I have already changed some functions (like sqrt) to accept D32 image only. Then addS is now for D32 only while it might be possible to use it for D8 - but there could be overflow problems. Suggest deciding this matter for every function.
As a side note, should we have a BinaryImage type (perhaps newtype of Image GrayScale D8) that would be the only image type accepted for masks and such, and could be produced by comparison operators?
The text was updated successfully, but these errors were encountered: