Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unexpected ligand pka values #143

Open
mbatgh opened this issue Mar 22, 2022 · 2 comments
Open

unexpected ligand pka values #143

mbatgh opened this issue Mar 22, 2022 · 2 comments
Labels

Comments

@mbatgh
Copy link

mbatgh commented Mar 22, 2022

Hi,

I just used propka3 (as downloaded and installed from github) to analyze a few structures from the PDB.
I used the "-o 7" command line option, and other than that, all defaults.
The results look in most cases as expected, but I have three cases were the results for bound ligands are very unexpected.
these are: 7JTO, 7JTP, 6W8I (the output .pka files from propka are attached)
what I see is:
7JTO: I get pka=10.66 for a ligand nitrogen (chain B res VKA N65) which is directly bound to an aromatic ring
7JTP: as above for X6M N1, also there is one more piperazine N (chain A res X6M N) which propka seems to ignore.
6W8I: chain D res TKY N50, pka = 9.65 - this is an amide nitrogen

If I understood this correctly then, at pH~7, all the nitrogens mentioned aboved should be protonated/charged according to propka, which I cannot see happening for these compounds.
Please let me know in case I overlooked/misunderstood something here!

thanks,
Michael

pkaoutputs.zip

@jhjensen2
Copy link
Member

For some reason the code is assigning the wrong atom type to these Ns. For example for 6W8I N50 is assigned to be a tertiary N (N33), but should be an amide (NAM) and thus non-tritrateable.

So these problems appear to be due to bugs in the code. I am no longer active on PropKa, but perhaps someone can look into this?

@jhjensen2 jhjensen2 added the bug label Mar 29, 2022
@mbatgh
Copy link
Author

mbatgh commented Mar 29, 2022

Thanks for the reply ... I take it the relevant code is supposed to be in: ligand.py
I was, in fact surprised, that propka tries to infer atom types/bond orders, etc from
PDB input alone, as this is rather difficult and error prone, is there a way to supply an sdf or mol2 file
instead of relying on the PDB?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants