score discrepancies about oddt HOT 4 OPEN

Hi Michel,

Thanks for reporting the issue. May you please share how you prepared the molecules in PDBQT format? Reading back PDBQT files is many times not the best idea, as they loose information about connectivity, bond orders in particular. I assume that you use OB as the toolkit. When I read back your ligand file this is what OB generates

obabel 1A30_FH_ligand.pdbqt -osmi
[C](NC(=O)[C]([C][C]C(=O)[O])[NH3])(C(=O)N[C]([C][C]([C])[C])C(=O)[O])[C]C(=O)[O]	1A30_FH_ligand.pdbqt
1 molecule converted

As you can see there are some radicals, which might be the issue here. I would recommend starting with a format that has proper bond orders, which are essential for marking donors and acceptors.

Alternatively there is an autodock_vina_descriptor which uses native Vina library and should work for you.

from oddt.

Thanks for your reply Maciej
I did not prepare the PDBQT files but used from a paper published by Rentzsch et al 10.1093/bib/bbv008 but i do not understand why it would make a difference. I run both programs using the native PDBQT format. I would expect both program to end up doing the same thing or am I missing something ?
Are you saying that your program reads the PDBQT (which provides all the data needed for Vina) but then somehow reassigns atom types?

Will the AutoDock_vina_decriptor return ligand internal energies ?

the reason for my email was mainly that a user sing Vina with some PDBQT files would expect to get the same results when using oddt with the same input files.

-Michel

from oddt.

oddt_vina_sescriptor scores the representation of molecule in the toolkit, Openbabel or RDKit. If you produce PDBQT with ODDT I would expect the scores to be identical. In your case, the PDBQT is already there so what you should be using is the aforementioned autodock_vina_descriptor, which should produce 1:1 results for you - it uses vina --score_only binary and should produce the exact set of partial scores as Vina does out of the box.

The exact command line can be found here:

The oddt_vina_sescriptor was intended as a faster alternative to be used in ODDT pipelines, as it avoids expensive IO and conversion to PDBQT which is prone to error, as you witnessed.

from oddt.

yes you are right, the AutoDockVina.py will run the same binary as used on the command line and give me the same values, although it does not report the ligand internal energy terms.

I generated PDBQT files ODDT and compared with my PDBWT files. The only differences is the AutoDock atom type of sulfur atoms in MET36, MET46,CYS67 and CYS95 in both chains A and B of the receptor which are SA in my file and S in the files produced by ODDT. However, none of these amino acid are close enough to the ligand to hydrogen bond.

In AutoDock the donors and acceptors are encoded by the atom type HD, OA, SA etc, but I guess this gets overwritten by your perception of donors and acceptors, even when the input is the native PDBQT used by Vina. I guess that is what leads to the differences in the results.

However, what I do not understand is that when I run Vina on the PDBQT files generated with ODDT I get the same results as with my PDBQT files i.e. hydrogen = 3.59471 not 6.018104553222656 which is to be expected as the only difference in PDBQT files is the TYPE of S atoms which do not interact with the ligand. So I am still unclear where and why the difference arises.

from oddt.