-
Notifications
You must be signed in to change notification settings - Fork 405
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
[Feature] Support the reasoning from BaiLing LLM #1541
base: main
Are you sure you want to change the base?
Conversation
This commit includes the access to BaiLing LLM and gets the reasoning.
The example of evalute bailing api
Based on current experiment, we update some generation arguments for better reasoning
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.
For .py
files, please use lowercase. Additionally, the models should be copied into opencompass/configs/modeling
folder.
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.
For .py
files, please use lowercase. Additionally, the models should be copied into opencompass/configs/modeling
folder.
Please fix the lint issue with |
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
We hope opencompass can use the LLM named BaiLing to reason and evaluate it.
Modification
The PR support access the BaiLing HTTP endpoint to get the reasoning result.
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:
After PR: