Netiquette · Download · News · Gallery · G-quadruplexes · DSSR-Jmol · DSSR-PyMOL · Video Overview · DSSR v2.5.1 (DSSR Manual) · Homepage
I was for a whole no longer using op1_op2 since I thought that the PDBNo surprise.
had taken care of the wrong anionic oxygen attributions.
That was assuming a little too mach and such misattributions are still found in the PDB.
(see for exemple residue 625 chain 0 in 4HUB that interacts through its N3 with the "OP1" of a m1A - should be OP2).
(other examples can be found)
Thus using op1_op2 seems still mandatory.The 3DNA programs in general, op1_op2 in particular, are just tools meant to be employed as users see fit. Early on in 3DNA development, I noticed a larger than expected RMSD value between a rebuilt structure vs its experimental counterpart. The source of the discrepancy was traced to wrong labeling of the O1P/O2P (OP1/OP2) atoms. So I wrote the small op1_op2 utility program to make the correction, and distributed it with the 3DNA package, in the hope that it may be useful to others as well. I am glad to know that it is still of some value to the community.
Yet, we stopped using it also because it gets rid of some parts of the header, especially
those that describe symmetry operations.
I such I kindly ask for a version with a -header option that would keep the original headerNote that op1_op2 was designed to be simple and small. Moreover, nearly all 3DNA programs check only ATOM/HETATM records, without bothering about anything else. At this stage, I do not feel it is of general interest to expand op1_op2 for your specific need.
for those who need it.
o1p_o2p 4hub.pdb 4hub-corrected.pdb
*PO4 group at residue 1MA 628 on chain 0 [#621] does NOT conform to convention*
*PO4 group at residue UR3 2619 on chain 0 [#2510] does NOT conform to convention*
Funded by the NIH R24GM153869 grant on X3DNA-DSSR, an NIGMS National Resource for Structural Bioinformatics of Nucleic Acids
Created and maintained by Dr. Xiang-Jun Lu, Department of Biological Sciences, Columbia University