Hi, I refined a structure using phenix.refine. The R/R free decreased slightly from 13.46/15.87 to 13.0/15.6. But, molprobity said there were 3 CB outliers (starting from 0). I looked at those residues in COOT. I could NOT really see a different between the refined and initial model. In addition I looked at COOT validate-->density fit analysis I cannot see ANY difference in the peak heights (same numerical value too). I looked at RSCC (using phenix validate tools as well). I still can't see a difference in the plots. I am not sure how to get rid of the 3 CB outliers that have crept in since I can't pick them out as worse off in the refined model. I ask since in another case > 3 CB outliers, with the same results in picking them out in COOT/RSCC. I am wondering if there is another way I can see the deviation and fix it? Thank you, George
The program KiNG (which can be launched from the validation GUI, and is
also available via the MolProbity server) will display the CB outliers
graphically - represented by a sphere, the radius of which indicates the
displacement from ideal position.
Since this is obviously a very high resolution structure, the first thing
to check is whether these residues are in alternate conformations. It is
quite common (although almost always wrong) for disordered residues to be
split starting at CB, i.e. assuming that the mainchain is rigid and only
the sidechain atoms differ between conformations. This tends to lead to CB
outliers, because the mainchain actually needs to be flexible as well. It
is much better to simply split the entire residue, regardless of how much
you think the mainchain needs to move; by the time you can see clear
alternate conformations you usually have so much data that the extra
parameters won't be a problem. (It's often a good idea to split the
adjacent residues as well, since their backbones may also need to flex a
little bit to accommodate the central residue.)
On Wed, Nov 5, 2014 at 11:43 AM, George Devaniranjan wrote: Hi, I refined a structure using phenix.refine. The R/R free decreased slightly from 13.46/15.87 to 13.0/15.6. But, molprobity said there were 3 CB outliers (starting from 0). I looked at those residues in COOT. I could NOT really see a different
between the refined and initial model. In addition I looked at COOT
validate-->density fit analysis
I cannot see ANY difference in the peak heights (same numerical value too). I looked at RSCC (using phenix validate tools as well).
I still can't see a difference in the plots. I am not sure how to get rid of the 3 CB outliers that have crept in since
I can't pick them out as worse off in the refined model. I ask since in another case > 3 CB outliers, with the same results in
picking them out in COOT/RSCC. I am wondering if there is another way I can see the deviation and fix it? Thank you,
George _______________________________________________
phenixbb mailing list
[email protected]
http://phenix-online.org/mailman/listinfo/phenixbb
The problem of all these metrics is that they are binary: YES (=outlier) or NO (=not an outlier). You may be 1.e-5 or so (just making up a number) away from NO but the program may still consider it as outlier. And obviously you will not see that different on graphics (in Coot for instance). This is exactly why I don't particularly like functions with kinks and instead prefere smoothly differentiable ones! Phenix.refine uses CB restraints by default, so unless you disabled it or your model is very poor, you should not have these outliers after refinement (again, normally). Pavel On 11/5/14 11:43 AM, George Devaniranjan wrote:
Hi,
I refined a structure using phenix.refine.
The R/R free decreased slightly from 13.46/15.87 to 13.0/15.6.
But, molprobity said there were 3 CB outliers (starting from 0).
I looked at those residues in COOT. I could NOT really see a different between the refined and initial model.
In addition I looked at COOT validate-->density fit analysis I cannot see ANY difference in the peak heights (same numerical value too).
I looked at RSCC (using phenix validate tools as well). I still can't see a difference in the plots.
I am not sure how to get rid of the 3 CB outliers that have crept in since I can't pick them out as worse off in the refined model.
I ask since in another case > 3 CB outliers, with the same results in picking them out in COOT/RSCC.
I am wondering if there is another way I can see the deviation and fix it?
Thank you, George
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
On Fri, Nov 7, 2014 at 2:08 AM, Pavel Afonine
Phenix.refine uses CB restraints by default, so unless you disabled it or your model is very poor, you should not have these outliers after refinement (again, normally).
Why is this enabled by default? CB outliers are diagnostic for other errors in the model, like the scenario of the partially-split sidechain I described. This is the reason why they're the only chiral centers flagged in MolProbity. If the rest of the atoms in the residue are compatible with a proper CB position, the standard geometry restraints should be sufficient to keep it there. If not, adding more restraints will either introduce other errors into model geometry, or mask the actual problem with the model. Either way, this is not actually going to lead to better structures.
Thank you both for your replies.
@Nataniel-thank you, I will look into King.
@Pavel -I was experimenting with NO restraints (since this was 0.8A
structure) and as you suggested the deviations though 3 were barely "out".
I asked the question more since I could not see the difference in COOT
density fit.
Just to clarify, when you say restraints, you are talking about wxc right?
On Fri, Nov 7, 2014 at 11:35 AM, Nathaniel Echols
On Fri, Nov 7, 2014 at 2:08 AM, Pavel Afonine
wrote: Phenix.refine uses CB restraints by default, so unless you disabled it or your model is very poor, you should not have these outliers after refinement (again, normally).
Why is this enabled by default? CB outliers are diagnostic for other errors in the model, like the scenario of the partially-split sidechain I described. This is the reason why they're the only chiral centers flagged in MolProbity. If the rest of the atoms in the residue are compatible with a proper CB position, the standard geometry restraints should be sufficient to keep it there. If not, adding more restraints will either introduce other errors into model geometry, or mask the actual problem with the model. Either way, this is not actually going to lead to better structures.
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
@Pavel -I was experimenting with NO restraints (since this was 0.8A structure)
Unrestrained refinement at 0.8A resolution is unlikely to yield anything good.
Just to clarify, when you say restraints, you are talking about wxc right?
Refinement target is T = wxc * wxc_scale * Tdata + wc * Trestraints. This is all detailed in: Towards automated crystallographic structure refinement with phenix.refine. Afonine PV, Grosse-Kunstleve RW, Echols N, Headd JJ, Moriarty NW, Mustyakimov M, Terwilliger TC, Urzhumtsev A, Zwart PH, Adams PD. Acta Cryst. D68, 352-367 (2012). http://journals.iucr.org/d/issues/2012/04/00/ba5180/ba5180.pdf Pavel
Hi Nat, It is enabled by default because it is as equal piece of information as restraints on lengths of covalent bonds, values of covalent angles and all other restraints. It is simply extra information that would be shame to not use actively especially if it comes for free, and is trivial to define unambiguously (unlike Ramachandran restraints, for instance). I've made it default perhaps a year ago and I've not seen any problem related to this since then. I can demonstrate improvements in low-resolution real-space refinement when using CB restraints vs not using them, for example. If you can bring an example that proofs your concerns (that is clearly shows that using these restraints is counterproductive) I will be happy to investigate! As to diagnostics, I think proper use of existing metrics such as local (per atom) 2mFo-DFc and mFo-DFc map fit, along with local standard geometry quality metrics (clashes, deviations from ideal targets, etc) should be totally sufficient to identify problems. Pavel On 11/7/14 8:35 AM, Nathaniel Echols wrote:
On Fri, Nov 7, 2014 at 2:08 AM, Pavel Afonine
mailto:[email protected]> wrote: Phenix.refine uses CB restraints by default, so unless you disabled it or your model is very poor, you should not have these outliers after refinement (again, normally).
Why is this enabled by default? CB outliers are diagnostic for other errors in the model, like the scenario of the partially-split sidechain I described. This is the reason why they're the only chiral centers flagged in MolProbity. If the rest of the atoms in the residue are compatible with a proper CB position, the standard geometry restraints should be sufficient to keep it there. If not, adding more restraints will either introduce other errors into model geometry, or mask the actual problem with the model. Either way, this is not actually going to lead to better structures.
participants (3)
-
George Devaniranjan
-
Nathaniel Echols
-
Pavel Afonine