Dženan Zukić

Here is a link to a relevant discussion, and the most relevant [post](https://discourse.itk.org/t/add-a-parallel-compression-method-to-nrrd-and-or-metaimage/696/14?u=dzenanz).

Also tagging @kindlmann.

It is one of the default modules. You would need to disable `ITK_BUILD_DEFAULT_MODULES` and `ITKGroup_Core` to get the option `Module_ITKIONRRD`. That is because `Module_ITKTestKernel`, which is part of `Core`, depends...

I guess the description needs to change. We need these operators for making averages etc. And otherwise to make `RGBPixel` as similar to other possible pixel types (`float`, `short` etc)...

Maybe it is using a lot of memory, thus causing use of swap file in the CI runner? If we request `RUN_SERIAL`, that might help.

Confirmed that ITK's IO detects 8-bit image. Loading it in Slicer results in a mostly black image. Slightly updated code which works on my computer: ```c++ #include int main(int, char**)...

This is a problem with nifti library itself. Function `nifti_findimgname` ignores the actual given filename, and searches through a list of supported extensions: https://github.com/InsightSoftwareConsortium/ITK/blob/5e28b1d05d0d9ad42aec8f86def5d345628ef4d1/Modules/ThirdParty/NIFTI/src/nifti/niftilib/nifti1_io.c#L2846-L2914

It looks like it was not rectified [upstream](https://github.com/NIFTI-Imaging/nifti_clib/blob/7934f742f435c3d6628a1099cd2dba14d6cd2216/niftilib/nifti1_io.c#L2841-L2909) either. It would be good if @vanossj propagated the issue to [nifti_clib](https://github.com/NIFTI-Imaging/nifti_clib/issues).

On the CI, the test fails with a different [error message](https://open.cdash.org/tests/1992207025): ```log Traceback (most recent call last): File "/Users/runner/work/ITK/ITK/Modules/Core/ImageFunction/wrapping/test/itkLinearImageFunctionWrappingTest.py", line 23, in interp = itk.LinearInterpolateImageFunction.New(image) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/runner/work/ITK/ITK/build/Wrapping/Generators/Python/itk/support/template_class.py", line 751,...

It feels like we should update [clang format style](https://github.com/InsightSoftwareConsortium/ITK/blob/v5.3.0/.clang-format) to allow the changes proposed here. I am not sure whether that can accomplish it.