Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Could use "DHW" dimension order with ITKReader?

See original GitHub issue

Is your feature request related to a problem? Please describe. There are different data storing order in Nibabel and ITK, WHD in Nibabel and DHW in ITK, Now MONAI uses the only dimension order WHD both with nibabel reader and ITK reader, paritcularly do data transpose in ITKReader. However, when using MONAI trained model in C++ with ITK library, addtiional transposes are needed, It’s terrible and WHD order is not optimal performance.

Describe the solution you’d like Could choose different dimension order when using Nibabel or ITKReader?

Issue Analytics

State:
Created 2 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

wylicommented, Sep 28, 2021

yes, it’ll work as long as these properties are defined: https://github.com/Project-MONAI/MONAI/blob/dev/monai/data/image_reader.py#L233-L240

0reactions

wylicommented, Dec 20, 2021

thanks for the comment, this pull request adds a reverse_indexing option to ITKReader. Models trained with reverse_indexing=True should be compatible with the ITK c++ spatial indexing convention.