Hugging Face's logo

jolovicdev
/
Lacuna-V1

Text Generation
Transformers
Safetensors
llama
code
code-completion
code-editing
fill-in-the-middle
autocomplete
lacuna
text-generation-inference
Model card Files
xet
 Community
jolovicdev commited on
Commit
6f188c2
·
verified ·
1 Parent(s): 8e79234

Polish Lacuna V1 model card

Browse files
Files changed (1) hide show
  1. README.md +28 -14
README.md CHANGED
@@ -13,21 +13,33 @@ tags:
13
 
14
  # Lacuna V1
15
 
16
- Lacuna V1 is an experimental code edit completion model.
 
17
 
18
- It predicts replacement code for numbered edit regions inside a Seed-Coder FIM
19
- prompt. It is a completion model, not a chat model.
20
 
21
- ## Marker Format
 
 
 
 
 
 
 
 
 
22
 
23
  Markers define the regions to replace.
24
 
25
- - Region 1: `<|marker_1|>` opens, `<|marker_2|>` closes
26
- - Region 2: `<|marker_3|>` opens, `<|marker_4|>` closes
27
- - Additional regions continue with the same numbered pattern
 
 
28
 
29
- The prompt should contain the surrounding code context and marker placeholders.
30
- The completion starts at the first marker and returns the replacement span with
31
  markers included.
32
 
33
  ## Typical Input
@@ -56,6 +68,8 @@ total += item.value;
56
  <|marker_2|>
57
  ```
58
 
 
 
59
  For multiple edited regions, the output keeps the same marker order:
60
 
61
  ```text
@@ -68,11 +82,11 @@ second replacement
68
 
69
  ## Completion Settings
70
 
71
- ```text
72
- temperature: 0
73
- top_p: 1
74
- max_tokens: 256
75
- ```
76
 
77
  Use a larger `max_tokens` value for longer or multi-region edits.
78
 
 
13
 
14
  # Lacuna V1
15
 
16
+ > Experimental code edit completion model for numbered marker spans inside
17
+ > Seed-Coder FIM prompts.
18
 
19
+ Lacuna V1 predicts replacement code for marked edit regions. It is a completion
20
+ model, not a chat model.
21
 
22
+ ## At A Glance
23
+
24
+ | Field | Value |
25
+ | --- | --- |
26
+ | Type | Completion model |
27
+ | Task | Code edit completion |
28
+ | Prompt style | Seed-Coder FIM + numbered markers |
29
+ | License | Apache-2.0 |
30
+
31
+ ## Marker Contract
32
 
33
  Markers define the regions to replace.
34
 
35
+ | Region | Open marker | Close marker |
36
+ | ---: | --- | --- |
37
+ | 1 | <code>&lt;&#124;marker_1&#124;&gt;</code> | <code>&lt;&#124;marker_2&#124;&gt;</code> |
38
+ | 2 | <code>&lt;&#124;marker_3&#124;&gt;</code> | <code>&lt;&#124;marker_4&#124;&gt;</code> |
39
+ | N | <code>&lt;&#124;marker_2N-1&#124;&gt;</code> | <code>&lt;&#124;marker_2N&#124;&gt;</code> |
40
 
41
+ The prompt contains the surrounding code context and marker placeholders. The
42
+ completion starts at the first marker and returns the replacement span with
43
  markers included.
44
 
45
  ## Typical Input
 
68
  <|marker_2|>
69
  ```
70
 
71
+ ### Multiple Regions
72
+
73
  For multiple edited regions, the output keeps the same marker order:
74
 
75
  ```text
 
82
 
83
  ## Completion Settings
84
 
85
+ | Setting | Value |
86
+ | --- | --- |
87
+ | `temperature` | `0` |
88
+ | `top_p` | `1` |
89
+ | `max_tokens` | `256` |
90
 
91
  Use a larger `max_tokens` value for longer or multi-region edits.
92