Author: Uri Blass
Date: 15:03:53 06/04/03
Go up one level in this thread
On June 04, 2003 at 16:30:45, Michel Langeveld wrote:
>>>//Nullmover with only material
>>>Nodes per sec.: 319485
>>
>>>//Nullmover with everything switched on:
>>>Nodes per sec.: 301770
>>
>>This looks strange. I think you should expect a much bigger difference in
>>nodes/s.
>>
>>Regards,
>>Dieter
>
>Yes I was also thinking it was odd...
>I expected also a bigger difference ... Am not sure why this is ...
>
>my eval starts with:
>
>int generatePositionScore(int alpha, int beta)
>{
> evalCounter++;
>
> if (isDraw()) return 0;
> }
>
> scoreType score = p.materialWhite - p.materialBlack;
>
> //lazy eval
> if (score - 150 > beta) return score;
> if (score + 150 < alpha) return score;
>
> ...
>}
>
>It can be that the first part which I call lazy eval catches a lot of positions
>.... or there is a much bigger hotspot as the evaluation currently.
>I will run a profile to see if I can find more out ....
Did you try to test your program without lazy evaluation?
I think that there may be important cases when the difference between the score
and the material evaluation is more than 1.5 pawn(I assume 150 is 1.5 pawn) so
lazy evaluation cause more demage then the problem that it solves.
Uri
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.