Dev Builds » 20141103-1536

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 06:06:18 1987822 2386 179 748 1459 -84.48 ± 8.51
ncm-et-4 06:04:45 1973903 2359 148 769 1442 -93.67 ± 8.52
ncm-et-5 01:47:32 2014850 725 58 217 450 -77.45 ± 15.3
ncm-et-6 01:47:25 2025165 721 47 223 451 -86.56 ± 15.14
ncm-et-7 01:47:28 2023040 710 48 232 430 -92.14 ± 15.68
ncm-et-8 01:47:25 1997408 719 36 235 448 -98.74 ± 15.08
ncm-et-9 06:02:03 1988911 2384 183 791 1410 -90.61 ± 8.74
ncm-et-10 06:01:20 1982454 2377 187 738 1452 -82.03 ± 8.55
ncm-et-11 01:47:22 1987190 699 50 221 428 -86.75 ± 15.7
ncm-et-12 01:47:19 2001376 704 56 233 415 -89.27 ± 16.16
ncm-et-13 06:01:31 1991676 2394 160 775 1459 -91.3 ± 8.49
ncm-et-14 01:47:18 2018395 713 43 227 443 -91.73 ± 15.27
ncm-et-15 06:01:19 1986939 2397 145 704 1548 -82.54 ± 8.06
ncm-et-16 01:47:26 2018236 712 67 217 428 -74.31 ± 15.91
20000 1407 6330 12263 -87.31 ± 2.93

Test Detail

ID Host Started (UTC) Duration Base NPS Games Wins Losses Draws Elo CLI PGN
85340 ncm-et-4 2019-06-15 14:51 00:22:27 1963538 147 8 37 102 -69.45 ± 30.29
85339 ncm-et-10 2019-06-15 14:49 00:24:15 1960473 159 17 47 95 -66.35 ± 34.04
85338 ncm-et-9 2019-06-15 14:48 00:25:55 1982676 166 5 56 105 -110.3 ± 30.6
85337 ncm-et-13 2019-06-15 14:47 00:26:27 1985561 174 6 64 104 -120.41 ± 31.45
85336 ncm-et-3 2019-06-15 14:46 00:26:58 1962611 176 10 49 117 -78.29 ± 28.95
85335 ncm-et-15 2019-06-15 14:46 00:27:08 1969105 178 7 50 121 -85.62 ± 27.81
85334 ncm-et-3 2019-06-15 13:30 01:14:56 1969581 500 32 145 323 -79.9 ± 17.68
85333 ncm-et-10 2019-06-15 13:30 01:18:04 1964695 500 44 161 295 -82.83 ± 19.23
85332 ncm-et-4 2019-06-15 13:30 01:19:45 1938859 500 34 183 283 -106.78 ± 19.66
85331 ncm-et-13 2019-06-15 13:30 01:15:56 1968478 500 36 162 302 -89.48 ± 18.77
85330 ncm-et-15 2019-06-15 13:30 01:14:51 1971885 500 30 135 335 -74.06 ± 17.05
85329 ncm-et-9 2019-06-15 13:30 01:16:37 1962766 500 41 174 285 -94.7 ± 19.67
85202 ncm-et-3 2019-06-14 10:10 01:18:01 1978014 500 36 158 306 -86.52 ± 18.58
85201 ncm-et-4 2019-06-14 10:08 01:17:29 1976472 500 34 167 299 -94.7 ± 18.88
85200 ncm-et-13 2019-06-14 10:07 01:14:55 1975141 500 31 143 326 -79.17 ± 17.51
85199 ncm-et-10 2019-06-14 10:07 01:15:26 1964163 500 31 160 309 -91.71 ± 18.34
85198 ncm-et-15 2019-06-14 10:06 01:15:55 1976232 500 33 143 324 -77.71 ± 17.65
85197 ncm-et-9 2019-06-14 10:06 01:16:32 1973130 500 35 159 306 -88.0 ± 18.56
85196 ncm-et-3 2019-06-14 08:50 01:19:07 1964764 500 47 166 287 -84.31 ± 19.64
85195 ncm-et-10 2019-06-14 08:49 01:16:14 1966164 500 38 157 305 -84.31 ± 18.66
85194 ncm-et-13 2019-06-14 08:49 01:16:35 1972188 500 30 163 307 -94.7 ± 18.42
85193 ncm-et-9 2019-06-14 08:49 01:15:33 1965227 500 49 166 285 -82.83 ± 19.76
85192 ncm-et-4 2019-06-14 08:49 01:17:42 1930759 500 31 156 313 -88.74 ± 18.15
85191 ncm-et-15 2019-06-14 08:49 01:16:04 1965997 500 24 149 327 -88.74 ± 17.31
20052 ncm-et-11 2018-04-17 17:31 00:29:53 2007687 199 14 64 121 -89.21 ± 29.63
20051 ncm-et-12 2018-04-17 17:30 00:31:09 2015166 204 21 66 117 -77.92 ± 30.9
20050 ncm-et-3 2018-04-17 17:29 00:31:32 2025408 210 16 61 133 -75.62 ± 27.96
20049 ncm-et-16 2018-04-17 17:29 00:31:36 2015800 212 20 62 130 -69.75 ± 28.77
20048 ncm-et-4 2018-04-17 17:29 00:32:13 2009201 212 13 63 136 -83.51 ± 27.32
20047 ncm-et-7 2018-04-17 17:28 00:32:16 2022141 210 19 56 135 -61.86 ± 27.76
20046 ncm-et-9 2018-04-17 17:28 00:32:49 2026063 218 14 71 133 -93.0 ± 28.15
20045 ncm-et-15 2018-04-17 17:28 00:32:30 2019046 219 13 62 144 -79.07 ± 26.25
20044 ncm-et-8 2018-04-17 17:28 00:32:49 1998371 219 9 75 135 -108.06 ± 27.46
20043 ncm-et-14 2018-04-17 17:28 00:32:32 2017420 213 10 64 139 -90.05 ± 26.59
20042 ncm-et-13 2018-04-17 17:28 00:33:03 2024099 220 17 71 132 -87.06 ± 28.55
20041 ncm-et-10 2018-04-17 17:27 00:33:26 2019370 218 24 62 132 -61.19 ± 28.77
20040 ncm-et-5 2018-04-17 17:27 00:33:44 2005765 225 21 60 144 -60.84 ± 26.94
20039 ncm-et-6 2018-04-17 17:27 00:33:50 2022956 221 18 68 135 -79.99 ± 28.14
20038 ncm-et-12 2018-04-17 16:13 01:16:10 1987586 500 35 167 298 -93.95 ± 18.95
20037 ncm-et-6 2018-04-17 16:13 01:13:35 2027374 500 29 155 316 -89.48 ± 17.96
20036 ncm-et-9 2018-04-17 16:12 01:14:37 2023609 500 39 165 296 -89.48 ± 19.11
20035 ncm-et-10 2018-04-17 16:12 01:13:55 2019859 500 33 151 316 -83.57 ± 18.04
20034 ncm-et-8 2018-04-17 16:12 01:14:36 1996446 500 27 160 313 -94.7 ± 18.07
20033 ncm-et-3 2018-04-17 16:12 01:15:44 2026555 500 38 169 293 -93.2 ± 19.24
20032 ncm-et-11 2018-04-17 16:12 01:17:29 1966694 500 36 157 307 -85.78 ± 18.53
20031 ncm-et-5 2018-04-17 16:12 01:13:48 2023936 500 37 157 306 -85.04 ± 18.6
20030 ncm-et-4 2018-04-17 16:12 01:15:09 2024590 500 28 163 309 -96.19 ± 18.28
20029 ncm-et-14 2018-04-17 16:12 01:14:46 2019371 500 33 163 304 -92.46 ± 18.62
20028 ncm-et-15 2018-04-17 16:12 01:14:51 2019372 500 38 165 297 -90.22 ± 19.05
20027 ncm-et-16 2018-04-17 16:12 01:15:50 2020673 500 47 155 298 -76.25 ± 19.12
20026 ncm-et-13 2018-04-17 16:12 01:14:35 2024592 500 40 172 288 -93.95 ± 19.51
20025 ncm-et-7 2018-04-17 16:12 01:15:12 2023939 500 29 176 295 -105.25 ± 18.99

Commit

Commit ID 8ab9c2511a36a929a17a689125c919c927aee786
Author lucasart
Date 2014-11-03 15:36:24 UTC
Cleanup MAX_PLY This area has become obscure and tricky over the course of incremental changes that did not respect the original's consistency and clarity. Now, it's not clear why we use MAX_PLY = 120, or why we use MAX_PLY+6, among other things. This patch does the following: * ID loop: depth ranges from 1 to MAX_PLY-1, and due to TT constraint (depth must fit into an int8_t), MAX_PLY should be 128. * stack[]: plies now range from 0 to MAX_PLY-1, hence stack[MAX_PLY+4], because of the extra 2+2 padding elements (for ss-2 and ss+2). Document this better, while we're at it. * Enforce 0 <= ply < MAX_PLY: - stop condition is now ss->ply >= MAX_PLY and not ss->ply > MAX_PLY. - assert(ss->ply < MAX_PLY), before using ss+1 and ss+2. - as a result, we don't need the artificial MAX_PLY+6 range. Instead we can use MAX_PLY+4 and it's clear why (for ss-2 and ss+2). * fix: extract_pv_from_tt() and insert_pv_in_tt() had no reason to use MAX_PLY_PLUS_6, because the array is indexed by plies, so the range of available plies applies (0..MAX_PLY before, and now 0..MAX_PLY-1). Tested with debug compile, using MAX_PLY=16, and running bench at depth 17, using 1 and 7 threads. No assert() fired. Feel free to submit to more severe crash-tests, if you can think of any. No functional change.
Copyright 2011–2024 Next Chess Move LLC