-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leaderboard 2.0: should we fetch data from model card? #1373
Comments
It's not like they are blocked from doing so, right? One option was to use git-lfs. I see some pros and cons of this suggestion:
|
I'd definitely prefer keeping it in one place ( Aside from this, not all models will have model cards (e.g. proprietary ones won't), so we'd have to keep track of this in two places at once. |
Great points, maybe let's edit the README here https://github.com/embeddings-benchmark/mteb/blob/main/docs/adding_a_model.md to say that the preferred way for submissions is via PR to Another advantage of this is that we get the full result files with more metadata |
+1 to everything. If at some point we want to switch over entirely, we could convert the metadata on HF pages into files we can PR into the results repo. |
I agree with everything here. The current benchmark does not support the metadata files from HF. We can either have it fetch from the model metadata from HF or add CI to |
It would be great if we at least transfered the results from the old leaderboard to |
I'll try to collect all available scores |
Add reference for visibility embeddings-benchmark/results#43 |
Moved the discussion to the referenced (embeddings-benchmark/results#43) |
Currently, model metadata files become quite extensive if they cover all tasks in mteb (#1368). This makes it frustrating for users to see what scores a model has (having scores for >30 datasets doesn't really give a great overview). The ideal solution would probably be to either:
mteb_results/*
folderLet me know what you guys think (@Muennighoff, @imenelydiaker, @isaac-chung, @orionw, @x-tabdeveloping)
The text was updated successfully, but these errors were encountered: