ChessGUI and multiple engines solving testsuites

[Matthias Gemuh]

If ChessGUI would use multiple engines for solving testsuites, how would you like the results presented (in GUI and in files) ?
How many engines at most ?

Matthias.

[swami]

If ChessGUI would use multiple engines for solving testsuites, how would you like the results presented (in GUI and in files) ?
How many engines at most ?

Matthias.

Both files and GUI, but preferably GUI if you had one option.

50 engines minimum if that is possible.

[Matthias Gemuh]

If ChessGUI would use multiple engines for solving testsuites, how would you like the results presented (in GUI and in files) ?
How many engines at most ?

Matthias.

How should the data be formated in files ?

How should the data be formated in GUI ?

Matthias.

[Mike S.]

It will always be useful to have an ASCII output file with a "normal" table to look at, like

Code: Select all

Pos.#  Rybka 2.3.2a   Zappa Mexico II   Fritz ...
00001      03:17            01:59
00002      00:02
00003      (n/a)

But for many testers, it would also be useful to have such a table in CSV format, separated by semicolon ";", for easy import in Excel and other spreadheet programs. There, ratings can be calculated, results can be grouped by topics, etc.

http://de.wikipedia.org/wiki/CSV_%28Dateiformat%29

Code: Select all

Pos.#;Rybka 2.3.2a;Zappa Mexico II;Fritz
00001;03:17;01.59
00002;00:02
00003;(n/a)

Importing normal text tables can be a pain, because the calc program cannot know for example, where one engine name ends and where the next engine name begins, etc. The number of spaces between fields is always different und ambigous.

In the GUI, it will probably be more useful to present the engine results per position each, as a simple top-down list like

Code: Select all

Position No. 00345:
----------------------
Rybka 2.3.2a:    22:17
Zappa Mexico II: 18:45
(etc.)

(the numbers here are just random examples)