open-compass / open-compass/VLMEvalKit

TextVQA results on LLaVA 1.5 and 1.6

Open
#855 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
4.4k
Forks
768
Avg merge
1d 10h
Merged PRs (30d)
17

Description

  1. I'm confused as to why for llava1.5, the model used is "liuhaotian/llava-v1.5-7b", but for llava 1.6, it's "llava-hf/llava-v1.6-vicuna-7b-hf" instead of "liuhaotian/llava-v1.6-vicuna-7b"?
  2. I run the code on "llava_v1.5_7b" but got result only 21.9, which is much lower than the official results of LLaVA. Why did such results occur?
  3. For "llava_next_vicuna_7b", when I use the original configuration code ("llava-hf/llava-v1.6-vicuna-7b-hf"), the acc is bout 63.9. However, when I change the model to "liuhaotian/llava-v1.6-vicuna-7b" ("llava_next_vicuna_7b": partial(LLaVA, model_path="liuhaotian/llava-v1.6-vicuna-7b"),), the accuracy is suddenly drops to 25.47.
  4. I notice that for llava, the authors use OCR tokens in the inference process. But it seems that in VLMEvalKit, the OCR tokens are not used?

I'm really confused about these questions. Looking forward to your reply.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the llava_v1.5_7b and llava_next_vicuna_7b model configurations named in the issue, then trace the TextVQA inference path and its OCR-token handling. Reproduce the reported accuracy differences with both model paths and document whether the results and OCR behavior match the expected configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
computer-vision, machine-learning, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.