- changed status to resolved
Wrong nps in the first and second depth and the depth starts with zero
Issue #1
resolved
Hi, first time i test your engine, I was testing with various positions, and it shows wrong nps in the first and second depth and the depth starts with zero, here a uci ouput from Arena 3
6rk/7p/Q2R1p2/1p2n3/4b3/1P4NP/P1P2PPK/2q5 b - - 0 1
#!
2015-08-31 19:58:49,728<--1:info depth 0 seldepth 0 score cp 35 nodes 25 time 0 nps 25000000000 pv
2015-08-31 19:58:49,730<--1:info depth 1 seldepth 2 score cp 34 nodes 247 time 0 nps 247000000000 pv c1c2 a6b5
2015-08-31 19:58:49,732<--1:info depth 2 seldepth 2 score cp 34 nodes 741 time 2 nps 370481 pv c1c2 a6b5
2015-08-31 19:58:49,734<--1:info depth 3 seldepth 4 score cp 40 nodes 4143 time 6 nps 690465 pv c1c2 a6b5 e4c6
2015-08-31 19:58:49,736<--1:info depth 4 seldepth 4 score cp 42 nodes 8722 time 8 nps 1090181 pv c1c2 d6f6 e5d7 g3e4 c2e4
2015-08-31 19:58:49,742<--1:info depth 5 seldepth 5 score cp 57 nodes 18563 time 14 nps 1325852 pv c1c2 d6f6 e4c6 a6a7 e5d7
2015-08-31 19:58:49,759<--1:info depth 6 seldepth 6 score cp 48 nodes 49441 time 31 nps 1594778 pv c1c2 d6f6 e4c6 a6a7 g8d8 h2g1
2015-08-31 19:58:49,793<--1:info depth 7 seldepth 8 score cp 51 nodes 110462 time 65 nps 1699318 pv c1c2 d6f6 e4c6 a6a7 e5d7 f6d6 g8a8
2015-08-31 19:58:49,943<--1:info depth 8 seldepth 10 score cp 37 nodes 385330 time 215 nps 1792130 pv c1c2 d6f6 e4c6 a6a7 c2c3 a7e7 e5g6 e7d6
2015-08-31 19:58:51,516<--1:info depth 9 seldepth 14 score mate 7 nodes 3535086 time 1788 nps 1977004 pv c1f1 g3f1 g8g2 h2h1 g2f2 h1g1 f2g2 g1h1 g2g8 h1h2 e5f3 h2h1 g8g1
2015-08-31 19:59:23,825-->1:stop
2015-08-31 19:59:23,841<--1:bestmove c1f1 ponder g3f1
Comments (3)
-
-
Thanks for reporting this issue. It's most likely cause by low resolution of the clock on your platform (Windows?).
-
reporter Excelent!! and yes, I use Windows
- Log in to comment
engine: Assume at least 1 microsecond has past.
On systems with very low clock precision nps can give weird values.
Fixes
#1.→ <<cset 93b3af7047e6>>