Author: martin fierz
Date: 06:38:14 11/17/03
Go up one level in this thread
On November 17, 2003 at 07:43:54, K. Burcham wrote: >On November 17, 2003 at 04:20:42, martin fierz wrote: > >>On November 16, 2003 at 20:08:45, K. Burcham wrote: >> >>> >>>why do programs allow humans to control these openings? >>>why do programs allow humans to set up these walls instead of exchange pawns for >>>open files? >>>why can't code be written to exchange pawns even when early in book? >>> >>>why stage these matches when so many know what needs to be done with opening >>>code? I wish I knew why this was such a big deal to write code for. >>> >>>I am glad we have highly accomplished GM, but aggravating giving them easy win. >>>I would prefer letting them outplay the program in an open position. >>> >>>kburcham >> >>the real question should be: why do programs like fritz play these closed >>positions worse than any 2000 player? fritz' programmers surely know about those >>weaknesses, why have they never been addressed? with a whole team of >>professionals working on it... > >I dont agree. Kasparov worked on this closed position, once he had it, it was to >late for the program. the program played defensive moves while Kasparov was on >the offensive---big difference, then too late. the program did not play defensive moves! it played nothing at all, moved pieces back and forth etc. that's the problem here. what you are asking for is a cheap fix to this problem: not to let a closed position arise at all. if you do this, by adding *ridiculous* eval terms like "fewer pawns are good for the machine", you will also hurt the program in positions where it is actually *good* to close the position. the programs (or better: their programmers) will have to learn to deal with those closed positions. it may not be easy, but it must be possible... it was not a bad position from an objective point of view! cheers martin
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.