From: Joona Kiiski <joona.kiiski@gmail.com>
Date: Sun, 7 Apr 2013 08:23:52 +0000 (+0100)
Subject: Don't treat king safety differently in AnalysisMode
X-Git-Url: https://git.sesse.net/?p=stockfish;a=commitdiff_plain;h=c2902112e51b50c8ebcf263825597f437fdf56e7

Don't treat king safety differently in AnalysisMode

Rationale:

- Current settings seem to make engine *significantly* weaker in analysis mode.
- In practice this setting only has effect when king safety scores are high.
- Even in analysis mode its far more important to know if one side is getting mated,
rather than get evaluation correct with 1cp accuracy.

No functional change
---

diff --git a/src/evaluate.cpp b/src/evaluate.cpp
index 3d9a3112..6990a71d 100644
--- a/src/evaluate.cpp
+++ b/src/evaluate.cpp
@@ -289,14 +289,6 @@ namespace Eval {
     Weights[KingDangerUs]   = weight_option("Cowardice", "Cowardice", WeightsInternal[KingDangerUs]);
     Weights[KingDangerThem] = weight_option("Aggressiveness", "Aggressiveness", WeightsInternal[KingDangerThem]);
 
-    // King safety is asymmetrical. Our king danger level is weighted by
-    // "Cowardice" UCI parameter, instead the opponent one by "Aggressiveness".
-    // If running in analysis mode, make sure we use symmetrical king safety. We
-    // do this by replacing both Weights[kingDangerUs] and Weights[kingDangerThem]
-    // by their average.
-    if (Options["UCI_AnalyseMode"])
-        Weights[KingDangerUs] = Weights[KingDangerThem] = (Weights[KingDangerUs] + Weights[KingDangerThem]) / 2;
-
     const int MaxSlope = 30;
     const int Peak = 1280;