270
ChessBase 13
position analysis, because no time is specified and the variation tree is dynamically
restructured as the search progresses. After the function has been started the
program calculates indefinitely and generates an analysis tree with the best moves
and replies. The tree is dynamically updated and weaker variations are removed.
The program analyses candidate moves and makes the moves for further analysis, as
every chess player would do it himself. This generates a tree which changes from
iteration to iteration. Every iteration increases the processor time.
In the notation variations are shown in grey if they do not seem good at the current
depth. If a variation cannot be proved to be good at two consecutive depths it
disappears from the notation, so that only the best continuations are analysed and
displayed.
During the analysis there are two ways you can influence the analysis:
Stop Process: This halts the analysis. The result can be stored as a different game,
or the existing notation can be overwritten.
Open Cloud Engines: You can add cloud engines to the analysis to improve the
quality. The function then accesses engines that are running in parallel.
One engine makes the candidate moves and creates a variation tree. In the example
this is done by Fritz 13.
The additional cloud engines calculate answers to the moves simultaneously, which are
then added without losing any time. In the example this is done by the Houdini engine.
The title bar of the engine window tells us what function the engine has.
The candidate engine runs in multi-variation mode, because it has to calculate a lot of
candidate moves.
During the deep analysis other engines can be added to th e cloud server without
interrupting the analysis. These engines automatically adopt the correct roles. If
individual cloud engines stop running the analysis continues, as long as at least one
local engine is running.
Skip Iteration: This skips an analysis level, which increases the processor time and
the analysis depth of the engine.
Note: Variations that are in the notation at the start of the analysis are never
deleted and are always analysed, unless they are the results of a previous Cloud
Analysis.
ChessBase 2014