Winboard Forum

Source code and executables (only Linux and Mac OS X so far, a Windows binary will follow when someone (probably Dann) has compiled it) for Glaurung 0.1.7 are now available from my Glaurung page. In this version, the two old bugs which occasionally caused incorrect mate or draw scores to be displayed have finally been fixed. There are also numerous other minor improvements and bug fixes. I think this version is stronger than 0.1.6, but by how much remains to be seen.

My tests indicate that Glaurung is now stronger than Gothmog, at least in blitz games. I therefore ask those who organize tournaments and allow only one program per author to use Glaurung rather than Gothmog, unless your tournament rules require that all engines use their own opening book. Glaurung does not yet have any opening book support, but it is planned for the near future.

Tord

Binary:
ftp://cap.connx.com/pub/chess-engines/n ... aurung.exe

compressed with bzip2:
ftp://cap.connx.com/pub/chess-engines/n ... ng.exe.bz2

Hi Dann,

Dann Corbit wrote:Binary:
ftp://cap.connx.com/pub/chess-engines/n ... aurung.exe

this is the old version 0.1.6!

compressed with bzip2:
ftp://cap.connx.com/pub/chess-engines/n ... ng.exe.bz2

And this the still older version 0.1.5!

Regards,
Franz.

Dann Corbit wrote:Binary:
ftp://cap.connx.com/pub/chess-engines/n ... aurung.exe

compressed with bzip2:
ftp://cap.connx.com/pub/chess-engines/n ... ng.exe.bz2

Hi Dann!

Thanks, but are you sure this is the right version? After running your glaurung.exe through 'strings' I am 99% sure that this is version 0.1.5 or 0.1.6 rather than the new 0.1.7. Have a look at the following sequence of strings, for instance:

Code: Select all

option name Static pruning depth type spin default 3 min 0 max 4
option name Passed pawns type spin default 120 min 0 max 200
option name King safety type spin default 100 min 0 max 200
option name Hash type spin default 32 min 1 max 256
id author Tord Romstad
id name %s %s
Glaurung
0.1.5

The UCI options in Glaurung 0.1.7 look like this:

Code: Select all

  printf("option name Hash type spin default 32 min 1 max 256\n");
  printf("option name King safety type spin default 100 min 0 max 200\n");
  printf("option name Passed pawns type spin default 130 min 0 max 200\n");
  printf("option name Pawn structure type spin default 150 min 0 max 200\n");
  printf("option name Static pruning depth type spin default 3 min 0 max 4\n");

This does not match the output from running 'strings' on your glaurung.exe. Note also that the version number 0.1.5 is found in your .exe file, which is yet another indication that you must have compiled the wrong version.

I just checked the source code at my web page, and can confirm that the files found there are the correct versions.

Tord

I will take a look and see what is wrong.

I figured out what was wrong.

Earlier versions of Glaurung I had stored in directory
\pgn\winboard-engines\glaurung

And the new version unloaded itself into a subdirectory called:
\pgn\winboard-engines\glaurung\src

and so I built and delivered the wrong version.

Amazingly, this happens to me all the time (I am sure at least twenty times it has happened in the thousands of builds I have done).

This one will do better I think:

E:\pgn\winboard-engines\glaurung\src\Release>glaurung.exe
uci
id name Glaurung 0.1.7
id author Tord Romstad
option name Hash type spin default 32 min 1 max 256
option name King safety type spin default 100 min 0 max 200
option name Passed pawns type spin default 130 min 0 max 200
option name Pawn structure type spin default 150 min 0 max 200
option name Static pruning depth type spin default 3 min 0 max 4
uciok


Sorry about the mix up.

Here I am, whining about it at the old Winboard forum a while back:
http://f11.parsimony.net/forum16635/messages/61603.htm

Tested what was there to make sure:

ftp> bin
200 Type Binary
ftp> get glaurung.exe
200 Port command received
150 Opening data connection
226 Transfer complete
ftp: 122880 bytes received in 0.01Seconds 12288.00Kbytes/sec.
ftp> get glaurung.exe.bz2
200 Port command received
150 Opening data connection
226 Transfer complete
ftp: 60130 bytes received in 0.01Seconds 6013.00Kbytes/sec.
ftp> quit
221 Goodbye

E:\pgn\winboard-engines\glaurung\src\Release>glaurung.exe
uci
id name Glaurung 0.1.7
id author Tord Romstad
option name Hash type spin default 32 min 1 max 256
option name King safety type spin default 100 min 0 max 200
option name Passed pawns type spin default 130 min 0 max 200
option name Pawn structure type spin default 150 min 0 max 200
option name Static pruning depth type spin default 3 min 0 max 4
uciok
quit

E:\pgn\winboard-engines\glaurung\src\Release>bzip2 -d glaurung.exe.bz2
bzip2: Output file glaurung.exe already exists.

E:\pgn\winboard-engines\glaurung\src\Release>del *.exe

E:\pgn\winboard-engines\glaurung\src\Release>bzip2 -d glaurung.exe.bz2

E:\pgn\winboard-engines\glaurung\src\Release>glaurung.exe
uci
id name Glaurung 0.1.7
id author Tord Romstad
option name Hash type spin default 32 min 1 max 256
option name King safety type spin default 100 min 0 max 200
option name Passed pawns type spin default 130 min 0 max 200
option name Pawn structure type spin default 150 min 0 max 200
option name Static pruning depth type spin default 3 min 0 max 4
uciok
quit

Dann Corbit wrote:I figured out what was wrong.

Earlier versions of Glaurung I had stored in directory
\pgn\winboard-engines\glaurung

And the new version unloaded itself into a subdirectory called:
\pgn\winboard-engines\glaurung\src

and so I built and delivered the wrong version.

Amazingly, this happens to me all the time (I am sure at least twenty times it has happened in the thousands of builds I have done).

Twenty times out of thousands of builds hardly qualify as "all the time", IMHO. I am sure that I would have made such mistakes far more often.
If I understand you right, you prefer that I do not put the source files in a subdirectory in future releases?

As always, thanks a lot for your help! I have now updated my Glaurung page with the new Windows binary.

Tord

Actually, it is better to leave it the same (whatever that is).

The thing that drives me nuts is when the directory structure changes every time.

For instance, suppose an author writes an engine called "foobird".

The first relase has a zip with no paths in it.
The second release uses a subdirectory called ".\foobird-1.0"
The third release puts the source in ".\foobird-1.1-3-source"
the fourth release puts the source in ".\fb\src"
The fifth release puts the source in ".\foobird-fun\coolrod\bozammo\src"

You get the picture.
I favor either:
1. No special subdirectories -- let me name it
OR
2. Whatever it is, make it always the same.