Transposing volume axes for modified volume headers

[MartinSalinas98]

Xmipp, until now, did not read volume headers, and assumed a certain order was followed (fields mapc-mapr-maps always were 1,2,3).

This caused some volumes with modified order to not be processed properly within xmipp, being unintentionally transposed.

With this PR, Xmipp will now be able to read any volume with any values of those fields correctly.

PS: Updated action versions & Ubuntu version.

[MartinSalinas98]

Update: Converted MRC is slightly smaller in test. Apparently Xmipp does not (and has not done for a long time) properly write the metadata for pixel size. This image is original & converted volumes, with full contour level in Chimera to visualize the size of the full cube they are in. It is appreciable that the converted (yellow) is somewhat smaller.

Without taking that into account, conversion works as expected with the changes in mapc,mapr,maps header values.

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

The version of Java (11.0.3) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17. Read more here