NVIDIA-NeMo / NVIDIA-NeMo/Megatron-Bridge

Verify evals on Papers with Code

Open
#5,017 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:model community-request needs-triage support
Dominant language
Python
Stars
920
Forks
505
Avg merge
1d 16h
Merged PRs (30d)
253

Description

Hi,

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

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

The paper has results on Image Understanding, Computer Use Agents, OCR, and 8 additional task pages.

The Nemotron 3 Nano Omni (Reasoning) result currently ranks second on OCRBench v2.

The Nemotron 3 Nano Omni result currently ranks third on ScreenSpot.

The Nemotron 3 Nano Omni (Reasoning) result currently ranks third on RefCOCO.

The Nemotron 3 Nano Omni (Reasoning) result currently ranks fourth on CharXiv (DQ).

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 OCRBench v2
Papers with Code: #3 on RefCOCO
Papers with Code: #3 on ScreenSpot

Kind regards,

Niels

Contributor guide

Open the contributing guide

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 reviewing the linked Papers with Code paper, its 26 verified evaluations, and the listed OCRBench v2, ScreenSpot, RefCOCO, and CharXiv results. Compare the scores, model names, benchmark protocols, and openness metadata with the paper or official release artifacts. Done means reporting any discrepancies and confirming which imported results are accurate.

Written by the indexing model from the issue text.

Assessment

Tech stack
huggingface
Domain
documentation, machine-learning
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.