SEARCHING FOR BLUNDERS Sample Clauses

SEARCHING FOR BLUNDERS. You can very quickly locate blunders with the help of the internal engines. Create a dataset with the games you want to check (see Selecting Games for details), then while in List mode, call the Engines | Search for blunders command in the main menu, and the Set analysis properties window will appear. Select an Engine from the drop-down list and set the other options. You can set up to three levels of verification, so that after a first analysis of all the moves (at a depth you specify), the moves that were identified as blunders are analyzed a second time at a greater depth, and after that even a third time at a fixed time limit. Naturally, while searching the program will skip the moves available in the opening library. Evaluation delta (in hundredths of a pawn) determines the minimum allowed difference between the game move evaluation and the evaluation of the move suggested by the engine. Evaluation delta may be set in hundredths of a pawn (in the Centipawns box) or as a difference between the chess evaluations (in the Symbols box). Chess evaluations are as follows: °; °/µ; µ; ³/µ; ³; =/³; =; ²/=; ²; ²/±; ±; ±/; . Evaluation delta between two neighboring evaluations is 1, Evaluation delta between = and ² is 2, etc. If the difference in evaluations is greater or equal to the value set in both boxes of the Evaluation delta section, the move will be considered a blunder. For example, let’s set Evaluation delta as follows: Centipawns = 100 and Symbols = 2. In this case the move that “blunders” 150 hundredths of a pawn, but does not change the position evaluation, will not be considered a blunder. In other words, a weak move in a won position, which does not miss the decisive advantage, will not be considered a blunder; the same refers to a weak move in a hopeless position. If the Set blunders class option is enabled, all the blunders discovered will be included into the standard Blunders class (see Standard Classes for details).