Upload README.md with huggingface_hub
Browse files
README.md
CHANGED
|
@@ -158,12 +158,20 @@ the ones served by the application.
|
|
| 158 |
|
| 159 |
The in-app version additionally wraps Nova's policy output with a
|
| 160 |
small calibration layer used to tune playing strength across rating
|
| 161 |
-
tiers. The
|
| 162 |
-
|
| 163 |
-
|
| 164 |
-
|
| 165 |
-
|
| 166 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 167 |
|
| 168 |
**Every move the in-app bot plays still originates from Nova's policy
|
| 169 |
distribution.** Stockfish is never used to suggest, generate, or
|
|
|
|
| 158 |
|
| 159 |
The in-app version additionally wraps Nova's policy output with a
|
| 160 |
small calibration layer used to tune playing strength across rating
|
| 161 |
+
tiers. The primary lever is a **per-tier temperature schedule**. On
|
| 162 |
+
top of that, Nova's sampled candidates pass through a probabilistic
|
| 163 |
+
quality check: high-confidence picks (where Nova's policy concentrates
|
| 164 |
+
significant probability mass on a single move) are played directly,
|
| 165 |
+
while lower-confidence picks may be sent to Stockfish for a low-depth
|
| 166 |
+
evaluation. If the evaluation falls below a tier-dependent quality
|
| 167 |
+
threshold, the move *may* be replaced by re-sampling from Nova's
|
| 168 |
+
distribution. Both the rate at which positions are evaluated and the
|
| 169 |
+
rate at which sub-threshold moves are actually replaced vary by tier,
|
| 170 |
+
so the bot's mistake profile matches the empirical chess.com CP-loss
|
| 171 |
+
profile at that level — at lower tiers, more sub-optimal moves slip
|
| 172 |
+
through (because players at that level make them); at higher tiers,
|
| 173 |
+
far fewer do. Additional calibration components layer on top of this
|
| 174 |
+
base flow.
|
| 175 |
|
| 176 |
**Every move the in-app bot plays still originates from Nova's policy
|
| 177 |
distribution.** Stockfish is never used to suggest, generate, or
|