sedicla wrote: ↑Sun Oct 13, 2019 8:33 pm
Gabor Szots wrote: ↑Sun Oct 13, 2019 8:22 pm
sedicla wrote: ↑Sun Oct 13, 2019 3:30 pm
- Syzygy endgame tablebase support, using fathom probing tool, Special thanks to Jon Dart.
- UCI protocol support. I recommend running as UCI engine from now on.
Does that mean Tucano is not able to use the syzygy bases in WB mode? Or something else?
EDIT: I have found a variable syzygy_path in the executable so it seems there is a command line parameter for using syzygy in WB mode.
Yes, it supports syzygy in WB mode too. Both have the same option name, and the command line parameter should work for both.
Let me know.
With -syzygy_path it seems to find the tablebases. With -syzygypath it seems it does not find them.
Here the debug for the former:
2019-10-13 21:53:27,525 Arena 3.5.1
2019-10-13 21:53:27,525
2019-10-13 21:53:27,962**----------New game---2019-10-13 21:53:27,962 V -------------
2019-10-13 21:53:28,087**screen: 1536x864
2019-10-13 21:53:28,087**Monitors: 1
2019-10-13 21:53:28,087**Monitor0: 1536x864
2019-10-13 21:53:28,087**FormMonitor: 0
2019-10-13 21:53:28,087**DesktopRect: 0/0 .. 1536/864
2019-10-13 21:53:28,197**Loading 1
2019-10-13 21:53:42,383*1*------------------Starting engine 1 Tucano 8.00 64-bit WB-------------------
2019-10-13 21:53:42,383*1*Configured Engine 1 Type: WB2
2019-10-13 21:53:42,383*1*Engine 1 dir: E:\Sakk\Engines\Tucano
2019-10-13 21:53:42,383*1*Engine 1 commandline: E:\Sakk\Engines\Tucano\Tucano_8.00-x64.exe -hash 256 -threads 1 -syzygy_path F:\Sakk\syzygy
2019-10-13 21:53:42,492*1*Child Process Prio Adj: PID 4360 conhost.exe
2019-10-13 21:53:42,492*1*Engine 1 ProcessID: 9600
2019-10-13 21:53:42,492*1*Engine 1 Prio:32 ThreadPrio:0
2019-10-13 21:53:42,492-->1:xboard
2019-10-13 21:53:42,492-->1:protover 2
2019-10-13 21:53:42,602<--1:Tucano chess engine by Alcides Schulz - 8.00 (type 'help' for information)
2019-10-13 21:53:42,602<--1: hash table: 256 MB, threads: 1
2019-10-13 21:53:42,602<--1:# using egtb syzygy path=F:\Sakk\syzygy TB_LARGEST=6
And for the latter:
2019-10-13 21:55:48,513-->1:?
2019-10-13 21:55:48,513-->1:force
2019-10-13 21:55:48,513-->1:quit
2019-10-13 21:55:49,013*1*------------------Starting engine 1 Tucano 8.00 64-bit WB-------------------
2019-10-13 21:55:49,013*1*Configured Engine 1 Type: WB2
2019-10-13 21:55:49,013*1*Engine 1 dir: E:\Sakk\Engines\Tucano
2019-10-13 21:55:49,013*1*Engine 1 commandline: E:\Sakk\Engines\Tucano\Tucano_8.00-x64.exe -hash 256 -threads 1 -syzygypath F:\Sakk\syzygy
2019-10-13 21:55:49,122*1*Child Process Prio Adj: PID 11980 conhost.exe
2019-10-13 21:55:49,122*1*Engine 1 ProcessID: 5216
2019-10-13 21:55:49,122*1*Engine 1 Prio:32 ThreadPrio:0
2019-10-13 21:55:49,122-->1:xboard
2019-10-13 21:55:49,122-->1:protover 2
2019-10-13 21:55:49,185<--1:Tucano chess engine by Alcides Schulz - 8.00 (type 'help' for information)
2019-10-13 21:55:49,232<--1: hash table: 256 MB, threads: 1
2019-10-13 21:55:49,232<--1:feature setboard=1
2019-10-13 21:55:49,232-->1:accepted setboard
2019-10-13 21:55:49,232<--1:feature myname="tucano_8.00"
2019-10-13 21:55:49,232<--1:feature colors=0
2019-10-13 21:55:49,232-->1:accepted colors
2019-10-13 21:55:49,232<--1:feature analyze=1
2019-10-13 21:55:49,232-->1:accepted analyze
2019-10-13 21:55:49,232<--1:feature option="Hash -spin 64 8 16384"
2019-10-13 21:55:49,232-->1:accepted option
2019-10-13 21:55:49,232<--1:feature option="Threads -spin 1 1 64"
2019-10-13 21:55:49,232-->1:accepted option
2019-10-13 21:55:49,263<--1:feature option="SyzygyPath -path """
2019-10-13 21:55:49,263-->1:accepted option
2019-10-13 21:55:49,294<--1:feature done=1
2019-10-13 21:55:49,294-->1:accepted done
2019-10-13 21:55:49,294*1*Child Process Prio Adj: PID 11980 conhost.exe
2019-10-13 21:55:49,466-->1:new
2019-10-13 21:55:49,466-->1:random
2019-10-13 21:55:49,466-->1:level 40 2 0
2019-10-13 21:55:49,466-->1:post
2019-10-13 21:55:49,466-->1:hard
2019-10-13 21:55:49,466-->1:easy
So in my view the UCI and WB option name for syzygy tables are not the same.