google-research / google-research/sam

Verify evals on Papers with Code

Open
#61 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
646
Forks
81
PR merge metrics
No merged PRs in 30d

Description

Hi,

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

I've made the [paper](https://paperswithcode.co/paper/2010.01412) and [2 paper-native evaluations](https://paperswithcode.co/paper/2010.01412#results) available on Papers with Code.

The paper is part of the [Image Classification](https://paperswithcode.co/tasks/image-classification) task page.

The EffNet-L2 (SAM) result currently ranks first on [CIFAR-100](https://paperswithcode.co/benchmark/cifar-100?task=image-classification&eval=10774).

The EffNet-L2 (SAM) result currently ranks third on [Oxford-IIIT Pets](https://paperswithcode.co/benchmark/oxford-iiit-pets?task=image-classification&eval=10773).

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 CIFAR-100](https://paperswithcode.co/api/v1/papers/2010.01412/leaderboard-badge.svg?eval=10774&live=1)](https://paperswithcode.co/api/v1/papers/2010.01412/leaderboard-badge-link?eval=10774)
[![Papers with Code: #3 on Oxford-IIIT Pets](https://paperswithcode.co/api/v1/papers/2010.01412/leaderboard-badge.svg?eval=10773&live=1)](https://paperswithcode.co/api/v1/papers/2010.01412/leaderboard-badge-link?eval=10773)

Kind regards,

Niels

Contributor guide

Open the contributing guide

Research direction

Start with the linked Papers with Code paper, Image Classification task page, and CIFAR-100 and Oxford-IIIT Pets result pages, then compare their scores, model name, protocols, and openness metadata with the repository's published information. Done means confirming the entries or reporting specific corrections to the relevant result or project metadata.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation, machine-learning
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.