In quiescence I mainly only count piece values if I don't add a mobility term.Uri Blass wrote:I do not understand how do you get something close to it unless you have only piece square table and mobility in the evaluation and even in the last case you only test the speed of the cheap evaluation function when most of the time is not used in the evaluation function.Henk wrote:If I have 16 pieces and say 40 moves. I get a factor 40/16. That's more than 200%.Stan Arts wrote:Losing a ply is a 200-300% slowdown. That sounds a bit off.Henk wrote: If I compute mobility in eval I loose at least one ply. And nothing beats an extra ply they say. So for instance my eval would be 0.1 Pawns more accurate but in some positions it wouldn't see that it looses a piece or gets check mated.
I can calculate mobility ten times and raytrace a dancing dinosaur before that happens.
This saves me a ply but my chess program plays not better than 1800-2200 elo I guess, so the extra ply doesn't seem to help me much. But if I add a mobility term my chess program seems to play even worse. My piece square table only contains an estimate of a mobility factor.