terryyz commited on
Commit
3410eb4
1 Parent(s): acbcd27

Update app.py

Browse files
Files changed (1) hide show
  1. app.py +1 -37
app.py CHANGED
@@ -15,43 +15,7 @@ from share_btn import community_icon_html, loading_icon_html, share_js, share_bt
15
 
16
  FORMATS = """## Model Formats
17
 
18
- The model is pretrained on code and is formatted with special tokens in addition to the pure code data,\
19
- such as prefixes specifying the source of the file or tokens separating code from a commit message.\
20
- Use these templates to explore the model's capacities:
21
-
22
- ### 1. Prefixes 🏷️
23
- For pure code files, use any combination of the following prefixes:
24
-
25
- ```
26
- <reponame>REPONAME<filename>FILENAME<gh_stars>STARS\ncode<|endoftext|>
27
- ```
28
- STARS can be one of: 0, 1-10, 10-100, 100-1000, 1000+
29
-
30
- ### 2. Commits 💾
31
- The commits data is formatted as follows:
32
-
33
- ```
34
- <commit_before>code<commit_msg>text<commit_after>code<|endoftext|>
35
- ```
36
-
37
- ### 3. Jupyter Notebooks 📓
38
- The model is trained on Jupyter notebooks as Python scripts and structured formats like:
39
-
40
- ```
41
- <start_jupyter><jupyter_text>text<jupyter_code>code<jupyter_output>output<jupyter_text>
42
- ```
43
-
44
- ### 4. Issues 🐛
45
- We also trained on GitHub issues using the following formatting:
46
- ```
47
- <issue_start><issue_comment>text<issue_comment>...<issue_closed>
48
- ```
49
-
50
- ### 5. Fill-in-the-middle 🧩
51
- Fill in the middle requires rearranging the model inputs. The playground handles this for you - all you need is to specify where to fill:
52
- ```
53
- code before<FILL_HERE>code after
54
- ```
55
  """
56
 
57
  if not torch.cuda.is_available():
 
15
 
16
  FORMATS = """## Model Formats
17
 
18
+ The model is pretrained on code and specifically learns to use APIs from the unknonw libraries.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
19
  """
20
 
21
  if not torch.cuda.is_available():