Difference between revisions of "Hints for improving a refinement"
| Line 3: | Line 3: | ||
Ok, you did your average and you are not yet satisfied. Looks like you should be able to get better results? | Ok, you did your average and you are not yet satisfied. Looks like you should be able to get better results? | ||
| + | == Classification== | ||
Do you have a single class? If you are aligning two or more classes together, the alignment would get stuck at some point (funnily enough, in this circumstances the FSC can easily lie about the attained resolution, even when using a golden standard procedure!). A first approach to diagnose this is to check the cross correlation of the alignment (in column 10 of the [[table]]). A simple inspection of the histogram can be very revealing, especially if you detect different behaviours when considering particles stemming from different tomograms (column 20) or models (column 21). | Do you have a single class? If you are aligning two or more classes together, the alignment would get stuck at some point (funnily enough, in this circumstances the FSC can easily lie about the attained resolution, even when using a golden standard procedure!). A first approach to diagnose this is to check the cross correlation of the alignment (in column 10 of the [[table]]). A simple inspection of the histogram can be very revealing, especially if you detect different behaviours when considering particles stemming from different tomograms (column 20) or models (column 21). | ||
| − | The next of level approach would be running a [[PCA]] on the last [[refined table]]. | + | The next of level approach would be running a [[PCA]] on the last [[refined table]]. You probably want to start this approach using as classification mask the ''alignment'' mask that was used by the alignment project. |
| + | |||
| + | <tt> ddb myProject:eigentable -ws eigentable</tt> | ||
| + | <tt> o = dpkpca.eigentable.showHistograms(eigentable);</tt> | ||
Revision as of 08:51, 19 May 2016
Ok, you did your average and you are not yet satisfied. Looks like you should be able to get better results?
Classification
Do you have a single class? If you are aligning two or more classes together, the alignment would get stuck at some point (funnily enough, in this circumstances the FSC can easily lie about the attained resolution, even when using a golden standard procedure!). A first approach to diagnose this is to check the cross correlation of the alignment (in column 10 of the table). A simple inspection of the histogram can be very revealing, especially if you detect different behaviours when considering particles stemming from different tomograms (column 20) or models (column 21).
The next of level approach would be running a PCA on the last refined table. You probably want to start this approach using as classification mask the alignment mask that was used by the alignment project.
ddb myProject:eigentable -ws eigentable o = dpkpca.eigentable.showHistograms(eigentable);
