MatCaviar commited on
Commit
7105a0f
Β·
verified Β·
1 Parent(s): f4ebf88

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +56 -3
README.md CHANGED
@@ -1,3 +1,56 @@
1
- ---
2
- license: apache-2.0
3
- ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: apache-2.0
3
+ ---
4
+ ---
5
+ license: apache-2.0
6
+ ---
7
+ # AlchemistCoder: Harmonizing and Eliciting Code Capability by Hindsight Tuning on Multi-source Data
8
+
9
+ [[πŸ€— HuggingFace](https://huggingface.co/internlm/AlchemistCoder-DS-6.7B)]
10
+ [[πŸ“ƒ Paper](https://arxiv.org/abs/xxxxx)]
11
+ [[🌐 Project Page](https://internlm.github.io/AlchemistCoder/)]
12
+
13
+
14
+ ## ✨ Highlights
15
+ > **Abstract:** *Open-source Large Language Models (LLMs) and their specialized variants, particularly Code LLMs, have recently delivered impressive performance. However, previous Code LLMs are typically fine-tuned on single-source data with limited quality and diversity, which may insufficiently elicit the potential of pre-trained Code LLMs. In this paper, we present AlchemistCoder, a series of Code LLMs with enhanced code generation and generalization capabilities fine-tuned on multi-source data. To achieve this, we pioneer to unveil inherent conflicts among the various styles and qualities in multi-source code corpora and introduce data-specific prompts with hindsight relabeling, termed AlchemistPrompts, to harmonize different data sources and instruction-response pairs. Additionally, we propose incorporating the data construction process into the fine-tuning data as code comprehension tasks, including instruction evolution, data filtering, and code review. Extensive experiments demonstrate that AlchemistCoder holds a clear lead among all models of the same size (6.7B/7B) and rivals or even surpasses larger models (15B/33B/70B), showcasing the efficacy of our method in refining instruction-following capabilities and advancing the boundaries of code intelligence.*
16
+
17
+ - **AlchemistPrompts**: Designed as data-specific prompts for harmonizing inherent conflicts in multi-source data and mitigating the instruction/response misalignment at a fined-grained level.
18
+ - **Code Comprehenstion Tasks**: Sourced from the process of data construction, consisting of instruction evolution, data filtering, and code review.
19
+ - **Harmonized Multi-source Data**: Instruction tuned on 200M tokens, including 6 types of high-quality data.
20
+ - **Superior Model Performance**: Surpassing all the open-source models of the same size (6.7/7B), and rivaling or even beating larger models (15B/33B/70B/ChatGPT) on 6 code benchmarks.
21
+ - **Advanced generic capabilities**: Demonstrated by the significant improvements on MMLU, BBH, and GSM8K.
22
+
23
+
24
+ ## πŸš€ Quick Start
25
+ ```python
26
+ import torch
27
+ from transformers import AutoModelForCausalLM, AutoTokenizer
28
+
29
+ tokenizer = AutoTokenizer.from_pretrained("internlm/AlchemistCoder-L-7B", trust_remote_code=True)
30
+ model = AutoModelForCausalLM.from_pretrained("internlm/AlchemistCoder-L-7B", trust_remote_code=True, torch_dtype=torch.bfloat16).cuda()
31
+ model = model.eval()
32
+
33
+ input_text = "Implement the Dijkstra algorithm in Python"
34
+ inputs = tokenizer(input_text, return_tensors="pt").to(model.device)
35
+ outputs = model.generate(**inputs, max_length=128)
36
+ print(tokenizer.decode(outputs[0], skip_special_tokens=True))
37
+ ```
38
+
39
+
40
+ ## πŸ§ͺ Evaluation and Fine-tune
41
+ Please refer to [**AlchemistCoder**](https://github.com/InternLM/AlchemistCoder) and [**InternLM**](https://github.com/InternLM/InternLM/tree/main).
42
+
43
+ ## πŸ˜ƒ Acknowledgments
44
+ *AlchemistCoder* is built with [**InternLM**](https://github.com/InternLM) and [**OpenCompass**](https://github.com/open-compass). Thanks for their awesome work!
45
+
46
+ ## πŸ“§ Contact
47
+ If you have any questions, please create an issue on this repository or contact us at:
48
49
50
+
51
+ ## 🌟 Citation
52
+ If you find our work useful, please consider citing:
53
+
54
+ ```bibtex
55
+
56
+ ```