-
Notifications
You must be signed in to change notification settings - Fork 66
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
Multimer and Alphafold3 prediction #98
Comments
I have the same issue, has this issue been solved? |
The AF2 module doesn't seem to dock the ligand and target. I am not sure why. I switched my pipeline to (1) RFdiffusion (2) ProteinMPNN from dl_binder_design and (3) Chai-1 (without MSAs). I sort my solutions on the ipTM score given by Chai-1. |
I noticed a similar issue for binder-target designs. I ran May I understand why you prefer Chai-1 over AF3? @21tesla |
No preference of Chai-1 over AF3... It was just straightforward to set up Chai-1 and write a batch script to send proteins to it and afterwards, sort the ipTM values. It works reasonably fast too, when you skip the requirement for an MSA. I have it all running on an L40S (Cuda 12.4). |
I see. Thanks! |
May I ask how to use multimer parameters for predicting complexes in the AF2 initial guess section after designing the sequence for ProteinMPPNN. Why do some proteins with poor plddt_binder (=50) and pae_interaction (=27) predicted by AlphaFold3 have high iptm and ptm scores and small PAE when I use AlphaFold3 for prediction?
The text was updated successfully, but these errors were encountered: