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

lfinder is only partially robust to mismatches between MOAD naming schemes and pdb structure lines #1

Open
lucagl opened this issue Mar 5, 2021 · 1 comment
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@lucagl
Copy link
Owner

lucagl commented Mar 5, 2021

The naming scheme of binding moad is to associate any residue name appearing on a line to a increasing res number, for each chain (for instance 1cqf--> BGC GAL GLA F:1 G:1 I:1 ..) will look for ligand1=(BGC F 1, GAL F 2, GLA F 3), ligand2 =(BGC G 1, GAL G 2, GLA G 3), ligand2 =(BGC I 1, GAL I 2, GLA I 3) ecc..

So far, the strategy used to overcome mismatches is to skip progressively in order (from the MOAD naming scheme) the name-chainID-ResNumber. This works most of times but not always. An example is 4z0u.pdb where the pdb skips the first 4 names and start from the 5th but keeping to index of the number at the beginning (usually everything is shifted accordingly).

In general, one could device more flexible strategies to overcome mismatches

@lucagl lucagl added question Further information is requested documentation Improvements or additions to documentation labels Mar 5, 2021
@lucagl
Copy link
Owner Author

lucagl commented Apr 10, 2021

Other examples of failures due to mismatches: 3ebb, 4ii9, 4k76, 5azg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant