-
Notifications
You must be signed in to change notification settings - Fork 7
Add support to use AlphaFold3 command line outputs in addition to AlphaFold3 Server outputs #4
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
Comments
Yes, this is in the works, but I cannot give you an ETA. |
This is a great news thats this functionnality is on its way. |
Hi, any news on this implementation? Thanks a lot. |
Hi! I made a fork of the original AlphaBridge repository with enabled support for local installation of AlphaFold3 output. It's a very "crutch"-like solution that simply masks AF3 output as the output of AlphaFold Server and currently doesn't have support for ligands, but it works for proteins. https://github.com/ruslan-uoc/AlphaBridge-AF3LocalPatch.git AlphaBridge is great and I am looking forward for the implementation of this functionality from the authors of the original paper, but until then, I hope it will be of some help. Cheers! |
Sorry for the delay in my response! Thank you for your feedback and for sharing your fork with the community,it’s great to see such engagement. I’m currently working on addressing this issue, alongside adding support for ligands and post-translational modifications. You can expect an update with these improvements by the end of this month. |
Thanks @ruslan-uoc and @Dan-salv for this information! |
Hi @phupe , I think i replied to you already by mail, but the 'Trunk branch' provides support for the locally installed version output, so I am close the issue |
AlphaBridge is really great, thanks for making this tool available.
Is there any plan to add support to use AlphaFold3 command line outputs in addition to AlphaFold3 Server outputs as filenames and json entries are not extacly the same.
Thanks.
The text was updated successfully, but these errors were encountered: