Subdocs #510
Merged
Subdocs #510
Conversation
This file contains 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
Leymore
reviewed
Oct 27, 2023
| # Import datasets and subjective evaluation summarizer | ||
| from mmengine.config import read_base | ||
| with read_base(): | ||
| from .datasets.subjectivity_cmp.subjectivity_cmp import subjectivity_datasets |
There was a problem hiding this comment.
Suggested change
| from .datasets.subjectivity_cmp.subjectivity_cmp import subjectivity_datasets | |
| from .datasets.subjective_cmp.subjective_cmp import subjective_datasets |
The following is similar, no further repetition.
Comment on lines
52
to
62
| _meta_template = dict( | ||
| round=[ | ||
| dict(role="HUMAN", begin='\n<|im_start|>user\n', end='<|im_end|>'), | ||
| dict( | ||
| role="BOT", | ||
| begin="\n<|im_start|>assistant\n", | ||
| end='<|im_end|>', | ||
| generate=True), | ||
| ], ) | ||
|
|
||
| ... |
There was a problem hiding this comment.
Suggested change
| _meta_template = dict( | |
| round=[ | |
| dict(role="HUMAN", begin='\n<|im_start|>user\n', end='<|im_end|>'), | |
| dict( | |
| role="BOT", | |
| begin="\n<|im_start|>assistant\n", | |
| end='<|im_end|>', | |
| generate=True), | |
| ], ) | |
| ... | |
| models = [...] |
Comment on lines
15
to
16
| 我们提供了一个基于[z-bench](https://github.com/zhenbench/z-bench)的demo测试集：[subjective_demo.xlsx](https://opencompass.openxlab.space/utils/subjective_demo.xlsx | ||
| )。 |
There was a problem hiding this comment.
Suggested change
| 我们提供了一个基于[z-bench](https://github.com/zhenbench/z-bench)的demo测试集：[subjective_demo.xlsx](https://opencompass.openxlab.space/utils/subjective_demo.xlsx | |
| )。 | |
| 我们提供了一个基于[z-bench](https://github.com/zhenbench/z-bench)的demo测试集：[subjective_demo.xlsx](https://opencompass.openxlab.space/utils/subjective_demo.xlsx)。 |
|
|
||
| ## Evaluation Report | ||
|
|
||
| The evaluation report will be output to output/.../summary/timestamp/report.md, which includes win rate statistics, battle scores, and ELO ratings. The specific format is as follows: |
There was a problem hiding this comment.
Do we need to give more details about what is win / tie / lose / not bad / etc. ?
Leymore
approved these changes
Oct 27, 2023
liushz
pushed a commit
to liushz/opencompass
that referenced
this pull request
Nov 27, 2023
* rename * add en subdoc * fix name * fix writing * update --------- Co-authored-by: Leymore <zfz-960727@163.com>
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.
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
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
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: