Skip to content

Commit

Permalink
Don't treat king safety differently in AnalysisMode
Browse files Browse the repository at this point in the history
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
  • Loading branch information
zamar authored and mcostalba committed Apr 9, 2013
1 parent 9498b2a commit c290211
Showing 1 changed file with 0 additions and 8 deletions.
8 changes: 0 additions & 8 deletions src/evaluate.cpp
Expand Up @@ -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;

Expand Down

0 comments on commit c290211

Please sign in to comment.