Answers.Body: <p>The PGN standard is found <a href="http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm" rel="nofollow noreferrer">here</a>; it does not mention the <code>[%eval]</code> syntax at all. It specifies comments starting with <code>[</code> and ending with <code>]</code> 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.</p>
  
  <p>The only other places where evaluation is mentioned in standard, §13.8 and especially <a href="http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm#c16.2.5" rel="nofollow noreferrer">§16.2.5.6</a>, centipawns are used (which would favor the first option):</p>
  
  <blockquote>
    <h3>16.2.5.6: Opcode "ce": centipawn evaluation</h3>
    
    <p>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.</p>
  </blockquote>
  
  <p>It does not mention the ply depth at all.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-12T21:26:11.713Z
Answers.Text: [This document](http://www.enpassant.dk/chess/palview/enhancedpgn.htm) mentions %eval and used full pawn syntax, but I don't know how official it is (the header says it is a draft).
Answers.UserDisplayName: Michal
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-13T07:45:21.863Z
Answers.Text: Well found, but it's just an *example* of what you could do with comments, it doesn't describe a syntax.
Answers.UserDisplayName: Glorfindel
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-15T07:04:50.273Z
Answers.Text: If I remember well, operational codes (opcode) are for the EPD format (electronic position description). The [%eval ] code, are used inside comments of moves.
Answers.UserDisplayName: djnavas
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-06-12T17:13:52.000Z
Answers.LastActivityDate: 2018-06-12T17:13:52.000Z
Answers.UserDisplayName: Glorfindel
Body: <p>I've seen two formats of <code>[%eval]</code> syntax in PGN:</p>
  
  <ul>
  <li><code>[%eval 250,5]</code> meaning white is +2.5 pawn up at depth 5</li>
  <li><code>[%eval +0.25]</code> means white is 0.25 pawn up</li>
  </ul>
  
  <p>Is any of those mentioned by some PGN standard? Which one is more popular?</p>
  
Tags: <engines><software><pgn>
Title: What is %eval syntax in PGN
ThreadText: # What is %eval syntax in PGN
  
  (Asked by: username_0 on 2018-06-12)
  
  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?
  
  **Tags:** engines, software, pgn
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-06-12. Score: 3
  
  The PGN standard is found [here](http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm); 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](http://www.saremba.de/chessgml/standards/pgn/pgn-complete.htm#c16.2.5), 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.
  
  > **Comments:**
  > **username_0**: [This document](http://www.enpassant.dk/chess/palview/enhancedpgn.htm) mentions %eval and used full pawn syntax, but I don't know how official it is (the header says it is a draft).  
  > **username_1**: Well found, but it's just an *example* of what you could do with comments, it doesn't describe a syntax.  
  > **username_2**: If I remember well, operational codes (opcode) are for the EPD format (electronic position description). The [%eval ] code, are used inside comments of moves.  
  
  ---
  
  