-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Odd release in conjunction with RoseTTAFold gaining traction #7
Comments
It's about RoseTTAFold just recently gaining traction in the newscycle which is important to make more people aware of it, not the release date of the source code.
Seriously? The model alone doesn't allow you to reproduce the underlying approach used or compare it with other methods. Which is the whole point of gaining knowledge to refine approaches, not just using them in a model.
What exactly is it that you call superior? Alphafold seems to be still a bit more precise, but an open-source system as is RoseTTAFold which can be improved quickly and openly, and which is far more efficient in what it does, will soon become the "superior" solution. |
We announced our plans to release our full methods in a peer-reviewed paper at CASP14 last December, which we have now done alongside this source code. You'll see that our paper was submitted to Nature in early May; this release has been in the works for a long time. |
While it's great you finally release your code publicly (after months of criticism for keeping it secret against the ethos of mutual aid in the scientific world) it certainly seems strange to do it just around the time RoseTTAFold , a system that does nearly the same thing for free at a fraction of the computational cost, gains significant traction in news stories.
That sudden release might give the impression of an orchestrated effort of your PR department to bury the RoseTTAFold news story.
I'm certain you will deny any of this, but to be without the shadow of a doubt in the future, DeepMind might want to share their work openly and proactively with the scientific world, instead of releasing what seems in a defensive way.
The text was updated successfully, but these errors were encountered: