PEFT
Safetensors
lora
qlora
code-generation
python
Raghul09 commited on
Commit
acae1ff
·
verified ·
1 Parent(s): 489a8d5

Upload README.md with huggingface_hub

Browse files
Files changed (1) hide show
  1. README.md +97 -164
README.md CHANGED
@@ -1,199 +1,132 @@
1
  ---
2
- library_name: transformers
3
- tags: []
 
 
 
4
  ---
5
 
6
- # Model Card for Model ID
7
 
8
- <!-- Provide a quick summary of what the model is/does. -->
 
 
9
 
 
 
 
10
 
 
11
 
12
- ## Model Details
13
 
14
- ### Model Description
 
 
 
15
 
16
- <!-- Provide a longer summary of what this model is. -->
 
17
 
18
- This is the model card of a 🤗 transformers model that has been pushed on the Hub. This model card has been automatically generated.
 
19
 
20
- - **Developed by:** [More Information Needed]
21
- - **Funded by [optional]:** [More Information Needed]
22
- - **Shared by [optional]:** [More Information Needed]
23
- - **Model type:** [More Information Needed]
24
- - **Language(s) (NLP):** [More Information Needed]
25
- - **License:** [More Information Needed]
26
- - **Finetuned from model [optional]:** [More Information Needed]
27
 
28
- ### Model Sources [optional]
 
 
29
 
30
- <!-- Provide the basic links for the model. -->
31
 
32
- - **Repository:** [More Information Needed]
33
- - **Paper [optional]:** [More Information Needed]
34
- - **Demo [optional]:** [More Information Needed]
35
 
36
- ## Uses
 
 
 
37
 
38
- <!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
 
39
 
40
- ### Direct Use
 
 
 
41
 
42
- <!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
 
43
 
44
- [More Information Needed]
45
 
46
- ### Downstream Use [optional]
 
 
 
 
 
 
 
 
 
47
 
48
- <!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
 
49
 
50
- [More Information Needed]
51
 
52
- ### Out-of-Scope Use
 
 
 
 
53
 
54
- <!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
 
 
55
 
56
- [More Information Needed]
57
 
58
- ## Bias, Risks, and Limitations
 
 
59
 
60
- <!-- This section is meant to convey both technical and sociotechnical limitations. -->
 
61
 
62
- [More Information Needed]
63
 
64
- ### Recommendations
 
 
 
 
 
 
 
 
65
 
66
- <!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
67
 
68
- Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
69
 
70
- ## How to Get Started with the Model
 
 
71
 
72
- Use the code below to get started with the model.
 
 
73
 
74
- [More Information Needed]
 
 
 
75
 
76
- ## Training Details
77
-
78
- ### Training Data
79
-
80
- <!-- This should link to a Dataset Card, perhaps with a short stub of information on what the training data is all about as well as documentation related to data pre-processing or additional filtering. -->
81
-
82
- [More Information Needed]
83
-
84
- ### Training Procedure
85
-
86
- <!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
87
-
88
- #### Preprocessing [optional]
89
-
90
- [More Information Needed]
91
-
92
-
93
- #### Training Hyperparameters
94
-
95
- - **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
96
-
97
- #### Speeds, Sizes, Times [optional]
98
-
99
- <!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
100
-
101
- [More Information Needed]
102
-
103
- ## Evaluation
104
-
105
- <!-- This section describes the evaluation protocols and provides the results. -->
106
-
107
- ### Testing Data, Factors & Metrics
108
-
109
- #### Testing Data
110
-
111
- <!-- This should link to a Dataset Card if possible. -->
112
-
113
- [More Information Needed]
114
-
115
- #### Factors
116
-
117
- <!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
118
-
119
- [More Information Needed]
120
-
121
- #### Metrics
122
-
123
- <!-- These are the evaluation metrics being used, ideally with a description of why. -->
124
-
125
- [More Information Needed]
126
-
127
- ### Results
128
-
129
- [More Information Needed]
130
-
131
- #### Summary
132
-
133
-
134
-
135
- ## Model Examination [optional]
136
-
137
- <!-- Relevant interpretability work for the model goes here -->
138
-
139
- [More Information Needed]
140
-
141
- ## Environmental Impact
142
-
143
- <!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
144
-
145
- Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
146
-
147
- - **Hardware Type:** [More Information Needed]
148
- - **Hours used:** [More Information Needed]
149
- - **Cloud Provider:** [More Information Needed]
150
- - **Compute Region:** [More Information Needed]
151
- - **Carbon Emitted:** [More Information Needed]
152
-
153
- ## Technical Specifications [optional]
154
-
155
- ### Model Architecture and Objective
156
-
157
- [More Information Needed]
158
-
159
- ### Compute Infrastructure
160
-
161
- [More Information Needed]
162
-
163
- #### Hardware
164
-
165
- [More Information Needed]
166
-
167
- #### Software
168
-
169
- [More Information Needed]
170
-
171
- ## Citation [optional]
172
-
173
- <!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
174
-
175
- **BibTeX:**
176
-
177
- [More Information Needed]
178
-
179
- **APA:**
180
-
181
- [More Information Needed]
182
-
183
- ## Glossary [optional]
184
-
185
- <!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
186
-
187
- [More Information Needed]
188
-
189
- ## More Information [optional]
190
-
191
- [More Information Needed]
192
-
193
- ## Model Card Authors [optional]
194
-
195
- [More Information Needed]
196
-
197
- ## Model Card Contact
198
-
199
- [More Information Needed]
 
1
  ---
2
+ base_model: meta-llama/Llama-3.2-3B
3
+ library_name: peft
4
+ tags: [lora, qlora, code-generation, python]
5
+ datasets: [sahil2801/CodeAlpaca-20k]
6
+ license: llama3.2
7
  ---
8
 
9
+ # Python code generation LLaMA 3.2 3B + QLoRA
10
 
11
+ **HumanEval pass@1: 40.5% 54.1%** on the uncontaminated subset — a 13.6-point gain
12
+ from a 9.2M-parameter adapter (0.285% of the model), trained in under two hours on a
13
+ single free-tier T4.
14
 
15
+ The base model already writes correct code. It just writes it in JavaScript 42% of the
16
+ time, wrapped in markdown fences. This adapter makes Python the default and the output
17
+ directly executable.
18
 
19
+ ## Results
20
 
21
+ **HumanEval, first 50 problems** (greedy decoding, deterministic):
22
 
23
+ | | Base | Fine-tuned | Δ |
24
+ |---|---|---|---|
25
+ | **Clean subset (37 problems)** | **40.5%** | **54.1%** | **+13.6 pts** |
26
+ | All 50 | 46.0% | 58.0% | +12.0 pts |
27
 
28
+ The clean subset excludes 13 problems whose function names appear in the training data
29
+ (see Contamination). It is the number to cite.
30
 
31
+ **Custom eval set** 40 hand-written Python problems with executable unit tests, all 40
32
+ reference solutions verified to pass before use:
33
 
34
+ | | Base | Fine-tuned |
35
+ |---|---|---|
36
+ | Valid Python (free-form instruction) | 57.5% | **100%** |
37
+ | Language correct | 62.5% | **100%** |
38
+ | pass@1 | 82.5% | **90%** |
 
 
39
 
40
+ Without a specified function signature, the base model emitted non-Python for 15 of 40
41
+ problems and markdown-fenced (non-executable) output for 2 more. The adapter reaches
42
+ 100% executable Python with no prompt engineering.
43
 
44
+ ## Usage
45
 
46
+ The prompt format is load-bearing.
 
 
47
 
48
+ ```python
49
+ from transformers import AutoModelForCausalLM, AutoTokenizer, BitsAndBytesConfig
50
+ from peft import PeftModel
51
+ import torch
52
 
53
+ bnb = BitsAndBytesConfig(load_in_4bit=True, bnb_4bit_quant_type="nf4",
54
+ bnb_4bit_compute_dtype=torch.float16, bnb_4bit_use_double_quant=True)
55
 
56
+ base = AutoModelForCausalLM.from_pretrained(
57
+ "meta-llama/Llama-3.2-3B", quantization_config=bnb, device_map="auto")
58
+ model = PeftModel.from_pretrained(base, "Raghul09/llama-code-gen-lora")
59
+ tok = AutoTokenizer.from_pretrained("Raghul09/llama-code-gen-lora")
60
 
61
+ prompt = f"### Instruction:\n{instruction}\n\n### Response:\n"
62
+ ```
63
 
64
+ ## Training
65
 
66
+ | | |
67
+ |---|---|
68
+ | Base | meta-llama/Llama-3.2-3B |
69
+ | Quantization | 4-bit NF4 + double quant — 6.43 GB → 2.20 GB (66%) |
70
+ | LoRA | r=16, α=32, q/k/v/o across 28 layers |
71
+ | Trainable | 9,175,040 / 3,221,924,864 (0.285%) |
72
+ | Data | CodeAlpaca-20K, AST-filtered to Python — 6,418 / 802 / 803 |
73
+ | max_length | 256, set from measured distribution (p50=89, p95=211) |
74
+ | Hardware | single T4, 1.88 h, **4.17 GB peak VRAM** |
75
+ | Checkpoint | epoch 2 of 3 — val loss 0.475; epoch 3 rose to 0.485 |
76
 
77
+ Full fine-tuning of this model requires roughly 50 GB. QLoRA brought it to 4.17 GB,
78
+ a 12x reduction, which is what made it feasible on free-tier hardware.
79
 
80
+ ## Rank sweep
81
 
82
+ | Rank | Trainable | Val loss | Valid Python | pass@1 |
83
+ |---|---|---|---|---|
84
+ | 8 | 4,587,520 | 0.4795 | 100% | 82.5% |
85
+ | **16** | **9,175,040** | **0.4753** | **100%** | **90.0%** |
86
+ | 32 | 18,350,080 | 0.4739 | 100% | 82.5% |
87
 
88
+ Quadrupling rank bought 1.2% lower validation loss and no consistent gain in pass@1.
89
+ The target behaviour is genuinely low-rank — consistent with the LoRA paper's central
90
+ hypothesis, tested here rather than assumed.
91
 
92
+ ## Contamination
93
 
94
+ 13 of the 50 HumanEval problems have their function names defined in CodeAlpaca. The
95
+ fine-tuned model scores 69.2% on those versus ~52% on clean problems, under both prompt
96
+ formats tested. Headline numbers use the clean subset only.
97
 
98
+ Function-name matching catches exact reuse but misses paraphrased problems, so 26% is a
99
+ lower bound on overlap, not an estimate.
100
 
101
+ ## Limitations
102
 
103
+ - **Synthetic training data.** CodeAlpaca-20K is GPT-generated via self-instruct,
104
+ unverified, stylistically homogeneous. Quality is bounded by the teacher model.
105
+ - **Conformance over capability.** With a function signature specified in the prompt,
106
+ the base model already reaches 97.5% valid Python and 82.5% pass@1. This adapter's
107
+ main contribution is removing the need for that prompt engineering.
108
+ - **Python only.** Training data was AST-filtered to Python.
109
+ - **Short outputs.** Median training example was 89 tokens; long generations degrade.
110
+ - **Known failure modes:** repetition loops causing mid-generation truncation; calling
111
+ helper functions it never defines.
112
 
113
+ ## Methodology notes
114
 
115
+ Three measurement errors found and corrected during evaluation:
116
 
117
+ 1. **Naming confound.** Initial pass@1 read 35% base / 50% fine-tuned. 17 of 20 failures
118
+ were `NameError` — correct code under a different function name than the test called.
119
+ Specifying signatures corrected the baseline by 47 points, to 82.5%.
120
 
121
+ 2. **Indentation destruction.** Raw-format HumanEval returned 0% for both models. The
122
+ fence-stripper called `.strip()`, removing leading indentation from function bodies.
123
+ All 50 failures were `IndentationError`.
124
 
125
+ 3. **Training-data contamination.** A keyword-based Python filter kept 58.7% of
126
+ CodeAlpaca; AST-parsing a 300-example sample showed 38% weren't valid Python — mostly
127
+ Java and JavaScript matching on shared keywords like `for` and `class`. Replaced with
128
+ `ast.parse` plus a syntax-tree check: 0% contamination on re-check.
129
 
130
+ Sequence packing was disabled after batch inspection revealed it silently disabled
131
+ completion-only loss masking. Packing requires Flash Attention for block-diagonal
132
+ masking, which requires Ampere; the T4 is Turing.