Skip to content

Add Texel tuning for outcome-labeled HCE positions - #5

Merged
KnightStackSys merged 1 commit into
mainfrom
feature/texel-hce-tuning-20261113
Nov 13, 2026
Merged

KnightStackSys merged 1 commit into
mainfrom
feature/texel-hce-tuning-20261113

Conversation

@KnightStackSys

Copy link
Copy Markdown
Owner

Summary

  • Add tunex ... texel for fitting integer HCE Eval* options against a JSONL dataset of labeled native FEN4 positions.
  • Use the engine's static evaluation, not search scores; convert side-to-move values into Red+Yellow team perspective before minimizing Texel logistic mean squared error.
  • Implement bounded integer coordinate descent, game-grouped train/validation separation, and select the best held-out weights.
  • Add atomic checkpoints with dataset/config hashes, resume safety, dataset/result validation, example configuration and Lucide-icon documentation.
  • Add regression tests covering labels, perspective, validation, mock-engine fitting, and resumption.

Dependency

Requires the companion IronPhoenix PR adding eval -> info string eval cp N. Use UseNNUE=false so HCE weights affect results. SpellWarden's evaluator has no runtime Eval* options, so this fit is intentionally IronPhoenix-only for now.

Validation

GitHub CI pending; no real dataset fit or Elo improvement is claimed. Confirm the chosen weights with independent paired SPRT.

Fit integer Eval* weights by minimizing a logistic static-evaluation loss against completed-game outcomes, with game-grouped train/validation holdout, checkpointing, resume safeguards, perspective correction, dataset validation, UCI static-eval support, and tests. Document IronPhoenix companion eval command requirement.
@KnightStackSys
KnightStackSys merged commit d38aac4 into main Nov 13, 2026
4 checks passed
@KnightStackSys
KnightStackSys deleted the feature/texel-hce-tuning-20261113 branch November 13, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant