Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: Mobility in Chess Evaluation Function at terminal-nodes

Author: Uri Blass

Date: 13:40:51 12/28/05

Go up one level in this thread


On December 28, 2005 at 16:30:26, Will Singleton wrote:

>On December 28, 2005 at 16:04:28, Tord Romstad wrote:
>
>>On December 28, 2005 at 15:31:55, Roman Hartmann wrote:
>>
>>>On December 28, 2005 at 15:27:34, Dann Corbit wrote:
>>>
>>>>How are you calculating mobility?
>>>>A 10:1 loss in speed is very traumatic.
>>>>Unless you are only counting wood in your evaluation, you should not see that
>>>>traumatic of a degradation.
>>>
>>>Several problems:
>>>-outdated board design 10x12
>>
>>16x12 may be slightly more convenient, but 10x12 isn't outdated
>>at all.  There is no reason why mobility evaluation should be expensive
>>on a 10x12 board.
>>
>>>-legal move generator instead of pseudo legal
>>
>>You shouldn't generate moves at all when evaluating mobility.  This
>>is almost certainly the main reason why you see such a big slowdown.
>>When you generate moves, you do a lot of work which is not necessary
>>when you just want to evaluate mobility.  You don't need the moves
>>at all, just the number of moves.
>
>Could you clarify?  In my program, I have to gen the moves in order to count
>them.  Do you mean that your mobility doesn't consider legality or viability?
>
>Will

I do not understand why.

generating moves include putting them in a list.
Why do you need to put the moves in a list in order to count them?

In the past my mobility function used only the number of legal moves.
Today it also use the number of the legal moves but only when the king is not
under threat.

When the king is under threat the mobility evaluation calculate number of
illegal moves but not illegal moves of pinned pieces that expose the king to
another attack.

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.