[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [computer-go] Minimax with random evaluations
Russell Wallace wrote:
On Fri, 21 Jan 2005 09:19:50 -0500, Don Dailey <drd@xxxxxxxxxxxxxxxxx> wrote:
Evaluation function is: #define EVAL (8192 - (rand() & 0x3fff))
I'm not sure it matters and could just as easily have used rand()
I don't understand this - what benefit would minimax search give if
the evaluation function is random? How is the result different from
just making a random move?
(Maybe I'm missing something obvious, in which case enlightenment
would be appreciated :))
- Russell
_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/
If you search one ply as MAX player, you get higher evaluation score
when the number of available move options increases, because the
expected maximum value gets higher.
If you search two plys, beginning at MIN player, the lowest score will
be on move for which the opponent has the least number of answers
available. This pattern continues inductively.
But the main point is that at the last branch before the search horizon,
random evaluation scores function as a noisy way to calculate the number
of options available. In many games having lots of move options
correlates somewhat with a good position. But, as noted previously, this
is not very relevant in the context of go.
Regards,
--
Antti Huima (Mr.)
Director, Conformiq Tools
mobile: +358 40 528 8667
email: antti.huima@xxxxxxxxxxxxxxxxx
Conformiq Software Ltd.
Stella Terra, Lars Sonckin kaari 16
FIN-02600 Espoo, Finland
tel: +358 10 286 6300
fax: +358 10 286 6309
http://www.conformiq.com/
_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/