ClΓ©mentine commited on
Commit
2246286
β€’
1 Parent(s): a1272b7

added FAQ in about tab

Browse files
Files changed (2) hide show
  1. app.py +2 -0
  2. src/display/about.py +73 -14
app.py CHANGED
@@ -9,6 +9,7 @@ from src.display.about import (
9
  EVALUATION_QUEUE_TEXT,
10
  INTRODUCTION_TEXT,
11
  LLM_BENCHMARKS_TEXT,
 
12
  TITLE,
13
  )
14
  from src.display.css_html_js import custom_css
@@ -269,6 +270,7 @@ with demo:
269
  gr.Plot(value=chart, min_width=500)
270
  with gr.TabItem("πŸ“ About", elem_id="llm-benchmark-tab-table", id=2):
271
  gr.Markdown(LLM_BENCHMARKS_TEXT, elem_classes="markdown-text")
 
272
 
273
  with gr.TabItem("πŸš€ Submit here! ", elem_id="llm-benchmark-tab-table", id=3):
274
  with gr.Column():
 
9
  EVALUATION_QUEUE_TEXT,
10
  INTRODUCTION_TEXT,
11
  LLM_BENCHMARKS_TEXT,
12
+ FAQ_TEXT,
13
  TITLE,
14
  )
15
  from src.display.css_html_js import custom_css
 
270
  gr.Plot(value=chart, min_width=500)
271
  with gr.TabItem("πŸ“ About", elem_id="llm-benchmark-tab-table", id=2):
272
  gr.Markdown(LLM_BENCHMARKS_TEXT, elem_classes="markdown-text")
273
+ gr.Markdown(FAQ_TEXT, elem_classes="markdown-text")
274
 
275
  with gr.TabItem("πŸš€ Submit here! ", elem_id="llm-benchmark-tab-table", id=3):
276
  with gr.Column():
src/display/about.py CHANGED
@@ -10,22 +10,9 @@ The leaderboard's backend runs the great [Eleuther AI Language Model Evaluation
10
  """
11
 
12
  LLM_BENCHMARKS_TEXT = f"""
13
- Useful links: [FAQ](https://huggingface.co/spaces/HuggingFaceH4/open_llm_leaderboard/discussions/179), [Community resources](https://huggingface.co/spaces/HuggingFaceH4/open_llm_leaderboard/discussions/174), [Collection of best models](https://huggingface.co/collections/open-llm-leaderboard/llm-leaderboard-best-models-652d6c7965a4619fb5c27a03).
14
-
15
  # Context
16
  With the plethora of large language models (LLMs) and chatbots being released week upon week, often with grandiose claims of their performance, it can be hard to filter out the genuine progress that is being made by the open-source community and which model is the current state of the art.
17
 
18
- ## Icons
19
- - {ModelType.PT.to_str(" : ")} model: new, base models, trained on a given corpora
20
- - {ModelType.FT.to_str(" : ")} model: pretrained models finetuned on more data
21
- Specific fine-tune subcategories (more adapted to chat):
22
- - {ModelType.IFT.to_str(" : ")} model: instruction fine-tunes, which are model fine-tuned specifically on datasets of task instruction
23
- - {ModelType.RL.to_str(" : ")} model: reinforcement fine-tunes, which usually change the model loss a bit with an added policy.
24
- If there is no icon, we have not uploaded the information on the model yet, feel free to open an issue with the model information!
25
-
26
- "Flagged" indicates that this model has been flagged by the community, and should probably be ignored! Clicking the link will redirect you to the discussion about the model.
27
- (For ex, the model was trained on the evaluation data, and is therefore cheating on the leaderboard.)
28
-
29
  ## How it works
30
 
31
  πŸ“ˆ We evaluate models on 7 key benchmarks using the <a href="https://github.com/EleutherAI/lm-evaluation-harness" target="_blank"> Eleuther AI Language Model Evaluation Harness </a>, a unified framework to test generative language models on a large number of different evaluation tasks.
@@ -66,18 +53,90 @@ Side note on the baseline scores:
66
  - for log-likelihood evaluation, we select the random baseline
67
  - for GSM8K, we select the score obtained in the paper after finetuning a 6B model on the full GSM8K training set for 50 epochs
68
 
 
 
 
 
 
 
 
 
 
 
69
  ## Quantization
70
  To get more information about quantization, see:
71
  - 8 bits: [blog post](https://huggingface.co/blog/hf-bitsandbytes-integration), [paper](https://arxiv.org/abs/2208.07339)
72
  - 4 bits: [blog post](https://huggingface.co/blog/4bit-transformers-bitsandbytes), [paper](https://arxiv.org/abs/2305.14314)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
73
  """
74
 
 
75
  EVALUATION_QUEUE_TEXT = """
76
  # Evaluation Queue for the πŸ€— Open LLM Leaderboard
77
 
78
  Models added here will be automatically evaluated on the πŸ€— cluster.
79
 
80
- ## Some good practices before submitting a model
81
 
82
  ### 1) Make sure you can load your model and tokenizer using AutoClasses:
83
  ```python
 
10
  """
11
 
12
  LLM_BENCHMARKS_TEXT = f"""
 
 
13
  # Context
14
  With the plethora of large language models (LLMs) and chatbots being released week upon week, often with grandiose claims of their performance, it can be hard to filter out the genuine progress that is being made by the open-source community and which model is the current state of the art.
15
 
 
 
 
 
 
 
 
 
 
 
 
16
  ## How it works
17
 
18
  πŸ“ˆ We evaluate models on 7 key benchmarks using the <a href="https://github.com/EleutherAI/lm-evaluation-harness" target="_blank"> Eleuther AI Language Model Evaluation Harness </a>, a unified framework to test generative language models on a large number of different evaluation tasks.
 
53
  - for log-likelihood evaluation, we select the random baseline
54
  - for GSM8K, we select the score obtained in the paper after finetuning a 6B model on the full GSM8K training set for 50 epochs
55
 
56
+ ## Icons
57
+ - {ModelType.PT.to_str(" : ")} model: new, base models, trained on a given corpora
58
+ - {ModelType.FT.to_str(" : ")} model: pretrained models finetuned on more data
59
+ Specific fine-tune subcategories (more adapted to chat):
60
+ - {ModelType.IFT.to_str(" : ")} model: instruction fine-tunes, which are model fine-tuned specifically on datasets of task instruction
61
+ - {ModelType.RL.to_str(" : ")} model: reinforcement fine-tunes, which usually change the model loss a bit with an added policy.
62
+ If there is no icon, we have not uploaded the information on the model yet, feel free to open an issue with the model information!
63
+
64
+ "Flagged" indicates that this model has been flagged by the community, and should probably be ignored! Clicking the link will redirect you to the discussion about the model.
65
+
66
  ## Quantization
67
  To get more information about quantization, see:
68
  - 8 bits: [blog post](https://huggingface.co/blog/hf-bitsandbytes-integration), [paper](https://arxiv.org/abs/2208.07339)
69
  - 4 bits: [blog post](https://huggingface.co/blog/4bit-transformers-bitsandbytes), [paper](https://arxiv.org/abs/2305.14314)
70
+
71
+ ## Useful links
72
+ - [Community resources](https://huggingface.co/spaces/HuggingFaceH4/open_llm_leaderboard/discussions/174)
73
+ - [Collection of best models](https://huggingface.co/collections/open-llm-leaderboard/llm-leaderboard-best-models-652d6c7965a4619fb5c27a03)
74
+ """
75
+
76
+ FAQ_TEXT = """
77
+ ---------------------------
78
+ # FAQ
79
+ Below are some common questions - if this FAQ does not answer you, feel free to create a new issue, and we'll take care of it as soon as we can!
80
+
81
+ ## 1) Submitting a model
82
+ My model requires `trust_remote_code=True`, can I submit it?
83
+ - *We only support models that have been integrated in a stable version of the `transformers` library for automatic submission, as we don't want to run possibly unsage code on our cluster.*
84
+
85
+ What about models of type X?
86
+ - *We only support models that have been integrated in a stable version of the `transformers` library for automatic submission.*
87
+
88
+ How can I follow when my model is launched?
89
+ - *You can look for its request file [here](https://huggingface.co/datasets/open-llm-leaderboard/requests) and follow the status evolution, or directly in the queues above the submit form.*
90
+
91
+ My model disappeared from all the queues, what happened?
92
+ - *A model disappearing from all the queues usually means that there has been a failure. You can check if that is the case by looking for your model [here](https://huggingface.co/datasets/open-llm-leaderboard/requests).*
93
+
94
+ What causes an evaluation failure?
95
+ - *Most of the failures we get come from problems in the submissions (corrupted files, config problems, wrong parameters selected for eval ...), so we'll be grateful if you first make sure you have followed the steps in `About`. However, from time to time, we have failures on our side (hardware/node failures, problem with an update of our backend, connectivity problem ending up in the results not being saved, ...).*
96
+
97
+ How can I report an evaluation failure?
98
+ - *As we store the logs for all models, feel free to create an issue, **where you link to the requests file of your model** (look for it [here](https://huggingface.co/datasets/open-llm-leaderboard/requests/tree/main)), so we can investigate! If the model failed due to a problem on our side, we'll relaunch it right away!*
99
+ *Note: Please do not re-upload your model under a different name, it will not help*
100
+
101
+ ## 2) Model results
102
+ What kind of information can I find?
103
+ - *Let's imagine you are interested in the Yi-34B results. You have access to 3 different information categories:*
104
+ - *The [request file](https://huggingface.co/datasets/open-llm-leaderboard/requests/blob/main/01-ai/Yi-34B_eval_request_False_bfloat16_Original.json): it gives you information about the status of the evaluation*
105
+ - *The [aggregated results folder](https://huggingface.co/datasets/open-llm-leaderboard/results/tree/main/01-ai/Yi-34B): it gives you aggregated scores, per experimental run*
106
+ - *The [details dataset](https://huggingface.co/datasets/open-llm-leaderboard/details_01-ai__Yi-34B/tree/main): it gives you the full details (scores and examples for each task and a given model)*
107
+
108
+
109
+ Why do models appear several times in the leaderboard?
110
+ - *We run evaluations with user selected precision and model commit. Sometimes, users submit specific models at different commits and at different precisions (for example, in float16 and 4bit to see how quantization affects performance). You should be able to verify this by displaying the `precision` and `model sha` columns in the display. If, however, you see models appearing several time with the same precision and hash commit, this is not normal.*
111
+
112
+ What is this concept of "flagging"?
113
+ - *This mechanism allows user to report models that have unfair performance on the leaderboard. This contains several categories: exceedingly good results on the leaderboard because the model was (maybe accidentally) trained on the evaluation data, models that are copy of other models not atrributed properly, etc.*
114
+
115
+ My model has been flagged improperly, what can I do?
116
+ - *Every flagged model has a discussion associated with it - feel free to plead your case there, and we'll see what to do together with the community.*
117
+
118
+ ## 3) Editing a submission
119
+ I upgraded my model and want to re-submit, how can I do that?
120
+ - *Please open an issue with the precise name of your model, and we'll remove your model from the leaderboard so you can resubmit. You can also resubmit directly with the new commit hash!*
121
+
122
+ I need to rename my model, how can I do that?
123
+ - *You can use @Weyaxi 's [super cool tool](https://huggingface.co/spaces/Weyaxi/open-llm-leaderboard-renamer) to request model name changes, then open a discussion where you link to the created pull request, and we'll check them and merge them as needed.*
124
+
125
+ ## 4) Other
126
+ Why don't you display closed source model scores?
127
+ - *This is a leaderboard for Open models, both for philosophical reasons (openness is cool) and for practical reasons: we want to ensure that the results we display are accurate and reproducible, but 1) commercial closed models can change their API thus rendering any scoring at a given time incorrect 2) we re-run everything on our cluster to ensure all models are run on the same setup and you can't do that for these models.*
128
+
129
+ I have an issue about accessing the leaderboard through the Gradio API
130
+ - *Since this is not the recommended way to access the leaderboard, we won't provide support for this, but you can look at tools provided by the community for inspiration!*
131
  """
132
 
133
+
134
  EVALUATION_QUEUE_TEXT = """
135
  # Evaluation Queue for the πŸ€— Open LLM Leaderboard
136
 
137
  Models added here will be automatically evaluated on the πŸ€— cluster.
138
 
139
+ ## First steps before submitting a model
140
 
141
  ### 1) Make sure you can load your model and tokenizer using AutoClasses:
142
  ```python