Author: Severi Salminen
Date: 03:19:15 11/30/00
Go up one level in this thread
>That's about all I have to say... would love to hear some more original ideas >about testing engines! One thing: bitboards! Bitboards are a "very" good error indicator, at least in my engine which is under construction. All of my bugs has come visible because of bitboards. My makemove and board drawing functions allways report errors when they see something odd (like there should be a white piece on a1 but none of the piece type bitboards has anything on a1 etc.). Bitboards has allways the information of a single piece or a pawn distributed to (at least) two places - or three if using rotated bitboards. With arrays this kind of simple checking doesn't occur and errors are harder to catch. I'd also like to have a set of positions in which we would know allmost everything: what is the best move in 1 ply search, 2 ply..., the same with qsearch and with null moves - assuming maybe only material evaluation. We would have the info on exact tree sizes and the PV. It would be easier to test that everything goes the right way. Severi
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.