[Feature] add lveval benchmark #914
Conversation
| dict( | ||
| type=LVEvalcmrcDataset, | ||
| abbr="LVEval_" + name_len, | ||
| path="Infinigence/LVEval", |
There was a problem hiding this comment.
Thank you for the PR. I noticed the dataset path (Infinigence/LVEval) isn't relative to our project's root. Could you please update it to a relative path, like ./data/LVEval, for better consistency and accessibility?
Also, I can't access the dataset at this path. Could you provide a sample or mock data for testing purposes?
There was a problem hiding this comment.
This is a huggingface data path, which should be directly loaded by hf datasets lib. Could you please access or download from this URL: https://huggingface.co/datasets/Infinigence/LVEval ?
There was a problem hiding this comment.
Sorry for the misunderstanding regarding your data path. My mistake, and I appreciate your patience.
|
Please add a README.md for this dataset. |
* add lveval benchmark * add LVEval readme file * update LVEval readme file * Update configs/eval_bluelm_32k_lveval.py * Update configs/eval_llama2_7b_lveval.py --------- Co-authored-by: yuantao <[email protected]> Co-authored-by: Mo Li <[email protected]>
* add lveval benchmark * add LVEval readme file * update LVEval readme file * Update configs/eval_bluelm_32k_lveval.py * Update configs/eval_llama2_7b_lveval.py --------- Co-authored-by: yuantao <[email protected]> Co-authored-by: Mo Li <[email protected]>
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
Merge LVEval benchmark to opencompass.
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: