Titovs jdev8 commited on
Commit
2ba7b66
1 Parent(s): 016356f

Update README.md (#5)

Browse files

- Update README.md (9977838f7f1b6b7045cc1102162f1ea76ba71fe3)


Co-authored-by: Anton Shapkin <[email protected]>

Files changed (1) hide show
  1. README.md +9 -2
README.md CHANGED
@@ -47,11 +47,14 @@ The model was trained on one A100 GPU with following hyperparameters:
47
  | `max_lr` | 1e-4 |
48
  | `scheduler` | linear |
49
  | `total_batch_size` | 256 (~130K tokens per step) |
 
50
 
 
51
 
52
  # Fine-tuning data
53
 
54
- For this model we used 15K exmaples of Kotlin Exercices dataset {TODO: link!}. For more information about the dataset follow th link.
 
55
 
56
  # Evaluation
57
 
@@ -62,4 +65,8 @@ Fine-tuned model:
62
  | **Model name** | **Kotlin HumanEval Pass Rate** | **Kotlin Completion** |
63
  |:---------------------------:|:----------------------------------------:|:----------------------------------------:|
64
  | `base model` | 26.89 | 0.388 |
65
- | `fine-tuned model` | 42.24 | 0.344 |
 
 
 
 
 
47
  | `max_lr` | 1e-4 |
48
  | `scheduler` | linear |
49
  | `total_batch_size` | 256 (~130K tokens per step) |
50
+ | `num_epochs` | 4 |
51
 
52
+ More details about finetuning can be found in the technical report
53
 
54
  # Fine-tuning data
55
 
56
+ For this model we used 15K exmaples of Kotlin Exercices dataset {TODO: link!}. Every example follows HumanEval like format. In total dataset contains about 3.5M tokens.
57
+ For more information about the dataset follow the link.
58
 
59
  # Evaluation
60
 
 
65
  | **Model name** | **Kotlin HumanEval Pass Rate** | **Kotlin Completion** |
66
  |:---------------------------:|:----------------------------------------:|:----------------------------------------:|
67
  | `base model` | 26.89 | 0.388 |
68
+ | `fine-tuned model` | 42.24 | 0.344 |
69
+
70
+ # Ethical Considerations and Limitations
71
+
72
+ Code Llama and its variants are a new technology that carries risks with use. The testing conducted to date could not cover all scenarios. For these reasons, as with all LLMs, Kexer's potential outputs cannot be predicted in advance, and the model may in some instances produce inaccurate or objectionable responses to user prompts. The model was fine-tuned on a specific data format (Kotlin tasks), and deviation from this format can also lead to inaccurate or undesirable responses to user queries. Therefore, before deploying any applications of Kexer, developers should perform safety testing and tuning tailored to their specific applications of the model.