-
Notifications
You must be signed in to change notification settings - Fork 205
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
Relion5 Ctf estimation: BUG: MDin should contain a rlnMicrographPreExposure label #1167
Comments
Hello, I am running into the same error message in RELION 5 tomo CTF estiomation job. Have you figured out the problem? BUG: MDin should contain a rlnMicrographPreExposure label Thanks, |
Hi, My problem was fixed. It turned out that the CTFFIND4 couldn't run on the cluster. The solution is to add "export LC_ALL=C" to my ~/.bashrc. Hope it helps. |
I have added "export LC_ALL=C" to my ~/.bashrc, but this bug still here. |
"I have the same issue, have you resolved it? |
HI, |
Hiya, I tried an earlier version of ctffind4 (I am afraid that I cannot find exactly which version at present, as was using someone else's installation) and this ran absolutely fine, so might be an issue with the 2019 version of ctffind4? |
Thanks @HDuyvesteyn , I changed the ctffind version from 4.1.14 to 4.1.5 and the bug disappeared, so it is indeed likely a bug in the new version. |
@HDuyvesteyn - did you try the version
edited as I just tested and that does work. |
Raise an error when CTF estimation failed on all images; also add LC_ALL=C to avoid problems in CTFFIND. Fixes #1167. Thanks to @huwjenkins.
Repaired in #1212 by @huwjenkins. |
hi! I'm doing CtfFind using Relion5.
I did Import and MotionCorr as the tutorial, but when I'm doing CTF estimation with input tilt series corrected_tilt_series.star, it gave the error information "BUG: MDin should contain a rlnMicrographPreExposure label":
I checked the star files, and the star file for each tomogram contains the rlnMicrographPreExposure
How can I solve it?
Thanks!!!
The text was updated successfully, but these errors were encountered: