Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Avoid storing the same move duplicated in both killer moves #458

Merged
merged 1 commit into from Oct 24, 2023

Conversation

eduherminio
Copy link
Member

@eduherminio eduherminio commented Oct 24, 2023

Score of Lynx 1787 killer vs Lynx 1786 - main: 1496 - 1420 - 1584  [0.508] 4500
...      Lynx 1787 killer playing White: 990 - 468 - 792  [0.616] 2250
...      Lynx 1787 killer playing Black: 506 - 952 - 792  [0.401] 2250
...      White vs Black: 1942 - 974 - 1584  [0.608] 4500
Elo difference: 5.9 +/- 8.2, LOS: 92.0 %, DrawRatio: 35.2 %
SPRT: llr 0.969 (33.5%), lbound -2.25, ubound 2.89

@eduherminio eduherminio marked this pull request as ready for review October 24, 2023 12:52
@eduherminio eduherminio merged commit 09a9a89 into main Oct 24, 2023
21 checks passed
@eduherminio eduherminio deleted the bugfix/killer-moves-store-same-move-twice branch October 24, 2023 12:52
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.

None yet

1 participant