-
-
Notifications
You must be signed in to change notification settings - Fork 686
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MRC file format bug and compatibility fixes. #4019
MRC file format bug and compatibility fixes. #4019
Conversation
The computed values are unused and MRC extended headers are not fully supported.
The MRC input image file didn't get magically converted to a hash file. It will need to be manually updated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That file needs to be replaced by the hash (and uploaded data.kitware.com), otherwise looks fine.
I uploaded the test file here: https://data.kitware.com/#folder/64413821cffd1a074ef04595 Here is the hash file to be put into the repository: |
c1b3432
to
f611ccd
Compare
MRC image collected as a tilt series had spacing being computed a zero. This causes the image to be unreadable but ITK. Set the spacing to 1 in the case.
The MRC2014 specification updated/clarifed the spec that the first two bytes should contain the specified value to determine endian. This appears to be enforced with Python mrcfile. This patch enables compatibility.
f611ccd
to
8ca5d1f
Compare
Sorry, I merged these via rebase (without a merge commit). I now realize that will prevent same hashes from being used in release branch (#4023). |
Addresses issues with the system stamp, 0 -spacing, and remove dead code creating warnings.
This PR is also based on the release branch so that it can also be back patched.