Update README.md
Browse files
README.md
CHANGED
|
@@ -30,8 +30,6 @@ For more details, you can refer to our [technical report](https://github.com/Mot
|
|
| 30 |
- Training time: 42 days
|
| 31 |
- Training data: 2.4T tokens
|
| 32 |
|
| 33 |
-
*Notice: A detailed technical report will be released at a later time.*
|
| 34 |
-
|
| 35 |
# Evaluation
|
| 36 |
|
| 37 |
When models are released, their accompanying technical reports or papers often present benchmark results based on evaluation settings chosen by the developers. While this is a common and understandable practice, it can lead to challenges when comparing models across different organizations. The same model may yield different scores depending on evaluation conditions, and details of these conditions are not always fully disclosed. This lack of standardization can make it difficult for the open-source community to interpret and trust reported results. We therefore reference performance scores based on the official numbers reported by each model’s developers in their respective publications.
|
|
|
|
| 30 |
- Training time: 42 days
|
| 31 |
- Training data: 2.4T tokens
|
| 32 |
|
|
|
|
|
|
|
| 33 |
# Evaluation
|
| 34 |
|
| 35 |
When models are released, their accompanying technical reports or papers often present benchmark results based on evaluation settings chosen by the developers. While this is a common and understandable practice, it can lead to challenges when comparing models across different organizations. The same model may yield different scores depending on evaluation conditions, and details of these conditions are not always fully disclosed. This lack of standardization can make it difficult for the open-source community to interpret and trust reported results. We therefore reference performance scores based on the official numbers reported by each model’s developers in their respective publications.
|