Author: Robert Hyatt
Date: 10:32:14 05/11/98
Go up one level in this thread
On May 11, 1998 at 13:22:40, Don Dailey wrote: >On May 11, 1998 at 10:38:32, Roland Pfister wrote: > >> >>On May 10, 1998 at 23:54:16, Stuart Cracraft wrote: >> >>> >>>On May 10, 1998 at 22:58:55, Robert Hyatt wrote: >>> >>>>However, without a book, most anything can happen, given the right >>>>time control and opponent. But, in general, it shouldn't play like >>>>that... and it certainly knows that those queen moves are all bad... >>> >>>I am curious how most people are preventing the queen from moving >>>out? Rewarding it to stay on its original square or penalizing it if >>>found on other than its original square? How about penalizing it >>>an amount that is linearly increased by the number of moves its >>>made so far when other pieces still remain to be developed? >>> >>>What is the best way to prevent her royal highness from wandering? >>> >>>(I use the last method but sometimes end up with very high penalties >>>on the queen after a series of moves that won some material or induced >>>a very bad positional problem for the computer's opponent.) >>> >>>--Stuart >> >>I got 2 tips from fellow programmers at CC events: >> >>1. penalize the queen if it is on file a, b, g or h during development. >> I use that. >> >>2. penalize queen for distance to its minor pieces (bishops and >>knights). >> I have not tried that yet. The idea is: if a queen is supported by one >> minor piece it can be very dangerous (for the opponent). If she is >>alone >> there are only shallow threats. >> >>Roland > >I have something in my code simply to penalize the queen for moving >if less than 3 minor pieces are out. The penalty is not very >large. > >- Don I penalize the queen in basically the same way... except that for a time, it was corrupted by a "score-=-PENALTY;" error that basically encouraged queen before pieces, rather than discouraged it... :)
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.