astex-icube / astex Goto Github PK

It would be great to have some of the classical operations on image processing such as adding two images of the same size, point-wise multiplication and matrix multiplication.
They are relatively easy and can also be implemented in place of Itk filter (such as itk::NaryAddImageFilter) if necessary.

Everything is in the title. I have stumbled upon this issue only for ImageRGB types, though.

Hello,

It seems the latest ITK does not support itkSimpleFastMutexLock.h. Is there a quick solution?

csv

The following is only a minor inconvenience, and I have provided a workaround on the bottom of the issue.

Probably because of how itk works, the types for images are not the same between their non-const and const version, so instead of using const ImageX, we use ConstImageX. The current problem with this syntax is that the const version of an image cannot be deduced, which can enforce the use of several redundant template members.

Example: in the following code, I want to make a itk filter that inputs an image using an ASTex Image type as a template. The following is perfectly fine:

template<typename TInput> class FilterGetisGI : public itk::ImageToImageFilter<typename TInput::ItkImg, typename TInput::ItkImg>

But it enforces that TInput is a non ConstImageType, because the output of the filter is necessarily non ConstImageType as well. I would like to use something like:

template<typename TNonConstImage> class FilterGetisGI : public itk::ImageToImageFilter<typename TConstImage::ItkImg (?), typename TNonConstImage::ItkImg>

but it is not currently possible to deduce the Const version of an image from its NonConst version. A current workaround is to use something like:

template<typename TNonConstImage, TConstImage> class FilterGetisGI : public itk::ImageToImageFilter<typename TConstImage::ItkImg, typename TNonConstImage::ItkImg>

which forces the user to provide the Const version of the image type with the NonConst.

• Add a way to deduce const image types from non const image types
• Add a way to deduce non const image types from const image types

Real-valued image types, such as ImageGrayd and ImageRGBd, produce empty files when called with the default syntax (save(filename)). This enforces the use of IO::save01_in_u8(image, filename), but this is inconvenient with template types that can be different Image types.

I suggest to change save(filename) so that it saves real-valued images by assuming their value is between 0 and 1, and clamp values that are not in this range.

• Change the behavior of the save function to make it usable by templates

We should create an ImageType that allows the user to have a variable number of channels, for example one comprised of red, green, blue, alpha, normal, and height. This would be useful to extend the scope of ASTex to various textures. One would be able to apply classic operators such as * or +.

• Create a custom ImageType with a variable number of channels