GreKo Chess Engine

-
I compiled Vladimir Medvedev's UCI engine GreKo for Android (ARM) for use in Chess for Android and put the binary on UCI engines for Android (with kind permission of Vladimir). Below a screenshot and the results of a few quick matches with other engines on a Nexus S (1GHz Hummingbird) with 32MB hash and Nalimov/Gaviota/Scorpio endgame tablebases on SD card.

Greko 8.0 - RobboLito 0.085e4l     0.0 - 10.0  +0/-10/=0   0.00%
Greko 8.0 - IvanHoe-Beta v999947c  0.5 - 9.5   +0/-9/=1    5.00%
Greko 8.0 - Stockfish 2.0          1.0 - 9.0   +1/-9/=0   10.00%
Greko 8.0 - Rotor 0.6a             3.0 - 7.0   +2/-6/=2   30.00%
Greko 8.0 - Gaviota v0.80.0.107    5.5 - 4.5   +4/-3/=3   55.00%
Greko 8.0 - GNU Chess 5.07.153.3b  6.0 - 4.0   +6/-4/=0   60.00%
Greko 8.0 - RedQueen 0.9.5         6.5 - 3.5   +5/-2/=3   65.00%
Greko 8.0 - BikJump v2.1P         10.0 - 0.0   +10/-0/=0 100.00%
Greko 8.0 - ZCT-0.3.2500          10.0 - 0.0   +10/-0/=0 100.00%


Comments

Anonymous said…
what means TB CACHE,CPUs,HASH TABLE?
every time i make it HASH TABLE=64mb
TB Cache=64mb CPUs=1. Optimal settings?
August 23, 2011 at 1:51 PM
Aart Bik said…
hash = size of the chess engine hash table
tb cache = size of the endgame tablebases cache
cpus = number of threads to use in engine on a multicore processor

optimal settings depend heavily on actual device as well as the particular chess engine; on a single core CPUs should be 1; hash size of 32MB and TB cache of 8MB usually performs well
August 23, 2011 at 5:22 PM
Post a Comment

Popular posts from this blog

Checkers Move Generation

-
I was able to make a small improvement in the checkers move generator (written in Java for the Android SDK). The following table shows run times of several perft depths before and after optimization when run on the emulator (which should mimic actual run times on the phone quite well). DEPTH #LEAF NODES ORIGINAL OPTIMIZED TIME TIME ==================================== 7 179740 2.9s 1.9s 8 845931 14.2s 9.7s 9 3963680 66.3s 45.6s 10 18391564 294.6s 208.7s P.S. Runtimes for a C++ checkers move generator on a 2.2 GHz Core 2 Duo are given at my checkers page .
Read more

Connecting Chess for Android to a Remote Server

-
Image
I have received several questions on how to connect Chess for Android running on an Android device (e.g. a phone) as client to a remote chess server (e.g. a powerful desktop), so I decided to write a small document with detailed instructions. What you will need: The server software from Bernhard Wallner's chess utilities , suited for your server's operating system (if, say, your desktop runs Windows, you will need to download the Windows version). You do not need to download the client software in this case. The network enabled version of Chess for Android . On the server, start the engine server software, and construct a new row for every engine you want to run remotely. Assign a name, port number, and select the full path to each engine binary (an executable that runs on the server). You can also supply command line options for starting the engine. Check the active checkboxes and click start when done. This yields something similar to the screenshots below. Here, I have s
Read more

Connecting with the DGT Board

-
Image
After all the fun I had connecting Chess for Android with the Millennium  over Bluetooth, I was curious if I could provide similar support for the DGT electronic chess boards. Some of these have Bluetooth capabilities, most use USB connections, and some older models, like the one I have, still use the RS-232 connector. To my pleasant surprise, by combining the original serial cable of DGT with a USB-to-serial cable and a female-USB-to-USB-C cable, I was able to get an actually working connection between my DGT board and my tablet or phone. Next was implementing support in Chess for Android. Luckily, DGT kindly shared the protocol documentation with me, and after a fun weekend of hacking, Chess for Android now proudly supports DGT electronic chess boards as well.
Read more