microsoft / microsoft/MoGe

Verify evals on Papers with Code

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

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
3k
Forks
234
PR merge metrics
No merged PRs in 30d

Description

Hi,

Niels here from the open-source team at Hugging Face.

I've made the following papers and their evaluation results available on Papers with Code:

The MoGe-3 (ViT-G) results currently rank first on DIODE (relative), ETH3D (relative), KITTI (relative), and Sintel (relative).

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?

You can also edit the task, methods, project page, and GitHub URL directly from each 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: SOTA on DIODE (relative)
Papers with Code: SOTA on ETH3D (relative)
Papers with Code: SOTA on KITTI (relative)
Papers with Code: SOTA on Sintel (relative)
Papers with Code: #2 on NYUv2 (relative)
Papers with Code: #2 on iBims-1 (metric)

Kind regards,

Niels

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 with the Papers with Code pages for MoGe-2 and MoGe-3 linked in the issue, then review the listed evaluation results and leaderboard entries. Verify the score, model name, benchmark protocol, and openness metadata against the papers and project information. Done means reporting any corrections needed or confirming that the entries are accurate.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.