-
Notifications
You must be signed in to change notification settings - Fork 16
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
Changing parameters in Alphalink2 #28
Comments
Hi! Sorry, the parameters are not directly exposed at the moment. They can be changed in or via inference.py https://github.com/Rappsilber-Laboratory/AlphaLink2/blob/main/inference.py#L329 https://github.com/Rappsilber-Laboratory/AlphaLink2/blob/main/inference.py#L334 or added to run_alphalink.sh e.g.,
I should expose these... For more complicated complexes it also makes sense to test the v3 weights. Hope AlphaLink2 helps you! Keep in mind it wasn't optimised for DSSO. |
The arguments are now exposed in run_alphalink.sh |
Just had a quick follow-up question about the method not being optimized for DSSO. Our assumption was that since the Ca-Ca distance limit for DSSO is comparable to that for SDA we could use DSSO. Are there other considerations to be made here? |
No. It was just to manage expectations. SDA is already fairly low resolution at least compared to the evolutionary information used in structure prediction and DSSO data is usually sparser than SDA. If there is not much support in the evolutionary data, it's sometimes hard to get the structures close enough to form an interface. |
We are very excited to use Alphalink2 to predict antigen-antibody structures for several complexes where we have DSSO based cross linking data. Alphalink2 is a really useful software and fits well into our workflow. Thank you for this open source platform.
I have a locally installed version of Alphalink2 and have successfully generated models for a complex of interest and also experimentally validated the predicted interface. I didn't see notes on how to change parameters like recycling iterations and sampling in the README file in the local version. These would be very useful for some of the other complicated complexes we are working on. Many thanks!
The text was updated successfully, but these errors were encountered: