Author: Robert Hyatt
Date: 11:17:16 10/05/98
Go up one level in this thread
On October 05, 1998 at 10:17:08, blass uri wrote: > >On October 05, 1998 at 09:28:56, Robert Hyatt wrote: > >>On October 05, 1998 at 03:53:31, blass uri wrote: >> >>>I can use the command trace to tell crafty to display crafty's tree >>>but the problem is that it is dispayed too fast and I cannot go back in the >>>screen >>> >>>can I tell crafty to print what it display in the screen or to tell crafty to >>>stop searching after a fixed number of nodes? >>> >>>Uri >> >>I don't think this is useful for anything but my own debugging. > >It can be useful to understand better how crafty works by seeing an example. > >Uri > > Note that in debugging, I hardly ever use this, because I have a hard time parsing/understanding millions of lines of output. IE think about a search that covers 100,000,000 nodes, something I have seen happen many times in standard games. That is a *bunch* of output, that no human will ever be able to cope with... > This >>program searches at about 80K nodes per sec on a P6/200, and nearly 200K >>nodes per sec on a PII/450. After 5 seconds you have 1,000,000 lines of >>output, which is hopeless to scan. >> >>I often use it by putting the right commands in a file, like this: >> >>sd=4 >>tr 100 >>ponder=off >>setboard >>move >>quit >> >>then run crafty: >> >>crafty output_file >> >>and when it finishes I can edit output_file and poke around in 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.