Difference between revisions of "Extended Position Description"

From Chessprogramming wiki
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 5: Line 5:
  
 
=EPD Syntax=  
 
=EPD Syntax=  
One EPD string or record consists of one text line of variable length composed of four fields separated by a space character followed by zero or more operations. The four data fields, which describe the position, are common with the FEN-Specification, while the [[Halfmove Clock|halfmove clock]] and [[Forsyth-Edwards Notation#Fullmovecounter|full move counter]], obligatory in Forsyth-Edwards Notation are replaced by optional '''hmvc''' and '''fmvn''' operations, and 0, 1 are their default values <ref>[http://www.talkchess.com/forum3/viewtopic.php?f=7&t=70048&start=5 Re: Fun challenge for best cool code] by [[Harm Geert Muller]], [[CCC]], February 28, 2019</ref>.
+
One EPD string or record consists of one text line of variable length composed of four fields separated by a space character followed by zero or more operations. The four data fields, which describe the position, are common with the [[Forsyth-Edwards Notation#FEN Syntax|FEN-Specification]], while the [[Halfmove Clock|halfmove clock]] and [[Forsyth-Edwards Notation#Fullmovecounter|full move counter]], obligatory in Forsyth-Edwards Notation are replaced by optional '''hmvc''' and '''fmvn''' operations, and 0, 1 are their default values <ref>[http://www.talkchess.com/forum3/viewtopic.php?f=7&t=70048&start=5 Re: Fun challenge for best cool code] by [[Harm Geert Muller]], [[CCC]], February 28, 2019</ref>.
  
 
''[https://en.wikipedia.org/wiki/Terminal_and_nonterminal_symbols Terminal and none terminal symbols] of a variant of [https://en.wikipedia.org/wiki/Backus%E2%80%93Naur_form BNF] below are embedded in ' ' resp. < >.''
 
''[https://en.wikipedia.org/wiki/Terminal_and_nonterminal_symbols Terminal and none terminal symbols] of a variant of [https://en.wikipedia.org/wiki/Backus%E2%80%93Naur_form BNF] below are embedded in ' ' resp. < >.''
Line 114: Line 114:
  
 
=Forum Posts=
 
=Forum Posts=
 +
* [https://groups.google.com/d/msg/rec.games.chess.computer/0-xpXHbfzh4/GoKIkW0SKoUJ Help on PGN/ EPD-Format and its implementation wanted] by [[Rudolf Posch]], [[Computer Chess Forums|rgcc]], November 05, 1996 » [[Portable Game Notation|PGN]]
 
* [https://www.stmintz.com/ccc/index.php?id=20631 EPD examples: Bratko-Kopec test suite] by [[Steven Edwards|Steven J. Edwards]], [[CCC]], June 15, 1998 » [[Bratko-Kopec Test]]
 
* [https://www.stmintz.com/ccc/index.php?id=20631 EPD examples: Bratko-Kopec test suite] by [[Steven Edwards|Steven J. Edwards]], [[CCC]], June 15, 1998 » [[Bratko-Kopec Test]]
 
* [https://www.stmintz.com/ccc/index.php?id=137052 EPD format] by [[Stefan Meyer-Kahlen]], [[CCC]], November 07, 2000
 
* [https://www.stmintz.com/ccc/index.php?id=137052 EPD format] by [[Stefan Meyer-Kahlen]], [[CCC]], November 07, 2000
Line 125: Line 126:
 
* [http://www.talkchess.com/forum3/viewtopic.php?f=7&t=70048 Fun challenge for best cool code] by [[Ed Schroder|Ed Schröder]], [[CCC]], February 28, 2019
 
* [http://www.talkchess.com/forum3/viewtopic.php?f=7&t=70048 Fun challenge for best cool code] by [[Ed Schroder|Ed Schröder]], [[CCC]], February 28, 2019
 
: [http://www.talkchess.com/forum3/viewtopic.php?f=7&t=70048&start=3 Re: Fun challenge for best cool code] by [[Harm Geert Muller]], [[CCC]], February 28, 2019
 
: [http://www.talkchess.com/forum3/viewtopic.php?f=7&t=70048&start=3 Re: Fun challenge for best cool code] by [[Harm Geert Muller]], [[CCC]], February 28, 2019
 +
* [http://www.talkchess.com/forum3/viewtopic.php?f=2&t=71135 Scid vs. PC - EPD Export feature] by [[Steven Atkinson]], [[CCC]], June 29, 2019 » [[Scid vs. PC]]
  
 
=External Links=
 
=External Links=

Latest revision as of 19:22, 13 August 2020

Home * Chess * Position * Extended Position Description

Extended Position Description (EPD)
describes a chess position similar to the Forsyth-Edwards Notation (FEN). Unlike FEN, EPD is designed to be expandable by the addition of new operations. EPD was developed by John Stanback and Steven Edwards. Its first implementation is in Stanback's chessplaying program Zarkov. Steven Edwards specified the EPD standard for computer chess applications as part of the Portable Game Notation [1].

EPD Syntax

One EPD string or record consists of one text line of variable length composed of four fields separated by a space character followed by zero or more operations. The four data fields, which describe the position, are common with the FEN-Specification, while the halfmove clock and full move counter, obligatory in Forsyth-Edwards Notation are replaced by optional hmvc and fmvn operations, and 0, 1 are their default values [2].

Terminal and none terminal symbols of a variant of BNF below are embedded in ' ' resp. < >.

<EPD> ::=  <Piece Placement>
       ' ' <Side to move>
       ' ' <Castling ability>
       ' ' <En passant target square>
      {' ' <operation>}

Piece Placement

The Piece Placement is determined rank by rank in big-endian order, that is starting at the 8th rank down to the first rank. Each rank is separated by the terminal symbol '/' (slash). One rank, scans piece placement in little-endian file-order from the A to H. A decimal digit counts consecutive empty squares, the pieces are identified by a single letter from standard English names for chess pieces as used in the Algebraic Chess Notation. Uppercase letters are for white pieces, lowercase letters for black pieces.

<Piece Placement> ::= <rank8>'/'<rank7>'/'<rank6>'/'<rank5>'/'<rank4>'/'<rank3>'/'<rank2>'/'<rank1>
<ranki>       ::= [<digit17>]<piece> {[<digit17>]<piece>} [<digit17>] | '8'
<piece>       ::= <white Piece> | <black Piece>
<digit17>     ::= '1' | '2' | '3' | '4' | '5' | '6' | '7'
<white Piece> ::= 'P' | 'N' | 'B' | 'R' | 'Q' | 'K'
<black Piece> ::= 'p' | 'n' | 'b' | 'r' | 'q' | 'k'

Side to move

Side to move is one lowercase letter for either White ('w') or Black ('b').

<Side to move> ::= {'w' | 'b'}

Castling ability

If neither side can castle, the symbol '-' is used, otherwise each of four individual castling rights for king and queen castling for both sides are indicated by a sequence of one to four letters.

<Castling ability> ::= '-' | ['K'] ['Q'] ['k'] ['q'] (1..4)

En passant target square

The en passant target square is specified after a double push of a pawn, no matter whether an en passant capture is really possible or not. Other moves than double pawn pushes imply the symbol '-' for this FEN field.

<En passant target square> ::= '-' | <epsquare>
<epsquare>   ::= <fileLetter> <eprank>
<fileLetter> ::= 'a' | 'b' | 'c' | 'd' | 'e' | 'f' | 'g' | 'h'
<eprank>     ::= '3' | '6'

Operations

<operation> ::= <opcode> {' '<operand>} ';'
<opcode>    ::= <letter> {<letter> | <digit> | '_'} (up to 14)
<operand>   ::= <stringOperand>
              | <sanMove>
              | <unsignedOperand>
              | <integerOperand>
              | <floatOperand>

<stringOperand>  ::= '"' {<char>} '"'

<sanMove>        ::= <PieceCode> [<Disambiguation>] <targetSquare> [<promotion>] ['+'|'#']
                   | <castles>
<castles>        ::= 'O-O' | 'O-O-O' (upper case O, not zero)
<PieceCode>      ::= '' | 'N' | 'B' | 'R' | 'Q' | 'K'
<Disambiguation> ::= <fileLetter> | <digit18>
<targetSquare>   ::= <fileLetter> <digit18>
<fileLetter> ::= 'a' | 'b' | 'c' | 'd' | 'e' | 'f' | 'g' | 'h'
<promotion>      ::=  '=' <PiecePromotion>
<PiecePromotion> ::= 'N' | 'B' | 'R' | 'Q'

<unsignedOperand>::= <digit19> { <digit> } | '0'
<integerOperand> ::= ['-' | '+'] <unsignedIntegerOperand>
<floatOperand>   ::= <integerOperand> '.' <digit> {<digit>}
<digit18> ::= '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8'
<digit19> ::= '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9'
<digit>   ::= '0' | <digit19>

Opcode mnemonics

  • acd analysis count depth [3]
  • acn analysis count nodes
  • acs analysis count seconds
  • am avoid move(s)
  • bm best move(s)
  • c0 comment (primary, also c1 though c9)
  • ce centipawn evaluation
  • dm direct mate fullmove count
  • draw_accept accept a draw offer
  • draw_claim claim a draw
  • draw_offer offer a draw
  • draw_reject reject a draw offer
  • eco Encyclopedia of Chess Openings opening code
  • fmvn fullmove number
  • hmvc halfmove clock
  • id position identification
  • nic New In Chess opening code
  • noop no operation
  • pm predicted move
  • pv predicted variation
  • rc repetition count
  • resign game resignation
  • sm supplied move
  • tcgs telecommunication game selector
  • tcri telecommunication receiver identification
  • tcsi telecommunication sender identification
  • v0 variation name (primary, also v1 though v9)

See also

Forum Posts

Re: Fun challenge for best cool code by Harm Geert Muller, CCC, February 28, 2019

External Links

References

Up one Level