-
Notifications
You must be signed in to change notification settings - Fork 361
Update readme #961
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
Update readme #961
Conversation
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super neat, some nits and notably a small reorg suggestion in the task intro to put more relevant evals first
- **Reasoning**: MUSR, DROP (discrete reasoning) | ||
- **Long Context**: RULER | ||
- **Dialogue**: MT-Bench | ||
- **Holistic Evaluation**: HELM, BIG-Bench |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BigBench is also in knowledge
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would change holistic evaluation to "Across the board capabilities testing" or something like this
adds tasks list to readme, shortens intro paragrpah and add example for python API
adds tasks list to readme, shortens intro paragrpah and add example for python API