Author: John Brownlee
Date: 19:14:13 02/24/05
Go up one level in this thread
zappa log file showing incorrect initialization of tbcache (0 kb) >>set_option(): hash = 134217728 (128M) >>hash_reallocate(): Allocated transposition table: 128M >>set_option(): phash = 8388608 (8M) >>set_option(): threads = 1 >>game_start_thread(0): spawning worker thread! >>hash_reallocate(): Allocated pawn hash table: 8M >>hash_reallocate(): Allocated king hash table: 8M >>worker_cpu(): CPU0 starting. >>set_option(): kibitz = 3 >>set_option(): book = ../../book/public.zbook >>set_option(): tbpath = E:\Tbs >>tablebase_init(): searching for EGTBs at path "E:\Tbs" >>tablebase_init(): found EGTBs with up to 5 pieces. >>tablebase_init(): EGTB indices & decompression using 15890kb of memory >>set_option(): tbcache = 16 >>tablebase_setcache(): allocated 0kb of memory. --------------------------------------------------------------- zappa log showing correct initialization of 4M tbcache: set_option(): resignscore = -30000 set_option(): tbcache = 4194304 (4M) tablebase_setcache(): allocated 4096kb of memory. set_option(): tbpath = ../../EGTB tablebase_init(): searching for EGTBs at path "../../EGTB" tablebase_init(): found EGTBs with up to 5 pieces. tablebase_init(): EGTB indices & decompression using 1612kb of memory set_option(): hash = 134217728 (128M) hash_reallocate(): Allocated transposition table: 128M set_option(): phash = 8388608 (8M) set_option(): threads = 1 game_start_thread(0): spawning worker thread! set_option(): scorepov = 1 hash_reallocate(): Allocated pawn hash table: 8M hash_reallocate(): Allocated king hash table: 8M worker_cpu(): CPU0 starting. --------------------------------------------------------------- Friends, First I discovered that the default 8M tbcache is not configured during zappa startup. Zappa correctly set up tbcache when I specified tbcache 4M or 16M in zappa.ini. It seems that the program forgets to perform this default tbcache initialization. When trying to use zappa as a uci engine under Arena, zappa first initializes the tbpath and tbcache according to the settings in zappa.ini, then Arena performs a re-initialization of the egtb settings tbpath and tbcache, using Arena's common uci settings. This second round of initialization overrides the first round of settings for tbpath and tbcache in zappa.ini. I found under Arena that the tbcache initialization for uci engines does not use the letter M after the tbcache size. Therefore zappa thinks that the tbcache is being initialized to 16 bytes rather than 16M bytes, so it rounds down to 0 bytes. If under Arena the tbcache size (which is applied in common to common to all uci engines) is set to 8, then zappa will somehow?? not be deceived into trying to initialize tbcache to 8 bytes, and will not attempt to change the tbcache size. In this case the tbcache setting from zappa.ini will remain in effect and the egtb's will work ok. For now I will use zappa as a WB engine, so I can set individual options in zappa.ini. I think it is only necessary to explicitly configure a tbcache to something different than 8M (try 4M or 16M) to get the egtb function working. I hope this information is helpful to you. If I have made some incorrect guesses in my analysis, I welcome your comments and corrections. Regards, John
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.