Feature #2380
closed
How to get best CTF estimation from database
Added by Neil Voss over 11 years ago.
Updated over 10 years ago.
Category:
Python scripting
Description
Hi All,
I am sure many of noticed over the last year my complete tear down of the CTF infrastructure. Hopefully it is working for you now, if not please file a bug and let me know.
Anyway, the next step is when doing a CTF correction or displaying on the web the program will query all the CTF estimations for an image and try to decide the best estimation for that image. Currently, it is using legacy code, i.e., the one with the highest confidence value and it does not care which program it came from.
I propose that it uses my new CTF resolution criteria to get the best CTF estimation by default. In makestack, I think it should be a choice, but there are many calls for the best CTF in the code that you may not realize and adding an option to even program would be hard to implement on a short notice, e.g., FREALIGN recon. I have already made the changes to my code, but I have not submitted them to the truck. I wanted to hear from you first.
Thanks,
Neil
Files
Sorry for the slow response. I am in favor of adding your new criterion as an option, but I really want it to be completely backwards compatible. In other words, I would like the option to get the best CTF the old way as well as the new way. Is that possible?
Hi Scott,
So far, I have only updated the web viewer part, I think it might be a little clunky to choose the type of sorting, but it could be added.
With makestack, the most critical part, it will be a drop down menu to select the type of criteria to choose. Other places that need an option is frealign and relion.
Well, I don't use the typical Appion infrastructure for generating Frealign parameter files, so it wouldn't be to big of a deal for me as long as you don't remove the old functions and instead make new functions with new names. I don't even have Relion installed, so that's not a big deal for me either.
Hey Neil,
I ran Ace2, but it is failing because getBestCtfValueForImage was replaced with getBestCtfByResolution and the resolution method does not take the "method" parameter that is being sent to it.
Not sure if you forgot to check in a file with corresponding changes, or if the method param can just be removed from all the calls.
Also, is Ace2 in a good usable state? or are you planning more changes to it for the near future?
Thanks,
amber
Hi Amber,
Sorry about that. The only reason that function is called is to print the current best CTF values. It is not used by the program.
I've made changes to ACE2, but I am sure if they are improvements, so I am not committing them at this time. Also, I wanted it to be stable for you.
r17815 fixed the null first in sorting error Bridget found today in myamiweb display. At the same time, I changed the sorting to have two levels with 80_percent_resolution as the primary sort.
Neil, please see if this is reasonable. If so, it may make sense o do this at python level.
I almost have the makestack component implemented. It will look like this (ignore my font)
- Status changed from Assigned to In Code Review
- Assignee changed from Neil Voss to Amber Herold
- Related to Bug #2854: normalization options commented out? added
- Status changed from In Code Review to Closed
Also available in: Atom
PDF
