For the test position:
[d]rnbqkb1r/pppp4/4pn1p/5pp1/3P4/4P1B1/PPP2PPP/RN1QKBNR w KQkq - 0 6
The program reports as a kibitz:
Code: Select all
[+0.056/8/6,507,627] 6 Nc3 Nc6 7 Bb5 g4 8 Bh4 Bb4 9 Ne2 d6 10 Bxf6 Qxf6 11 Bxc6+ bxc6
I've left out reporting for the total TB hit count, elapsed time, and search termination status in favor of reporting the most pertinent data (and a long PV) on a single text line.
A bit more data appears on the EPD output. Here's the EPD for a different position:
Code: Select all
8/8/3K4/2p5/2k5/2P5/2b4P/8 b - - 1 54 acd 11; acn 2774069; cc 39.330 39.324; nef 2.04572e+06; nep 4.88825e-07; nuf 2.05813e+06; nup 4.85879e-07; pes +3.667; pv Bd3 h3 Be4 Ke5 Bg2 h4 Kxc3 h5 Bf3 h6 c4; te 1.356; tu 1.347;
cc: chess clock (pair of DDD:HH:MM:SS.mmm with leading suppression)
nef: node elapsed frequency (Hz) (nodes/wall time)
nep: node elapsed period (seconds) (inverse of nef)
nuf: node usage frequency (Hz) (nodes/total CPU time for all cores)
nup: node usage period (seconds) (inverse of nuf)
pes: pawn equivalent score
pv: predicted variation
te: elapsed time (DDD:HH:MM:SS.mmm with leading suppression)
tu: usage time (DDD:HH:MM:SS.mmm with leading suppression)
For the nef/nep/nuf/nup operators the operand value will be the symbol NAN (i.e., Not A Number) if calculation of its value would require a division by zero.
