Spaces:
Runtime error
Runtime error
pminervini
commited on
Commit
•
a008a91
1
Parent(s):
b495946
update
Browse files- src/display/about.py +91 -4
src/display/about.py
CHANGED
@@ -96,16 +96,78 @@ If there is no icon, we have not uploaded the information on the model yet, feel
|
|
96 |
FAQ_TEXT = """
|
97 |
---------------------------
|
98 |
# FAQ
|
|
|
|
|
99 |
## 1) Submitting a model
|
100 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
101 |
## 2) Model results
|
102 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
103 |
## 3) Editing a submission
|
104 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
105 |
"""
|
106 |
|
107 |
EVALUATION_QUEUE_TEXT = """
|
108 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
109 |
"""
|
110 |
|
111 |
CITATION_BUTTON_LABEL = "Copy the following snippet to cite these results"
|
@@ -117,4 +179,29 @@ CITATION_BUTTON_TEXT = r"""
|
|
117 |
publisher = {Hugging Face},
|
118 |
howpublished = "\url{https://huggingface.co/spaces/hallucinations-leaderboard/leaderboard}"
|
119 |
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
120 |
"""
|
|
|
96 |
FAQ_TEXT = """
|
97 |
---------------------------
|
98 |
# FAQ
|
99 |
+
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!
|
100 |
+
|
101 |
## 1) Submitting a model
|
102 |
+
My model requires `trust_remote_code=True`, can I submit it?
|
103 |
+
- *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.*
|
104 |
+
What about models of type X?
|
105 |
+
- *We only support models that have been integrated in a stable version of the `transformers` library for automatic submission.*
|
106 |
+
How can I follow when my model is launched?
|
107 |
+
- *You can look for its request file [here](https://huggingface.co/datasets/hallucinations-leaderboard/requests) and follow the status evolution, or directly in the queues above the submit form.*
|
108 |
+
My model disappeared from all the queues, what happened?
|
109 |
+
- *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/hallucinations-leaderboard/requests).*
|
110 |
+
What causes an evaluation failure?
|
111 |
+
- *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, ...).*
|
112 |
+
How can I report an evaluation failure?
|
113 |
+
- *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/hallucinations-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!*
|
114 |
+
*Note: Please do not re-upload your model under a different name, it will not help*
|
115 |
+
|
116 |
## 2) Model results
|
117 |
+
What kind of information can I find?
|
118 |
+
- *Let's imagine you are interested in the Yi-34B results. You have access to 3 different information categories:*
|
119 |
+
- *The [request file](https://huggingface.co/datasets/hallucinations-leaderboard/requests/blob/main/01-ai/Yi-34B_eval_request_False_bfloat16_Original.json): it gives you information about the status of the evaluation*
|
120 |
+
- *The [aggregated results folder](https://huggingface.co/datasets/hallucinations-leaderboard/results/tree/main/01-ai/Yi-34B): it gives you aggregated scores, per experimental run*
|
121 |
+
Why do models appear several times in the leaderboard?
|
122 |
+
- *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.*
|
123 |
+
What is this concept of "flagging"?
|
124 |
+
- *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.*
|
125 |
+
My model has been flagged improperly, what can I do?
|
126 |
+
- *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.*
|
127 |
+
|
128 |
## 3) Editing a submission
|
129 |
+
I upgraded my model and want to re-submit, how can I do that?
|
130 |
+
- *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!*
|
131 |
+
|
132 |
+
## 4) Other
|
133 |
+
Why don't you display closed source model scores?
|
134 |
+
- *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.*
|
135 |
+
I have an issue about accessing the leaderboard through the Gradio API
|
136 |
+
- *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!*
|
137 |
"""
|
138 |
|
139 |
EVALUATION_QUEUE_TEXT = """
|
140 |
+
# Evaluation Queue for the Hallucinations Leaderboard
|
141 |
+
Models added here will be automatically evaluated on the EIDF cluster.
|
142 |
+
|
143 |
+
## First steps before submitting a model
|
144 |
+
### 1) Make sure you can load your model and tokenizer using AutoClasses:
|
145 |
+
```python
|
146 |
+
from transformers import AutoConfig, AutoModel, AutoTokenizer
|
147 |
+
config = AutoConfig.from_pretrained("your model name", revision=revision)
|
148 |
+
model = AutoModel.from_pretrained("your model name", revision=revision)
|
149 |
+
tokenizer = AutoTokenizer.from_pretrained("your model name", revision=revision)
|
150 |
+
```
|
151 |
+
If this step fails, follow the error messages to debug your model before submitting it. It's likely your model has been improperly uploaded.
|
152 |
+
Note: make sure your model is public!
|
153 |
+
Note: if your model needs `use_remote_code=True`, we do not support this option yet but we are working on adding it, stay posted!
|
154 |
+
|
155 |
+
### 2) Convert your model weights to [safetensors](https://huggingface.co/docs/safetensors/index)
|
156 |
+
It's a new format for storing weights which is safer and faster to load and use. It will also allow us to add the number of parameters of your model to the `Extended Viewer`!
|
157 |
+
|
158 |
+
### 3) Make sure your model has an open license!
|
159 |
+
This is a leaderboard for Open LLMs, and we'd love for as many people as possible to know they can use your model 🤗
|
160 |
+
|
161 |
+
### 4) Fill up your model card
|
162 |
+
When we add extra information about models to the leaderboard, it will be automatically taken from the model card
|
163 |
+
|
164 |
+
### 5) Select the correct precision
|
165 |
+
Not all models are converted properly from `float16` to `bfloat16`, and selecting the wrong precision can sometimes cause evaluation error (as loading a `bf16` model in `fp16` can sometimes generate NaNs, depending on the weight range).
|
166 |
+
|
167 |
+
## In case of model failure
|
168 |
+
If your model is displayed in the `FAILED` category, its execution stopped.
|
169 |
+
Make sure you have followed the above steps first.
|
170 |
+
If everything is done, check you can launch the EleutherAIHarness on your model locally, using the command in the About tab under "Reproducibility" with all arguments specified (you can add `--limit` to limit the number of examples per task).
|
171 |
"""
|
172 |
|
173 |
CITATION_BUTTON_LABEL = "Copy the following snippet to cite these results"
|
|
|
179 |
publisher = {Hugging Face},
|
180 |
howpublished = "\url{https://huggingface.co/spaces/hallucinations-leaderboard/leaderboard}"
|
181 |
}
|
182 |
+
|
183 |
+
@software{eval-harness,
|
184 |
+
author = {Gao, Leo and
|
185 |
+
Tow, Jonathan and
|
186 |
+
Biderman, Stella and
|
187 |
+
Black, Sid and
|
188 |
+
DiPofi, Anthony and
|
189 |
+
Foster, Charles and
|
190 |
+
Golding, Laurence and
|
191 |
+
Hsu, Jeffrey and
|
192 |
+
McDonell, Kyle and
|
193 |
+
Muennighoff, Niklas and
|
194 |
+
Phang, Jason and
|
195 |
+
Reynolds, Laria and
|
196 |
+
Tang, Eric and
|
197 |
+
Thite, Anish and
|
198 |
+
Wang, Ben and
|
199 |
+
Wang, Kevin and
|
200 |
+
Zou, Andy},
|
201 |
+
title = {A framework for few-shot language model evaluation},
|
202 |
+
month = sep,
|
203 |
+
year = 2021,
|
204 |
+
publisher = {Zenodo},
|
205 |
+
version = {v0.0.1},
|
206 |
+
doi = {10.
|
207 |
"""
|