The BozoChess EPD lexicon

[sje]

The BozoChess EPD lexicon:

For a number of reasons including the fact that BozoChess is open source, I've decided to make the program a reference document for the EPD lexicon.

Some of the EPD operations are new, while others have been around since day one.

So far:

Code: Select all

Operation   Semantics                      Sample
---------   ---------                      ---------

id          Record identification string   id Problem.023;   id BWTC.0031;
            (whitespace must be quoted)    id "Game 13, ply 32";

cte         Component time (elapsed)       cte 000.00:00:00.001;   cte 000.00:03:08.475;
            (DDD.HH:MM:SS.mmm format)      cte 000.00:00:00.000;   cte 999.23:59:59.999;

ctu         Component time (total used)    cte 000.00:00:00.001;   cte 000.00:03:08.475;
            (DDD.HH:MM:SS.mmm format)      cte 000.00:00:00.000;   cte 999.23:59:59.999;

pes         Pawn equivalent score          pes +12.982;   pes -0.030;   pes 0.000;
            (decimal pawns or symbol)      pes MateIn3;   pes LoseIn10;   pes Checkmated;

dm          Direct mate full move count    dm 1;   dm 4;   dm 107;
            (range 1..1023)                dm 1023;

pv          Predicted variation            pv;  pv e8=Q Rxe8 Rxe8 Kc6;
            (All proper SAN moves)         pv Kd6 f8=Q+ Kc6 Qc5+ Kb7 Nxb5;

acn         Analysis count (nodes)         acn 0;   acn 328;
            (range 0..2^64-1)              acn 10000000000;

bm          Best moves                     bm e4;   bm gxh1=Q+;
            (All proper SAN moves)         bm Qh4+ Nxd3+ Nf3+;

Notes:

1) The old "ce" (centipawn evaluation) is deprecated; use "pes" instead.

2) The old "hmvc" (halfmove counter) is deprecated; the value is now supplied as the fifth token in the leading FEN data.

3) The old "fmvn" (fullmove number) is deprecated; the value is now supplied as the sixth token in the leading FEN data.

4) The old "pm" (predicted move) is deprecated; the "pv" first operand (if present) is used instead.

5) The "cte" operation indicates elapsed wall clack time; the "ctu" operation is the sum of all CPU usage time.

6) All clock time data is preseted with millisecand resolution; internal resolution may be higher or lower.

7) A draw evaluation is presented as "0.000".

8) All non-draw numeric evaluations are presented with a leading "+" or "-'.

9) A mate in N evaluation (N > 0) is presented as "MateIn<N>".

10) A lose in N evaluation (N > 0) is presented as "LoseIn<N>".

11) A checkmated evaluation (e.g., "LoseIn0") is presented as "Checkmated".

[sje]

And another EPD operation (chess clock settings):

Code: Select all

Operation   Semantics                       Samples
---------   ---------                       -------

ctcc        Component times (chess clock)   ctcc 000.00:05:00.000 000.00:05:00.000;
            (for White and then Black)      ctcc 000.01:57:37.982 000.01:44:03.928;