-
Notifications
You must be signed in to change notification settings - Fork 13
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
This benchmark could lead to wrong conclusion. #7
Comments
We adopt the answer ranking strategy [1, 2, 3] for evaluating existing MLLMs with multiple-choice questions. Specifically, for each choice of a question, we compute the likelihood that an MLLM generates the content of this choice given the question. We select the choice with the highest likelihood as model’s prediction. Our evaluation strategy does not rely on the instruction-following capabilities of models to output “A” or “B” or “C” or “D”. [1] Dai, Wenliang, et al. "InstructBLIP: Towards General-purpose Vision-Language Models with Instruction Tuning." arXiv preprint arXiv:2305.06500 (2023). https://arxiv.org/abs/2305.06500 |
I understand, and am simply pointing out the fundamental flaws using likelihood as an evaluation index: this may not be the best approach to evaluate a LLM. |
Thank you for sharing your findings. With multiple-choice questions, our benchmark aims to provide an objective and effective evaluation of Multimodal LLMs, since it is difficult to evaluate open-form prediction objectively. However, currently, considering that some Multimodal LLMs lack the instruction-following capabilities to output “A” or “B” or “C” or “D”, we follow previous work to adopt the answer ranking strategy for a fair comparison. Since LLaVA-vicuna-7B is fine-tuned on multimodal data with relatively long texts, it may not be good at responding to short answers in our choices. We haven't found similar observations in other models as you point out. |
Example false evaluation:
The model's answer was correct as shown in
open_prediction
. However, the metrics said otherwise.---- update
After checking on around 120 examples, I found that the false evaluation rate is above 50%. There can be either false positive or false negative matches.
False negative match:
False positive match:
The model used for the above test is finetuned
LLaVA-vicuna-7B
The text was updated successfully, but these errors were encountered: