AtomicDB

Sign in Register

What a position row shows

Each position in the database is stored as one row. The row keeps three things apart: what the engine said about this position itself, what the analysed moves below it add up to, and whether it is solved.

Scores are in centipawns (100 = one pawn) from the side to move, the chessdb.cn convention used everywhere on this site. Positions and the moves between them form a graph (see Repetition for why it is not a simple tree).

The header of a position in the explorer: UNSOLVED, White to move, best line +1261cp with a BACKED 36 chip, then a line saying the position was analysed with 12.78B nodes across 6 passes, and the Request analysis button.
The header of the start position: unsolved, headlined by its backed value (+1261, through a chain 36 plies deep).

The fields

FieldWhat it is
eval_cpThe latest engine analysis of this position. It is what one search reported, and nothing more.
backed_evalThe backed value: the best result the side to move can reach, worked out (by negamax) from the analyses that really exist below this position.
backed_moveThe move the backed value came through. It points at where to look; it is not a recommendation an engine made here.
status, closureFor a solved position, the verdict and the gate it closed through. Anything still open carries UNKNOWN and no closure.
backed_pliesHow deep the backing chain runs, counted in plies (half-moves) below this position.
backed_nodesThe analysis size of the weakest link on that chain. A long chain is worth what its thinnest search is worth.

Which number a position shows

One position, one number. A position headlines its best known value, in this order:

  1. a proven status, if it has one;
  2. otherwise the backed value;
  3. otherwise the point eval (eval_cp).

The point eval never headlines while something better is known. It stays available as the position's own search context in the tooltip and in the API point field.

← Method Backed values →