Skip to content
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

Error when evaluating MMBench_TEST_EN #57

Closed
KosumosuL opened this issue Jan 19, 2024 · 4 comments
Closed

Error when evaluating MMBench_TEST_EN #57

KosumosuL opened this issue Jan 19, 2024 · 4 comments

Comments

@KosumosuL
Copy link

Looks like the annotation in MMBench_TEST_EN does not contains the key "answer"? Yet the prefetch_acc has to access this key, as shown in

if matched == item['answer']:

@YongLD
Copy link

YongLD commented Jan 20, 2024

Because The test_file have no key "answer", I think they do not add the answer of the choise in the file MMBENCH_TEST_EN.tsv.

@kennymckormick
Copy link
Member

Hi, @KosumosuL ,
The label of testing samples is confidential, to obtain the evaluation accuracy of MMBench test split, please upload it to the evaluation service of send it to [email protected]

@KosumosuL
Copy link
Author

Hi, @KosumosuL , The label of testing samples is confidential, to obtain the evaluation accuracy of MMBench test split, please upload it to the evaluation service of send it to [email protected]

I can understand that. My point is, however, the code should consider this situation for avoiding this error, or the readme should point this out.

@kennymckormick
Copy link
Member

Hi, @KosumosuL , The label of testing samples is confidential, to obtain the evaluation accuracy of MMBench test split, please upload it to the evaluation service of send it to [email protected]

I can understand that. My point is, however, the code should consider this situation for avoiding this error, or the readme should point this out.

Hi, @KosumosuL , that's a good point, I have fixed the problem in this commit: e992046, the evaluation skip for MMBench_TEST will be skipped on any non-official servers. You can try again on the latest main branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants