Transformers
tokenizer
gpt-2
Adiii143 commited on
Commit
c210965
·
verified ·
1 Parent(s): 52bcbae

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +37 -154
README.md CHANGED
@@ -1,199 +1,82 @@
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
  library_name: transformers
3
+ tags:
4
+ - tokenizer
5
+ - gpt-2
6
+ license: apache-2.0
7
+ datasets:
8
+ - code-search-net/code_search_net
9
+ base_model:
10
+ - openai-community/gpt2
11
  ---
12
 
13
+ # Model Card for Code-Net Tokenizer Trained on GPT-2
 
 
 
14
 
15
+ This model card describes a custom tokenizer trained on the existing GPT-2 tokenizer using the CodeSearchNet dataset. The tokenizer was adapted to better handle code-specific tokenization, leveraging the large scale and fine-grained vocabulary of the GPT-2 model.
16
 
17
  ## Model Details
18
 
19
  ### Model Description
20
 
21
+ This tokenizer was fine-tuned on the CodeSearchNet dataset, which contains millions of code snippets in multiple programming languages. The tokenizer was initialized with the GPT-2 tokenizer and then adapted to better handle the unique characteristics of programming language syntax and semantics.
 
 
22
 
23
+ - **Developed by:** [Your Name or Organization]
24
  - **Funded by [optional]:** [More Information Needed]
25
  - **Shared by [optional]:** [More Information Needed]
26
+ - **Model type:** Tokenizer
27
+ - **Language(s) (NLP):** Python, Java, JavaScript, Go, Ruby, etc.
28
+ - **License:** Apache 2.0
29
+ - **Finetuned from model [optional]:** openai-community/gpt2
30
 
31
  ### Model Sources [optional]
32
 
 
 
33
  - **Repository:** [More Information Needed]
34
  - **Paper [optional]:** [More Information Needed]
35
  - **Demo [optional]:** [More Information Needed]
36
 
37
  ## Uses
38
 
 
 
39
  ### Direct Use
40
 
41
+ The tokenizer can be used directly in any NLP tasks that involve source code, such as code generation, code summarization, or bug detection, by replacing the original GPT-2 tokenizer with this newly trained version.
 
 
42
 
43
  ### Downstream Use [optional]
44
 
45
+ When plugged into a code-generation or code-understanding pipeline, this tokenizer can help improve the model’s understanding of programming languages and code structure.
 
 
46
 
47
  ### Out-of-Scope Use
48
 
49
+ This tokenizer is specifically designed for tokenizing programming code. It is not suited for general text-based NLP tasks like natural language processing, sentiment analysis, or text generation outside the context of source code.
 
 
50
 
51
  ## Bias, Risks, and Limitations
52
 
53
+ This model may introduce bias based on the dataset it was trained on. For example, the tokenizer might have difficulty with edge cases or rare programming language constructs that were underrepresented in the training data.
 
 
54
 
55
  ### Recommendations
56
 
57
+ Users should be aware of potential limitations when applying this tokenizer to specific, less-common programming languages. Additionally, it may not handle malformed code or highly unconventional syntaxes well.
 
 
58
 
59
  ## How to Get Started with the Model
60
 
61
+ You can use the tokenizer by loading it via the Hugging Face `transformers` library:
 
 
62
 
63
+ ```python
64
+ from transformers import GPT2Tokenizer
65
 
66
+ # Load the custom tokenizer
67
+ tokenizer = GPT2Tokenizer.from_pretrained("your-model-name")
68
 
69
+ # Tokenize a code snippet
70
+ code_snippet = "def hello_world(): print('Hello, world!')"
71
+ tokens = tokenizer.encode(code_snippet)
72
+ print(tokens)
73
+ ```
74
+ ### Training Details
75
+ Training Data
76
+ The tokenizer was trained using the CodeSearchNet dataset, which contains millions of code snippets from various programming languages. This dataset is diverse in terms of programming languages and code style, helping to create a more versatile tokenizer.
77
 
78
+ Dataset: CodeSearchNet Dataset
79
+ Languages Covered: Python
80
 
81
  ### Training Procedure
82
+ The tokenizer was trained using the original GPT-2 tokenizer as a base and fine-tuned on the CodeSearchNet dataset. This involved segmenting code into subword units to ensure that tokenization respects common syntax and identifiers in code.