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

Extreme amount of clashes in some multimer predictions #236

Closed
dennissv opened this issue Nov 6, 2021 · 10 comments
Closed

Extreme amount of clashes in some multimer predictions #236

dennissv opened this issue Nov 6, 2021 · 10 comments
Labels
error report Something isn't working

Comments

@dennissv
Copy link

dennissv commented Nov 6, 2021

Sometimes when using the multimer models I get extreme amount of clashes in the predictions to the point where the proteins are just a blob. At first I thought it was a problem with my local installation but I tried running some problematic proteins on the Colab notebook and get similar results there. An example would be the following protein sequence as a heptamer;

MEENVTEDSILSTELRGQEIRIEEVPNEDTLVVYLSRGGRNAKESQSANSNNTGDIDKHGRHRADNCICLSKVHYEIDGDILCIREMKPFVYINKVSILRRRSTNKTKEDTETQKSP

clashes

The complete disregard for stereochemistry only seem to appear in regions with very low confidence. The only modification I have made is to disable the Amber relaxation step but this never seemed to cause large issues like these in the monomer version nor in the ColabFold multimer version. I also doubt that Amber can resolve these clashes in a meaningful way?

Is this expected behaviour without Amber and for proteins that are hard to model or is something wrong?

@dennissv dennissv changed the title Extreme amount of clashes in multimer predictions Extreme amount of clashes in some multimer predictions Nov 6, 2021
@arashnh11
Copy link

Which model is this from? And do you have an alignment RMSD w.r.t the experimental?
We are working on an octamer complex and see clashes too. In our case model_3 had the best outcome though still off...

@tony9664
Copy link

tony9664 commented Nov 6, 2021

I'm also seeing some similar serious clashes when predicting multimers. Colabfold was good though.

@arashnh11
Copy link

arashnh11 commented Nov 6, 2021 via email

@arashnh11
Copy link

OK, here is the comparison of clashes for 7KEU: magenta: v2.1.0 green: RCSB.

Screen Shot 2021-11-06 at 2 54 50 PM

@dennissv
Copy link
Author

dennissv commented Nov 9, 2021

@arashnh11 2.1.0 included new multimer models for protein complexes which is where I started observing these issues. ColabFold used a flexible linker solution which didn't provide the same accuracy but also never displayed these clashes.

Some proteins work very well and it's been great seeing these models. But whenever a protein has some region with low confidence it quickly becomes a tangled mess. I've heard several people having the same issues, some examples can be found here; https://twitter.com/RolandDunbrack/status/1457538160561377283

Is there any update on this?

@arashnh11
Copy link

@dennissv Do you know of some sample multimers with good alignment with reference PDBs?
Haven't heard any update yet. I can tweet our failed Octamer testcase above, but I believe this is more of a bug...

@tfgg
Copy link
Collaborator

tfgg commented Nov 11, 2021

We think we may have identified the issue with overlapping domains but need to test a bit more. It will take us a few days at least to be sure.

@arashnh11
Copy link

arashnh11 commented Nov 11, 2021

@tfgg Thanks for the update. Please let us know if there is any information we can provide or any additional tests we can do to help. One thing we tested was the Amber relaxation on multiple cases and it seems that it actually increased the clashes for the relaxed model vs unrelaxed, though the general structure was about the same, i.e., no improvements.

@dennissv
Copy link
Author

This seems largely fixed with the new v2 multimer models. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
error report Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants
@tfgg @Augustin-Zidek @arashnh11 @dennissv @tony9664 and others