Skip to content
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

Failing to read tomograms written out by cryoCARE #43

Closed
alisterburt opened this issue Feb 28, 2023 · 2 comments · Fixed by #44
Closed

Failing to read tomograms written out by cryoCARE #43

alisterburt opened this issue Feb 28, 2023 · 2 comments · Fixed by #44

Comments

@alisterburt
Copy link
Contributor

Came across an issue with cryoCARE generated tomograms with @AndrikovonKugelgen - they are also misinterpreted by IMOD

/Users/alisterburt/mambaforge/envs/py/lib/python3.10/site-packages/mrcfile/mrcinterpreter.py:342: RuntimeWarning: Expected 2649024000 bytes in data block but limit is 2648966400

This is probably a problem with mrcfile and the headers that cryoCARE is writing, checking in detail now and will report over there if I can reproduce outside of cryoCARE

@alisterburt
Copy link
Contributor Author

@AndrikovonKugelgen found the issue - the extended header was not copied into the output file and the header contains a reference to the number of bytes found in the extended header. This led to an offset in where the data was expected to start within the file.

@jychoi0616
Copy link

Sorry to ask here again when this issue was already closed.
I have a feeling that the still opened issue (#29) may be related to this.

So how would you get around this in the end? And could cryoCARE code be fixed about "possibility of writing invalid headers" please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants