4

I've seen two formats of [%eval] syntax in PGN:

  • [%eval 250,5] meaning white is +2.5 pawn up at depth 5
  • [%eval +0.25] means white is 0.25 pawn up

Is any of those mentioned by some PGN standard? Which one is more popular?

0

1 Answer 1

3

The PGN standard is found here; it does not mention the [%eval] syntax at all. It specifies comments starting with [ and ending with ] but no format for what's inside; that means that program are free to export and import these comments the way they want, without necessarily being compatible.

The only other places where evaluation is mentioned in standard, §13.8 and especially §16.2.5.6, centipawns are used (which would favor the first option):

16.2.5.6: Opcode "ce": centipawn evaluation

The opcode "ce" indicates the evaluation of the indicated position in centipawn units. It takes a single operand, an optionally signed integer that gives an evaluation of the position from the viewpoint of the active player; i.e., the player with the move.

It does not mention the ply depth at all.

3
  • This document mentions %eval and used full pawn syntax, but I don't know how official it is (the header says it is a draft).
    – Michal
    Commented Jun 12, 2018 at 21:26
  • Well found, but it's just an example of what you could do with comments, it doesn't describe a syntax.
    – Glorfindel
    Commented Jun 13, 2018 at 7:45
  • If I remember well, operational codes (opcode) are for the EPD format (electronic position description). The [%eval ] code, are used inside comments of moves.
    – djnavas
    Commented Jun 15, 2018 at 7:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.