pre-commit.ci autofix

DOes this PR also fix #130?

@ericpre can you rebase to throw out the unrelated changes and ease the review.

There is one more that I need to do here is add an option to specify the navigation shape, because in case of 4D-STEM data saved by Velox, the data seems to be saved as a stack even if the MRC2014 specification supports it - this is consistent with the way mrcfile reads the data.

Codecov Report

Patch coverage: 86.95% and project coverage change: +0.32 🎉

Comparison is base (b9e67c3) 85.01% compared to head (5eb77ab) 85.33%.

@@            Coverage Diff             @@
##             main     #131      +/-   ##
==========================================
+ Coverage   85.01%   85.33%   +0.32%     
==========================================
  Files          73       73              
  Lines        9062     9076      +14     
  Branches     2049     2053       +4     
==========================================
+ Hits         7704     7745      +41     
+ Misses        893      860      -33     
- Partials      465      471       +6     

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

DOes this PR also fix #130?

Yes, it does! :)

The failure of the "Test Packaging" build is expected because it downloads the test files from the main branch and the file are not there, not until the PR is merged.

Would it make sense to add the non-FEI test file from #96 to the tests?
(though it seems that the so far not tested parts of the code seem to be related to FEI headers and this extra file might not give any added value)

Would it make sense to add the non-FEI test file from #96 to the tests? (though it seems that the so far not tested parts of the code seem to be related to FEI headers and this extra file might not give any added value)

Yes, mrc files generated by Velox seems to use the "non-FEI" files code path, which is covered by the other files. The file provided in #96 are larger and doesn't seem to increase coverage.

While I was at it, improve the documentation to close #93! :)

Would it make sense to add the non-FEI test file from #96 to the tests? (though it seems that the so far not tested parts of the code seem to be related to FEI headers and this extra file might not give any added value)

Yes, mrc files generated by Velox seems to use the "non-FEI" files code path, which is covered by the other files. The file provided in #96 are larger and doesn't seem to increase coverage.

Well one of the current test files is 32 MB, so larger than the 4.5 MB one from #96, but I don't know if could replace that one.

Well one of the current test files is 32 MB, so larger than the 4.5 MB one from #96, but I don't know if could replace that one.

Sorry, there is a typo in my message and anyway I wasn't very clear! What I should have say to explain my reasoning is:

• the mrc 4D-STEM test file generated by Velox seems to be as small as they can be.
• the mrc files generated by IMOD could be smaller and it would be good to ask/get a smaller one and add it later.

I would suggest to add other type of mrc files (one from the type in #91) in another PR, once we have got smallest possible file.