RosettaCommons / RosettaCommons/foundry
Input direct from PDB file fails
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 966
- Forks
- 181
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 2
Description
Hi there,
Thanks for the early release of the model, it's great to look at and play around with!
I am having issues with running predictions with ligands directly from a PDB file. It appears to be an issue with finding chiral centres with rdkit. Both the examples modelforge/tests/data/example_from_pdb_with_inter_chain_bond.pdb and modelforge/tests/data/example_pdb_with_clashing_ligand_name.pdb fail when loaded directly with rf3 fold inputs='modelforge/tests/data/example_from_pdb_with_inter_chain_bond.pdb'
Symptoms: the prediction hangs for a long time at WARNING:atomworks.ml.transforms.rdkit_utils:Initial conformer generation based on distance geometry failed. Successful: 0. Falling back to generating a conformer starting from random coordinates. example_pdb_with_clashing_ligand_name hangs for approx 2 hours. example_pdb_with_inter_chain_bond hangs for over 12 hours.
Afterwards it fails to find chiral centres with rdkit, and the run fails.
PDB files with no ligand run successfully. Log files attached for both examples.
Thanks.
example_pdb_with_inter_chain_bond.log
example_pdb_with_clashing_ligand_name.log
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce with the rf3 fold command and the two inputs in modelforge/tests/data/example_from_pdb_with_inter_chain_bond.pdb and modelforge/tests/data/example_pdb_with_clashing_ligand_name.pdb. Start by examining the attached logs and the RDKit chiral-centre and conformer-generation failure. Done means ligand-containing PDB inputs complete prediction without hanging or failing to find chiral centres.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100