Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Verify evals on Papers with Code

Open
  • Is something wrong?
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the linked Papers with Code paper and its MMAU and MMSU result pages, then compare the imported scores, model name, benchmark protocols, and openness metadata with the paper or official release artifacts. The work is done when each result is confirmed or the needed corrections are identified and communicated.

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 2 verified paper-native evaluations available on Papers with Code.

The paper is part of the Audio understanding task page.

The Step-Audio-R1.5 results currently rank second on MMAU and MMSU.

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 MMAU
Papers with Code: #2 on MMSU

Kind regards,

Niels

Dominant language
Python
Stars
699
Forks
51
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 stepfun-ai/Step-Audio-R1

All issues in stepfun-ai/Step-Audio-R1

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.