Home * Search * Selectivity * Extensions * Capture Extensions

Capture Extensions were used early in brute-force chess programs to minimize some horizon effects. Due to the self-restricting nature of captures in Chess (max. 30 pieces may be captured per game), one may consider this a good idea. However, extending every capture was discarded by most programmers, and some constrains or conditions were applied, i.e. to extend only forced recaptures on the same target square.

Hans Berliner suggested to extend only those (re)captures, which restore the material balance at the root. Furthermore, capture extensions are often restricted to PV-nodes, or some programs assign fractional extensions to different kinds of captures, considering SEE, distance of target square to the opponent king, recapturing on the same square, and material balance as mentioned.

A lot of todays programs, more focused on reductions rather than extensions in the Scout part of their PVS, most often don't reduce captures, which makes it a kind of implicit extension relative to reduced late quiet moves. It also seems worth a try to reduce even captures with negative SEE while performing LMR.

However, it seems important to extend captures if a transition to certain late endgames occurs. Ed Schröder for instance extends three plies in Rebel if entering the pawn endgame, and the static, incremental updated score dominated by material is not outside a +-3 pawn window around zero: The extension is very powerful, it will often avoid REBEL entering a lost ending and vice versa [1].

See also


Publications


Forum Posts


External Links


References

  1. ^ Programmer Corner - How Rebel Plays Chess by Ed Schröder, Extension Techniques: Endgame, pdf reprint

What links here?


Up one Level