Verify evals on Papers with Code

Open
#123 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Quiet
Domain
documentation

Research direction

Open the linked Papers with Code paper and its five verified evaluation entries, then compare their scores, model names, benchmark protocols, and openness metadata with the paper or official release artifacts. Check the linked task, methods, project, and GitHub pages; done means any discrepancies are identified and the relevant Papers with Code metadata is corrected or confirmed.

Written by the indexing model from the issue text.

Description

Hi,

Niels here from the open-source team at Hugging Face. Congratulations on your work!

I've made the paper and 5 verified paper-native evaluations available on Papers with Code.

The paper has results on Document Understanding, OCR, and Image Understanding task pages.

The OV-Encoder-Lang + Qwen3-4B-Instruct2507 results currently rank second on InfoVQA and OCRBench v2.

Would it be possible to verify these results and let me know if any score, model name, benchmark protocol, or openness metadata should be corrected? The imported rows are tied to the paper or its official release artifacts; comparison-table baselines were not added.

You can also edit the task, methods, project page, and GitHub URL directly from the paper page using your Hugging Face account.

If you'd like to showcase the results in your repository README, you can copy these live leaderboard badges (or use the “Copy PwC badge” button in the Results section):

Papers with Code: #2 on InfoVQA
Papers with Code: #2 on OCRBench v2

Kind regards,

Niels

Dominant language
Python
Stars
400
Forks
20
No merged PRs in 30d

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.

More from EvolvingLMMs-Lab/OneVision-Encoder

All issues in EvolvingLMMs-Lab/OneVision-Encoder

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.