Author: chandler yergin
Date: 09:08:47 03/29/05
Go up one level in this thread
On March 28, 2005 at 16:39:15, Vincent Lejeune wrote: >On March 28, 2005 at 04:22:30, chandler yergin wrote: > >>On March 27, 2005 at 13:46:35, Vincent Lejeune wrote: >> >>>On March 27, 2005 at 11:01:17, chandler yergin wrote: >>> >>>>Thank you Vincent! >>>>Of course we human can see the Line... it's not that difficult a Problem for us. >>>> >>>>I Notice you 'gave up' at Ply 31. The Tree keeps getting bigger, >>>> and the time for each Iteration gets longer and longer.. >>>> >>>>How many thousands of hours do you anticipate it would take the Program to >>>>find the Mate? >>>> >>>>I don't blame you for not wanting to waste your young years waiting for it >>>>to finally arrive at Mate. >>>> >>>>;) >>> >>>I'd say 2-3 hours for Rebel Pro Deo on a 3 Ghz CPU >> >> >>We can both say anything.. a demonstration would be nice. >>The main point is, the Programs have a long way to go to compete with Humans! > >Pro deo seems to hang after 5 min :( > >Hiarcs 9 seems on a the way to solve the puzzle , but I've to stop it after 7 >hours : > >8/p3P3/rp6/kp6/1p4PK/1P6/1P5p/4r2R w - - 0 1 > >Analysis by Hiarcs 9: >... >1.e8C Tg1 > = (0.01) Profondeur: 18/50 00:01:17 31561kN >1.e8C Tg1 > = (0.25) Profondeur: 18/50 00:01:20 32476kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 Te1 5.g6 Tg1 6.Rh7 Tf1 7.g7 Tg1 8.g8D Tg7+ >9.Rh6 Tg6+ 10.Rh5 > +- (4.45) Profondeur: 18/50 00:02:05 48696kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 Te1 5.g6 Tg1 6.Rh7 Tf1 7.g7 Tg1 8.g8D Tg7+ >9.Rh6 Tg6+ 10.Rh5 > +- (4.70) Profondeur: 19/50 00:02:15 52246kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 Te1 5.g6 Tg1 6.Rh7 Tf1 7.g7 Tg1 8.g8D Tg7+ >9.Rh6 Tg6+ > +- (4.73) Profondeur: 19/51 00:02:19 53992kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 Te1 5.g6 Tg1 6.Rh7 Tf1 7.g7 Tg1 8.g8D Tg7+ >9.Rh6 Tg6+ > +- (4.98) Profondeur: 20/51 00:02:30 58286kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 Te1 5.g6 Tg1 6.Rh7 Tf1 7.g7 Tg1 8.Rh8 Tc1 >9.g8D Tg1 10.Dg2 Te1 11.Cd6 Te8+ 12.Rg7 Te7+ 13.Rf6 Th7 14.Txh2 Txh2 15.Dxh2 > +- (6.50) Profondeur: 20/53 00:03:22 78691kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 Te1 5.g6 Tg1 6.Rh7 Tf1 7.g7 Tg1 8.Rh8 Tc1 >9.g8D Tg1 10.Dg2 Te1 11.Cd6 Te8+ 12.Rg7 Te7+ 13.Rf6 Th7 14.Txh2 Txh2 15.Dxh2 > +- (6.75) Profondeur: 21/53 00:04:00 92686kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 Te1 5.g6 Tg1 6.Rh7 Tf1 7.g7 Tg1 8.Rh8 Tc1 >9.g8D Tg1 10.Dg7 Tf1 > +- (10.95) Profondeur: 21/53 00:26:44 662790kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 > +- (10.95) Profondeur: 22/58 00:27:58 709986kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 > +- (11.20) Profondeur: 23/58 00:29:32 751673kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 Te1 5.g6 Tg1 6.Rh7 Tf1 7.g7 Tg1 8.Rh8 Tc1 >9.g8D Tg1 10.Dg7 Tf1 11.Rh7 Tg1 12.Dg6 Tf1 > +- (12.03) Profondeur: 23/61 05:12:40 7710691kN >1.e8C Tg1 2.Rh5 Te1 3.g5 Tg1 4.Rh6 Te1 5.g6 Tg1 6.Rh7 Tf1 7.g7 Tg1 8.Rh8 Tc1 >9.g8D Tg1 10.Dg7 Tf1 11.Rh7 Tg1 12.Dg6 Tf1 > +- (11.78) Profondeur: 24/61 05:14:36 7802639kN >1.e8C Tg1 2.Rh5 Tf1 3.g5 Tg1 4.Rh6 Tf1 5.g6 Tg1 6.Rh7 Te1 7.g7 Tg1 8.Rh8 Tf1 >9.g8D Tg1 10.Dg7 Tf1 11.Rh7 Tg1 12.Dg6 Tc1 13.Rh6 Tg1 14.Dg5 Td1 > +- (11.11) Profondeur: 24/61 05:31:25 8256669kN >1.e8C Tg1 2.Rh5 Tf1 3.g5 Tg1 4.Rh6 Tf1 5.g6 Tg1 6.Rh7 Te1 7.g7 Tg1 8.Rh8 Tf1 >9.g8D Tg1 10.Dg7 Tf1 11.Rh7 Tg1 12.Dg6 Te1 13.Rh6 > +- (11.11) Profondeur: 25/61 06:01:53 9124204kN Thanks for trying... As you see as the Depth of Search goes deeper, the number of possible moves increases, and the time time for each iteration takes longer and longer.. I think one way to 'short cut' would be to Clip the Analysis to Notation, and start search from that point again, do that periodically, to Mate. No reason to wear out a Hrd Drive or yourself. ;)
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.