Dev Builds » 20200215-1410

You are viewing an old NCM Stockfish dev build test. You may find the most recent dev build tests using Stockfish 15 as the baseline here.

Use this dev build

NCM plays each Stockfish dev build 20,000 times against Stockfish 7. This yields an approximate Elo difference and establishes confidence in the strength of the dev builds.

Summary

Host Duration Avg Base NPS Games Wins Losses Draws Elo
ncm-et-3 10:04:40 1962651 3997 2473 80 1444 +240.12 ± 8.89
ncm-et-4 10:04:25 1961863 3968 2463 67 1438 +242.91 ± 8.89
ncm-et-9 10:03:24 1968516 4001 2503 64 1434 +246.08 ± 8.91
ncm-et-10 10:03:21 1965187 4002 2512 54 1436 +248.63 ± 8.88
ncm-et-15 10:03:39 1968419 4032 2484 64 1484 +240.93 ± 8.74
20000 12435 329 7236 +243.72 ± 3.96

Test Detail

ID Host Started (UTC) Duration Base NPS Games Wins Losses Draws Elo CLI PGN
116217 ncm-et-9 2020-02-17 10:10 00:00:46 1966468 1 1 0 0 +1129.65 ± 376.02
116216 ncm-et-10 2020-02-17 10:10 00:00:56 1957250 2 1 0 1 +190.5 ± 634.21
116215 ncm-et-15 2020-02-17 10:06 00:05:14 1965537 32 24 0 8 +338.0 ± 135.38
116214 ncm-et-4 2020-02-17 08:59 01:11:07 1970042 468 290 7 171 +243.39 ± 25.83
116213 ncm-et-3 2020-02-17 08:56 01:15:11 1961690 497 299 10 188 +230.94 ± 24.66
116212 ncm-et-10 2020-02-17 08:54 01:14:45 1969550 500 319 6 175 +255.3 ± 25.54
116211 ncm-et-9 2020-02-17 08:53 01:15:41 1975603 500 316 5 179 +253.02 ± 25.18
116210 ncm-et-15 2020-02-17 08:50 01:14:33 1978722 500 304 6 190 +238.66 ± 24.39
116209 ncm-et-4 2020-02-17 07:43 01:15:41 1975447 500 325 10 165 +257.59 ± 26.5
116208 ncm-et-3 2020-02-17 07:39 01:16:01 1963839 500 323 15 162 +249.64 ± 26.84
116207 ncm-et-10 2020-02-17 07:38 01:14:55 1965072 500 328 4 168 +268.17 ± 26.05
116206 ncm-et-9 2020-02-17 07:37 01:15:00 1964767 500 301 9 190 +232.26 ± 24.49
116205 ncm-et-15 2020-02-17 07:35 01:14:16 1971286 500 325 12 163 +255.3 ± 26.71
116204 ncm-et-4 2020-02-17 06:28 01:13:31 1974675 500 305 7 188 +238.66 ± 24.57
116203 ncm-et-3 2020-02-17 06:24 01:13:16 1965078 500 306 10 184 +236.51 ± 24.97
116202 ncm-et-10 2020-02-17 06:22 01:14:56 1970323 500 299 5 196 +234.38 ± 23.91
116201 ncm-et-9 2020-02-17 06:21 01:15:05 1966320 500 333 7 160 +270.57 ± 26.87
116200 ncm-et-15 2020-02-17 06:18 01:15:18 1964917 500 314 7 179 +248.53 ± 25.26
116199 ncm-et-4 2020-02-17 05:12 01:15:03 1969398 500 321 10 169 +253.02 ± 26.16
116198 ncm-et-3 2020-02-17 05:08 01:15:18 1962458 500 307 12 181 +235.45 ± 25.24
116197 ncm-et-10 2020-02-17 05:06 01:14:45 1969085 500 315 8 177 +248.53 ± 25.45
116196 ncm-et-9 2020-02-17 05:04 01:15:33 1969714 500 311 12 177 +239.74 ± 25.55
116195 ncm-et-15 2020-02-17 05:03 01:14:15 1969562 500 312 4 184 +249.64 ± 24.75
116194 ncm-et-4 2020-02-17 03:52 01:18:34 1934486 500 295 9 196 +226.0 ± 24.06
116193 ncm-et-3 2020-02-17 03:49 01:17:52 1964609 500 301 10 189 +231.21 ± 24.59
116192 ncm-et-9 2020-02-17 03:49 01:14:49 1969568 500 300 8 192 +232.26 ± 24.31
116191 ncm-et-10 2020-02-17 03:48 01:17:17 1962310 500 298 9 193 +229.12 ± 24.27
116190 ncm-et-15 2020-02-17 03:47 01:14:51 1960461 500 292 12 196 +219.87 ± 24.15
116189 ncm-et-4 2020-02-17 02:36 01:15:42 1966464 500 299 12 189 +227.04 ± 24.65
116188 ncm-et-3 2020-02-17 02:33 01:14:50 1961845 500 316 8 176 +249.64 ± 25.53
116187 ncm-et-9 2020-02-17 02:32 01:15:21 1965087 500 313 9 178 +245.2 ± 25.4
116186 ncm-et-10 2020-02-17 02:32 01:15:02 1961689 500 326 10 164 +258.75 ± 26.59
116185 ncm-et-15 2020-02-17 02:30 01:15:57 1967714 500 301 5 194 +236.51 ± 24.06
116184 ncm-et-4 2020-02-17 01:17 01:17:28 1939624 500 304 8 188 +236.51 ± 24.61
116183 ncm-et-3 2020-02-17 01:16 01:15:40 1960312 500 309 6 185 +244.1 ± 24.76
116182 ncm-et-9 2020-02-17 01:15 01:15:43 1967392 500 308 10 182 +238.66 ± 25.12
116181 ncm-et-10 2020-02-17 01:15 01:16:10 1965251 500 309 6 185 +244.1 ± 24.76
116180 ncm-et-15 2020-02-17 01:14 01:15:18 1972816 500 287 7 206 +219.87 ± 23.31
116179 ncm-et-10 2020-02-16 23:59 01:14:35 1966155 500 317 6 177 +253.02 ± 25.38
116178 ncm-et-9 2020-02-16 23:59 01:15:26 1971727 500 320 4 176 +258.75 ± 25.38
116177 ncm-et-15 2020-02-16 23:59 01:13:57 1964763 500 325 11 164 +256.44 ± 26.61
116176 ncm-et-4 2020-02-16 23:59 01:17:19 1964772 500 324 4 172 +263.42 ± 25.71
116175 ncm-et-3 2020-02-16 23:59 01:16:32 1961381 500 312 9 179 +244.1 ± 25.32

Commit

Commit ID be5a2f015e45886e32867b4559ef51dd694a3cec
Author Joost VandeVondele
Date 2020-02-15 14:10:07 UTC
Fix for incorrect VALUE_MATE_IN_MAX_PLY usage. Fixes #2533, fixes #2543, fixes #2423. the code that prevents false mate announcements depending on the TT state (GHI), incorrectly used VALUE_MATE_IN_MAX_PLY. The latter constant, however, also includes, counterintuitively, the TB win range. This patch fixes that, by restoring the behavior for TB win scores, while retaining the false mate correctness, and improving the mate finding ability. In particular no alse mates are announced with the poisened hash testcase ``` position fen 8/8/8/3k4/8/8/6K1/7R w - - 0 1 go depth 40 position fen 8/8/8/3k4/8/8/6K1/7R w - - 76 1 go depth 20 ucinewgame ``` mates are found with the testcases reported in #2543 ``` position fen 4k3/3pp3/8/8/8/8/2PPP3/4K3 w - - 0 1 setoption name Hash value 1024 go depth 55 ucinewgame ``` and ``` position fen 4k3/4p3/8/8/8/8/3PP3/4K3 w - - 0 1 setoption name Hash value 1024 go depth 45 ucinewgame ``` furthermore, on the mate finding benchmark (ChestUCI_23102018.epd), performance improves over master, roughly reaching performance with the false mate protection reverted ``` Analyzing 6566 mate positions for best and found mates: ----------------best ---------------found nodes master revert fixed master revert fixed 16000000 4233 4236 4235 5200 5201 5199 32000000 4583 4585 4585 5417 5424 5418 64000000 4852 4853 4855 5575 5584 5579 128000000 5071 5068 5066 5710 5720 5716 256000000 5280 5282 5279 5819 5827 5826 512000000 5471 5468 5468 5919 5935 5932 ``` On a testcase with TB enabled, progress is made consistently, contrary to master ``` setoption name SyzygyPath value ../../../syzygy/3-4-5/ setoption name Hash value 2048 position fen 1R6/3k4/8/K2p4/4n3/2P5/8/8 w - - 0 1 go depth 58 ucinewgame ``` The PR (prior to a rewrite for clarity) passed STC: LLR: 2.94 (-2.94,2.94) {-1.50,0.50} Total: 65405 W: 12454 L: 12384 D: 40567 Ptnml(0-2): 920, 7256, 16285, 7286, 944 http://tests.stockfishchess.org/tests/view/5e441a3be70d848499f63d15 passed LTC: LLR: 2.94 (-2.94,2.94) {-1.50,0.50} Total: 27096 W: 3477 L: 3413 D: 20206 Ptnml(0-2): 128, 2215, 8776, 2292, 122 http://tests.stockfishchess.org/tests/view/5e44e277e70d848499f63d63 The incorrectly named VALUE_MATE_IN_MAX_PLY and VALUE_MATED_IN_MAX_PLY were renamed into VALUE_TB_WIN_IN_MAX_PLY and VALUE_TB_LOSS_IN_MAX_PLY, and correclty defined VALUE_MATE_IN_MAX_PLY and VALUE_MATED_IN_MAX_PLY were introduced. One further (corner case) mistake using these constants was fixed (go mate X), which could lead to a premature return if X > MAX_PLY / 2, but TB were present. Thanks to @svivanov72 for one of the reports and help fixing the issue. closes https://github.com/official-stockfish/Stockfish/pull/2552 Bench: 4932981
Copyright 2011–2024 Next Chess Move LLC