Hi all, If I use the riding H atoms come out of phenix.refine in molprobity, it gives me a decent clash score. But if I strip the H atoms and let molprobity to add H atoms, I get a much worse clash score. I saw the manual of phenix recommends the first method. So what is the cause of the difference here? I know long time ago that phenix and molprobity used different bond length to add the riding H atoms. I don't know what the situation is now. Does phenix.refine refine the riding H atom positions? Thanks. -- Jianghai
On Fri, Oct 29, 2010 at 2:01 PM, Jianghai Zhu
If I use the riding H atoms come out of phenix.refine in molprobity, it gives me a decent clash score. But if I strip the H atoms and let molprobity to add H atoms, I get a much worse clash score. I saw the manual of phenix recommends the first method. So what is the cause of the difference here? I know long time ago that phenix and molprobity used different bond length to add the riding H atoms. I don't know what the situation is now. Does phenix.refine refine the riding H atom positions?
It won't refine them against X-ray data, but it will perform geometry regularization to idealize their positions - which also includes shortening the bond lengths to match what we observe by X-ray diffraction. The program Reduce (used by Molprobity and Phenix), on the other hand, uses the nuclear distances, which I think are on average 0.1A longer. The Richardson lab is working on standardizing and reconciling the different bond lengths, but it's a messy problem (especially when neutron diffraction is involved). -Nat
That is what I thought. But wouldn't the nuclear distance be more accurate? and we should use the molprobity bond length, the longer one? On the other hand, phenix knows how to rotate a methyl group to avoid the H-H collision. -- Jianghai On Oct 29, 2010, at 5:42 PM, Nathaniel Echols wrote:
On Fri, Oct 29, 2010 at 2:01 PM, Jianghai Zhu
wrote: If I use the riding H atoms come out of phenix.refine in molprobity, it gives me a decent clash score. But if I strip the H atoms and let molprobity to add H atoms, I get a much worse clash score. I saw the manual of phenix recommends the first method. So what is the cause of the difference here? I know long time ago that phenix and molprobity used different bond length to add the riding H atoms. I don't know what the situation is now. Does phenix.refine refine the riding H atom positions?
It won't refine them against X-ray data, but it will perform geometry regularization to idealize their positions - which also includes shortening the bond lengths to match what we observe by X-ray diffraction. The program Reduce (used by Molprobity and Phenix), on the other hand, uses the nuclear distances, which I think are on average 0.1A longer. The Richardson lab is working on standardizing and reconciling the different bond lengths, but it's a messy problem (especially when neutron diffraction is involved).
-Nat _______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
On Fri, Oct 29, 2010 at 2:56 PM, Jianghai Zhu
That is what I thought. But wouldn't the nuclear distance be more accurate? and we should use the molprobity bond length, the longer one?
I'm not sure what is most accurate from the standpoint of a molecular modeler or chemist, but as far as X-ray diffraction is concerned, the shorter distance is better - however, the difference in R-factors is minimal, even at atomic resolution. Internally, we're using the same monomer library that Refmac uses, so it's non-trivial to switch to the longer distances. I suspect it might improve the geometry, but I haven't tested this. For what it's worth, the validation tools in PHENIX (which includes most of Molprobity at this point) always strip and re-add hydrogens before calculating clashes, so the result will always reflect the longer bonds. -Nat
As I said, stripping the H and re-add the H has a little problem. Because the methyl group can rotate, phenix.refine actually rotates the H atoms on the methyl group, a lot of clashes can be avoided. While the molprobity and phenix validation tools can't do that, a lot more clashes appear. -- Jianghai On Oct 29, 2010, at 6:35 PM, Nathaniel Echols wrote:
On Fri, Oct 29, 2010 at 2:56 PM, Jianghai Zhu
wrote: That is what I thought. But wouldn't the nuclear distance be more accurate? and we should use the molprobity bond length, the longer one?
I'm not sure what is most accurate from the standpoint of a molecular modeler or chemist, but as far as X-ray diffraction is concerned, the shorter distance is better - however, the difference in R-factors is minimal, even at atomic resolution. Internally, we're using the same monomer library that Refmac uses, so it's non-trivial to switch to the longer distances. I suspect it might improve the geometry, but I haven't tested this.
For what it's worth, the validation tools in PHENIX (which includes most of Molprobity at this point) always strip and re-add hydrogens before calculating clashes, so the result will always reflect the longer bonds.
-Nat _______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
Jianghai, the "fundamental" problem is that phenix.refine and Molprobity use different definitions for X-H distances. phenix.refine uses CCP4 Monomer Library as a source of geometry restraints, and Monomer Library uses "shorter" (X-ray) distances for X-H (but not for all entries, see below). phenix.reduce and Molprobity both use "longer" X-H distances. Unfortunately this is not the end of inconsistencies since the Monomer Library uses "shorter" X-H distances for amino-acids and "longer" X-H distances for everything else (as far as I know). For refinement against X-ray data it is good to use "shorter" distances (as SHELXL does), and for refinement against neutron data it is good to use "longer" ones. What's good for validation (Molprobity, etc) - I do not know. But what I do know for sure is that things should be consistent, at least within one program (PHENIX). Currently this is not the case, sorry. It is a part of our plans to address this problem. All the best! Pavel. On 10/29/10 2:01 PM, Jianghai Zhu wrote:
Hi all,
If I use the riding H atoms come out of phenix.refine in molprobity, it gives me a decent clash score. But if I strip the H atoms and let molprobity to add H atoms, I get a much worse clash score. I saw the manual of phenix recommends the first method. So what is the cause of the difference here? I know long time ago that phenix and molprobity used different bond length to add the riding H atoms. I don't know what the situation is now. Does phenix.refine refine the riding H atom positions?
Thanks.
-- Jianghai
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb
Hi, I have a Cd(2)Cl(4)O(6) cluster in my structure and would like to set-up constraint files for it PHENIX. Any help here would be appreciated. O Cl Cl Cl O . . . . . . . . . . . . . . . . . O . . . Cd Cd . . . O . . . . . . . . . . . O Cl O Thanks, John John Rose Ph.D. Associate Professor B204B, The Fred C. Davison Life Sciences Complex 120 Green Street Department of Biochemistry and Molecular Biology University of Georgia Athens, GA 30602-7229 ========================================= Phone: 706-542-1750 Fax: 706-542-3077
Hi John, here is what I would do (I hope Nigel suggests a better approach): option 1: create a PDB file with this construct using Coot, and make sure the geometry is approximately correct. Then try phenix.ready_set cluster.pdb to obtain a CIF file defining ideal geometry. Make sure the CIF files defines the geometry the way you expect it (inspect it visually or using REEL). option 2: threat these atoms as a bunch of independent atoms and use phenix.refine to define restraints: http://phenix-online.org/documentation/refinement.htm#anch84 (in addition to what's listed in the link above - custom restraints for bonds and angles, you can also define the planarity restraints). Pavel. On 11/1/10 12:36 PM, John Rose wrote:
Hi,
I have a Cd(2)Cl(4)O(6) cluster in my structure and would like to set-up constraint files for it PHENIX. Any help here would be appreciated.
O Cl Cl Cl O . . . . . . . . . . . . . . . . . O . . . Cd Cd . . . O . . . . . . . . . . . O Cl O
Thanks,
John
participants (4)
-
Jianghai Zhu
-
John Rose
-
Nathaniel Echols
-
Pavel Afonine