You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to the AlphaFold Server, thank you for providing the open-source version of your latest method.
Similar to the AF Server Output Terms, does the open source version prevent using the predicted structures in automated systems i.e., docking and simulation software?
The specific restriction is noted below:
In connection with any automated system that predicts the binding or interaction of the protein with ligands or peptides, including, but not limited to, Glide or AutoDock.
This information is not explicitly noted in the open source version's Output Terms of Use.
This has also not been brought up in any of the previously submitted issues.
It will be very helpful for the research community to have this information.
The text was updated successfully, but these errors were encountered:
Different terms apply to use of AlphaFold Server and the code and weights released on GitHub.
The use of outputs with automated systems that predict the binding or interaction of proteins with ligands or peptides is only prohibited by the AlphaFold Server terms. However, you should read the terms applying to your use of AlphaFold 3 in full to ensure your intended use is compliant and, if required, seek independent legal advice.
Dear Authors,
In addition to the AlphaFold Server, thank you for providing the open-source version of your latest method.
Similar to the AF Server Output Terms, does the open source version prevent using the predicted structures in automated systems i.e., docking and simulation software?
The specific restriction is noted below:
This information is not explicitly noted in the open source version's Output Terms of Use.
This has also not been brought up in any of the previously submitted issues.
It will be very helpful for the research community to have this information.
The text was updated successfully, but these errors were encountered: