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

Is RDKit correctly assigning connectivities from ligand PDBs? #23

Closed
martimunicoy opened this issue Aug 6, 2020 · 1 comment · Fixed by #28 or #29
Closed

Is RDKit correctly assigning connectivities from ligand PDBs? #23

martimunicoy opened this issue Aug 6, 2020 · 1 comment · Fixed by #28 or #29
Labels
question Further information is requested

Comments

@martimunicoy
Copy link
Owner

We should double check some of the "known tricky" cases below:

  • Tertiary nitrogens like NH4
  • Carboxylic acids
  • Carboxylates
@martimunicoy martimunicoy added the question Further information is requested label Aug 6, 2020
@martimunicoy martimunicoy changed the title Is RDKit correctly assigning connectivies from ligand PDBs? Is RDKit correctly assigning connectivities from ligand PDBs? Aug 24, 2020
@martimunicoy martimunicoy linked a pull request Aug 24, 2020 that will close this issue
4 tasks
@martimunicoy
Copy link
Owner Author

I analyzed three different compounds:

  • Ammonium, [NH4+]
  • Malonate, O=C([O-])CC(O)=O
  • Trimethylglycine, C[N+](C)(C)CC(=O)[O-]

When representing RDKit's structures obtained from PDB files (with connectivity) and SMILES, the same connectivity is observed in each pair. The results are displayed in the following example. So, apparently, RDKit is able to assign the right connectivity in both cases (only when the PDB file that is read contains information about the connectivity).

@martimunicoy martimunicoy linked a pull request Sep 2, 2020 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant