We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I compiled Xiphos on my mac an ran some tests. At the 1500 STS positions Xiphos 0.5 reached a much lower solving rate than expected.
The log file shows, that after receiving go movetime 193 (msec) Xiphos finished all positions in 43..45 (msec)!
Is this an macOS issue?
Starting engine /Users/max/chess/Xiphos/xiphos-0.5 ... >> uci << Xiphos 0.5 BMI2 by Milos Tatarevic << threads=1 << hash=128MB << id name Xiphos 0.5 BMI2 << id author Milos Tatarevic << option name Hash type spin default 128 min 1 max 32768 << option name Threads type spin default 1 min 1 max 128 << option name Ponder type check default false << option name SyzygyPath type string default <empty> << option name SyzygyProbeDepth type spin default 1 min 1 max 100 << uciok >> setoption name Hash value 128 >> setoption name Contempt value 0 >> setoption name Threads value 1 >> setoption name Cores value 1 >> setoption name Max CPUs value 1 Pos 1 1kr5/3n4/q3p2p/p2n2p1/PppB1P2/5BP1/1P2Q2P/3R2K1 w - - bm f5; id "STS(v1.0) Undermine.001"; c0 "f5=10, Be5+=2, Bf2=3, Bg4=2"; c7 "f5 Be5+ Bf2 Bg4"; c8 "10 2 3 2"; c9 "f4f5 d4e5 d4f2 f3g4"; 2019-07-11T13:41:21.615597 >> isready 2019-07-11T13:41:21.621338 << hash=128MB 2019-07-11T13:41:21.621606 << threads=1 2019-07-11T13:41:21.621630 << readyok 2019-07-11T13:41:21.621658 >> ucinewgame 2019-07-11T13:41:21.621672 >> position fen 1kr5/3n4/q3p2p/p2n2p1/PppB1P2/5BP1/1P2Q2P/3R2K1 w - - 0 1 2019-07-11T13:41:21.621695 >> go movetime 193 2019-07-11T13:41:21.632647 << info depth 1 score cp 55 nodes 189 tbhits 0 time 1 nps 94500 pv f3g4 2019-07-11T13:41:21.632791 << info depth 2 score cp 106 nodes 302 tbhits 0 time 1 nps 151000 pv e2g2 g5f4 2019-07-11T13:41:21.632910 << info depth 3 score cp 106 nodes 362 tbhits 0 time 1 nps 181000 pv e2g2 g5f4 f3d5 2019-07-11T13:41:21.633039 << info depth 4 score cp 106 nodes 423 tbhits 0 time 1 nps 211500 pv e2g2 g5f4 f3d5 e6d5 2019-07-11T13:41:21.633635 << info depth 5 score cp 39 nodes 1008 tbhits 0 time 2 nps 336000 pv d1e1 g5f4 e2e6 a6e6 e1e6 2019-07-11T13:41:21.634122 << info depth 6 score cp 120 nodes 1376 tbhits 0 time 2 nps 458666 pv d1e1 d5c7 e1c1 g5f4 c1c4 f4g3 2019-07-11T13:41:21.635202 << info depth 7 score cp 120 nodes 1856 tbhits 0 time 3 nps 464000 pv d1e1 d5c7 e1c1 g5f4 c1c4 f4g3 h2g3 2019-07-11T13:41:21.637107 << info depth 8 score cp 80 nodes 4129 tbhits 0 time 5 nps 688166 pv d1e1 d5c7 e1c1 c7d5 f4f5 d5c7 c1c4 e6f5 2019-07-11T13:41:21.640855 << info depth 9 score cp 117 nodes 9596 tbhits 0 time 9 nps 959600 pv f4g5 h6g5 f3g4 d5c7 d1c1 c4c3 e2a6 c7a6 b2c3 b4c3 2019-07-11T13:41:21.641146 << info depth 10 score cp 117 nodes 10068 tbhits 0 time 9 nps 1006800 pv f4g5 h6g5 f3g4 d5c7 d1c1 c4c3 e2a6 c7a6 b2c3 b4c3 2019-07-11T13:41:21.655614 << info depth 11 score cp 117 nodes 32284 tbhits 0 time 24 nps 1291360 pv f4g5 h6g5 f3g4 c8e8 d1c1 b4b3 g4h3 b8a8 h3f1 a8b7 f1g2 e8f8 c1c4 2019-07-11T13:41:21.659276 << info depth 12 score cp 117 nodes 36777 tbhits 0 time 27 nps 1313464 pv f4g5 h6g5 f3g4 c8e8 d1c1 b4b3 g4h3 b8a8 h3f1 a8b7 f1g2 e8f8 2019-07-11T13:41:21.676137 << info depth 13 score cp 127 nodes 64367 tbhits 0 time 44 nps 1430377 pv f4g5 h6g5 f3d5 e6d5 d4e5 b8a8 d1d5 d7b8 e5b8 a6b6 g1g2 b6c6 e2f3 a8b8 d5a5 c6f3 2019-07-11T13:41:21.678720 << bestmove f4g5 ponder h6g5 Engine best move is not one of the solution moves?? Total points for this theme so far : 0/10
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I compiled Xiphos on my mac an ran some tests. At the 1500 STS positions Xiphos 0.5 reached a much lower solving rate than expected.
The log file shows, that after receiving go movetime 193 (msec) Xiphos finished all positions in 43..45 (msec)!
Is this an macOS issue?
The text was updated successfully, but these errors were encountered: