And still no information about Tucanos extremely low nps...Milos wrote: ↑Sat Aug 04, 2018 6:23 pmTechnically it is Kranium's fault. He provided the binary. And I am more and more convinced that all this is intentional on Anton's side. Sorry, but too many circumstantial evidence. They simply don't care to have properly working Ivanhoe. And the reason is because they want both NN "engines" to be in division 3. It is pretty obvious that with fully functioning Ivanhoe, there is close to 0% chance for both NN's to go through. It's a scam, period.
(in this case it could be a display error though, as the depths look high)
From current game, Tucano 7.05 is Black:
Code: Select all
Depth
move white black
1 NaN NaN
2 NaN NaN
3 24 26
4 26 29
5 26 29
6 25 28
7 27 28
8 25 26
9 27 27
10 27 28
11 28 26
12 28 26
13 29 27
14 25 27
15 26 25
16 24 25
17 26 25
18 26 25
19 26 27
20 24 27
21 24 25
22 25 32
23 25 30
24 26 27
25 22 29
26 24 26
27 23 28
28 24 25
29 25 29
30 28 30
31 31 30
32 30 28
33 29 29
Speed
move white black
1 NaN NaN
2 NaN NaN
3 10,018.929 1,054.255
4 10,198.404 1,234.929
5 10,364.662 1,179.049
6 10,192.882 1,318.178
7 10,451.718 1,321.748
8 10,083.177 1,306.382
9 10,520.03 303.82
10 10,585.231 529.738
11 10,810.212 281.362
12 10,935.495 1,044.053
13 11,445.326 642.428
14 11,145.498 1,029.782
15 10,992.486 1,215.486
16 11,122.792 951.436
17 11,101.299 1,246.276
18 11,037.72 1,212.287
19 11,190.085 980.622
20 11,077.496 1,177.331
21 11,064.12 323.457
22 10,930.517 1,176.836
23 11,319.215 754.579
24 11,392.174 180.042
25 11,574.41 1,150.731
26 11,409.278 437.179
27 10,893.732 491.258
28 11,212.323 554.163
29 11,804.625 1,186.502
30 11,916.579 691.296
31 12,440.173 733.955
32 12,569.352 1,246.682
33 13,155.351 796.561
Post by Joost Buijs » Sat Aug 04, 2018 6:31 am
Yesterday I was watching the game between Deus-X and Tucano and noticed that Tucano shows an incredibly low speed (around 1 mnps, sometimes even lower), so I suspect it was only using one core. Also the configured hash (1024 Mb) seems very low for a lazy-smp engine with these long thinking times. Maybe misconfiguration or is this normal behaviour for Tucano? I don't know.