Remarks, hints and limitations
It's assumed that the people who are interested in this util (chess programmers mainly) have
the knowledge how batch files work.
1. MEA produces an excellent EPD with scores, depth of each position in the epd_out folder.
2. Our experience (so far) has been we had more success with the sfx EPD's than with the lcx EPD's.
3. For easy sharing results a text file is produced from each created html output.
4. The disadvantage of the MEA fixed movetime [MT] is that it abrupts aborts the search when the movetime limit is reached. An alternative is including depth, for example:
Tells the engine to finish after 20 plies with a maximum time of 1 second.
5. An abrupt time control with [MT] of say 250ms isn't comparable with:
• A regular time control;
• 250ms is a factor 12 slower than CCRL 40/2.
6. Some engines (in fact a bit more than some) have the habit to surpress the mainlines of the early plies, some hide the first x plies, some hide the main lines the first 100ms and there are even those who use 1 full second. It's probably inspired by a speed gain of 1-2 millieseconds. When there is no main line NICE will report the number of cases found in the error column of the html and the result will be unreliable.
7.1 When an engine uses to much time "Used Time" in the HTML will be colored red.
7.2 When an engine plays too fast "Used Time" in the HTML will be colored blue.
8. For more examples, technical details, inner working of NICE or questions check out this thread on Talkchess.