gmberton / gmberton/VPR-methods-evaluation

Verify evals on Papers with Code

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

Nobody has claimed this yet.

Dominant language
Python
Stars
203
Forks
34
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 and 48 paper-native evaluations available on Papers with Code.

The paper is part of the Visual Place Recognition task page.

The EigenPlaces (ResNet-50, 2048D) result currently ranks first on St Lucia.

The EigenPlaces (ResNet-50, 2048D) result currently ranks third on San Francisco Landmark.

The EigenPlaces (ResNet-50, 512D) results currently rank third on two metrics on San Francisco Landmark.

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 St Lucia
Papers with Code: #3 on San Francisco Landmark

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 linked paper and its 48 Papers with Code evaluations, then compare the EigenPlaces entries for St Lucia and San Francisco Landmark with the repository's published results. Verify the scores, model names, benchmark protocols, and openness metadata, and report any corrections needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
computer-vision
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.