-
Notifications
You must be signed in to change notification settings - Fork 88
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
Utilizing Precomputed MSA with Constraints for Complex Structure Prediction #62
Comments
@kehan777 you can refer to example_constraint.json and example.json with msa. Add the precomputed MSA in "proteinChain". |
Thank you for your answer, i use example_constraint.json like: secondly, i modified position2 However, the position change did not yield significantly different results. 8dkw_contact2_seed_101_sample_0.txt is a .cif file 8dkw_contact_seed_101_sample_0.txt 8dkw_contact2_seed_101_sample_0.txt |
Hi @kehan777 , thanks you for actively trying out our features. I tried to reproduce your results on my local environment and on Protenix's webserver, but my results show that the two contacts will get significantly different results. I checked your result and it seems that the constraints are not in effect. Maybe you can check if your branch is |
Thank you for your answer, and it work! another quenstions, can you use existing msa in constraint.json to predict? If possible, please provide examples |
Yes, Proteinx supports precomputed MSA and constraints at the same time. Just simply fill field If it does not work, I suppose it might because you have run |
Thank you! |
Hello,
I am working on complex structure prediction using Protenix and have precomputed MSA results.
I would like to incorporate additional constraints (e.g., distance restraints) into the prediction pipeline.
However, I am unsure how to properly integrate these constraints with the existing MSA data.
Could you provide more details or documentation on how to:
Use precomputed MSA results and constraints json in Protenix.
Thank you for your help!
The text was updated successfully, but these errors were encountered: