Versatile input img axes order

[ClementCaporal]

Should closes #43

This PR should allow user to use any dimension order in cfg.TEST.BY_CHUNKS.INPUT_IMG_AXES_ORDER.

• Some change noise comes from trimmed final space ending line.
• Propose to refactor the use of cfg.TEST.BY_CHUNKS.INPUT_IMG_AXES_ORDER using util.order_dimension
• All change affect the same region than your commit https://github.com/danifranco/BiaPy/commit/c6cc49d8e728d9c1d1f30f57e23ea698eeca4316 + the detection.after_merge_patches_by_chunks_proccess_patch
  • Concerning after_merge_patches_by_chunks_proccess_patch I was hesitating between:
    • saving the temporary data with channel in last position here. Or keeping the original user image dimension order
    • If the orginal user image dimension is kept, then after_merge_patches_by_chunks_proccess_patch had to be adapted too.

But I decided to keep the original user image dimension so I can just superpose the two images using my favorite viewer to look at the different steps easily. I didn't find a test folder but don't hesitate to ask me to add more things or to close the PR if doesn't correspond to standards!

[ClementCaporal]

Hello @danifranco as discussed in #43 I made new changes:

• Removed commit noise to focus on what is truly changed.
• Add the versatile order to the multi gpu process. So it should be versatile everywhere now.

Hopefully ready to merge. I have to open new issue to solve before everything can work, but I think for this particular issue of versatile loading it is "solved".

If you prefer to have one big PR, i can also do that