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

Verify evals on Papers with Code

Open
#3,717 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the linked Papers with Code paper page and its CALLHOME Part2 and CALLHOME Part2 Two-Speaker evaluation pages. Compare the displayed scores, model name, benchmark protocol, and openness metadata with the paper, then check the repository README if the leaderboard badges are relevant. Done means reporting any discrepancies or confirming that the entries are correct.

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

The paper is part of the Speaker Diarization task page.

The TOLD (EEND-OLA + SOAP) results currently rank first on CALLHOME Part2 (diarization) and CALLHOME Part2 Two-Speaker (diarization).

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 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: SOTA on CALLHOME Part2 (diarization)
Papers with Code: SOTA on CALLHOME Part2 Two-Speaker (diarization)

Kind regards,

Niels

Dominant language
Python
Stars
20.4k
Forks
2k
Avg merge
6h 31m
Merged PRs (30d)
169

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.

More from modelscope/FunASR

All issues in modelscope/FunASR

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.