3D classification separating signal in different directions?

Hi everyone,

I have a 3.7A structure of protein-tRNA complex. The map looks mostly clean and interpretable but it has some anisotropy.

I am trying to split two states, one with the modified tRNA and one with the unmodified tRNA (I know both species are present on the grid from other experiments).

I did 3D classification with the filter resolution of 3.7, 2 classes, initialization mode:PCA, number of epochs 3, default parameters and with the focused mask on the region of interest. Then I did Non-uniform refinement with the output maps and particles.

This generated two classes with particles split almost evenly. In The active site I observe big and small density around adenine, which could be modified and unmodified states (first picture). However, I see this weird streakiness pattern. Looking at the base pairs, in one class I see some streakiness roughly in one direction and in another class I see streakiness in a different direction (2nd picture).

My questions are, is it possible that 3D classification is splitting signal in different directions and not actual conformations?

Can I trust this data?

Also, another weird thing is cFAR score in both of this structures is doubled compared to the original map (0.20-0.25 VS 0.1). Although, the original map looks better overall.

Hi @Ana, short answer yes, it is possible for 3D classification to separate on view rather than conformation. It is also possible for one conformation to have much more significant orientation biases than another, or for misalignment to introduce spurious bias (the orientation distribution is only as accurate as the alignments). If you combine data with slightly different pixel sizes, or if the data has significant residual beam tilt - causing magnification to vary with defocus - classification could also separate on apparent size.

In addition to carefully inspecting the maps and orientation distributions of the classes and separate refinements, you could also reconstruct with the angles from the consensus refinement (which might be more accurate/consistent), and try different numbers of classes, focused masking, classification with alignment (heterogeneous refinement, or Class3D with local search in Relion), or 3D variability analysis. You can verify that aligning maps (which might shift during classification with alignment or refinement, or reflect shifts in from aligning different groups of particles) or modifying the pixel size in ChimeraX doesn’t explain the differences you see.

Your models can help as well, based on how easy it is to rebuild them into different densities and if the resulting models have good statistics and appearance.

2 Likes

Hi Ana,

I agree with all the things Daniel said above. Another thing you can do to validate the orientation distribution of your maps is use a reference-free method where the input map doesn’t bias the data as much, such as 2D classification, on each of your 3D classes. If you see a particular view being over-represented in the most populated classes this is a sign that orientation bias may be a problem.

Another thing that you can do to improve the reconstructions is use the Rebalance Orientations job in CryoSPARC. This will get rid of particles from over-represented angles and improve the cFAR score. Generally, the guidance is to aim for a cFAR score of ~0.5. But if the features of the map look like protein i.e. nice alpha-helix and beta-strand density in regions which are actually protein, then I’d trust maps with a cFAR as low as ~0.3.

Hi Daniel, thank you for your response it is very helpful. Could you clarify what you mean by reconstruct with angles from the consensus refinement?

The strange thing is cFAR for my map is 0.1 but it looks perfectly interpretable and clean, there is some streakiness but it is still good enough to confidently build a model, it looks cleaner than some maps I have seen with much higher cFAR. When I rebalance particles, it does not seem to increase cFAR too much, only maybe by 0.05, does not matter what percentile I use. What could be the reason for this?

3DFSC sphericity is around 0.86 with a mask.