Add bio.rodeo usability score badge to README - #9
Merged
Conversation
Added a badge for bio.rodeo usability score.
Contributor
Author
|
Hi @shenoynikhil! Would you be open to this PR? |
Collaborator
|
Thanks for this interesting tool! Will merge this now :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi folks!
Congratulations on Nesso-1 — and thank you for the plain Apache 2.0 on the weights. Cofolding models that predict affinity tend to arrive gated behind a form, so it's a nice change to just be able to
pip installand go.This PR adds one line to the badge row:
What bio.rodeo is: A catalog of biological foundation models that I run — roughly 1,800 of them now, growing as I work back through the preprint archives. Each one is scored out of 100 on how much of it was actually released: not the licence label, but the weights, the code, the training data, the docs, and the terms attached to every one of those. The rubric is the Model Openness Framework (https://arxiv.org/abs/2403.13784).
What this badge shows: The usability axis — whether someone can take the release and actually run it, weighted toward weights, inference code and architecture. Nesso-1 scores 100 there, which is the ceiling. Its overall openness score is 75 against a catalog median of 41, and https://bio.rodeo/models/nesso-1#openness breaks that down component by component if you want to see where the two diverge. Happy to point the badge at the overall number instead if you'd rather — it's a one-word change to the URL.
Nothing to maintain once it's in: the badge pulls the number from the API on each render, so it tracks the assessment rather than freezing today's value.
Full disclosure: bio.rodeo is mine, so I'd be delighted if this landed. Equally, it's your README and one more badge may not be what it needs... feel free to close if you don't want to highlight Nesso-1's openness. If some part of the assessment reads wrong to you, though, do say so; there's a "Flag content" link on the model page, or you can just reply here.
Thanks for shipping it open. 🙏