Spaces:
Running
Running
app.py
CHANGED
@@ -38,7 +38,7 @@ with gr.Blocks() as demo:
|
|
38 |
with gr.Column():
|
39 |
gr.Markdown(
|
40 |
"""<h1>The Optimal Vocabulary Size Predictor</h1>
|
41 |
-
<
|
42 |
This tool is used to predict the optimal vocabulary size given the non-vocabulary parameters.
|
43 |
We provide 3 ways for prediction:
|
44 |
|
@@ -50,7 +50,7 @@ with gr.Blocks() as demo:
|
|
50 |
Approach 3 will not only consider the case above, but also consider the case when the amount of data does not satisfy the optimal compute allocation, and can calculate the optimal vocabulary size with specified FLOPs.
|
51 |
|
52 |
**Thanks for trying** πππ!
|
53 |
-
</
|
54 |
""")
|
55 |
|
56 |
with gr.Row():
|
|
|
38 |
with gr.Column():
|
39 |
gr.Markdown(
|
40 |
"""<h1>The Optimal Vocabulary Size Predictor</h1>
|
41 |
+
<p style='font-size: 18px;'>
|
42 |
This tool is used to predict the optimal vocabulary size given the non-vocabulary parameters.
|
43 |
We provide 3 ways for prediction:
|
44 |
|
|
|
50 |
Approach 3 will not only consider the case above, but also consider the case when the amount of data does not satisfy the optimal compute allocation, and can calculate the optimal vocabulary size with specified FLOPs.
|
51 |
|
52 |
**Thanks for trying** πππ!
|
53 |
+
</p>
|
54 |
""")
|
55 |
|
56 |
with gr.Row():
|