DedeProGames commited on
Commit
493177f
·
verified ·
1 Parent(s): f9346af

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +65 -28
README.md CHANGED
@@ -27,6 +27,9 @@ share an **identical tokenizer, dataset, token budget (200M) and schedule
27
  shape**, so validation loss, bits-per-character and benchmark results are
28
  directly comparable across the series.
29
 
 
 
 
30
  ## Architecture
31
 
32
  | | 300k | 1M | 5M |
@@ -81,9 +84,10 @@ with automatic re-expansion, residual projections initialized at
81
  | hardware | Tesla T4 |
82
  | wall clock | 27 min |
83
 
84
- At 41 tokens per parameter this run is the closest of
85
- the three to the Chinchilla-optimal ratio of roughly 20, though still well above
86
- it. Train and validation loss tracked each other throughout — no overfitting.
 
87
 
88
  ## Results
89
 
@@ -97,43 +101,75 @@ Perplexity is not comparable across tokenizers, but it is comparable across
97
  these three models because they share one. Bits per character
98
  (loss / ln 2 / 2.35 chars-per-token) is the portable figure.
99
 
100
- Deltas: -0.4080 nats from LowOnMind-1M
101
- (5.0x the parameters),
102
- -0.7154 nats from LowOnMind-300k
103
- (16.6x).
104
 
105
  ### Real-word rate
106
 
107
  With a 1024-token byte-level vocabulary, no long word exists as a single token —
108
  the model has to assemble every one of them from fragments. The fraction of
109
- emitted words that are real English words measures this directly.
110
 
111
  | | rate |
112
  |---|---:|
113
  | LowOnMind-1M | 98.0% |
114
- | LowOnMind-5M | **96.3%** |
115
  | FineWeb-Edu itself (same lexicon) | 98.4% |
116
 
117
- Measured over 64 unconditional samples
118
- (5,398 words), using the same reference lexicon as
119
- LowOnMind-1M (words appearing at least 5 times in a 20k-document sample of the
120
- training corpus), so the rows are directly comparable.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
121
 
122
- LowOnMind-1M already reached 98.0% against a
123
- 98.4% ceiling, so this metric had
124
- almost no headroom left before this model was trained. It is reported for
125
- continuity, not as a place where 5x the parameters could have shown much.
126
 
127
- Most frequent non-words: `shima`, `meikimo`, `amiravicis`, `illuminator`, `hymenola`, `phillipsburg`, `perleti`, `almanine`
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
128
 
129
- ## BananaMind Base Bench 1.1
 
 
 
 
 
 
 
130
 
131
- Not yet evaluated. The two smaller models score
132
- [Elo 833 / 26.6% accuracy](https://huggingface.co/DedeProGames/LowOnMind-300k)
133
- and [Elo 843 / 28.9%](https://huggingface.co/DedeProGames/LowOnMind-1M) against
134
- a chance floor of Elo 805 and 25.0% accuracy. Neither clears significance
135
- against chance overall; only the `language_completion` category does, in both.
136
- Results for this model will be added once the benchmark has been run.
137
 
138
  ## Usage
139
 
@@ -156,8 +192,9 @@ KV cache and recomputes the full window at each generation step.
156
  At ~5M parameters this is still a research artifact, not a usable model. Expect
157
  fluent local syntax and register-appropriate structure, but **no reliable
158
  coherence across a paragraph**, no dependable factual knowledge, and no ability
159
- to track state across a passage. The 1024-token vocabulary caps absolute quality
160
- below what this parameter count could otherwise reach.
 
161
 
162
  The 512-token context and absent KV cache also make it unsuitable for any real
163
- workload.
 
27
  shape**, so validation loss, bits-per-character and benchmark results are
28
  directly comparable across the series.
29
 
30
+ It is also the first model in the family whose benchmark performance is
31
+ statistically distinguishable from chance.
32
+
33
  ## Architecture
34
 
35
  | | 300k | 1M | 5M |
 
84
  | hardware | Tesla T4 |
85
  | wall clock | 27 min |
86
 
87
+ At 41 tokens per parameter this run is the closest of the three to the
88
+ Chinchilla-optimal ratio of roughly 20 about 2x above it, against 10x for
89
+ LowOnMind-1M and 34x for LowOnMind-300k. Train and validation loss tracked
90
+ each other throughout; no overfitting.
91
 
92
  ## Results
93
 
 
101
  these three models because they share one. Bits per character
102
  (loss / ln 2 / 2.35 chars-per-token) is the portable figure.
103
 
104
+ Deltas: -0.4080 nats from LowOnMind-1M (5.0x the parameters),
105
+ -0.7154 nats from LowOnMind-300k (16.6x).
 
 
106
 
107
  ### Real-word rate
108
 
109
  With a 1024-token byte-level vocabulary, no long word exists as a single token —
110
  the model has to assemble every one of them from fragments. The fraction of
111
+ emitted words that are real English words was introduced to measure this.
112
 
113
  | | rate |
114
  |---|---:|
115
  | LowOnMind-1M | 98.0% |
116
+ | LowOnMind-5M | 96.3% |
117
  | FineWeb-Edu itself (same lexicon) | 98.4% |
118
 
119
+ Measured over 64 unconditional samples (5,398 words), using the same reference
120
+ lexicon as LowOnMind-1M: words appearing at least 5 times in a 20k-document
121
+ sample of the training corpus.
122
+
123
+ **This number went down, and it should not be read as degraded spelling.** The
124
+ drop is statistically real (z = 5.38, not sampling noise), but inspecting the
125
+ non-words shows what happened: `illuminator` is an ordinary English word,
126
+ `phillipsburg` is a US town, `shima` is a common element of Japanese place
127
+ names. They are counted as errors only because they fall below the reference
128
+ lexicon's frequency-5 threshold. The remainder (`hymenola`, `almanine`,
129
+ `perleti`, `amiravicis`) skew toward proper-noun and Latinate-technical
130
+ morphology rather than the malformed common words the metric was built to catch
131
+ — LowOnMind-300k produced things like `landship` and `parsetic`, failures of a
132
+ different kind.
133
+
134
+ **The metric has a floor problem as well as a ceiling problem.** As a model
135
+ improves it emits rarer real vocabulary — names, places, technical terms — which
136
+ a frequency-thresholded lexicon scores as wrong. So the measured rate can fall
137
+ while actual quality rises. Comparing against a full dictionary with proper-noun
138
+ handling, rather than a corpus-frequency cutoff, would be the fix. The 96.3%
139
+ figure is reported as-measured for continuity, but it should not be used to rank
140
+ these models.
141
 
142
+ ## BananaMind Base Bench 1.1
 
 
 
143
 
144
+ Evaluated on [BananaMind/BananaMind-Base-Bench-1.1](https://huggingface.co/datasets/BananaMind/BananaMind-Base-Bench-1.1),
145
+ the same 350-item English continuation-likelihood benchmark used across the
146
+ family, with identical scoring: context and each of the four continuations
147
+ tokenized separately with `add_special_tokens=False`, no BOS, selection by
148
+ highest mean conditional token log-probability.
149
+
150
+ Run validity: dataset SHA-256 matched, full schema validation passed, no context
151
+ required truncation against the 512-token window.
152
+
153
+ | Category | 300k | 1M | 5M | z vs chance (5M) | Elo (5M) |
154
+ |---|---:|---:|---:|---:|---:|
155
+ | language_completion | 46.0% | 52.0% | **62.0%** | **+6.04** | **1008** |
156
+ | world_knowledge | 22.0% | 22.0% | **38.0%** | +2.12 | 881 |
157
+ | context_tracking | 14.0% | 24.0% | 32.0% | +1.14 | 851 |
158
+ | quantitative | 32.0% | 28.0% | 28.0% | +0.49 | 872 |
159
+ | logical_reasoning | 24.0% | 28.0% | 26.0% | +0.16 | 900 |
160
+ | commonsense | 34.0% | 28.0% | 24.0% | -0.16 | 758 |
161
+ | code_completion | 14.0% | 20.0% | 16.0% | -1.47 | 805 |
162
 
163
+ | | 300k | 1M | 5M |
164
+ |---|---:|---:|---:|
165
+ | Overall Elo | 833 | 843 | **863** |
166
+ | Chance-level Elo (this grid) | 805 | 805 | 805 |
167
+ | Raw accuracy | 26.6% | 28.9% | **32.3%** |
168
+ | 95% CI | [22.0, 31.2] | [24.2, 33.6] | **[27.4, 37.2]** |
169
+ | z vs. chance | +0.69 | +1.68 | **+3.15** |
170
+ | significant vs. chance | no | no | **yes** |
171
 
172
+ Difficulty split: easy 30.8%, medium 33.3%, hard 32.8%.
 
 
 
 
 
173
 
174
  ## Usage
175
 
 
192
  At ~5M parameters this is still a research artifact, not a usable model. Expect
193
  fluent local syntax and register-appropriate structure, but **no reliable
194
  coherence across a paragraph**, no dependable factual knowledge, and no ability
195
+ to track state across a passage. Benchmark accuracy of 32.3% is above chance and
196
+ far below usefulness. The 1024-token vocabulary caps absolute quality below what
197
+ this parameter count could otherwise reach.
198
 
199
  The 512-token context and absent KV cache also make it unsuitable for any real
200
+ workload.