Tord Romstad wrote:
It is not asymmetric: Positive scores are good for white, negative scores are good for black.
Ok, the exemple I've shown is symmetric but I have seen some code where it is not (but I can't remember which code it was). What will be the involvement of asymmetric value like this one (for exemple) :
Code: Select all
if (COLOUR_IS_WHITE(board->turn)){
eval += 20; //+0.20 for white
}
else{
eval -= 14; // +0.14 for black -> kind of racism ? ;-)
}
Tord Romstad wrote:
It is simply a bonus for being the side to move. With the exception of zugzwang positions, which are very rare, it is usually better to be the side to move than to be in an otherwise identical position where it's the other side's turn to move.
OK, this seems logic to me. I think I understand better now. I will simply call it "side to move bonus", the term "tempo" seems a little bit confusing for me.
Tord Romstad wrote:
I do something similar, but I don't just have a constant bonus: I give additional bonuses for having the side to move combined with possible discovered checks and queen contact checks.
I will have a look at your code when I have time (and more experience in the reading of chess code) but I want to understand most of the fruit/toga code before.
Tord Romstad wrote:
I think it is easier and more natural to encourage the program for activating its pieces quickly, for instance by giving a progressive penalty based on the number of pieces with poor mobility.
In fact, the concept of "tempo" is somewhat hidden behind the "mobility code" ?
PS to Tord : Thank you for your reply.
PS to everyone : Sorry in advance, if my questions seems futile or stupid...