Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: Gothmog goes commercial

Author: Jorge Pichard

Date: 13:35:20 04/02/04

Go up one level in this thread


On April 02, 2004 at 14:23:31, Uri Blass wrote:

>On April 02, 2004 at 13:53:03, Tord Romstad wrote:
>
>>On April 02, 2004 at 13:01:02, Matthias Gemuh wrote:
>>
>>>Hi Tord,
>>
>>Hi Matthias!
>>
>>>I think the next version of Gothmog shall be "of commercial strength".
>>
>>Thanks for the kind words, but I think you are too optimistic.  And even if it
>>will some
>>day achieve "commercial strength", it will never be of "commercial quality".
>>
>>>You deserve the money.
>>
>>I don't want money.  I want people to have fun and be happy, and computer chess
>>in general (not only my engine) to advance.  :-)
>
>In that case I hope that you will support my idea of general search code.
>The idea is to have code(not chess related) that can be used for chess and for
>other games when people can use it for chess and for other games.
>
>I plan to think later again about improvement for that code and to add
>information.
>
>I think that it is important to have a small tree with probabilities for every
>move that the program remembers and modify during the search.
>
>I think that evaluation of every node in terms of probabilities and not in a
>number is also important(not only in chess) and I may add in the general search
>code something about it.
>
>I can give an example
>
>A good evaluation can evaluate that black has 0 chances to win here(I think that
>it is a draw but assume for the discussion that there is no knowledge to be sure
>about it)
>
>[D]5rk1/6pp/8/8/8/8/5PPP/5RK1 w - - 0 1

Interesting position, NOT even the top program like Shredder8 can evaluate it as
draw

New game

Analysis by Shredder 8:

1.f4 Rd8 2.Rc1 Kf7 3.Rc7+ Kf6 4.g4
  ±  (0.97)   Depth: 1/1   00:00:00
1.f4 Rd8 2.Rc1 Kf7 3.Rc7+ Kf6 4.g4
  ±  (0.97)   Depth: 6/14   00:00:00
1.f4 Rd8 2.Rc1 Kf7 3.Rc7+ Kf6 4.g4
  ±  (0.97)   Depth: 6/14   00:00:00
1.f4 Rd8 2.Rc1 Kf7 3.Rc7+ Kf6 4.g4
  ±  (0.97)   Depth: 6/14   00:00:00
1.f4 Rd8 2.Rc1 Kf7 3.Rc7+ Kf6 4.g4
  ±  (0.97)   Depth: 6/14   00:00:00
1.f4 Rd8 2.Rc1 Kf7 3.Rc7+ Kf6 4.g4
  ±  (0.97)   Depth: 6/14   00:00:00
1.f4 Rd8 2.Rc1 Kf7 3.Rc7+ Kf6 4.g4
  ±  (0.97)   Depth: 6/14   00:00:00
1.f4 Rc8 2.Kf2 Rc4 3.Ke3 Kf7
  ±  (0.97)   Depth: 6/14   00:00:00
1.f3 Rc8 2.Kf2 Rc4
  ±  (0.98)   Depth: 6/14   00:00:00
1.f3 Kf7 2.Re1 Rd8 3.Kf2 Ra8
  ±  (0.99)   Depth: 6/14   00:00:00
1.f3 Kf7 2.Kf2 Kf6 3.Re1 Rd8 4.Kg3
  ±  (0.97)   Depth: 7/11   00:00:00  13kN
1.f4 Rd8 2.Kf2 Ra8
  ±  (0.98)   Depth: 7/11   00:00:00  15kN
1.f4 Kf7 2.Re1 Kg6 3.g3 Kf5 4.Kf2
  ±  (0.99)   Depth: 7/12   00:00:00  18kN
1.f4 Rb8 2.Rc1 Kf7 3.Rc7+ Kf6 4.Kf2 Rb1 5.g3
  ±  (1.00)   Depth: 8/18   00:00:00  37kN
1.Rb1 Rc8 2.g3 Kf7 3.Rb6 Rf8
  ±  (1.01)   Depth: 8/18   00:00:00  44kN
1.Rb1 Rc8 2.g3 Kf7 3.Rb7+ Kf6 4.Kg2
  ±  (1.01)   Depth: 8/18   00:00:00  47kN
1.Rb1 Kf7 2.Rb6 Rc8 3.g3 Rc4
  ±  (1.03)   Depth: 9/22   00:00:00  75kN
1.Re1 Rd8 2.f4 Rd2 3.Re7 Kf8 4.Ra7 Rf2
  ±  (1.04)   Depth: 9/22   00:00:00  96kN
1.Re1 Rd8 2.f4 Kf7 3.Kf2 Rd3 4.g4 Rd2+ 5.Re2 Rd1
  ±  (1.04)   Depth: 9/22   00:00:00  98kN
1.Re1 Kf7 2.f4 Rc8 3.Kf2 g6 4.g3 Kf6
  ±  (1.06)   Depth: 10/19   00:00:00  142kN
1.f4 Rf5 2.g4 Rc5 3.Kf2 Rc2+ 4.Kg3 Kf7
  ±  (1.07)   Depth: 10/26   00:00:00  175kN
1.f4 Kf7 2.Re1
  ±  (1.07)   Depth: 10/26   00:00:00  191kN
1.f4 Kf7 2.Re1 Rc8 3.Kf2 Kg6 4.g4 Rc2+ 5.Re2 Rc1
  ±  (1.07)   Depth: 11/20   00:00:01  235kN
1.f4 Kf7 2.Re1 Kg6 3.g3 Rc8 4.Kf2 Rc2+ 5.Re2 Rc4
  ±  (1.07)   Depth: 12/22   00:00:01  340kN
1.f4 Rd8 2.Kf2 Rd2+ 3.Kf3 Rd3+ 4.Ke2 Rc3 5.Re1 g6 6.Kd2 Rb3 7.h3
  ±  (1.07)   Depth: 13/26   00:00:02  732kN
1.f4 Rd8 2.Kf2 Rd2+ 3.Kf3 Rd3+ 4.Ke2 Ra3 5.Re1 Kf7 6.Kf2 Kg6 7.g3 Kf5 8.Re5+ Kg6
9.h4 Kf6 10.Re8
  ±  (1.08)   Depth: 14/28   00:00:04  1257kN
1.f4 Rc8 2.g3 Kf7 3.Kg2 Rc2+ 4.Rf2 Rc3 5.Re2 Kf6 6.Kh3 Rc4 7.Kh4 Kf5
  ±  (1.10)   Depth: 15/30   00:00:09  2902kN
1.f4 Ra8 2.g3 g6 3.Re1 Kf7 4.Kf2 Ra2+ 5.Re2 Ra1
  ±  (1.10)   Depth: 16/31   00:00:15  4697kN
1.f4 Rb8 2.Re1 Rb2 3.Re7 h6 4.g3 Kh7 5.f5 h5 6.f6 Kg6 7.fxg7 Rb1+ 8.Kg2 Rg1+
9.Kxg1
  ±  (1.12)   Depth: 17/33   00:00:30  9395kN
1.f4 Rc8 2.g3 Rc4 3.Re1 Rc2 4.Re7 Kf8 5.Rb7 Rc1+ 6.Kg2 Rc4 7.h3 Rc8
  ±  (1.12)   Depth: 18/36   00:00:42  13205kN
1.g3 Kf7 2.Kg2 Kg6 3.f4 Kh5
  ±  (1.13)   Depth: 18/36   00:01:05  20327kN
1.g3 Kf7 2.Kg2 Ra8 3.f4 Ra3 4.Rb1 Ra2+ 5.Kh3 Rf2 6.Rb7+ Kf6 7.Rb6+ Kf5 8.Rb7 Kg6
9.Ra7
  ±  (1.13)   Depth: 18/36   00:01:14  23055kN
1.g3 g5 2.f4 gxf4 3.gxf4 Kg7 4.Kg2 Ra8 5.Kf3
  ±  (1.12)   Depth: 19/38   00:01:45  32716kN
1.f4 Kf7 2.Kf2 Kg6 3.g3 Kf5 4.Re1 Rb8 5.Re5+ Kg6
  ±  (1.13)   Depth: 19/38   00:01:48  33628kN
1.f4 Rb8 2.Re1 Rb2 3.Re7 h6 4.g3 Rc2 5.h3 Kh7 6.g4 Rd2 7.f5 Rc2
  ±  (1.15)   Depth: 19/38   00:02:33  47286kN
1.f4 Ra8 2.g3 Kf7 3.Kg2 Kg6 4.Rb1 Ra2+ 5.Kh3 Kf5 6.Rb7 Ke4 7.Rxg7 h5 8.Kh4 Rxh2+
9.Kg5 Ra2
  ±  (1.16)   Depth: 20/38   00:03:34  65962kN
1.f4 Kf7 2.g3 Kf6 3.Kg2 Rb8 4.Kf3 h5 5.Re1 Rb3+ 6.Re3 Rb5 7.Rc3
  ±  (1.19)   Depth: 21/39   00:05:28  100534kN
1.f4 Rb8 2.Kf2 h5 3.Re1 Kf7 4.Re5 Rb2+ 5.Kg3 g6 6.Kf3 Rb3+ 7.Re3 Rxe3+ 8.Kxe3
Ke6
  ±  (1.21)   Depth: 22/42   00:11:27  211267kN
1.f4 Ra8 2.g3 Kf7 3.Kg2 Kf6 4.Kf3 h5 5.Re1 Ra2 6.Re2 Ra3+ 7.Re3 Ra2 8.h3 Ra3
  ±  (1.22)   Depth: 23/43   00:16:45  308795kN
1.f4 Ra8 2.g3 Kf7 3.Kg2 Kf6 4.Kf3 h5 5.Re1 Ra3+ 6.Re3 Ra2 7.Re2 Ra3+ 8.Re3 Ra2
9.Re2 Ra3+ 10.Re3 Ra2
  ±  (1.22)   Depth: 24/44   00:22:41  396804kN
1.f4 Ra8 2.g3 Kf7 3.Kg2 Ra5 4.h3 h5 5.g4
  ±  (1.22)   Depth: 25/47   00:32:51  583668kN
1.f4 Ra8 2.Kf2 Kf7 3.g4 Ra3 4.Rb1 h6 5.Kg2 g6 6.h3 Ra2+ 7.Kg3 Ra3+ 8.Kh4 Ra4
  ±  (1.24)   Depth: 26/49   01:19:11  1383446kN

(Pichard, MyTown 02.04.2004)

>
>If you evaluate the root position as equal you may want to prune this position
>based on your probabilities when the remaining depth is not important when
>another position when black is a piece down may be interesting to search because
>you evaluate it as 90% win for white but 5% win for black so continue to search
>may reveal this information.
>
>see http://www.talkchess.com/forums/1/message.html?357887 for my last post in
>this subject.
>
>My code still does not code special code that is using some function to evaluate
>probabilities of win,draw,loss but I think that general code should allow this
>possibility(there is also need to add general hash code and general iterate
>code).
>
>I plan to think about the problem and I may post more code later and if you can
>help me by looking at the code and post your ideas it may be productive.
>
>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.