-
Notifications
You must be signed in to change notification settings - Fork 116
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
fixer.findMissingResidues() could not find the missing residues ! #305
Comments
The ATOM and SEQRES records don't match each other. It expects to be able to align them, with the ATOM records containing a subset of the residues present in SEQRES, and it offers to add the missing ones. But in this case the ATOM records have more residues, not less. For chain A they describe a chain of length 451 (residues 665 through 1115), but according to the SEQRES records there should only be 434 residues in the complete chain. Since it can't align them, it doesn't know what to add. |
Thank you Peter. |
Yeah, that's the reason that PDBFixer exists: it's really common for PDB files to be broken. :( Unfortunately, they sometimes are broken in ways it can't fix automatically. If |
Thanks. |
I'd be very cautious about trying to fully automate your pipeline. Even when PDBFixer is nominally able to "fix" all problems on its own, you should always inspect the results. Protein structures can be messed up in a whole lot of ways. There's no substitute for an expert human looking it over to check for problems. |
Hi,
I got a weird problem where fixer.findMissingResidues() could not find the missing residues, but the missing sequences are present in the SEQRES.
The PDB ID is 3LJ0 where there are two missing loops (not too long) in each chain (homodimer), The first missing loop starts from K759 to E771 (KNVSDENLKLQKE) and the second one starts from N845 to G851 (NLNNPSG).
https://files.rcsb.org/view/3LJ0.pdb
Does anyone have a solution for that?
The text was updated successfully, but these errors were encountered: