Next: Viewing with Emacs, Previous: Running the Regressions, Up: Regression
A more powerful way to run regressions is with the script regress.pike. This requires that you have Pike (http://pike.ida.liu.se) installed.
Executing ./regress.pike
without arguments will run all
testsuites that make all_batches
would run. The difference is
that unexpected results are reported immediately when they have been
found (instead of after the whole file has been run) and that statistics
of time consumption and node usage is presented for each test file and
in total.
To run a single test suite do e.g. ./regress.pike nicklas3.tst
or
./regress.pike nicklas3
. The result may look like:
nicklas3 2.96 614772 3322 469 Total nodes: 614772 3322 469 Total time: 2.96 (3.22) Total uncertainty: 0.00
The numbers here mean that the test suite took 2.96 seconds of processor
time and 3.22 seconds of real time. The consumption of reading nodes was
614772 for tactical reading, 3322 for owl reading, and 469 for
connection reading. The last line relates to the variability of the
generated moves in the test suite, and 0 means that none was decided by
the randomness contribution to the move valuation. Multiple testsuites
can be run by e.g. ./regress.pike owl ld_owl owl1
.
It is also possible to run a single testcase, e.g. ./regress.pike
strategy:6
, a number of testcases, e.g. ./regress.pike
strategy:6,23,45
, a range of testcases, e.g. ./regress.pike
strategy:13-15
or more complex combinations e.g. ./regress.pike
strategy:6,13-15,23,45 nicklas3:602,1403
.
There are also command line options to choose what engine to run, what
options to send to the engine, to turn on verbose output, and to use a
file to specify which testcases to run. Run ./regress.pike --help
for a complete and up to date list of options.