Verify evals on Papers with Code

Open
#16 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
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

Start with the linked paper and its seven Papers with Code evaluation pages for S3DIS, ScanNet200, nuScenes, Waymo Open Dataset, ScanNet, and SemanticKITTI. Compare each score, model name, benchmark protocol, and openness metadata with the paper, then report any corrections; the issue does not name repository files or tests.

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

The paper is part of the 3D semantic segmentation task page.

The D-DITR (multi-dataset) result currently ranks first on S3DIS.

The DITR results currently rank first on ScanNet200 and nuScenes.

The DITR result currently ranks second on Waymo Open Dataset.

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 S3DIS
Papers with Code: SOTA on ScanNet200
Papers with Code: SOTA on nuScenes
Papers with Code: #2 on Waymo Open Dataset
Papers with Code: #3 on ScanNet
Papers with Code: #3 on SemanticKITTI

Kind regards,

Niels

Dominant language
Python
Stars
113
Forks
8
PR merge metrics
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 VisualComputingInstitute/ditr

All issues in VisualComputingInstitute/ditr

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.