open-compass / open-compass/VLMEvalKit
Discrepancy in MM Math Evaluation Results: Possible Issue with Answer Extraction in VLMEvalkit
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 768
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 17
Description
Hi, everyone.
I’ve noticed a significant discrepancy between the evaluation results of the MM Math dataset and the results reported in the original paper.
In the original MM Math paper, GPT-4o achieved an accuracy of 31.8%, but the evaluation result using VLMEvalkit is only 22.5%.
This difference doesn’t seem to be caused by randomness in the model's outputs. Upon reviewing the code, I found that VLMEvalkit uses the answer extraction code provided by the original MM Math repository.
However, the current code seems to match every occurrence of the answer enclosed in \boxed{} in the output (see this line). This may lead to incorrect judgments if the model outputs the correct answer multiple times.
I believe this might be the reason for the performance discrepancy compared to the original MM Math paper.
Additionally, since the answers in this dataset are open-ended, using an LLM for answer extraction and comparison might be a better option than the hardcoded matching approach.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in vlmeval/dataset/mmmath.py at the answer-extraction code around line 315. Compare how repeated \boxed{} answers are matched with the behavior and results reported for the original MM Math evaluation, then determine whether extraction explains the discrepancy. Done means the suspected behavior is verified or ruled out and the appropriate extraction change is clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100