Author: Robert Hyatt
Date: 08:33:59 01/07/02
Go up one level in this thread
On January 07, 2002 at 11:29:59, Vincent Diepeveen wrote: >On January 07, 2002 at 10:03:41, David Rasmussen wrote: > >>In SEE, the king should of course be the last to capture, as no piece can >>capture the king. But the king should also have some large value to indicate a >>winning capture for the opposing side. In a position such as this: > >May i beg you pardon? > >If you can capture a king just like other moves somewhere >then some bug is in your program. He is talking about the SEE capture evaluator, and capturing the king there is the easiest way to make everything work correctly _and_ efficiently. > >>[D]2rqkb1r/p1pnpppp/3p3n/3B4/2BPP3/1QP5/PP3PPP/RN2K1NR w KQk - 0 1 >> >>The captures on f7 will be bishop, knight, bishop, king, queen. >> >>In my program in general, the king has a value of 0, as the kings value has >>never been used for anything before. For SEE, the value has to be used, however. >>To be safe, I would really want to give my king the value of 9 queens plus the >>value 2 knights, bishops and rooks, but then the value of a position with these >>pieces, and only one king on the opposing side will be to big to hold in my >>current Score type, as I am only willing to spend so many bits of scores, so it >>doesn't use up to much space in a hashentry. Actually, writing this, I will >>think out loud that there will always be two kings on the board, and as such, >>the values of the kings will balance out, which means it doesn't matter. Instead >>of not sending this post, I will send it anyway, as a windows into my idiotic >>brain. >> >>/David
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.